docs: add configuration options for ticket analysis review in compliance tool

Add Claude Opus 4.5 to PR Banchmark

CODE_OF_CONDUCT.md

@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 individual is representing the project or its community.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
-contacting a project maintainer at tal.r@qodo.ai . All complaints will
+contacting a project maintainer at dana.f@qodo.ai . All complaints will
 be reviewed and investigated and will result in a response that is deemed necessary and
 appropriate to the circumstances. Maintainers are obligated to maintain confidentiality
 with regard to the reporter of an incident.

LICENSE

@@ -1,202 +1,661 @@
+                    GNU AFFERO GENERAL PUBLIC LICENSE
+                       Version 3, 19 November 2007
 
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
 
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+                            Preamble
 
-   1. Definitions.
+  The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
 
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+our General Public Licenses are intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.
 
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
 
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
+  Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
 
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
+  A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate.  Many developers of free software are heartened and
+encouraged by the resulting cooperation.  However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
 
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
+  The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community.  It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server.  Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
 
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
+  An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals.  This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
 
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
+  The precise terms and conditions for copying, distribution and
+modification follow.
 
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
+                       TERMS AND CONDITIONS
 
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
+  0. Definitions.
 
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
+  "This License" refers to version 3 of the GNU Affero General Public License.
 
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
 
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
 
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
 
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
 
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
 
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
 
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
 
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
+  1. Source Code.
 
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
 
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
 
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
 
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
 
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
 
-   END OF TERMS AND CONDITIONS
+  The Corresponding Source for a work in source code form is that
+same work.
 
-   APPENDIX: How to apply the Apache License to your work.
+  2. Basic Permissions.
 
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
 
-   Copyright [2023] [Codium ltd]
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
 
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
 
-       http://www.apache.org/licenses/LICENSE-2.0
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
 
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Remote Network Interaction; Use with the GNU General Public License.
+
+  Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software.  This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the work with which it is combined will remain governed by version
+3 of the GNU General Public License.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU Affero General Public License from time to time.  Such new versions
+will be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU Affero General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU Affero General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU Affero General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU Affero General Public License as published
+    by the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU Affero General Public License for more details.
+
+    You should have received a copy of the GNU Affero General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source.  For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code.  There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU AGPL, see
+<https://www.gnu.org/licenses/>.

README.md

@@ -1,280 +1,36 @@
-<div align="center">
+# 🧠 PR Agent LEGACY STATUS (open source)
+Originally created and open-sourced by Qodo - the team behind next-generation AI Code Review.
 
-<div align="center">
+## 🚀 About
+PR Agent was the first AI assistant for pull requests, built by Qodo, and contributed to the open-source community.  
+It represents the first generation of intelligent code review - the project that started Qodo’s journey toward fully AI-driven development, Code Review.  
+If you enjoy this project, you’ll love the next-level PR Agent - Qodo free tier version, which is faster, smarter, and built for today’s workflows.  
 
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="https://www.qodo.ai/wp-content/uploads/2025/02/PR-Agent-Purple-2.png">
-  <source media="(prefers-color-scheme: light)" srcset="https://www.qodo.ai/wp-content/uploads/2025/02/PR-Agent-Purple-2.png">
-  <img src="https://codium.ai/images/pr_agent/logo-light.png" alt="logo" width="330">
+🚀 Qodo includes a free user trial, 250 tokens, bonus tokens for active contributors, and 50% more advanced features than this open-source version.
 
-</picture>
-<br/>
-
-[Installation Guide](https://qodo-merge-docs.qodo.ai/installation/) |
-[Usage Guide](https://qodo-merge-docs.qodo.ai/usage-guide/) |
-[Tools Guide](https://qodo-merge-docs.qodo.ai/tools/) |
-[Qodo Merge](https://qodo-merge-docs.qodo.ai/overview/pr_agent_pro/) 💎
-
-PR-Agent aims to help efficiently review and handle pull requests, by providing AI feedback and suggestions
-</div>
-
-[![Static Badge](https://img.shields.io/badge/Chrome-Extension-violet)](https://chromewebstore.google.com/detail/qodo-merge-ai-powered-cod/ephlnjeghhogofkifjloamocljapahnl)
-[![Static Badge](https://img.shields.io/badge/Pro-App-blue)](https://github.com/apps/qodo-merge-pro/)
-[![Static Badge](https://img.shields.io/badge/OpenSource-App-red)](https://github.com/apps/qodo-merge-pro-for-open-source/)
-[![Discord](https://badgen.net/badge/icon/discord?icon=discord&label&color=purple)](https://discord.com/invite/SgSxuQ65GF)
-<a href="https://github.com/Codium-ai/pr-agent/commits/main">
-<img alt="GitHub" src="https://img.shields.io/github/last-commit/Codium-ai/pr-agent/main?style=for-the-badge" height="20">
-</a>
-</div>
-
-[//]: # (### [Documentation]&#40;https://qodo-merge-docs.qodo.ai/&#41;)
-
-[//]: # ()
-[//]: # (- See the [Installation Guide]&#40;https://qodo-merge-docs.qodo.ai/installation/&#41; for instructions on installing PR-Agent on different platforms.)
-
-[//]: # ()
-[//]: # (- See the [Usage Guide]&#40;https://qodo-merge-docs.qodo.ai/usage-guide/&#41; for instructions on running PR-Agent tools via different interfaces, such as CLI, PR Comments, or by automatically triggering them when a new PR is opened.)
-
-[//]: # ()
-[//]: # (- See the [Tools Guide]&#40;https://qodo-merge-docs.qodo.ai/tools/&#41; for a detailed description of the different tools, and the available configurations for each tool.)
-
-## Table of Contents
-
-- [News and Updates](#news-and-updates)
-- [Overview](#overview)
-- [Example results](#example-results)
-- [Try it now](#try-it-now)
-- [Qodo Merge](https://qodo-merge-docs.qodo.ai/overview/pr_agent_pro/)
-- [How it works](#how-it-works)
-- [Why use PR-Agent?](#why-use-pr-agent)
-- [Data privacy](#data-privacy)
-- [Contributing](#contributing)
-- [Links](#links)
-
-## News and Updates
-
-## Apr 30, 2025
-
-A new feature is now available in the `/improve` tool for Qodo Merge 💎 - Chat on code suggestions.
-
-<img width="512" alt="image" src="https://codium.ai/images/pr_agent/improve_chat_on_code_suggestions_ask.png" />
-
-Read more about it [here](https://qodo-merge-docs.qodo.ai/tools/improve/#chat-on-code-suggestions).
-
-## Apr 16, 2025
-
-New tool for Qodo Merge 💎 - `/scan_repo_discussions`.
-
-<img width="635" alt="image" src="https://codium.ai/images/pr_agent/scan_repo_discussions_2.png" />
-
-Read more about it [here](https://qodo-merge-docs.qodo.ai/tools/scan_repo_discussions/).
-
-## Apr 14, 2025
-
-GPT-4.1 is out. And it's quite good on coding tasks...
-
-https://openai.com/index/gpt-4-1/
-
-<img width="512" alt="image" src="https://github.com/user-attachments/assets/a8f4c648-a058-4bdc-9825-2a4bb71a23e5" />
-
-## March 28, 2025
-
-A new version, v0.28, was released. See release notes [here](https://github.com/qodo-ai/pr-agent/releases/tag/v0.28).
-
-This version includes a new tool, [Help Docs](https://qodo-merge-docs.qodo.ai/tools/help_docs/), which can answer free-text questions based on a documentation folder.
-
-`/help_docs` is now being used to provide immediate automatic feedback to any user who [opens an issue](https://github.com/qodo-ai/pr-agent/issues/1608#issue-2897328825) on PR-Agent's open-source project
-
-## Overview
-
-<div style="text-align:left;">
-
-Supported commands per platform:
-
-|       |                                                                                                         | GitHub | GitLab | Bitbucket | Azure DevOps |
-| ----- |---------------------------------------------------------------------------------------------------------|:------:|:------:|:---------:|:------------:|
-| TOOLS | [Review](https://qodo-merge-docs.qodo.ai/tools/review/)                                                 |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Describe](https://qodo-merge-docs.qodo.ai/tools/describe/)                                             |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Improve](https://qodo-merge-docs.qodo.ai/tools/improve/)                                               |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Ask](https://qodo-merge-docs.qodo.ai/tools/ask/)                                                       |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | ⮑ [Ask on code lines](https://qodo-merge-docs.qodo.ai/tools/ask/#ask-lines)                             |   ✅   |   ✅   |           |              |
-|       | [Update CHANGELOG](https://qodo-merge-docs.qodo.ai/tools/update_changelog/)                             |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Help Docs](https://qodo-merge-docs.qodo.ai/tools/help_docs/?h=auto#auto-approval)                      |   ✅   |   ✅   |    ✅     |              |
-|       | [Ticket Context](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/) 💎            |   ✅   |   ✅   |    ✅     |              |
-|       | [Utilizing Best Practices](https://qodo-merge-docs.qodo.ai/tools/improve/#best-practices) 💎            |   ✅   |   ✅   |    ✅     |              |
-|       | [PR Chat](https://qodo-merge-docs.qodo.ai/chrome-extension/features/#pr-chat) 💎                        |   ✅   |        |           |              |
-|       | [Suggestion Tracking](https://qodo-merge-docs.qodo.ai/tools/improve/#suggestion-tracking) 💎            |   ✅   |   ✅   |           |              |
-|       | [CI Feedback](https://qodo-merge-docs.qodo.ai/tools/ci_feedback/) 💎                                    |   ✅   |        |           |              |
-|       | [PR Documentation](https://qodo-merge-docs.qodo.ai/tools/documentation/) 💎                             |   ✅   |   ✅   |           |              |
-|       | [Custom Labels](https://qodo-merge-docs.qodo.ai/tools/custom_labels/) 💎                                |   ✅   |   ✅   |           |              |
-|       | [Analyze](https://qodo-merge-docs.qodo.ai/tools/analyze/) 💎                                            |   ✅   |   ✅   |           |              |
-|       | [Similar Code](https://qodo-merge-docs.qodo.ai/tools/similar_code/) 💎                                  |   ✅   |        |           |              |
-|       | [Custom Prompt](https://qodo-merge-docs.qodo.ai/tools/custom_prompt/) 💎                                |   ✅   |   ✅   |    ✅     |              |
-|       | [Test](https://qodo-merge-docs.qodo.ai/tools/test/) 💎                                                  |   ✅   |   ✅   |           |              |
-|       | [Implement](https://qodo-merge-docs.qodo.ai/tools/implement/) 💎                                        |   ✅   |   ✅   |    ✅     |              |
-|       | [Scan Repo Discussions](https://qodo-merge-docs.qodo.ai/tools/scan_repo_discussions/) 💎                |   ✅   |        |           |              |
-|       | [Auto-Approve](https://qodo-merge-docs.qodo.ai/tools/improve/?h=auto#auto-approval) 💎                  |   ✅   |   ✅   |    ✅     |              |
-|       |                                                                                                         |        |        |           |              |
-| USAGE | [CLI](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#local-repo-cli)                |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [App / webhook](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#github-app)          |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Tagging bot](https://github.com/Codium-ai/pr-agent#try-it-now)                                         |   ✅   |        |           |              |
-|       | [Actions](https://qodo-merge-docs.qodo.ai/installation/github/#run-as-a-github-action)                  |   ✅   |   ✅   |    ✅     |      ✅      |
-|       |                                                                                                         |        |        |           |              |
-| CORE  | [PR compression](https://qodo-merge-docs.qodo.ai/core-abilities/compression_strategy/)                  |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | Adaptive and token-aware file patch fitting                                                             |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Multiple models support](https://qodo-merge-docs.qodo.ai/usage-guide/changing_a_model/)                |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Local and global metadata](https://qodo-merge-docs.qodo.ai/core-abilities/metadata/)                   |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Dynamic context](https://qodo-merge-docs.qodo.ai/core-abilities/dynamic_context/)                      |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Self reflection](https://qodo-merge-docs.qodo.ai/core-abilities/self_reflection/)                      |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Static code analysis](https://qodo-merge-docs.qodo.ai/core-abilities/static_code_analysis/) 💎         |   ✅   |   ✅   |           |              |
-|       | [Global and wiki configurations](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/) 💎 |   ✅   |   ✅   |    ✅     |              |
-|       | [PR interactive actions](https://www.qodo.ai/images/pr_agent/pr-actions.mp4) 💎                         |   ✅   |   ✅   |           |              |
-|       | [Impact Evaluation](https://qodo-merge-docs.qodo.ai/core-abilities/impact_evaluation/) 💎               |   ✅   |   ✅   |           |              |
-|       | [Code Validation 💎](https://qodo-merge-docs.qodo.ai/core-abilities/code_validation/)                   |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Auto Best Practices 💎](https://qodo-merge-docs.qodo.ai/core-abilities/auto_best_practices/)                     |   ✅   |      |         |            |
-- 💎 means this feature is available only in [Qodo Merge](https://www.qodo.ai/pricing/)
-
-[//]: # (- Support for additional git providers is described in [here]&#40;./docs/Full_environments.md&#41;)
-___
-
-‣ **Auto Description ([`/describe`](https://qodo-merge-docs.qodo.ai/tools/describe/))**: Automatically generating PR description - title, type, summary, code walkthrough and labels.
-\
-‣ **Auto Review ([`/review`](https://qodo-merge-docs.qodo.ai/tools/review/))**: Adjustable feedback about the PR, possible issues, security concerns, review effort and more.
-\
-‣ **Code Suggestions ([`/improve`](https://qodo-merge-docs.qodo.ai/tools/improve/))**: Code suggestions for improving the PR.
-\
-‣ **Question Answering ([`/ask ...`](https://qodo-merge-docs.qodo.ai/tools/ask/))**: Answering free-text questions about the PR.
-\
-‣ **Update Changelog ([`/update_changelog`](https://qodo-merge-docs.qodo.ai/tools/update_changelog/))**: Automatically updating the CHANGELOG.md file with the PR changes.
-\
-‣ **Help Docs ([`/help_docs`](https://qodo-merge-docs.qodo.ai/tools/help_docs/))**: Answers a question on any repository by utilizing given documentation.
-\
-‣ **Add Documentation 💎  ([`/add_docs`](https://qodo-merge-docs.qodo.ai/tools/documentation/))**: Generates documentation to methods/functions/classes that changed in the PR.
-\
-‣ **Generate Custom Labels 💎 ([`/generate_labels`](https://qodo-merge-docs.qodo.ai/tools/custom_labels/))**: Generates custom labels for the PR, based on specific guidelines defined by the user.
-\
-‣ **Analyze 💎 ([`/analyze`](https://qodo-merge-docs.qodo.ai/tools/analyze/))**: Identify code components that changed in the PR, and enables to interactively generate tests, docs, and code suggestions for each component.
-\
-‣ **Test 💎 ([`/test`](https://qodo-merge-docs.qodo.ai/tools/test/))**: Generate tests for a selected component, based on the PR code changes.
-\
-‣ **Custom Prompt 💎 ([`/custom_prompt`](https://qodo-merge-docs.qodo.ai/tools/custom_prompt/))**: Automatically generates custom suggestions for improving the PR code, based on specific guidelines defined by the user.
-\
-‣ **Generate Tests 💎 ([`/test component_name`](https://qodo-merge-docs.qodo.ai/tools/test/))**: Generates unit tests for a selected component, based on the PR code changes.
-\
-‣ **CI Feedback 💎 ([`/checks ci_job`](https://qodo-merge-docs.qodo.ai/tools/ci_feedback/))**: Automatically generates feedback and analysis for a failed CI job.
-\
-‣ **Similar Code 💎 ([`/find_similar_component`](https://qodo-merge-docs.qodo.ai/tools/similar_code/))**: Retrieves the most similar code components from inside the organization's codebase, or from open-source code.
-\
-‣ **Implement 💎 ([`/implement`](https://qodo-merge-docs.qodo.ai/tools/implement/))**: Generates implementation code from review suggestions.
-___
-
-## Example results
-
-</div>
-<h4><a href="https://github.com/Codium-ai/pr-agent/pull/530">/describe</a></h4>
-<div align="center">
-<p float="center">
-<img src="https://www.codium.ai/images/pr_agent/describe_new_short_main.png" width="512">
-</p>
-</div>
-<hr>
-
-<h4><a href="https://github.com/Codium-ai/pr-agent/pull/732#issuecomment-1975099151">/review</a></h4>
-<div align="center">
-<p float="center">
-<kbd>
-<img src="https://www.codium.ai/images/pr_agent/review_new_short_main.png" width="512">
-</kbd>
-</p>
-</div>
-<hr>
-
-<h4><a href="https://github.com/Codium-ai/pr-agent/pull/732#issuecomment-1975099159">/improve</a></h4>
-<div align="center">
-<p float="center">
-<kbd>
-<img src="https://www.codium.ai/images/pr_agent/improve_new_short_main.png" width="512">
-</kbd>
-</p>
-</div>
-
-<div align="left">
-
-</div>
-<hr>
-
-## Try it now
-
-Try the Claude Sonnet powered PR-Agent instantly on _your public GitHub repository_. Just mention `@CodiumAI-Agent` and add the desired command in any PR comment. The agent will generate a response based on your command.
-For example, add a comment to any pull request with the following text:
-
-```
-@CodiumAI-Agent /review
-```
-
-and the agent will respond with a review of your PR.
-
-Note that this is a promotional bot, suitable only for initial experimentation.
-It does not have 'edit' access to your repo, for example, so it cannot update the PR description or add labels (`@CodiumAI-Agent /describe` will publish PR description as a comment). In addition, the bot cannot be used on private repositories, as it does not have access to the files there.
+If you have an open-source project, you can get the Qodo paid version for free for your project, powered by Google Gemini 2.5 Pro – [https://www.qodo.ai/solutions/open-source/](https://www.qodo.ai/solutions/open-source/)
 
 ---
 
-## Qodo Merge 💎
+## ✨ Advanced Features in Qodo
 
-[Qodo Merge](https://www.qodo.ai/pricing/) is a hosted version of PR-Agent, provided by Qodo. It is available for a monthly fee, and provides the following benefits:
+### 🧭 PR → Ticket Automation  
+Seamlessly links pull requests to your project tracking system for end-to-end visibility.
 
-1. **Fully managed** - We take care of everything for you - hosting, models, regular updates, and more. Installation is as simple as signing up and adding the Qodo Merge app to your GitHub/GitLab/BitBucket repo.
-2. **Improved privacy** - No data will be stored or used to train models. Qodo Merge will employ zero data retention, and will use an OpenAI account with zero data retention.
-3. **Improved support** - Qodo Merge users will receive priority support, and will be able to request new features and capabilities.
-4. **Extra features** - In addition to the benefits listed above, Qodo Merge will emphasize more customization, and the usage of static code analysis, in addition to LLM logic, to improve results.
-See [here](https://qodo-merge-docs.qodo.ai/overview/pr_agent_pro/) for a list of features available in Qodo Merge.
+### ✅ Auto Best Practices  
+Learns your team’s standards and automatically enforces them during code reviews.
 
-## How it works
+### 🧪 Code Validation  
+Performs advanced static and semantic analysis to catch issues before merge.
 
-The following diagram illustrates PR-Agent tools and their flow:
+### 💬 PR Chat Interface  
+Lets you converse with your PR to explain, summarize, or suggest improvements instantly.
 
-![PR-Agent Tools](https://www.qodo.ai/images/pr_agent/diagram-v0.9.png)
+### 🔍 Impact Evaluation  
+Analyzes the business and technical effect of each change before approval.
 
-Check out the [PR Compression strategy](https://qodo-merge-docs.qodo.ai/core-abilities/#pr-compression-strategy) page for more details on how we convert a code diff to a manageable LLM prompt
+---
 
-## Why use PR-Agent?
-
-A reasonable question that can be asked is: `"Why use PR-Agent? What makes it stand out from existing tools?"`
-
-Here are some advantages of PR-Agent:
-
-- We emphasize **real-life practical usage**. Each tool (review, improve, ask, ...) has a single LLM call, no more. We feel that this is critical for realistic team usage - obtaining an answer quickly (~30 seconds) and affordably.
-- Our [PR Compression strategy](https://qodo-merge-docs.qodo.ai/core-abilities/#pr-compression-strategy)  is a core ability that enables to effectively tackle both short and long PRs.
-- Our JSON prompting strategy enables to have **modular, customizable tools**. For example, the '/review' tool categories can be controlled via the [configuration](pr_agent/settings/configuration.toml) file. Adding additional categories is easy and accessible.
-- We support **multiple git providers** (GitHub, GitLab, BitBucket), **multiple ways** to use the tool (CLI, GitHub Action, GitHub App, Docker, ...), and **multiple models** (GPT, Claude, Deepseek, ...)
-
-## Data privacy
-
-### Self-hosted PR-Agent
-
-- If you host PR-Agent with your OpenAI API key, it is between you and OpenAI. You can read their API data privacy policy here:
-https://openai.com/enterprise-privacy
-
-### Qodo-hosted Qodo Merge 💎
-
-- When using Qodo Merge 💎, hosted by Qodo, we will not store any of your data, nor will we use it for training. You will also benefit from an OpenAI account with zero data retention.
-
-- For certain clients, Qodo-hosted Qodo Merge will use Qodo’s proprietary models — if this is the case, you will be notified.
-
-- No passive collection of Code and Pull Requests’ data — Qodo Merge will be active only when you invoke it, and it will then extract and analyze only data relevant to the executed command and queried pull request.
-
-### Qodo Merge Chrome extension
-
-- The [Qodo Merge Chrome extension](https://chromewebstore.google.com/detail/qodo-merge-ai-powered-cod/ephlnjeghhogofkifjloamocljapahnl) serves solely to modify the visual appearance of a GitHub PR screen. It does not transmit any user's repo or pull request code. Code is only sent for processing when a user submits a GitHub comment that activates a PR-Agent tool, in accordance with the standard privacy policy of Qodo-Merge.
-
-## Contributing
-
-To contribute to the project, get started by reading our [Contributing Guide](https://github.com/qodo-ai/pr-agent/blob/b09eec265ef7d36c232063f76553efb6b53979ff/CONTRIBUTING.md).
-
-## Links
-
-- Discord community: https://discord.gg/kG35uSHDBc
-- Qodo site: https://www.qodo.ai/
-- Blog: https://www.qodo.ai/blog/
-- Troubleshooting: https://www.qodo.ai/blog/technical-faq-and-troubleshooting/
-- Support: support@qodo.ai
+## ❤️ Community
+This open-source release remains here as a community contribution from Qodo — the origin of modern AI-powered code collaboration.  
+We’re proud to share it and inspire developers worldwide.

SECURITY.md

@@ -59,6 +59,6 @@ steps:
 
 We take the security of PR-Agent seriously. If you discover a security vulnerability, please report it immediately to:
 
-Email: tal.r@qodo.ai
+Email: security@qodo.ai
 
 Please include a description of the vulnerability, steps to reproduce, and the affected PR-Agent version.

docker/Dockerfile

@@ -33,6 +33,11 @@ FROM base AS azure_devops_webhook
 ADD pr_agent pr_agent
 CMD ["python", "pr_agent/servers/azuredevops_server_webhook.py"]
 
+FROM base AS gitea_app
+ADD pr_agent pr_agent
+CMD ["python", "-m", "gunicorn", "-k", "uvicorn.workers.UvicornWorker", "-c", "pr_agent/servers/gunicorn_config.py","pr_agent.servers.gitea_app:app"]
+
+
 FROM base AS test
 ADD requirements-dev.txt .
 RUN pip install --no-cache-dir -r requirements-dev.txt && rm requirements-dev.txt

docker/Dockerfile.lambda

@@ -1,4 +1,4 @@
-FROM public.ecr.aws/lambda/python:3.12
+FROM public.ecr.aws/lambda/python:3.12 AS base
 
 RUN dnf update -y && \
     dnf install -y gcc python3-devel git && \
@@ -9,4 +9,10 @@ RUN pip install --no-cache-dir . && rm pyproject.toml
 RUN pip install --no-cache-dir mangum==0.17.0
 COPY pr_agent/ ${LAMBDA_TASK_ROOT}/pr_agent/
 
-CMD ["pr_agent.servers.serverless.serverless"]
+FROM base AS github_lambda
+CMD ["pr_agent.servers.github_lambda_webhook.lambda_handler"]
+
+FROM base AS gitlab_lambda
+CMD ["pr_agent.servers.gitlab_lambda_webhook.lambda_handler"]
+
+FROM github_lambda

docs/docs/.gitbook.yaml

@@ -0,0 +1,5 @@
+root: ./
+
+structure:
+  readme: ../README.md
+  summary: ./summary.md

docs/docs/ai_search/index.md

@@ -19,7 +19,6 @@
 </div>
 
 <style>
-Untitled
 .search-section {
     max-width: 800px;
     margin: 0 auto;
@@ -202,7 +201,23 @@ h1 {
 
 <script>
 window.addEventListener('load', function() {
-    function displayResults(responseText) {
+    function extractText(responseText) {
+        try {
+            console.log('responseText: ', responseText);
+            const results = JSON.parse(responseText);
+            const msg = results.message;
+
+            if (!msg || msg.trim() === '') {
+                return "No results found";
+            }
+            return msg;
+        } catch (error) {
+            console.error('Error parsing results:', error);
+            throw new Error("Failed parsing response message");
+        }
+    }
+
+    function displayResults(msg) {
         const resultsContainer = document.getElementById('results');
         const spinner = document.getElementById('spinner');
         const searchContainer = document.querySelector('.search-container');
@@ -214,8 +229,6 @@ window.addEventListener('load', function() {
         searchContainer.scrollIntoView({ behavior: 'smooth', block: 'start' });
 
         try {
-            const results = JSON.parse(responseText);
-
             marked.setOptions({
                 breaks: true,
                 gfm: true,
@@ -223,7 +236,7 @@ window.addEventListener('load', function() {
                 sanitize: false
             });
 
-            const htmlContent = marked.parse(results.message);
+            const htmlContent = marked.parse(msg);
 
             resultsContainer.className = 'markdown-content';
             resultsContainer.innerHTML = htmlContent;
@@ -242,7 +255,7 @@ window.addEventListener('load', function() {
             }, 100);
         } catch (error) {
             console.error('Error parsing results:', error);
-            resultsContainer.innerHTML = '<div class="error-message">Error processing results</div>';
+            resultsContainer.innerHTML = '<div class="error-message">Cannot process results</div>';
         }
     }
 
@@ -275,24 +288,24 @@ window.addEventListener('load', function() {
                 body: JSON.stringify(data)
             };
 
-            // const API_ENDPOINT = 'http://0.0.0.0:3000/api/v1/docs_help';
+            //const API_ENDPOINT = 'http://0.0.0.0:3000/api/v1/docs_help';
             const API_ENDPOINT = 'https://help.merge.qodo.ai/api/v1/docs_help';
 
             const response = await fetch(API_ENDPOINT, options);
+            const responseText = await response.text();
+            const msg = extractText(responseText);
 
             if (!response.ok) {
-                throw new Error(`HTTP error! status: ${response.status}`);
+                throw new Error(`An error (${response.status}) occurred during search: "${msg}"`);
             }
-
-            const responseText = await response.text();
-            displayResults(responseText);
+ 
+            displayResults(msg);
         } catch (error) {
             spinner.style.display = 'none';
-            resultsContainer.innerHTML = `
-                <div class="error-message">
-                    An error occurred while searching. Please try again later.
-                </div>
-            `;
+            const errorDiv = document.createElement('div');
+            errorDiv.className = 'error-message';
+            errorDiv.textContent = error instanceof Error ? error.message : String(error);
+            resultsContainer.replaceChildren(errorDiv);
         }
     }
 

docs/docs/chrome-extension/index.md

@@ -1,10 +1,12 @@
+`Platforms supported: GitHub Cloud`
+
 [Qodo Merge Chrome extension](https://chromewebstore.google.com/detail/pr-agent-chrome-extension/ephlnjeghhogofkifjloamocljapahnl){:target="_blank"} is a collection of tools that integrates seamlessly with your GitHub environment, aiming to enhance your Git usage experience, and providing AI-powered capabilities to your PRs.
 
 With a single-click installation you will gain access to a context-aware chat on your pull requests code, a toolbar extension with multiple AI feedbacks, Qodo Merge filters, and additional abilities.
 
-The extension is powered by top code models like Claude 3.7 Sonnet and o4-mini. All the extension's features are free to use on public repositories.
+The extension is powered by top code models like GPT-5. All the extension's features are free to use on public repositories.
 
-For private repositories, you will need to install [Qodo Merge](https://github.com/apps/qodo-merge-pro){:target="_blank"} in addition to the extension  (Quick GitHub app setup with a 14-day free trial. No credit card needed).
+For private repositories, you will need to install [Qodo Merge](https://github.com/apps/qodo-merge-pro){:target="_blank"} in addition to the extension.
 For a demonstration of how to install Qodo Merge and use it with the Chrome extension, please refer to the tutorial video at the provided [link](https://codium.ai/images/pr_agent/private_repos.mp4){:target="_blank"}.
 
 <img src="https://codium.ai/images/pr_agent/PR-AgentChat.gif" width="768">
@@ -12,3 +14,101 @@ For a demonstration of how to install Qodo Merge and use it with the Chrome exte
 ### Supported browsers
 
 The extension is supported on all Chromium-based browsers, including Google Chrome, Arc, Opera, Brave, and Microsoft Edge.
+
+## Features
+
+### PR chat
+
+The PR-Chat feature allows to freely chat with your PR code, within your GitHub environment.
+It will seamlessly use the PR as context to your chat session, and provide AI-powered feedback.
+
+To enable private chat, simply install the Qodo Merge Chrome extension. After installation, each PR's file-changed tab will include a chat box, where you may ask questions about your code.
+This chat session is **private**, and won't be visible to other users.
+
+All open-source repositories are supported.
+For private repositories, you will also need to install Qodo Merge. After installation, make sure to open at least one new PR to fully register your organization. Once done, you can chat with both new and existing PRs across all installed repositories.
+
+#### Context-aware PR chat
+
+Qodo Merge constructs a comprehensive context for each pull request, incorporating the PR description, commit messages, and code changes with extended dynamic context. This contextual information, along with additional PR-related data, forms the foundation for an AI-powered chat session. The agent then leverages this rich context to provide intelligent, tailored responses to user inquiries about the pull request.
+
+<img src="https://codium.ai/images/pr_agent/pr_chat_1.png" width="768">
+<img src="https://codium.ai/images/pr_agent/pr_chat_2.png" width="768">
+
+### Toolbar extension
+
+With Qodo Merge Chrome extension, it's [easier than ever](https://www.youtube.com/watch?v=gT5tli7X4H4) to interactively configure and experiment with the different tools and configuration options.
+
+For private repositories, after you found the setup that works for you, you can also easily export it as a persistent configuration file, and use it for automatic commands.
+
+<img src="https://codium.ai/images/pr_agent/toolbar1.png" width="512">
+
+<img src="https://codium.ai/images/pr_agent/toolbar2.png" width="512">
+
+### Qodo Merge filters
+
+Qodo Merge filters is a sidepanel option. that allows you to filter different message in the conversation tab.
+
+For example, you can choose to present only message from Qodo Merge, or filter those messages, focusing only on user's comments.
+
+<img src="https://codium.ai/images/pr_agent/pr_agent_filters1.png" width="256">
+
+<img src="https://codium.ai/images/pr_agent/pr_agent_filters2.png" width="256">
+
+### Enhanced code suggestions
+
+Qodo Merge Chrome extension adds the following capabilities to code suggestions tool's comments:
+
+- Auto-expand the table when you are viewing a code block, to avoid clipping.
+- Adding a "quote-and-reply" button, that enables to address and comment on a specific suggestion (for example, asking the author to fix the issue)
+
+<img src="https://codium.ai/images/pr_agent/chrome_extension_code_suggestion1.png" width="512">
+
+<img src="https://codium.ai/images/pr_agent/chrome_extension_code_suggestion2.png" width="512">
+
+## Data Privacy
+
+We take your code's security and privacy seriously:
+
+- The Chrome extension will not send your code to any external servers.
+- For private repositories, we will first validate the user's identity and permissions. After authentication, we generate responses using the existing Qodo Merge integration.
+
+## Options and Configurations
+
+### Accessing the Options Page
+
+To access the options page for the Qodo Merge Chrome extension:
+
+1. Find the extension icon in your Chrome toolbar (usually in the top-right corner of your browser)
+2. Right-click on the extension icon
+3. Select "Options" from the context menu that appears
+
+Alternatively, you can access the options page directly using this URL:
+
+[chrome-extension://ephlnjeghhogofkifjloamocljapahnl/options.html](chrome-extension://ephlnjeghhogofkifjloamocljapahnl/options.html)
+
+<img src="https://codium.ai/images/pr_agent/chrome_ext_options.png" width="256">
+
+### Configuration Options
+
+<img src="https://codium.ai/images/pr_agent/chrome_ext_settings_page.png" width="512">
+
+#### API Base Host
+
+For single-tenant customers, you can configure the extension to communicate directly with your company's Qodo Merge server instance.
+
+To set this up:
+
+- Enter your organization's Qodo Merge API endpoint in the "API Base Host" field
+- This endpoint should be provided by your Qodo DevOps Team
+
+*Note: The extension does not send your code to the server, but only triggers your previously installed Qodo Merge application.*
+
+#### Interface Options
+
+You can customize the extension's interface by:
+
+- Toggling the "Show Qodo Merge Toolbar" option
+- When disabled, the toolbar will not appear in your Github comment bar
+
+Remember to click "Save Settings" after making any changes.

docs/docs/core-abilities/auto_approval.md

@@ -0,0 +1,83 @@
+# Auto-approval 💎
+
+`Supported Git Platforms: GitHub, GitLab, Bitbucket`
+
+Under specific conditions, Qodo Merge can auto-approve a PR when a manual comment is invoked, or when the PR meets certain criteria.
+
+**To ensure safety, the auto-approval feature is disabled by default.**
+To enable auto-approval features, you need to actively set one or both of the following options in a pre-defined _configuration file_:
+
+```toml
+[config]
+enable_comment_approval = true # For approval via comments
+enable_auto_approval = true   # For criteria-based auto-approval
+```
+
+!!! note "Notes"
+    - These flags above cannot be set with a command line argument, only in the configuration file, committed to the repository.
+    - Enabling auto-approval must be a deliberate decision by the repository owner.
+
+## **Approval by commenting**
+
+To enable approval by commenting, set in the configuration file:
+
+```toml
+[config]
+enable_comment_approval = true
+```
+
+After enabling, by commenting on a PR:
+
+```
+/review auto_approve
+```
+
+Qodo Merge will approve the PR and add a comment with the reason for the approval.
+
+## **Auto-approval when the PR meets certain criteria**
+
+To enable auto-approval based on specific criteria, first, you need to enable the top-level flag:
+
+```toml
+[config]
+enable_auto_approval = true
+```
+
+There are two possible paths leading to this auto-approval - one via the `review` tool, and one via the `improve` tool. Each tool can independently trigger auto-approval.
+
+### Auto-approval via the `review` tool
+
+- **Review effort score criteria**
+
+    ```toml
+    [config]
+    enable_auto_approval = true
+    auto_approve_for_low_review_effort = X # X is a number between 1 and 5
+    ```
+    
+    When the [review effort score](https://www.qodo.ai/images/pr_agent/review3.png) is lower than or equal to X, the PR will be auto-approved (unless ticket compliance is enabled and fails, see below).
+
+- **Ticket compliance criteria**
+    
+    ```toml
+    [config]
+    enable_auto_approval = true
+    ensure_ticket_compliance = true # Default is false
+    ```
+    
+    If `ensure_ticket_compliance` is set to `true`, auto-approval for the `review` toll path will be disabled if no ticket is linked to the PR, or if the PR is not fully compliant with a linked ticket. This ensures that PRs are only auto-approved if their associated tickets are properly resolved.
+    
+    You can also prevent auto-approval if the PR exceeds the ticket's scope (see [here](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#configuration-options)).
+
+
+### Auto-approval via the `improve` tool
+
+PRs can be auto-approved when the `improve` tool doesn't find code suggestions.
+To enable this feature, set the following in the configuration file:
+
+```toml
+[config]
+enable_auto_approval = true
+auto_approve_for_no_suggestions = true
+```
+

docs/docs/core-abilities/auto_best_practices.md

@@ -41,13 +41,9 @@ When presenting the suggestions generated by the `improve` tool, Qodo Merge will
 
 Teams and companies can also manually define their own [custom best practices](https://qodo-merge-docs.qodo.ai/tools/improve/#best-practices) in Qodo Merge.
 
-When custom best practices exist, Qodo Merge will still generate an 'auto best practices' wiki file, though it won't be used by the `improve` tool.
-However, this auto-generated file can still serve two valuable purposes:
+When custom best practices exist, Qodo Merge will use both the auto-generated best practices and your custom best practices together. The auto best practices file provides additional insights derived from suggestions your team found valuable enough to implement, while also demonstrating effective patterns for writing AI-friendly best practices.
 
-1. It can help enhance your custom best practices with additional insights derived from suggestions your team found valuable enough to implement
-2. It demonstrates effective patterns for writing AI-friendly best practices
-
-Even when using custom best practices, we recommend regularly reviewing the auto best practices file to refine your custom rules.
+We recommend utilizing both auto and custom best practices to get the most comprehensive code improvement suggestions for your team.
 
 ## Relevant configurations
 

docs/docs/core-abilities/chat_on_code_suggestions.md

@@ -0,0 +1,55 @@
+# Chat on code suggestions 💎
+
+`Supported Git Platforms: GitHub, GitLab`
+
+## Overview
+
+Qodo Merge implements an orchestrator agent that enables interactive code discussions, listening and responding to comments without requiring explicit tool calls.
+The orchestrator intelligently analyzes your responses to determine if you want to implement a suggestion, ask a question, or request help, then delegates to the appropriate specialized tool.
+
+To minimize unnecessary notifications and maintain focused discussions, the orchestrator agent will only respond to comments made directly within the inline code suggestion discussions it has created (`/improve`) or within discussions initiated by the `/implement` command.
+
+##  Getting Started
+
+### Setup
+
+Enable interactive code discussions by adding the following to your configuration file (default is `True`):
+
+```toml
+[pr_code_suggestions]
+enable_chat_in_code_suggestions = true
+```
+
+
+### Activation
+
+#### `/improve`
+
+To obtain dynamic responses, the following steps are required:
+
+1. Run the `/improve` command (mostly automatic)
+2. Check the `/improve` recommendation checkboxes (_Apply this suggestion_) to have Qodo Merge generate a new inline code suggestion discussion
+3. The orchestrator agent will then automatically listen to and reply to comments within the discussion without requiring additional commands
+
+#### `/implement`
+
+To obtain dynamic responses, the following steps are required:
+
+1. Select code lines in the PR diff and run the `/implement` command
+2. Wait for Qodo Merge to generate a new inline code suggestion
+3. The orchestrator agent will then automatically listen to and reply to comments within the discussion without requiring additional commands
+
+
+## Explore the available interaction patterns
+
+!!! tip "Tip: Direct the agent with keywords"
+    Use "implement" or "apply" for code generation. Use "explain", "why", or "how" for information and help.
+
+=== "Asking for Details"
+    ![Chat on code suggestions ask](https://codium.ai/images/pr_agent/improve_chat_on_code_suggestions_ask.png){width=512}
+
+=== "Implementing Suggestions"
+    ![Chat on code suggestions implement](https://codium.ai/images/pr_agent/improve_chat_on_code_suggestions_implement.png){width=512}
+
+=== "Providing Additional Help"
+    ![Chat on code suggestions help](https://codium.ai/images/pr_agent/improve_chat_on_code_suggestions_help.png){width=512}

docs/docs/core-abilities/code_validation.md

@@ -1,3 +1,8 @@
+# Code Validation 💎
+
+`Supported Git Platforms: GitHub, GitLab, Bitbucket`
+
+
 ## Introduction
 
 The Git environment usually represents the final stage before code enters production. Hence, Detecting bugs and issues during the review process is critical.

docs/docs/core-abilities/compression_strategy.md

@@ -1,5 +1,8 @@
 
-## Overview - PR Compression Strategy
+`Supported Git Platforms: GitHub, GitLab, Bitbucket`
+
+
+## Overview
 
 There are two scenarios:
 

docs/docs/core-abilities/dynamic_context.md

@@ -1,4 +1,5 @@
-## TL;DR
+
+`Supported Git Platforms: GitHub, GitLab, Bitbucket`
 
 Qodo Merge uses an **asymmetric and dynamic context strategy** to improve AI analysis of code changes in pull requests.
 It provides more context before changes than after, and dynamically adjusts the context based on code structure (e.g., enclosing functions or classes).

docs/docs/core-abilities/fetching_ticket_context.md

@@ -9,8 +9,10 @@ This integration enriches the review process by automatically surfacing relevant
 
 **Ticket systems supported**:
 
-- GitHub
-- Jira (💎)
+- [GitHub/Gitlab Issues](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#githubgitlab-issues-integration)
+- [Jira (💎)](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#jira-integration)
+- [Linear (💎)](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#linear-integration)
+- [Monday (💎)](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#monday-integration)
 
 **Ticket data fetched:**
 
@@ -38,27 +40,80 @@ By understanding the reasoning and intent behind modifications, the LLM can offe
 Similarly to the `describe` tool, the `review` tool will use the ticket content to provide additional context for the code changes.
 
 In addition, this feature will evaluate how well a Pull Request (PR) adheres to its original purpose/intent as defined by the associated ticket or issue mentioned in the PR description.
-Each ticket will be assigned a label (Compliance/Alignment level), Indicates the degree to which the PR fulfills its original purpose, Options: Fully compliant, Partially compliant or Not compliant.
+Each ticket will be assigned a label (Compliance/Alignment level), Indicates the degree to which the PR fulfills its original purpose:
+
+- Fully Compliant
+- Partially Compliant
+- Not Compliant
+- PR Code Verified
 
 ![Ticket Compliance](https://www.qodo.ai/images/pr_agent/ticket_compliance_review.png){width=768}
 
-By default, the tool will automatically validate if the PR complies with the referenced ticket.
-If you want to disable this feedback, add the following line to your configuration file:
+A `PR Code Verified` label indicates the PR code meets ticket requirements, but requires additional manual testing beyond the code scope. For example - validating UI display across different environments (Mac, Windows, mobile, etc.).
 
-```toml
-[pr_reviewer]
-require_ticket_analysis_review=false
-```
 
-## GitHub Issues Integration
+#### Configuration options
 
-Qodo Merge will automatically recognize GitHub issues mentioned in the PR description and fetch the issue content.
-Examples of valid GitHub issue references:
+-
 
-- `https://github.com/<ORG_NAME>/<REPO_NAME>/issues/<ISSUE_NUMBER>`
+    By default, the `review` tool will automatically validate if the PR complies with the referenced ticket.
+    If you want to disable this feedback, add the following line to your configuration file:
+
+    ```toml
+    [pr_reviewer]
+    require_ticket_analysis_review=false
+    ```
+
+-
+
+    If you set:
+    ```toml
+    [pr_reviewer]
+    check_pr_additional_content=true
+    ```
+    (default: `false`)
+
+    the `review` tool will also validate that the PR code doesn't contain any additional content that is not related to the ticket. If it does, the PR will be labeled at best as `PR Code Verified`, and the `review` tool will provide a comment with the additional unrelated content found in the PR code.
+
+### Compliance tool
+
+The `compliance` tool also uses ticket context to validate that PR changes fulfill the requirements specified in linked tickets.
+
+#### Configuration options
+
+-
+
+    By default, the `compliance` tool will automatically validate if the PR complies with the referenced ticket.
+    If you want to disable ticket compliance checking in the compliance tool, add the following line to your configuration file:
+
+    ```toml
+    [pr_compliance]
+    require_ticket_analysis_review=false
+    ```
+
+-
+
+    If you set:
+    ```toml
+    [pr_compliance]
+    check_pr_additional_content=true
+    ```
+    (default: `false`)
+
+    the `compliance` tool will also validate that the PR code doesn't contain any additional content that is not related to the ticket.
+
+## GitHub/Gitlab Issues Integration
+
+Qodo Merge will automatically recognize GitHub/Gitlab issues mentioned in the PR description and fetch the issue content.
+Examples of valid GitHub/Gitlab issue references:
+
+- `https://github.com/<ORG_NAME>/<REPO_NAME>/issues/<ISSUE_NUMBER>` or `https://gitlab.com/<ORG_NAME>/<REPO_NAME>/-/issues/<ISSUE_NUMBER>`
 - `#<ISSUE_NUMBER>`
 - `<ORG_NAME>/<REPO_NAME>#<ISSUE_NUMBER>`
 
+Branch names can also be used to link issues, for example:
+- `123-fix-bug` (where `123` is the issue number)
+
 Since Qodo Merge is integrated with GitHub, it doesn't require any additional configuration to fetch GitHub issues.
 
 ## Jira Integration 💎
@@ -75,13 +130,17 @@ The recommended way to authenticate with Jira Cloud is to install the Qodo Merge
 
 Installation steps:
 
-1. Click [here](https://auth.atlassian.com/authorize?audience=api.atlassian.com&client_id=8krKmA4gMD8mM8z24aRCgPCSepZNP1xf&scope=read%3Ajira-work%20offline_access&redirect_uri=https%3A%2F%2Fregister.jira.pr-agent.codium.ai&state=qodomerge&response_type=code&prompt=consent) to install the Qodo Merge app in your Jira Cloud instance, click the `accept` button.<br>
-![Jira Cloud App Installation](https://www.qodo.ai/images/pr_agent/jira_app_installation1.png){width=384}
+1. Go to the [Qodo Merge integrations page](https://app.qodo.ai/qodo-merge/integrations)
 
-2. After installing the app, you will be redirected to the Qodo Merge registration page. and you will see a success message.<br>
+2. Click on the Connect **Jira Cloud** button to connect the Jira Cloud app
+
+3. Click the `accept` button.<br>
+![Jira Cloud App Installation](https://www.qodo.ai/images/pr_agent/jira_app_installation2.png){width=384}
+
+4. After installing the app, you will be redirected to the Qodo Merge registration page. and you will see a success message.<br>
 ![Jira Cloud App success message](https://www.qodo.ai/images/pr_agent/jira_app_success.png){width=384}
 
-3. Now Qodo Merge will be able to fetch Jira ticket context for your PRs.
+5. Now Qodo Merge will be able to fetch Jira ticket context for your PRs.
 
 **2) Email/Token Authentication**
 
@@ -190,7 +249,7 @@ This following steps will help you check if the basic auth is working correctly,
 
 2. run the following Python script (after replacing the placeholders with your actual values):
 
-??? example "Script to validate basic auth"
+???- example "Script to validate basic auth"
 
     ```python
     from jira import JIRA
@@ -246,7 +305,7 @@ This following steps will help you check if the token is working correctly, and
 
 2. run the following Python script (after replacing the placeholders with your actual values):
 
-??? example "Script to validate PAT token"
+??? example- "Script to validate PAT token"
 
     ```python
     from jira import JIRA
@@ -281,13 +340,90 @@ This following steps will help you check if the token is working correctly, and
             print(f"Error fetching JIRA ticket details: {e}")
     ```
 
+
+### Multi-JIRA Server Configuration 💎
+
+Qodo Merge supports connecting to multiple JIRA servers using different authentication methods.
+
+=== "Email/Token (Basic Auth)"
+
+    Configure multiple servers using Email/Token authentication:
+
+    - `jira_servers`: List of JIRA server URLs
+    - `jira_api_token`: List of API tokens (for Cloud) or passwords (for Data Center)
+    - `jira_api_email`: List of emails (for Cloud) or usernames (for Data Center)
+    - `jira_base_url`: Default server for ticket IDs like `PROJ-123`, Each repository can configure (local config file) its own `jira_base_url` to choose which server to use by default.
+
+    **Example Configuration:**
+    ```toml
+    [jira]
+    # Server URLs
+    jira_servers = ["https://company.atlassian.net", "https://datacenter.jira.com"]
+
+    # API tokens/passwords
+    jira_api_token = ["cloud_api_token_here", "datacenter_password"]
+
+    # Emails/usernames (both required)
+    jira_api_email = ["user@company.com", "datacenter_username"]
+
+    # Default server for ticket IDs
+    jira_base_url = "https://company.atlassian.net"
+    ```
+
+=== "PAT Auth"
+
+    Configure multiple servers using Personal Access Token authentication:
+
+    - `jira_servers`: List of JIRA server URLs
+    - `jira_api_token`: List of PAT tokens
+    - `jira_api_email`: Not needed (can be omitted or left empty)
+    - `jira_base_url`: Default server for ticket IDs like `PROJ-123`, Each repository can configure (local config file) its own `jira_base_url` to choose which server to use by default.
+
+    **Example Configuration:**
+    ```toml
+    [jira]
+    # Server URLs
+    jira_servers = ["https://server1.jira.com", "https://server2.jira.com"]
+
+    # PAT tokens only
+    jira_api_token = ["pat_token_1", "pat_token_2"]
+
+    # Default server for ticket IDs
+    jira_base_url = "https://server1.jira.com"
+    ```
+
+    **Mixed Authentication (Email/Token + PAT):**
+    ```toml
+    [jira]
+    jira_servers = ["https://company.atlassian.net", "https://server.jira.com"]
+    jira_api_token = ["cloud_api_token", "server_pat_token"]
+    jira_api_email = ["user@company.com", ""]  # Empty for PAT
+    ```
+
+=== "Jira Cloud App"
+
+    For Jira Cloud instances using App Authentication:
+
+    1. Install the Qodo Merge app on each JIRA Cloud instance you want to connect to
+    2. Set the default server for ticket ID resolution:
+
+    ```toml
+    [jira]
+    jira_base_url = "https://primary-team.atlassian.net"
+    ```
+
+    Full URLs (e.g., `https://other-team.atlassian.net/browse/TASK-456`) will automatically use the correct connected instance.
+
+
+
+
 ### How to link a PR to a Jira ticket
 
 To integrate with Jira, you can link your PR to a ticket using either of these methods:
 
 **Method 1: Description Reference:**
 
-Include a ticket reference in your PR description using either the complete URL format https://<JIRA_ORG>.atlassian.net/browse/ISSUE-123 or the shortened ticket ID ISSUE-123.
+Include a ticket reference in your PR description, using either the complete URL format `https://<JIRA_ORG>.atlassian.net/browse/ISSUE-123` or the shortened ticket ID `ISSUE-123` (without prefix or suffix for the shortened ID).
 
 **Method 2: Branch Name Detection:**
 
@@ -300,3 +436,92 @@ Name your branch with the ticket ID as a prefix (e.g., `ISSUE-123-feature-descri
     [jira]
     jira_base_url = "https://<JIRA_ORG>.atlassian.net"
     ```
+    Where `<JIRA_ORG>` is your Jira organization identifier (e.g., `mycompany` for `https://mycompany.atlassian.net`).
+
+## Linear Integration 💎
+
+### Linear App Authentication
+
+The recommended way to authenticate with Linear is to connect the Linear app through the Qodo Merge portal.
+
+Installation steps:
+
+1. Go to the [Qodo Merge integrations page](https://app.qodo.ai/qodo-merge/integrations)
+
+2. Navigate to the **Integrations** tab
+
+3. Click on the **Linear** button to connect the Linear app
+
+4. Follow the authentication flow to authorize Qodo Merge to access your Linear workspace
+
+5. Once connected, Qodo Merge will be able to fetch Linear ticket context for your PRs
+
+### How to link a PR to a Linear ticket
+
+Qodo Merge will automatically detect Linear tickets using either of these methods:
+
+**Method 1: Description Reference:**
+
+Include a ticket reference in your PR description using either:
+- The complete Linear ticket URL: `https://linear.app/[ORG_ID]/issue/[TICKET_ID]`
+- The shortened ticket ID: `[TICKET_ID]` (e.g., `ABC-123`) - requires linear_base_url configuration (see below).
+
+**Method 2: Branch Name Detection:**
+
+Name your branch with the ticket ID as a prefix (e.g., `ABC-123-feature-description` or `feature/ABC-123/feature-description`).
+
+!!! note "Linear Base URL"
+    For shortened ticket IDs or branch detection (method 2), you must configure the Linear base URL in your configuration file under the [linear] section:
+    
+    ```toml
+    [linear]
+    linear_base_url = "https://linear.app/[ORG_ID]"
+    ```
+    
+    Replace `[ORG_ID]` with your Linear organization identifier.
+
+## Monday Integration 💎
+
+### Monday App Authentication
+The recommended way to authenticate with Monday is to connect the Monday app through the Qodo Merge portal.
+
+Installation steps:
+
+1. Go to the [Qodo Merge integrations page](https://app.qodo.ai/qodo-merge/integrations)
+2. Navigate to the **Integrations** tab
+3. Click on the **Monday** button to connect the Monday app
+4. Follow the authentication flow to authorize Qodo Merge to access your Monday workspace
+5. Once connected, Qodo Merge will be able to fetch Monday ticket context for your PRs
+
+### Monday Ticket Context
+`Ticket Context and Ticket Compliance are supported for Monday items, but not yet available in the "PR to Ticket" feature.`
+
+When Qodo Merge processes your PRs, it extracts the following information from Monday items:
+
+* **Item ID and Name:** The unique identifier and title of the Monday item
+* **Item URL:** Direct link to the Monday item in your workspace
+* **Ticket Description:** All long text type columns and their values from the item
+* **Status and Labels:** Current status values and color-coded labels for quick context
+* **Sub-items:** Names, IDs, and descriptions of all related sub-items with hierarchical structure
+
+### How Monday Items are Detected
+Qodo Merge automatically detects Monday items from:
+
+* PR Descriptions: Full Monday URLs like https://workspace.monday.com/boards/123/pulses/456
+* Branch Names: Item IDs in branch names (6-12 digit patterns) - requires `monday_base_url` configuration
+
+### Configuration Setup (Optional)
+If you want to extract Monday item references from branch names or use standalone item IDs, you need to set the `monday_base_url` in your configuration file:
+
+To support Monday ticket referencing from branch names, item IDs (6-12 digits) should be part of the branch names and you need to configure `monday_base_url`:
+```toml
+[monday]
+monday_base_url = "https://your_monday_workspace.monday.com"
+```
+
+Examples of supported branch name patterns:
+
+* `feature/123456789` → extracts item ID 123456789
+* `bugfix/456789012-login-fix` → extracts item ID 456789012
+* `123456789` → extracts item ID 123456789
+* `456789012-login-fix` → extracts item ID 456789012

docs/docs/core-abilities/high_level_suggestions.md

@@ -0,0 +1,19 @@
+# High-level Code Suggestions 💎
+
+`Supported Git Platforms: GitHub, GitLab, Bitbucket Cloud, Bitbucket Server`
+
+## Overview
+High-level code suggestions, generated by the `improve` tool, offer big-picture code suggestions for your pull request. They focus on broader improvements rather than local fixes, and provide before-and-after code snippets to illustrate the recommended changes and guide implementation.
+
+### How it works
+
+=== "Example of a high-level suggestion"
+    ![code_suggestions_update](https://www.qodo.ai/images/pr_agent/high_level_suggestion_closed.png){width=512}
+    ![code_suggestions_update](https://www.qodo.ai/images/pr_agent/high_level_suggestion_open.png){width=512}
+
+___
+
+### Benefits for Developers
+
+- Help spot systematic issues in the pull request
+- Give the author another review angle, while giving them the freedom on how to address the suggestion.

docs/docs/core-abilities/impact_evaluation.md

@@ -1,4 +1,6 @@
-# Overview - Impact Evaluation 💎
+# Impact Evaluation 💎
+
+`Supported Git Platforms: GitHub, GitLab, Bitbucket`
 
 Demonstrating the return on investment (ROI) of AI-powered initiatives is crucial for modern organizations.
 To address this need, Qodo Merge has developed an AI impact measurement tools and metrics, providing advanced analytics to help businesses quantify the tangible benefits of AI adoption in their PR review process.

docs/docs/core-abilities/incremental_update.md

@@ -0,0 +1,33 @@
+# Incremental Update 💎
+
+`Supported Git Platforms: GitHub, GitLab (Both cloud & server. For server: Version 17 and above)`
+
+## Overview
+The Incremental Update feature helps users focus on feedback for their newest changes, making large PRs more manageable.
+
+### How it works
+
+=== "Update Option on Subsequent Commits"
+    ![code_suggestions_update](https://www.qodo.ai/images/pr_agent/inc_update_before.png){width=512}
+
+=== "Generation of Incremental Update"
+    ![code_suggestions_inc_update_result](https://www.qodo.ai/images/pr_agent/inc_update_shown.png){width=512}
+
+___
+
+Whenever new commits are pushed following a recent code suggestions report for this PR, an Update button appears (as seen above).
+
+Once the user clicks on the button:
+
+- The `improve` tool identifies the new changes (the "delta")
+- Provides suggestions on these recent changes
+- Combines these suggestions with the overall PR feedback, prioritizing delta-related comments
+- Marks delta-related comments with a textual indication followed by an asterisk (*) with a link to this page, so they can easily be identified
+
+### Benefits for Developers
+
+- Focus on what matters: See feedback on newest code first
+- Clearer organization: Comments on recent changes are clearly marked
+- Better workflow: Address feedback more systematically, starting with recent changes
+
+

docs/docs/core-abilities/index.md

@@ -2,12 +2,16 @@
 
 Qodo Merge utilizes a variety of core abilities to provide a comprehensive and efficient code review experience. These abilities include:
 
+- [Auto approval](https://qodo-merge-docs.qodo.ai/core-abilities/auto_approval/)
 - [Auto best practices](https://qodo-merge-docs.qodo.ai/core-abilities/auto_best_practices/)
-- [Code validation](https://qodo-merge-docs.qodo.ai/core-abilities/code_validation/)
-- [Compression strategy](https://qodo-merge-docs.qodo.ai/core-abilities/compression_strategy/)
+- [Chat on code suggestions](https://qodo-merge-docs.qodo.ai/core-abilities/chat_on_code_suggestions/)
+- [Chrome extension](https://qodo-merge-docs.qodo.ai/chrome-extension/)
+- [Code validation](https://qodo-merge-docs.qodo.ai/core-abilities/code_validation/) <!-- - [Compression strategy](https://qodo-merge-docs.qodo.ai/core-abilities/compression_strategy/) -->
 - [Dynamic context](https://qodo-merge-docs.qodo.ai/core-abilities/dynamic_context/)
 - [Fetching ticket context](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/)
+- [High-level Suggestions](https://qodo-merge-docs.qodo.ai/core-abilities/high_level_suggestions/)
 - [Impact evaluation](https://qodo-merge-docs.qodo.ai/core-abilities/impact_evaluation/)
+- [Incremental Update](https://qodo-merge-docs.qodo.ai/core-abilities/incremental_update/)
 - [Interactivity](https://qodo-merge-docs.qodo.ai/core-abilities/interactivity/)
 - [Local and global metadata](https://qodo-merge-docs.qodo.ai/core-abilities/metadata/)
 - [RAG context enrichment](https://qodo-merge-docs.qodo.ai/core-abilities/rag_context_enrichment/)

docs/docs/core-abilities/interactivity.md

@@ -1,4 +1,4 @@
-# Interactivity
+# Interactivity 💎
 
 `Supported Git Platforms: GitHub, GitLab`
 

docs/docs/core-abilities/metadata.md

@@ -1,4 +1,6 @@
-## Local and global metadata injection with multi-stage analysis
+# Local and global metadata injection with multi-stage analysis
+
+`Supported Git Platforms: GitHub, GitLab, Bitbucket`
 
 1\.
 Qodo Merge initially retrieves for each PR the following data:

docs/docs/core-abilities/rag_context_enrichment.md

@@ -1,6 +1,6 @@
 # RAG Context Enrichment 💎
 
-`Supported Git Platforms: GitHub, Bitbucket Data Center`
+`Supported Git Platforms: GitHub, GitLab, Bitbucket, Bitbucket Data Center`
 
 !!! info "Prerequisites"
     - RAG is available only for Qodo enterprise plan users, with single tenant or on-premises setup.
@@ -27,7 +27,7 @@ In order to enable the RAG feature, add the following lines to your configuratio
 enable_rag=true
 ```
 
-!!! example "RAG Arguments Options"
+???+ example "RAG Arguments Options"
 
     <table>
       <tr>
@@ -44,11 +44,18 @@ enable_rag=true
 
 RAG capability is exclusively available in the following tools:
 
-=== "`/review`"
-    The [`/review`](https://qodo-merge-docs.qodo.ai/tools/review/) tool offers the _Focus area from RAG data_ which contains feedback based on the RAG references analysis.
-    The complete list of references found relevant to the PR will be shown in the _References_ section, helping developers understand the broader context by exploring the provided references.
+=== "`/ask`"
+    The [`/ask`](https://qodo-merge-docs.qodo.ai/tools/ask/) tool can access broader repository context through the RAG feature when answering questions that go beyond the PR scope alone.
+    The _References_ section displays the additional repository content consulted to formulate the answer.
 
-    ![RAGed review tool](https://codium.ai/images/pr_agent/rag_review.png){width=640}
+    ![RAGed ask tool](https://codium.ai/images/pr_agent/rag_ask.png){width=640}
+
+
+=== "`/compliance`"
+    The [`/compliance`](https://qodo-merge-docs.qodo.ai/tools/compliance/) tool offers the _Codebase Code Duplication Compliance_ section which contains feedback based on the RAG references.
+    This section highlights possible code duplication issues in the PR, providing developers with insights into potential code quality concerns.
+
+    ![RAGed compliance tool](https://codium.ai/images/pr_agent/rag_compliance.png){width=640}
 
 === "`/implement`"
     The [`/implement`](https://qodo-merge-docs.qodo.ai/tools/implement/) tool utilizes the RAG feature to provide comprehensive context of the repository codebase, allowing it to generate more refined code output.
@@ -56,11 +63,11 @@ RAG capability is exclusively available in the following tools:
 
     ![RAGed implement tool](https://codium.ai/images/pr_agent/rag_implement.png){width=640}
 
-=== "`/ask`"
-    The [`/ask`](https://qodo-merge-docs.qodo.ai/tools/ask/) tool can access broader repository context through the RAG feature when answering questions that go beyond the PR scope alone.
-    The _References_ section displays the additional repository content consulted to formulate the answer.
+=== "`/review`"
+    The [`/review`](https://qodo-merge-docs.qodo.ai/tools/review/) tool offers the _Focus area from RAG data_ which contains feedback based on the RAG references analysis.
+    The complete list of references found relevant to the PR will be shown in the _References_ section, helping developers understand the broader context by exploring the provided references.
 
-    ![RAGed ask tool](https://codium.ai/images/pr_agent/rag_ask.png){width=640}
+    ![RAGed review tool](https://codium.ai/images/pr_agent/rag_review.png){width=640}
 
 ## Limitations
 

docs/docs/core-abilities/self_reflection.md

@@ -1,4 +1,4 @@
-## TL;DR
+`Supported Git Platforms: GitHub, GitLab, Bitbucket`
 
 Qodo Merge implements a **self-reflection** process where the AI model reflects, scores, and re-ranks its own suggestions, eliminating irrelevant or incorrect ones.
 This approach improves the quality and relevance of suggestions, saving users time and enhancing their experience.

docs/docs/core-abilities/static_code_analysis.md

@@ -1,11 +1,14 @@
-## Overview - Static Code Analysis 💎
+# Static Code Analysis 💎
+
+` Supported Git Platforms: GitHub, GitLab, Bitbucket`
+
 
 By combining static code analysis with LLM capabilities, Qodo Merge can provide a comprehensive analysis of the PR code changes on a component level.
 
 It scans the PR code changes, finds all the code components (methods, functions, classes) that changed, and enables to interactively generate tests, docs, code suggestions and similar code search for each component.
 
 !!! note "Language that are currently supported:"
-    Python, Java, C++, JavaScript, TypeScript, C#.
+    Python, Java, C++, JavaScript, TypeScript, C#, Go, Kotlin
 
 ## Capabilities
 

docs/docs/faq/index.md

@@ -26,7 +26,7 @@ ___
 
     #### Answer:<span style="display:none;">2</span>
 
-    - Modern AI models, like Claude Sonnet and GPT-4, are improving rapidly but remain imperfect. Users should critically evaluate all suggestions rather than accepting them automatically.
+    - Modern AI models, like Claude Sonnet and GPT-5, are improving rapidly but remain imperfect. Users should critically evaluate all suggestions rather than accepting them automatically.
     - AI errors are rare, but possible. A main value from reviewing the code suggestions lies in their high probability of catching **mistakes or bugs made by the PR author**. We believe it's worth spending 30-60 seconds reviewing suggestions, even if some aren't relevant, as this practice can enhance code quality and prevent bugs in production.
 
 
@@ -66,7 +66,7 @@ ___
 ___
 
 ??? note "Q: Can Qodo Merge review draft/offline PRs?"
-    #### Answer:<span style="display:none;">5</span>
+    #### Answer:<span style="display:none;">6</span>
 
     Yes. While Qodo Merge won't automatically review draft PRs, you can still get feedback by manually requesting it through [online commenting](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#online-usage).
 
@@ -74,7 +74,7 @@ ___
 ___
 
 ??? note "Q: Can the 'Review effort' feedback be calibrated or customized?"
-    #### Answer:<span style="display:none;">5</span>
+    #### Answer:<span style="display:none;">7</span>
 
     Yes, you can customize review effort estimates using the `extra_instructions` configuration option (see [documentation](https://qodo-merge-docs.qodo.ai/tools/review/#configuration-options)).
     
@@ -88,3 +88,35 @@ ___
     Note: The effort levels (1-5) are primarily meant for _comparative_ purposes, helping teams prioritize reviewing smaller PRs first. The actual review duration may vary, as the focus is on providing consistent relative effort estimates.
 
 ___
+
+??? note "Q: How to reduce the noise generated by Qodo Merge?"
+    #### Answer:<span style="display:none;">3</span>
+
+    The default configuration of Qodo Merge is designed to balance helpful feedback with noise reduction. It reduces noise through several approaches:
+
+    - Auto-feedback uses three highly structured tools (`/describe`, `/review`, and `/improve`), designed to be accessible at a glance without creating large visual overload
+    - Suggestions are presented in a table format rather than as committable comments, which are far noisier
+    - The 'File Walkthrough' section is folded by default, as it tends to be verbose
+    - Intermediate comments are avoided when creating new PRs (like "Qodo Merge is now reviewing your PR..."), which would generate email noise
+    
+    From our experience, especially in large teams or organizations, complaints about "noise" sometimes stem from the following issues:
+
+    - **Feedback from multiple bots**: When multiple bots provide feedback on the same PR, it creates confusion and noise. We recommend using Qodo Merge as the primary feedback tool to streamline the process and reduce redundancy.
+    - **Getting familiar with the tool**: Unlike many tools that provide feedback only on demand, Qodo Merge automatically analyzes and suggests improvements for every code change. While this proactive approach can feel intimidating at first, it's designed to continuously enhance code quality and catch bugs and problems when they occur. We recommend reviewing [this guide](https://qodo-merge-docs.qodo.ai/tools/improve/#understanding-ai-code-suggestions) to help align expectations and maximize the value of Qodo Merge's auto-feedback.
+
+    Therefore, at a global configuration level, we recommend using the default configuration, which is designed to reduce noise while providing valuable feedback.
+    
+    However, if you still find the feedback too noisy, you can adjust the configuration. Since each user and team has different needs, it's definitely possible - and even recommended - to adjust configurations for specific repos as needed.
+    Ways to adjust the configuration for noise reduction include for example:
+
+    - [Score thresholds for code suggestions](https://qodo-merge-docs.qodo.ai/tools/improve/#configuration-options)
+    - [Utilizing the `extra_instructions` field for more tailored feedback](https://qodo-merge-docs.qodo.ai/tools/improve/#extra-instructions)
+    - [Controlling which tools run automatically](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#github-app-automatic-tools-when-a-new-pr-is-opened)
+
+    Note that some users may prefer the opposite - more thorough and detailed feedback. Qodo Merge is designed to be flexible and customizable, allowing you to tailor the feedback to your team's specific needs and preferences.
+    Examples of ways to increase feedback include:
+
+    - [`Exhaustive` code suggestions](https://qodo-merge-docs.qodo.ai/tools/improve/#controlling-suggestions-depth)
+    - [Dual-publishing mode](https://qodo-merge-docs.qodo.ai/tools/improve/#dual-publishing-mode)
+    - [Interactive usage](https://qodo-merge-docs.qodo.ai/core-abilities/interactivity/)
+___

docs/docs/index.md

@@ -9,7 +9,7 @@ Qodo Merge is a hosted version of PR-Agent, designed for companies and teams tha
 
 - See the [Tools Guide](./tools/index.md) for a detailed description of the different tools.
 
-- See the [Video Tutorials](https://www.youtube.com/playlist?list=PLRTpyDOSgbwFMA_VBeKMnPLaaZKwjGBFT) for practical demonstrations on how to use the tools.
+- See the video tutorials [[1](https://www.youtube.com/playlist?list=PLRTpyDOSgbwFMA_VBeKMnPLaaZKwjGBFT), [2](https://www.youtube.com/watch?v=7-yJLd7zu40)] for practical demonstrations on how to use the tools.
 
 ## Docs Smart Search
 
@@ -24,49 +24,55 @@ To search the documentation site using natural language:
 
 ## Features
 
-PR-Agent and Qodo Merge offers extensive pull request functionalities across various git providers:
+PR-Agent and Qodo Merge offer comprehensive pull request functionalities integrated with various git providers:
 
-|       |                                                                                                         | GitHub | GitLab | Bitbucket | Azure DevOps |
-| ----- | ------------------------------------------------------------------------------------------------------- |:------:|:------:|:---------:|:------------:|
-| TOOLS | [Review](https://qodo-merge-docs.qodo.ai/tools/review/)                                                 |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Describe](https://qodo-merge-docs.qodo.ai/tools/describe/)                                             |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Improve](https://qodo-merge-docs.qodo.ai/tools/improve/)                                               |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Ask](https://qodo-merge-docs.qodo.ai/tools/ask/)                                                       |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | ⮑ [Ask on code lines](https://qodo-merge-docs.qodo.ai/tools/ask/#ask-lines)                             |   ✅   |   ✅   |           |              |
-|       | [Update CHANGELOG](https://qodo-merge-docs.qodo.ai/tools/update_changelog/)                             |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Help Docs](https://qodo-merge-docs.qodo.ai/tools/help_docs/?h=auto#auto-approval)                      |   ✅   |   ✅   |    ✅     |              |
-|       | [Ticket Context](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/) 💎            |   ✅   |   ✅   |    ✅     |              |
-|       | [Utilizing Best Practices](https://qodo-merge-docs.qodo.ai/tools/improve/#best-practices) 💎            |   ✅   |   ✅   |    ✅     |              |
-|       | [PR Chat](https://qodo-merge-docs.qodo.ai/chrome-extension/features/#pr-chat) 💎                        |   ✅   |        |           |              |
-|       | [Suggestion Tracking](https://qodo-merge-docs.qodo.ai/tools/improve/#suggestion-tracking) 💎            |   ✅   |   ✅   |           |              |
-|       | [CI Feedback](https://qodo-merge-docs.qodo.ai/tools/ci_feedback/) 💎                                    |   ✅   |        |           |              |
-|       | [PR Documentation](https://qodo-merge-docs.qodo.ai/tools/documentation/) 💎                             |   ✅   |   ✅   |           |              |
-|       | [Custom Labels](https://qodo-merge-docs.qodo.ai/tools/custom_labels/) 💎                                |   ✅   |   ✅   |           |              |
-|       | [Analyze](https://qodo-merge-docs.qodo.ai/tools/analyze/) 💎                                            |   ✅   |   ✅   |           |              |
-|       | [Similar Code](https://qodo-merge-docs.qodo.ai/tools/similar_code/) 💎                                  |   ✅   |        |           |              |
-|       | [Custom Prompt](https://qodo-merge-docs.qodo.ai/tools/custom_prompt/) 💎                                |   ✅   |   ✅   |    ✅     |              |
-|       | [Test](https://qodo-merge-docs.qodo.ai/tools/test/) 💎                                                  |   ✅   |   ✅   |           |              |
-|       | [Implement](https://qodo-merge-docs.qodo.ai/tools/implement/) 💎                                        |   ✅   |   ✅   |    ✅     |              |
-|       | [Scan Repo Discussions](https://qodo-merge-docs.qodo.ai/tools/scan_repo_discussions/) 💎                |   ✅   |        |           |              |
-|       | [Auto-Approve](https://qodo-merge-docs.qodo.ai/tools/improve/?h=auto#auto-approval) 💎                  |   ✅   |   ✅   |    ✅     |              |
-|       |                                                                                                         |        |        |           |              |
-| USAGE | [CLI](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#local-repo-cli)                |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [App / webhook](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#github-app)          |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Tagging bot](https://github.com/Codium-ai/pr-agent#try-it-now)                                         |   ✅   |        |           |              |
-|       | [Actions](https://qodo-merge-docs.qodo.ai/installation/github/#run-as-a-github-action)                  |   ✅   |   ✅   |    ✅     |      ✅      |
-|       |                                                                                                         |        |        |           |              |
-| CORE  | [PR compression](https://qodo-merge-docs.qodo.ai/core-abilities/compression_strategy/)                  |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | Adaptive and token-aware file patch fitting                                                             |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Multiple models support](https://qodo-merge-docs.qodo.ai/usage-guide/changing_a_model/)                |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Local and global metadata](https://qodo-merge-docs.qodo.ai/core-abilities/metadata/)                   |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Dynamic context](https://qodo-merge-docs.qodo.ai/core-abilities/dynamic_context/)                      |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Self reflection](https://qodo-merge-docs.qodo.ai/core-abilities/self_reflection/)                      |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Static code analysis](https://qodo-merge-docs.qodo.ai/core-abilities/static_code_analysis/) 💎         |   ✅   |   ✅   |           |              |
-|       | [Global and wiki configurations](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/) 💎 |   ✅   |   ✅   |    ✅     |              |
-|       | [PR interactive actions](https://www.qodo.ai/images/pr_agent/pr-actions.mp4) 💎                         |   ✅   |   ✅   |           |              |
-|       | [Impact Evaluation](https://qodo-merge-docs.qodo.ai/core-abilities/impact_evaluation/) 💎               |   ✅   |   ✅   |           |              | 
-|       | [Code Validation 💎](https://qodo-merge-docs.qodo.ai/core-abilities/code_validation/)                   |   ✅   |   ✅   |    ✅     |      ✅      |
-|       | [Auto Best Practices 💎](https://qodo-merge-docs.qodo.ai/core-abilities/auto_best_practices/)                     |   ✅   |      |         |            |
+|       |                                                                                                                     | GitHub | GitLab | Bitbucket | Azure DevOps | Gitea |
+| ----- |---------------------------------------------------------------------------------------------------------------------|:------:|:------:|:---------:|:------------:|:-----:|
+| [TOOLS](https://qodo-merge-docs.qodo.ai/tools/) | [Describe](https://qodo-merge-docs.qodo.ai/tools/describe/)                                                         |   ✅   |   ✅   |    ✅     |      ✅       |  ✅   |
+|       | [Review](https://qodo-merge-docs.qodo.ai/tools/review/)                                                             |   ✅   |   ✅   |    ✅     |      ✅       |  ✅   |
+|       | [Improve](https://qodo-merge-docs.qodo.ai/tools/improve/)                                                           |   ✅   |   ✅   |    ✅     |      ✅       |  ✅   |
+|       | [Ask](https://qodo-merge-docs.qodo.ai/tools/ask/)                                                                   |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | ⮑ [Ask on code lines](https://qodo-merge-docs.qodo.ai/tools/ask/#ask-lines)                                         |   ✅   |   ✅   |           |              |       |
+|       | [Help Docs](https://qodo-merge-docs.qodo.ai/tools/help_docs/?h=auto#auto-approval)                                  |   ✅   |   ✅   |    ✅     |              |       |
+|       | [Update CHANGELOG](https://qodo-merge-docs.qodo.ai/tools/update_changelog/)                                         |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | [Add Documentation](https://qodo-merge-docs.qodo.ai/tools/documentation/) 💎                                        |   ✅   |   ✅   |           |              |       |
+|       | [Analyze](https://qodo-merge-docs.qodo.ai/tools/analyze/) 💎                                                        |   ✅   |   ✅   |           |              |       |
+|       | [Auto-Approve](https://qodo-merge-docs.qodo.ai/tools/improve/?h=auto#auto-approval) 💎                              |   ✅   |   ✅   |    ✅     |              |       |
+|       | [CI Feedback](https://qodo-merge-docs.qodo.ai/tools/ci_feedback/) 💎                                                |   ✅   |        |           |              |       |
+|       | [Compliance](https://qodo-merge-docs.qodo.ai/tools/compliance/) 💎                                                  |   ✅   |   ✅   |    ✅     |              |       |
+|       | [Custom Prompt](https://qodo-merge-docs.qodo.ai/tools/custom_prompt/) 💎                                            |   ✅   |   ✅   |    ✅     |              |       |
+|       | [Generate Custom Labels](https://qodo-merge-docs.qodo.ai/tools/custom_labels/) 💎                                   |   ✅   |   ✅   |           |              |       |
+|       | [Generate Tests](https://qodo-merge-docs.qodo.ai/tools/test/) 💎                                                    |   ✅   |   ✅   |           |              |       |
+|       | [Implement](https://qodo-merge-docs.qodo.ai/tools/implement/) 💎                                                    |   ✅   |   ✅   |    ✅     |              |       |
+|       | [PR Chat](https://qodo-merge-docs.qodo.ai/chrome-extension/features/#pr-chat) 💎                                    |   ✅   |        |           |              |       |
+|       | [PR to Ticket](https://qodo-merge-docs.qodo.ai/tools/pr_to_ticket/) 💎                                              |   ✅   |   ✅   |    ✅     |              |       |
+|       | [Scan Repo Discussions](https://qodo-merge-docs.qodo.ai/tools/scan_repo_discussions/) 💎                            |   ✅   |        |           |              |       |
+|       | [Similar Code](https://qodo-merge-docs.qodo.ai/tools/similar_code/) 💎                                              |   ✅   |        |           |              |       |
+|       | [Suggestion Tracking](https://qodo-merge-docs.qodo.ai/tools/improve/#suggestion-tracking) 💎                        |   ✅   |   ✅   |           |              |       |
+|       | [Utilizing Best Practices](https://qodo-merge-docs.qodo.ai/tools/improve/#best-practices) 💎                        |   ✅   |   ✅   |    ✅     |              |       |
+|       |                                                                                                                     |        |        |           |              |       |
+| [USAGE](https://qodo-merge-docs.qodo.ai/usage-guide/) | [CLI](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#local-repo-cli)                            |   ✅   |   ✅   |    ✅     |      ✅       |  ✅   |
+|       | [App / webhook](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#github-app)                      |   ✅   |   ✅   |    ✅     |      ✅       |  ✅   |
+|       | [Tagging bot](https://github.com/Codium-ai/pr-agent#try-it-now)                                                     |   ✅   |        |           |              |       |
+|       | [Actions](https://qodo-merge-docs.qodo.ai/installation/github/#run-as-a-github-action)                              |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       |                                                                                                                     |        |        |           |              |       |
+| [CORE](https://qodo-merge-docs.qodo.ai/core-abilities/)  | [Adaptive and token-aware file patch fitting](https://qodo-merge-docs.qodo.ai/core-abilities/compression_strategy/) |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | [Auto Best Practices 💎](https://qodo-merge-docs.qodo.ai/core-abilities/auto_best_practices/)                       |   ✅   |        |           |              |       |
+|       | [Chat on code suggestions](https://qodo-merge-docs.qodo.ai/core-abilities/chat_on_code_suggestions/)                |   ✅   |  ✅   |           |              |       |
+|       | [Code Validation 💎](https://qodo-merge-docs.qodo.ai/core-abilities/code_validation/)                               |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | [Dynamic context](https://qodo-merge-docs.qodo.ai/core-abilities/dynamic_context/)                                  |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | [Fetching ticket context](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/)                  |   ✅   |  ✅   |    ✅     |              |       |
+|       | [Global and wiki configurations](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/) 💎             |   ✅   |   ✅   |    ✅     |              |       |
+|       | [Impact Evaluation](https://qodo-merge-docs.qodo.ai/core-abilities/impact_evaluation/) 💎                           |   ✅   |   ✅   |           |              |       |
+|       | [Incremental Update 💎](https://qodo-merge-docs.qodo.ai/core-abilities/incremental_update/)                         |   ✅   |        |           |              |       |
+|       | [Interactivity](https://qodo-merge-docs.qodo.ai/core-abilities/interactivity/)                                      |   ✅   |  ✅   |           |              |       |
+|       | [Local and global metadata](https://qodo-merge-docs.qodo.ai/core-abilities/metadata/)                               |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | [Multiple models support](https://qodo-merge-docs.qodo.ai/usage-guide/changing_a_model/)                            |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | [PR compression](https://qodo-merge-docs.qodo.ai/core-abilities/compression_strategy/)                              |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | [PR interactive actions](https://www.qodo.ai/images/pr_agent/pr-actions.mp4) 💎                                     |   ✅   |   ✅   |           |              |       |
+|       | [RAG context enrichment](https://qodo-merge-docs.qodo.ai/core-abilities/rag_context_enrichment/)                    |   ✅   |        |    ✅     |              |       |
+|       | [Self reflection](https://qodo-merge-docs.qodo.ai/core-abilities/self_reflection/)                                  |   ✅   |   ✅   |    ✅     |      ✅       |       |
+|       | [Static code analysis](https://qodo-merge-docs.qodo.ai/core-abilities/static_code_analysis/) 💎                     |   ✅   |   ✅   |           |              |       |
 !!! note "💎 means Qodo Merge only"
       All along the documentation, 💎 marks a feature available only in [Qodo Merge](https://www.codium.ai/pricing/){:target="_blank"}, and not in the open-source version.
 

docs/docs/installation/azure.md

@@ -1,19 +1,23 @@
 ## Azure DevOps Pipeline
 
-You can use a pre-built Action Docker image to run PR-Agent as an Azure devops pipeline.
-add the following file to your repository under `azure-pipelines.yml`:
+You can use a pre-built Action Docker image to run PR-Agent as an Azure DevOps pipeline.
+Add the following file to your repository under `azure-pipelines.yml`:
 
 ```yaml
 # Opt out of CI triggers
 trigger: none
 
 # Configure PR trigger
-pr:
-  branches:
-    include:
-    - '*'
-  autoCancel: true
-  drafts: false
+# pr:
+#   branches:
+#     include:
+#     - '*'
+#   autoCancel: true
+#   drafts: false
+
+# NOTE for Azure Repos Git:
+# Azure Repos does not honor YAML pr: triggers. Configure Build Validation
+# via Branch Policies instead (see note below). You can safely omit pr:.
 
 stages:
 - stage: pr_agent
@@ -61,6 +65,19 @@ Make sure to give pipeline permissions to the `pr_agent` variable group.
 
 > Note that Azure Pipelines lacks support for triggering workflows from PR comments. If you find a viable solution, please contribute it to our [issue tracker](https://github.com/Codium-ai/pr-agent/issues)
 
+### Azure Repos Git PR triggers and Build Validation
+
+Azure Repos Git does not use YAML `pr:` triggers for pipelines. Instead, configure Build Validation on the target branch to run the PR Agent pipeline for pull requests:
+
+1. Go to Project Settings → Repositories → Branches.
+2. Select the target branch and open Branch Policies.
+3. Under Build Validation, add a policy:
+   - Select the PR Agent pipeline (the `azure-pipelines.yml` above).
+   - Set it as Required.
+4. Remove the `pr:` section from your YAML (not needed for Azure Repos Git).
+
+This distinction applies specifically to Azure Repos Git. Other providers like GitHub and Bitbucket Cloud can use YAML-based PR triggers.
+
 ## Azure DevOps from CLI
 
 To use Azure DevOps provider use the following settings in configuration.toml:
@@ -71,7 +88,7 @@ git_provider="azure"
 ```
 
 Azure DevOps provider supports [PAT token](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows) or [DefaultAzureCredential](https://learn.microsoft.com/en-us/azure/developer/python/sdk/authentication-overview#authentication-in-server-environments) authentication.
-PAT is faster to create, but has build in expiration date, and will use the user identity for API calls.
+PAT is faster to create, but has built-in expiration date, and will use the user identity for API calls.
 Using DefaultAzureCredential you can use managed identity or Service principle, which are more secure and will create separate ADO user identity (via AAD) to the agent.
 
 If PAT was chosen, you can assign the value in .secrets.toml.

docs/docs/installation/bitbucket.md

@@ -39,6 +39,13 @@ Generate the token and add it to .secret.toml under `bitbucket_server` section
 bearer_token = "<your key>"
 ```
 
+Don't forget to also set the URL of your Bitbucket Server instance (either in `.secret.toml` or in `configuration.toml`):
+
+```toml
+[bitbucket_server]
+url = "<full URL to your Bitbucket instance, e.g.: https://git.bitbucket.com>"
+```
+
 ### Run it as CLI
 
 Modify `configuration.toml`:
@@ -47,10 +54,12 @@ Modify `configuration.toml`:
 git_provider="bitbucket_server"
 ```
 
+
+
 and pass the Pull request URL:
 
 ```shell
-python cli.py --pr_url https://git.onpreminstanceofbitbucket.com/projects/PROJECT/repos/REPO/pull-requests/1 review
+python cli.py --pr_url https://git.on-prem-instance-of-bitbucket.com/projects/PROJECT/repos/REPO/pull-requests/1 review
 ```
 
 ### Run it as service
@@ -63,6 +72,6 @@ docker push codiumai/pr-agent:bitbucket_server_webhook  # Push to your Docker re
 ```
 
 Navigate to `Projects` or `Repositories`, `Settings`, `Webhooks`, `Create Webhook`.
-Fill the name and URL, Authentication None select the Pull Request Opened checkbox to receive that event as webhook.
+Fill in the name and URL. For Authentication, select 'None'. Select the 'Pull Request Opened' checkbox to receive that event as a webhook.
 
 The URL should end with `/webhook`, for example: https://domain.com/webhook

docs/docs/installation/gitea.md

@@ -0,0 +1,47 @@
+## Run a Gitea webhook server
+
+1. In Gitea create a new user and give it "Reporter" role ("Developer" if using Pro version of the agent) for the intended group or project.
+
+2. For the user from step 1. generate a `personal_access_token` with `api` access.
+
+3. Generate a random secret for your app, and save it for later (`webhook_secret`). For example, you can use:
+
+```bash
+WEBHOOK_SECRET=$(python -c "import secrets; print(secrets.token_hex(10))")
+```
+
+4. Clone this repository:
+
+```bash
+git clone https://github.com/qodo-ai/pr-agent.git
+```
+
+5. Prepare variables and secrets. Skip this step if you plan on setting these as environment variables when running the agent:
+    - In the configuration file/variables:
+        - Set `config.git_provider` to "gitea"
+    - In the secrets file/variables:
+        - Set your AI model key in the respective section
+        - In the [Gitea] section, set `personal_access_token` (with token from step 2) and `webhook_secret` (with secret from step 3)
+
+6. Build a Docker image for the app and optionally push it to a Docker repository. We'll use Dockerhub as an example:
+
+```bash
+docker build -f /docker/Dockerfile -t pr-agent:gitea_app --target gitea_app .
+docker push codiumai/pr-agent:gitea_webhook  # Push to your Docker repository
+```
+
+7. Set the environmental variables, the method depends on your docker runtime. Skip this step if you included your secrets/configuration directly in the Docker image.
+
+```bash
+CONFIG__GIT_PROVIDER=gitea
+GITEA__PERSONAL_ACCESS_TOKEN=<personal_access_token>
+GITEA__WEBHOOK_SECRET=<webhook_secret>
+GITEA__URL=https://gitea.com # Or self host
+OPENAI__KEY=<your_openai_api_key>
+GITEA__SKIP_SSL_VERIFICATION=false # or true
+GITEA__SSL_CA_CERT=/path/to/cacert.pem
+```
+
+8. Create a webhook in your Gitea project. Set the URL to `http[s]://<PR_AGENT_HOSTNAME>/api/v1/gitea_webhooks`, the secret token to the generated secret from step 3, and enable the triggers `push`, `comments` and `merge request events`.
+
+9. Test your installation by opening a merge request or commenting on a merge request using one of PR Agent's commands.

docs/docs/installation/github.md

@@ -1,3 +1,5 @@
+In this page we will cover how to install and run PR-Agent as a GitHub Action or GitHub App, and how to configure it for your needs.
+
 ## Run as a GitHub Action
 
 You can use our pre-built Github Action Docker image to run PR-Agent as a Github Action.
@@ -51,6 +53,437 @@ When you open your next PR, you should see a comment from `github-actions` bot w
 
 See detailed usage instructions in the [USAGE GUIDE](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#github-action)
 
+### Configuration Examples
+
+This section provides detailed, step-by-step examples for configuring PR-Agent with different models and advanced options in GitHub Actions.
+
+#### Quick Start Examples
+
+##### Basic Setup (OpenAI Default)
+
+Copy this minimal workflow to get started with the default OpenAI models:
+
+```yaml
+name: PR Agent
+on:
+  pull_request:
+    types: [opened, reopened, ready_for_review]
+  issue_comment:
+jobs:
+  pr_agent_job:
+    if: ${{ github.event.sender.type != 'Bot' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+      contents: write
+    steps:
+      - name: PR Agent action step
+        uses: qodo-ai/pr-agent@main
+        env:
+          OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+```
+
+##### Gemini Setup
+
+Ready-to-use workflow for Gemini models:
+
+```yaml
+name: PR Agent (Gemini)
+on:
+  pull_request:
+    types: [opened, reopened, ready_for_review]
+  issue_comment:
+jobs:
+  pr_agent_job:
+    if: ${{ github.event.sender.type != 'Bot' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+      contents: write
+    steps:
+      - name: PR Agent action step
+        uses: qodo-ai/pr-agent@main
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          config.model: "gemini/gemini-1.5-flash"
+          config.fallback_models: '["gemini/gemini-1.5-flash"]'
+          GOOGLE_AI_STUDIO.GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
+          github_action_config.auto_review: "true"
+          github_action_config.auto_describe: "true"
+          github_action_config.auto_improve: "true"
+```
+
+#### Claude Setup
+
+Ready-to-use workflow for Claude models:
+
+```yaml
+name: PR Agent (Claude)
+on:
+  pull_request:
+    types: [opened, reopened, ready_for_review]
+  issue_comment:
+jobs:
+  pr_agent_job:
+    if: ${{ github.event.sender.type != 'Bot' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+      contents: write
+    steps:
+      - name: PR Agent action step
+        uses: qodo-ai/pr-agent@main
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          config.model: "anthropic/claude-3-opus-20240229"
+          config.fallback_models: '["anthropic/claude-3-haiku-20240307"]'
+          ANTHROPIC.KEY: ${{ secrets.ANTHROPIC_KEY }}
+          github_action_config.auto_review: "true"
+          github_action_config.auto_describe: "true"
+          github_action_config.auto_improve: "true"
+```
+
+#### Basic Configuration with Tool Controls
+
+Start with this enhanced workflow that includes tool configuration:
+
+```yaml
+on:
+  pull_request:
+    types: [opened, reopened, ready_for_review]
+  issue_comment:
+jobs:
+  pr_agent_job:
+    if: ${{ github.event.sender.type != 'Bot' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+      contents: write
+    name: Run pr agent on every pull request, respond to user comments
+    steps:
+      - name: PR Agent action step
+        id: pragent
+        uses: qodo-ai/pr-agent@main
+        env:
+          OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # Enable/disable automatic tools
+          github_action_config.auto_review: "true"
+          github_action_config.auto_describe: "true"
+          github_action_config.auto_improve: "true"
+          # Configure which PR events trigger the action
+          github_action_config.pr_actions: '["opened", "reopened", "ready_for_review", "review_requested"]'
+```
+
+#### Switching Models
+
+##### Using Gemini (Google AI Studio)
+
+To use Gemini models instead of the default OpenAI models:
+
+```yaml
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Set the model to Gemini
+        config.model: "gemini/gemini-1.5-flash"
+        config.fallback_models: '["gemini/gemini-1.5-flash"]'
+        # Add your Gemini API key
+        GOOGLE_AI_STUDIO.GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
+        # Tool configuration
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "true"
+```
+
+**Required Secrets:**
+
+- Add `GEMINI_API_KEY` to your repository secrets (get it from [Google AI Studio](https://aistudio.google.com/))
+
+**Note:** When using non-OpenAI models like Gemini, you don't need to set `OPENAI_KEY` - only the model-specific API key is required.
+
+##### Using Claude (Anthropic)
+
+To use Claude models:
+
+```yaml
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Set the model to Claude
+        config.model: "anthropic/claude-3-opus-20240229"
+        config.fallback_models: '["anthropic/claude-3-haiku-20240307"]'
+        # Add your Anthropic API key
+        ANTHROPIC.KEY: ${{ secrets.ANTHROPIC_KEY }}
+        # Tool configuration
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "true"
+```
+
+**Required Secrets:**
+
+- Add `ANTHROPIC_KEY` to your repository secrets (get it from [Anthropic Console](https://console.anthropic.com/))
+
+**Note:** When using non-OpenAI models like Claude, you don't need to set `OPENAI_KEY` - only the model-specific API key is required.
+
+##### Using Azure OpenAI
+
+To use Azure OpenAI services:
+
+```yaml
+      env:
+        OPENAI_KEY: ${{ secrets.AZURE_OPENAI_KEY }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Azure OpenAI configuration
+        OPENAI.API_TYPE: "azure"
+        OPENAI.API_VERSION: "2023-05-15"
+        OPENAI.API_BASE: ${{ secrets.AZURE_OPENAI_ENDPOINT }}
+        OPENAI.DEPLOYMENT_ID: ${{ secrets.AZURE_OPENAI_DEPLOYMENT }}
+        # Set the model to match your Azure deployment
+        config.model: "gpt-4o"
+        config.fallback_models: '["gpt-4o"]'
+        # Tool configuration
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "true"
+```
+
+**Required Secrets:**
+
+- `AZURE_OPENAI_KEY`: Your Azure OpenAI API key
+- `AZURE_OPENAI_ENDPOINT`: Your Azure OpenAI endpoint URL
+- `AZURE_OPENAI_DEPLOYMENT`: Your deployment name
+
+##### Using Local Models (Ollama)
+
+To use local models via Ollama:
+
+```yaml
+      env:
+        OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Set the model to a local Ollama model
+        config.model: "ollama/qwen2.5-coder:32b"
+        config.fallback_models: '["ollama/qwen2.5-coder:32b"]'
+        config.custom_model_max_tokens: "128000"
+        # Ollama configuration
+        OLLAMA.API_BASE: "http://localhost:11434"
+        # Tool configuration
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "true"
+```
+
+**Note:** For local models, you'll need to use a self-hosted runner with Ollama installed, as GitHub Actions hosted runners cannot access localhost services.
+
+#### Advanced Configuration Options
+
+##### Custom Review Instructions
+
+Add specific instructions for the review process:
+
+```yaml
+      env:
+        OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Custom review instructions
+        pr_reviewer.extra_instructions: "Focus on security vulnerabilities and performance issues. Check for proper error handling."
+        # Tool configuration
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "true"
+```
+
+##### Language-Specific Configuration
+
+Configure for specific programming languages:
+
+```yaml
+      env:
+        OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Language-specific settings
+        pr_reviewer.extra_instructions: "Focus on Python best practices, type hints, and docstrings."
+        pr_code_suggestions.num_code_suggestions: "8"
+        pr_code_suggestions.suggestions_score_threshold: "7"
+        # Tool configuration
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "true"
+```
+
+##### Selective Tool Execution
+
+Run only specific tools automatically:
+
+```yaml
+      env:
+        OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Only run review and describe, skip improve
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "false"
+        # Only trigger on PR open and reopen
+        github_action_config.pr_actions: '["opened", "reopened"]'
+```
+
+#### Using Configuration Files
+
+Instead of setting all options via environment variables, you can use a `.pr_agent.toml` file in your repository root:
+
+1. Create a `.pr_agent.toml` file in your repository root:
+
+```toml
+[config]
+model = "gemini/gemini-1.5-flash"
+fallback_models = ["anthropic/claude-3-opus-20240229"]
+
+[pr_reviewer]
+extra_instructions = "Focus on security issues and code quality."
+
+[pr_code_suggestions]
+num_code_suggestions = 6
+suggestions_score_threshold = 7
+```
+
+2. Use a simpler workflow file:
+
+```yaml
+on:
+  pull_request:
+    types: [opened, reopened, ready_for_review]
+  issue_comment:
+jobs:
+  pr_agent_job:
+    if: ${{ github.event.sender.type != 'Bot' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+      contents: write
+    name: Run pr agent on every pull request, respond to user comments
+    steps:
+      - name: PR Agent action step
+        id: pragent
+        uses: qodo-ai/pr-agent@main
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GOOGLE_AI_STUDIO.GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
+          ANTHROPIC.KEY: ${{ secrets.ANTHROPIC_KEY }}
+          github_action_config.auto_review: "true"
+          github_action_config.auto_describe: "true"
+          github_action_config.auto_improve: "true"
+```
+
+#### Troubleshooting Common Issues
+
+##### Model Not Found Errors
+
+If you get model not found errors:
+
+1. **Check model name format**: Ensure you're using the correct model identifier format (e.g., `gemini/gemini-1.5-flash`, not just `gemini-1.5-flash`)
+
+2. **Verify API keys**: Make sure your API keys are correctly set as repository secrets
+
+3. **Check model availability**: Some models may not be available in all regions or may require specific access
+
+##### Environment Variable Format
+
+Remember these key points about environment variables:
+
+- Use dots (`.`) or double underscores (`__`) to separate sections and keys
+- Boolean values should be strings: `"true"` or `"false"`
+- Arrays should be JSON strings: `'["item1", "item2"]'`
+- Model names are case-sensitive
+
+##### Rate Limiting
+
+If you encounter rate limiting:
+
+```yaml
+      env:
+        OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Add fallback models for better reliability
+        config.fallback_models: '["gpt-4o", "gpt-3.5-turbo"]'
+        # Increase timeout for slower models
+        config.ai_timeout: "300"
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "true"
+```
+
+##### Common Error Messages and Solutions
+
+**Error: "Model not found"**
+- **Solution**: Check the model name format and ensure it matches the exact identifier. See the [Changing a model in PR-Agent](../usage-guide/changing_a_model.md) guide for supported models and their correct identifiers.
+
+**Error: "API key not found"**
+- **Solution**: Verify that your API key is correctly set as a repository secret and the environment variable name matches exactly
+- **Note**: For non-OpenAI models (Gemini, Claude, etc.), you only need the model-specific API key, not `OPENAI_KEY`
+
+**Error: "Rate limit exceeded"**
+- **Solution**: Add fallback models or increase the `config.ai_timeout` value
+
+**Error: "Permission denied"**
+- **Solution**: Ensure your workflow has the correct permissions set:
+  ```yaml
+  permissions:
+    issues: write
+    pull-requests: write
+    contents: write
+  ```
+
+**Error: "Invalid JSON format"**
+
+- **Solution**: Check that arrays are properly formatted as JSON strings:
+
+```yaml
+
+Correct:
+config.fallback_models: '["model1", "model2"]'
+Incorrect (interpreted as a YAML list, not a string):
+config.fallback_models: ["model1", "model2"]
+```
+
+##### Debugging Tips
+
+1. **Enable verbose logging**: Add `config.verbosity_level: "2"` to see detailed logs
+2. **Check GitHub Actions logs**: Look at the step output for specific error messages
+3. **Test with minimal configuration**: Start with just the basic setup and add options one by one
+4. **Verify secrets**: Double-check that all required secrets are set in your repository settings
+
+##### Performance Optimization
+
+For better performance with large repositories:
+
+```yaml
+      env:
+        OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        # Optimize for large PRs
+        config.large_patch_policy: "clip"
+        config.max_model_tokens: "32000"
+        config.patch_extra_lines_before: "3"
+        config.patch_extra_lines_after: "1"
+        github_action_config.auto_review: "true"
+        github_action_config.auto_describe: "true"
+        github_action_config.auto_improve: "true"
+```
+
+#### Reference
+
+For more detailed configuration options, see:
+
+- [Changing a model in PR-Agent](../usage-guide/changing_a_model.md)
+- [Configuration options](../usage-guide/configuration_options.md)
+- [Automations and usage](../usage-guide/automations_and_usage.md#github-action)
+
 ### Using a specific release
 
 !!! tip ""
@@ -178,7 +611,9 @@ cp pr_agent/settings/.secrets_template.toml pr_agent/settings/.secrets.toml
 > For more information please check out the [USAGE GUIDE](../usage-guide/automations_and_usage.md#github-app)
 ---
 
-## Deploy as a Lambda Function
+## Additional deployment methods
+
+### Deploy as a Lambda Function
 
 Note that since AWS Lambda env vars cannot have "." in the name, you can replace each "." in an env variable with "__".<br>
 For example: `GITHUB.WEBHOOK_SECRET` --> `GITHUB__WEBHOOK_SECRET`
@@ -187,15 +622,16 @@ For example: `GITHUB.WEBHOOK_SECRET` --> `GITHUB__WEBHOOK_SECRET`
 2. Build a docker image that can be used as a lambda function
 
     ```shell
-    docker buildx build --platform=linux/amd64 . -t codiumai/pr-agent:serverless -f docker/Dockerfile.lambda
+    docker buildx build --platform=linux/amd64 . -t codiumai/pr-agent:github_lambda --target github_lambda -f docker/Dockerfile.lambda
    ```
+   (Note: --target github_lambda is optional as it's the default target)
+
 
 3. Push image to ECR
 
     ```shell
-
- docker tag codiumai/pr-agent:serverless <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:serverless
- docker push <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:serverless
+    docker tag codiumai/pr-agent:github_lambda <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:github_lambda
+    docker push <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:github_lambda
     ```
 
 4. Create a lambda function that uses the uploaded image. Set the lambda timeout to be at least 3m.
@@ -204,9 +640,31 @@ For example: `GITHUB.WEBHOOK_SECRET` --> `GITHUB__WEBHOOK_SECRET`
 7. Go back to steps 8-9 of [Method 5](#run-as-a-github-app) with the function url as your Webhook URL.
     The Webhook URL would look like `https://<LAMBDA_FUNCTION_URL>/api/v1/github_webhooks`
 
+#### Using AWS Secrets Manager
+
+For production Lambda deployments, use AWS Secrets Manager instead of environment variables:
+
+1. Create a secret in AWS Secrets Manager with JSON format like this:
+
+```json
+{
+  "openai.key": "sk-proj-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
+  "github.webhook_secret": "your-webhook-secret-from-step-2",
+  "github.private_key": "-----BEGIN RSA PRIVATE KEY-----\nMIIEpAIBAAKCAQEA...\n-----END RSA PRIVATE KEY-----"
+}
+```
+
+2. Add IAM permission `secretsmanager:GetSecretValue` to your Lambda execution role
+3. Set these environment variables in your Lambda:
+
+```bash
+AWS_SECRETS_MANAGER__SECRET_ARN=arn:aws:secretsmanager:us-east-1:123456789012:secret:pr-agent-secrets-AbCdEf
+CONFIG__SECRET_PROVIDER=aws_secrets_manager
+```
+
 ---
 
-## AWS CodeCommit Setup
+### AWS CodeCommit Setup
 
 Not all features have been added to CodeCommit yet.  As of right now, CodeCommit has been implemented to run the Qodo Merge CLI on the command line, using AWS credentials stored in environment variables.  (More features will be added in the future.)  The following is a set of instructions to have Qodo Merge do a review of your CodeCommit pull request from the command line:
 
@@ -223,7 +681,7 @@ Not all features have been added to CodeCommit yet.  As of right now, CodeCommit
 
 ---
 
-#### AWS CodeCommit IAM Role Example
+##### AWS CodeCommit IAM Role Example
 
 Example IAM permissions to that user to allow access to CodeCommit:
 
@@ -255,7 +713,7 @@ Example IAM permissions to that user to allow access to CodeCommit:
 }
 ```
 
-#### AWS CodeCommit Access Key and Secret
+##### AWS CodeCommit Access Key and Secret
 
 Example setting the Access Key and Secret using environment variables
 
@@ -265,7 +723,7 @@ export AWS_SECRET_ACCESS_KEY="XXXXXXXXXXXXXXXX"
 export AWS_DEFAULT_REGION="us-east-1"
 ```
 
-#### AWS CodeCommit CLI Example
+##### AWS CodeCommit CLI Example
 
 After you set up AWS CodeCommit using the instructions above, here is an example CLI run that tells pr-agent to **review** a given pull request.
 (Replace your specific PYTHONPATH and PR URL in the example)
@@ -274,4 +732,4 @@ After you set up AWS CodeCommit using the instructions above, here is an example
 PYTHONPATH="/PATH/TO/PROJECTS/pr-agent" python pr_agent/cli.py \
   --pr_url https://us-east-1.console.aws.amazon.com/codesuite/codecommit/repositories/MY_REPO_NAME/pull-requests/321 \
   review
-```
+```

docs/docs/installation/gitlab.md

@@ -42,11 +42,14 @@ Note that if your base branches are not protected, don't set the variables as `p
 
 > **Note**: The `$CI_SERVER_FQDN` variable is available starting from GitLab version 16.10. If you're using an earlier version, this variable will not be available. However, you can combine `$CI_SERVER_HOST` and `$CI_SERVER_PORT` to achieve the same result. Please ensure you're using a compatible version or adjust your configuration.
 
+> **Note**: The `gitlab__SSL_VERIFY` environment variable can be used to specify the path to a custom CA certificate bundle for SSL verification. GitLab exposes the `$CI_SERVER_TLS_CA_FILE` variable, which points to the custom CA certificate file configured in your GitLab instance.
+> Alternatively, SSL verification can be disabled entirely by setting `gitlab__SSL_VERIFY=false`, although this is not recommended.
+
 ## Run a GitLab webhook server
 
 1. In GitLab create a new user and give it "Reporter" role ("Developer" if using Pro version of the agent) for the intended group or project.
 
-2. For the user from step 1. generate a `personal_access_token` with `api` access.
+2. For the user from step 1, generate a `personal_access_token` with `api` access.
 
 3. Generate a random secret for your app, and save it for later (`shared_secret`). For example, you can use:
 
@@ -61,12 +64,13 @@ git clone https://github.com/qodo-ai/pr-agent.git
 ```
 
 5. Prepare variables and secrets. Skip this step if you plan on setting these as environment variables when running the agent:
-1. In the configuration file/variables:
-    - Set `config.git_provider` to "gitlab"
+    1. In the configuration file/variables:
+        - Set `config.git_provider` to "gitlab"
 
-2. In the secrets file/variables:
-    - Set your AI model key in the respective section
-    - In the [gitlab] section, set `personal_access_token` (with token from step 2) and `shared_secret` (with secret from step 3)
+    2. In the secrets file/variables:
+        - Set your AI model key in the respective section
+        - In the [gitlab] section, set `personal_access_token` (with token from step 2) and `shared_secret` (with secret from step 3)
+        - **Authentication type**: Set `auth_type` to `"private_token"` for older GitLab versions (e.g., 11.x) or private deployments. Default is `"oauth_token"` for gitlab.com and newer versions.
 
 6. Build a Docker image for the app and optionally push it to a Docker repository. We'll use Dockerhub as an example:
 
@@ -82,9 +86,70 @@ CONFIG__GIT_PROVIDER=gitlab
 GITLAB__PERSONAL_ACCESS_TOKEN=<personal_access_token>
 GITLAB__SHARED_SECRET=<shared_secret>
 GITLAB__URL=https://gitlab.com
+GITLAB__AUTH_TYPE=oauth_token  # Use "private_token" for older GitLab versions
 OPENAI__KEY=<your_openai_api_key>
 ```
 
 8. Create a webhook in your GitLab project. Set the URL to `http[s]://<PR_AGENT_HOSTNAME>/webhook`, the secret token to the generated secret from step 3, and enable the triggers `push`, `comments` and `merge request events`.
 
 9. Test your installation by opening a merge request or commenting on a merge request using one of PR Agent's commands.
+
+## Deploy as a Lambda Function
+
+Note that since AWS Lambda env vars cannot have "." in the name, you can replace each "." in an env variable with "__".<br>
+For example: `GITLAB.PERSONAL_ACCESS_TOKEN` --> `GITLAB__PERSONAL_ACCESS_TOKEN`
+
+1. Follow steps 1-5 from [Run a GitLab webhook server](#run-a-gitlab-webhook-server).
+2. Build a docker image that can be used as a lambda function
+
+    ```shell
+    docker buildx build --platform=linux/amd64 . -t codiumai/pr-agent:gitlab_lambda --target gitlab_lambda -f docker/Dockerfile.lambda
+   ```
+
+3. Push image to ECR
+
+    ```shell
+    docker tag codiumai/pr-agent:gitlab_lambda <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:gitlab_lambda
+    docker push <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:gitlab_lambda
+    ```
+
+4. Create a lambda function that uses the uploaded image. Set the lambda timeout to be at least 3m.
+5. Configure the lambda function to have a Function URL.
+6. In the environment variables of the Lambda function, specify `AZURE_DEVOPS_CACHE_DIR` to a writable location such as /tmp. (see [link](https://github.com/Codium-ai/pr-agent/pull/450#issuecomment-1840242269))
+7. Go back to steps 8-9 of [Run a GitLab webhook server](#run-a-gitlab-webhook-server) with the function URL as your Webhook URL.
+    The Webhook URL would look like `https://<LAMBDA_FUNCTION_URL>/webhook`
+
+### Using AWS Secrets Manager
+
+For production Lambda deployments, use AWS Secrets Manager instead of environment variables:
+
+1. Create individual secrets for each GitLab webhook with this JSON format (e.g., secret name: `project-webhook-secret-001`)
+
+```json
+{
+  "gitlab_token": "glpat-xxxxxxxxxxxxxxxxxxxxxxxx",
+  "token_name": "project-webhook-001"
+}
+```
+
+2. Create a main configuration secret for common settings (e.g., secret name: `pr-agent-main-config`)
+
+```json
+{
+  "openai.key": "sk-proj-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
+}
+```
+
+3. Set these environment variables in your Lambda:
+
+```bash
+CONFIG__SECRET_PROVIDER=aws_secrets_manager
+AWS_SECRETS_MANAGER__SECRET_ARN=arn:aws:secretsmanager:us-east-1:123456789012:secret:pr-agent-main-config-AbCdEf
+```
+
+4. In your GitLab webhook configuration, set the **Secret Token** to the **Secret name** created in step 1:
+   - Example: `project-webhook-secret-001`
+
+**Important**: When using Secrets Manager, GitLab's webhook secret must be the Secrets Manager secret name.
+
+5. Add IAM permission `secretsmanager:GetSecretValue` to your Lambda execution role

docs/docs/installation/index.md

@@ -9,6 +9,7 @@ There are several ways to use self-hosted PR-Agent:
 - [GitLab integration](./gitlab.md)
 - [BitBucket integration](./bitbucket.md)
 - [Azure DevOps integration](./azure.md)
+- [Gitea integration](./gitea.md)
 
 ## Qodo Merge 💎
 

docs/docs/installation/locally.md

@@ -1,7 +1,7 @@
 To run PR-Agent locally, you first need to acquire two keys:
 
 1. An OpenAI key from [here](https://platform.openai.com/api-keys){:target="_blank"}, with access to GPT-4 and o4-mini (or a key for other [language models](https://qodo-merge-docs.qodo.ai/usage-guide/changing_a_model/), if you prefer).
-2. A personal access token from your Git platform (GitHub, GitLab, BitBucket) with repo scope. GitHub token, for example, can be issued from [here](https://github.com/settings/tokens){:target="_blank"}
+2. A personal access token from your Git platform (GitHub, GitLab, BitBucket,Gitea) with repo scope. GitHub token, for example, can be issued from [here](https://github.com/settings/tokens){:target="_blank"}
 
 ## Using Docker image
 
@@ -12,7 +12,7 @@ To invoke a tool (for example `review`), you can run PR-Agent directly from the
 - For GitHub:
 
     ```bash
-    docker run --rm -it -e OPENAI.KEY=<your key> -e GITHUB.USER_TOKEN=<your token> codiumai/pr-agent:latest --pr_url <pr_url> review
+    docker run --rm -it -e OPENAI.KEY=<your_openai_key> -e GITHUB.USER_TOKEN=<your_github_token> codiumai/pr-agent:latest --pr_url <pr_url> review
     ```
 
     If you are using GitHub enterprise server, you need to specify the custom url as variable.
@@ -40,6 +40,19 @@ To invoke a tool (for example `review`), you can run PR-Agent directly from the
     docker run --rm -it -e CONFIG.GIT_PROVIDER=bitbucket -e OPENAI.KEY=$OPENAI_API_KEY -e BITBUCKET.BEARER_TOKEN=$BITBUCKET_BEARER_TOKEN codiumai/pr-agent:latest --pr_url=<pr_url> review
     ```
 
+- For Gitea:
+
+    ```bash
+    docker run --rm -it -e OPENAI.KEY=<your key> -e CONFIG.GIT_PROVIDER=gitea -e GITEA.PERSONAL_ACCESS_TOKEN=<your token> codiumai/pr-agent:latest --pr_url <pr_url> review
+    ```
+
+    If you have a dedicated Gitea instance, you need to specify the custom url as variable:
+
+    ```bash
+    -e GITEA.URL=<your gitea instance url>
+    ```
+
+
 For other git providers, update `CONFIG.GIT_PROVIDER` accordingly and check the [`pr_agent/settings/.secrets_template.toml`](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/.secrets_template.toml) file for environment variables expected names and values.
 
 ### Utilizing environment variables

docs/docs/installation/qodo_merge.md

@@ -1,20 +1,20 @@
 Qodo Merge is a versatile application compatible with GitHub, GitLab, and BitBucket, hosted by QodoAI.
 See [here](https://qodo-merge-docs.qodo.ai/overview/pr_agent_pro/) for more details about the benefits of using Qodo Merge.
 
-## Trial Period and Licensing
+## Usage and Licensing
 
-### Cloud Users with Teams Account
+### Cloud Users
 
-A complimentary two-week trial is provided to all new users (with three additional grace usages). When the trial period ends, users will stop receiving feedback from Qodo Merge.
+Non-paying users will enjoy feedback on up to 75 PRs per git organization per month. Above this limit, PRs will not receive feedback until a new month begins. 
 
-Following the trial period, user licenses (seats) are required for continued access. Each user requires an individual seat license.
+For unlimited access, user licenses (seats) are required. Each user requires an individual seat license.
 After purchasing seats, the team owner can assign them to specific users through the management portal.
 
-With an assigned seat, users can seamlessly deploy the application across any of their code repositories.
+With an assigned seat, users can seamlessly deploy the application across any of their code repositories in a git organization, and receive feedback on all their PRs.
 
 ### Enterprise Account
 
-For organizations who require an Enterprise account, please [contact](https://www.qodo.ai/contact/#pricing) us to initiate a trial period, and to discuss pricing and licensing options.
+For companies who require an Enterprise account, please [contact](https://www.qodo.ai/contact/#pricing) us to initiate a trial period, and to discuss pricing and licensing options.
 
 
 ## Install Qodo Merge for GitHub
@@ -27,11 +27,13 @@ Qodo Merge for GitHub cloud is available for installation through the [GitHub Ma
 
 ### GitHub Enterprise Server
 
-To use Qodo Merge application on your private GitHub Enterprise Server, you will need to [contact](https://www.qodo.ai/contact/#pricing) Qodo for starting an Enterprise trial.
+To use Qodo Merge on your private GitHub Enterprise Server, you will need to [contact](https://www.qodo.ai/contact/#pricing) Qodo for starting an Enterprise trial.
+
+(Note: The marketplace app is not compatible with GitHub Enterprise Server. Installation requires creating a private GitHub App instead.)
 
 ### GitHub Open Source Projects
 
-For open-source projects, Qodo Merge is available for free usage. To install Qodo Merge for your open-source repositories, use the following marketplace [link](https://github.com/apps/qodo-merge-pro-for-open-source).
+For open-source projects, Qodo Merge is available for free usage. To install Qodo Merge for your open-source repositories, use the following marketplace [link](https://github.com/marketplace/qodo-merge-pro-for-open-source).
 
 ## Install Qodo Merge for Bitbucket
 
@@ -49,50 +51,80 @@ To use Qodo Merge application on your private Bitbucket Server, you will need to
 
 ### GitLab Cloud
 
-Since GitLab platform does not support apps, installing Qodo Merge for GitLab is a bit more involved, and requires the following steps:
+Installing Qodo Merge for GitLab uses GitLab's OAuth 2.0 application system and requires the following steps:
 
-#### Step 1
+#### Step 1: Create a GitLab OAuth 2.0 Application
 
-Acquire a personal, project or group level access token. Enable the “api” scope in order to allow Qodo Merge to read pull requests, comment and respond to requests.
+Create a new OAuth 2.0 application in your GitLab instance:
 
-<figure markdown="1">
-![Step 1](https://www.codium.ai/images/pr_agent/gitlab_pro_pat.png){width=750}
-</figure>
+1. Navigate to your GitLab group or subgroup settings
+2. Go to "Applications" in the left sidebar
+3. Click on "Add new application"
+4. Fill in the application details:
+   - **Name**: You can give any name you wish (e.g., "Qodo Merge")
+   - **Redirect URI**: `https://register.oauth.app.gitlab.merge.qodo.ai/oauth/callback`
+   - **Confidential**: Check this checkbox
+   - **Scopes**: Check the "api" scope
+   
+    <figure markdown="1">
+    ![Step 1](https://www.codium.ai/images/pr_agent/gitlab_pro_oauth_app_creation_image.png){width=750}
+    </figure>
 
-Store the token in a safe place, you won’t be able to access it again after it was generated.
+5. Click "Save application"
+6. Copy both the **Application ID** and **Secret** - store them safely as you'll need them for the next step
 
-#### Step 2
+#### Step 2: Register Your OAuth Application
 
-Generate a shared secret and link it to the access token. Browse to [https://register.gitlab.pr-agent.codium.ai](https://register.gitlab.pr-agent.codium.ai).
-Fill in your generated GitLab token and your company or personal name in the appropriate fields and click "Submit".
+1. Browse to: <https://register.oauth.app.gitlab.merge.qodo.ai>
+2. Fill in the registration form:
+   - **Host Address**: Leave empty if using gitlab.com ([for self-hosted GitLab servers](#gitlab-server), enter your GitLab base URL including scheme (e.g., https://gitlab.mycorp-inc.com) without trailing slash. Do not include paths or query strings.
+   - **OAuth Application ID**: Enter the Application ID from Step 1
+   - **OAuth Application Secret**: Enter the Secret from Step 1 
+   
+    <figure markdown="1">
+    ![Step 2](https://www.codium.ai/images/pr_agent/gitlab_pro_registration_form_image.png){width=750}
+    </figure>
 
-You should see "Success!" displayed above the Submit button, and a shared secret will be generated. Store it in a safe place, you won’t be able to access it again after it was generated.
+3. Click "Submit"
 
-#### Step 3
+#### Step 3: Authorize the OAuth Application
 
-Install a webhook for your repository or groups, by clicking “webhooks” on the settings menu. Click the “Add new webhook” button.
+If all fields show green checkmarks, a redirect popup from GitLab will appear requesting authorization for the OAuth app to access the "api" scope. Click "Authorize" to approve the application.
 
-<figure markdown="1">
-![Step 3.1](https://www.codium.ai/images/pr_agent/gitlab_pro_add_webhook.png)
-</figure>
+#### Step 4: Copy the Webhook Secret Token
 
-In the webhook definition form, fill in the following fields:
-URL: https://pro.gitlab.pr-agent.codium.ai/webhook
+If the authorization is successful, a message will appear displaying a generated webhook secret token. Copy this token and store it safely - you'll need it for the next step.
 
-Secret token: Your QodoAI key
-Trigger: Check the ‘comments’ and ‘merge request events’ boxes.
-Enable SSL verification: Check the box.
+#### Step 5: Install Webhooks
 
-<figure markdown="1">
-![Step 3.2](https://www.codium.ai/images/pr_agent/gitlab_pro_webhooks.png){width=750}
-</figure>
+Install a webhook for your repository or groups by following these steps:
 
-#### Step 4
+1. Navigate to your repository or group settings
+2. Click "Webhooks" in the settings menu
+3. Click the "Add new webhook" button
 
-You’re all set!
+    <figure markdown="1">
+    ![Step 5.1](https://www.codium.ai/images/pr_agent/gitlab_pro_add_webhook.png)
+    </figure>
+
+4. In the webhook definition form, fill in the following fields:
+   - **URL**: `https://pro.gitlab.pr-agent.codium.ai/webhook`
+   - **Secret token**: The webhook secret token generated in Step 4
+   - **Trigger**: Check the 'Comments' and 'Merge request events' boxes
+   - **Enable SSL verification**: Check this box
+
+    <figure markdown="1">
+    ![Step 5.2](https://www.codium.ai/images/pr_agent/gitlab_pro_webhooks.png){width=750}
+    </figure>
+
+5. Click "Add webhook"
+
+**Note**: Repeat this webhook installation for each group or repository that is under the group or subgroup where the OAuth 2.0 application was created in Step 1.
+
+#### Step 6: You’re all set!
 
 Open a new merge request or add a MR comment with one of Qodo Merge’s commands such as /review, /describe or /improve.
 
 ### GitLab Server
 
-For a trial period of two weeks on your private GitLab Server, the same [installation steps](#gitlab-cloud) as for GitLab Cloud apply. After the trial period, you will need to [contact](https://www.qodo.ai/contact/#pricing) Qodo for moving to an Enterprise account.
+For [limited free usage](https://qodo-merge-docs.qodo.ai/installation/qodo_merge/#cloud-users) on private GitLab Server, the same [installation steps](#gitlab-cloud) as for GitLab Cloud apply, aside from the [Host Address field mentioned in Step 2](#step-2-register-your-oauth-application) (where you fill in the hostname for your GitLab server, such as: https://gitlab.mycorp-inc.com). For unlimited usage, you will need to [contact](https://www.qodo.ai/contact/#pricing) Qodo for moving to an Enterprise account.

docs/docs/overview/pr_agent_pro.md

@@ -1,7 +1,12 @@
 ### Overview
 
-[Qodo Merge](https://www.codium.ai/pricing/){:target="_blank"} is a paid, hosted version of open-source [PR-Agent](https://github.com/Codium-ai/pr-agent){:target="_blank"}. A complimentary two-week trial is offered, followed by a monthly subscription fee.
-Qodo Merge is designed for companies and teams that require additional features and capabilities. It provides the following benefits:
+[Qodo Merge](https://www.codium.ai/pricing/){:target="_blank"} is a hosted version of the open-source [PR-Agent](https://github.com/Codium-ai/pr-agent){:target="_blank"}. 
+It is designed for companies and teams that require additional features and capabilities.
+
+Free users receive a quota of 75 monthly PR feedbacks per git organization. Unlimited usage requires a paid subscription. See [details](https://qodo-merge-docs.qodo.ai/installation/qodo_merge/#cloud-users).
+
+
+Qodo Merge provides the following benefits:
 
 1. **Fully managed** - We take care of everything for you - hosting, models, regular updates, and more. Installation is as simple as signing up and adding the Qodo Merge app to your GitHub\GitLab\BitBucket repo.
 
@@ -19,7 +24,7 @@ Here are some of the additional features and capabilities that Qodo Merge offers
 
 | Feature                                                                                                              | Description                                                                                                                                            |
 | -------------------------------------------------------------------------------------------------------------------- |--------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [**Model selection**](https://qodo-merge-docs.qodo.ai/usage-guide/PR_agent_pro_models/)                              | Choose the model that best fits your needs, among top models like `Claude Sonnet`, `o4-mini`                                                           |
+| [**Model selection**](https://qodo-merge-docs.qodo.ai/usage-guide/PR_agent_pro_models/)                              | Choose the model that best fits your needs                                                         |
 | [**Global and wiki configuration**](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/)              | Control configurations for many repositories from a single location; <br>Edit configuration of a single repo without committing code                   |
 | [**Apply suggestions**](https://qodo-merge-docs.qodo.ai/tools/improve/#overview)                                     | Generate committable code from the relevant suggestions interactively by clicking on a checkbox                                                        |
 | [**Suggestions impact**](https://qodo-merge-docs.qodo.ai/tools/improve/#assessing-impact)                            | Automatically mark suggestions that were implemented by the user (either directly in GitHub, or indirectly in the IDE) to enable tracking of the impact of the suggestions |
@@ -45,7 +50,7 @@ Here are additional tools that are available only for Qodo Merge users:
 
 ### Supported languages
 
-Qodo Merge leverages the world's leading code models, such as Claude 3.7 Sonnet and o3-mini.
+Qodo Merge leverages the world's leading code models, such as Claude 4 Sonnet, o4-mini and Gemini-2.5-Pro.
 As a result, its primary tools such as `describe`, `review`, and `improve`, as well as the PR-chat feature, support virtually all programming languages.
 
 For specialized commands that require static code analysis, Qodo Merge offers support for specific languages. For more details about features that require static code analysis, please refer to the [documentation](https://qodo-merge-docs.qodo.ai/tools/analyze/#overview).

docs/docs/pr_benchmark/index.md

@@ -2,200 +2,505 @@
 
 ## Methodology
 
-Qodo Merge PR Benchmark evaluates and compares the performance of two Large Language Models (LLMs) in analyzing pull request code and providing meaningful code suggestions.
-Our diverse dataset comprises of 400 pull requests from over 100 repositories, spanning various programming languages and frameworks to reflect real-world scenarios.
+Qodo Merge PR Benchmark evaluates and compares the performance of Large Language Models (LLMs) in analyzing pull request code and providing meaningful code suggestions.
+Our diverse dataset contains 400 pull requests from over 100 repositories, spanning multiple [programming languages](#programming-languages) to reflect real-world scenarios.
 
-- For each pull request, two distinct LLMs process the same prompt using the Qodo Merge `improve` tool, each generating two sets of responses. The prompt for response generation can be found [here](https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/code_suggestions/pr_code_suggestions_prompts_not_decoupled.toml).
+- For each pull request, we have pre-generated suggestions from eleven different top-performing models using the Qodo Merge `improve` tool. The prompt for response generation can be found [here](https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/code_suggestions/pr_code_suggestions_prompts_not_decoupled.toml). 
 
-- Subsequently, a high-performing third model (an AI judge) evaluates the responses from the initial two models to determine the superior one. We utilize OpenAI's `o3` model as the judge, though other models have yielded consistent results. The prompt for this comparative judgment is available [here](https://github.com/Codium-ai/pr-agent-settings/tree/main/benchmark).
+- To benchmark a model, we generate its suggestions for the same pull requests and ask a high-performing judge model to **rank** the new model's output against the pre-generated baseline suggestions. We utilize OpenAI's `o3` model as the judge, though other models have yielded consistent results. The prompt for this ranking judgment is available [here](https://github.com/Codium-ai/pr-agent-settings/tree/main/benchmark).
 
-- We aggregate comparison outcomes across all the pull requests, calculating the win rate for each model. We also analyze the qualitative feedback (the "why" explanations from the judge) to identify each model's comparative strengths and weaknesses.
+- We aggregate ranking outcomes across all pull requests, calculating performance metrics for the evaluated model. 
+
+- We also analyze the qualitative feedback from the judge to identify the model's comparative strengths and weaknesses against the established baselines.
 This approach provides not just a quantitative score but also a detailed analysis of each model's strengths and weaknesses.
 
-- For each model we build a "Model Card", comparing it against others. To ensure full transparency and enable community scrutiny, we also share the raw code suggestions generated by each model, and the judge's specific feedback. See example for the full output [here](https://github.com/Codium-ai/pr-agent-settings/blob/main/benchmark/sonnet_37_vs_gemini-2.5-pro-preview-05-06.md)
+A list of the models used for generating the baseline suggestions, and example results, can be found in the [Appendix](#appendix-example-results).
 
-Note that this benchmark focuses on quality: the ability of an LLM to process complex pull request with multiple files and nuanced task to produce high-quality code suggestions.
-Other factors like speed, cost, and availability, while also relevant for model selection, are outside this benchmark's scope.
+[//]: # (Note that this benchmark focuses on quality: the ability of an LLM to process complex pull request with multiple files and nuanced task to produce high-quality code suggestions.)
 
-## TL;DR
+[//]: # (Other factors like speed, cost, and availability, while also relevant for model selection, are outside this benchmark's scope. We do specify the thinking budget used by each model, which can be a factor in the model's performance.)
 
-Here's a summary of the win rates based on the benchmark:
+[//]: # ()
 
-[//]: # (| Model A                        | Model B                        | Model A Win Rate | Model B Win Rate |)
-
-[//]: # (|:-------------------------------|:-------------------------------|:----------------:|:----------------:|)
-
-[//]: # (| Gemini-2.5-pro-preview-05-06   | GPT-4.1                        |      70.4%       |      29.6%       |)
-
-[//]: # (| Gemini-2.5-pro-preview-05-06   | Sonnet 3.7                     |      78.1%       |      21.9%       |)
-
-[//]: # (| GPT-4.1                        | Sonnet 3.7                     |      61.0%       |      39.0%       |)
+## PR Benchmark Results
 
 <table>
   <thead>
     <tr>
-      <th style="text-align:left;">Model A</th>
-      <th style="text-align:left;">Model B</th>
-      <th style="text-align:center;">Model A Win Rate</th> <th style="text-align:center;">Model B Win Rate</th> </tr>
+      <th style="text-align:left;">Model Name</th>
+      <th style="text-align:left;">Version (Date)</th>
+      <th style="text-align:left;">Thinking budget tokens</th>
+      <th style="text-align:center;">Score</th>
+    </tr>
   </thead>
   <tbody>
     <tr>
-      <td style="text-align:left;">Gemini-2.5-pro-preview-05-06</td>
-      <td style="text-align:left;">GPT-4.1</td>
-      <td style="text-align:center; color: #1E8449;"><b>70.4%</b></td> <td style="text-align:center; color: #D8000C;"><b>29.6%</b></td> </tr>
+      <td style="text-align:left;">GPT-5-pro</td>
+      <td style="text-align:left;">2025-10-06</td>
+      <td style="text-align:left;"></td>
+      <td style="text-align:center;"><b>73.4</b></td>
+    </tr>
     <tr>
-      <td style="text-align:left;">Gemini-2.5-pro-preview-05-06</td>
-      <td style="text-align:left;">Sonnet 3.7</td>
-      <td style="text-align:center; color: #1E8449;"><b>78.1%</b></td> <td style="text-align:center; color: #D8000C;"><b>21.9%</b></td> </tr>
+      <td style="text-align:left;">GPT-5</td>
+      <td style="text-align:left;">2025-08-07</td>
+      <td style="text-align:left;">medium</td>
+      <td style="text-align:center;"><b>72.2</b></td>
+    </tr>
     <tr>
-      <td style="text-align:left;">Gemini-2.5-pro-preview-05-06</td>
-      <td style="text-align:left;">Gemini-2.5-flash-preview-04-17</td>
-      <td style="text-align:center; color: #1E8449;"><b>73.0%</b></td> <td style="text-align:center; color: #D8000C;"><b>27.0%</b></td> </tr>
+      <td style="text-align:left;">GPT-5</td>
+      <td style="text-align:left;">2025-08-07</td>
+      <td style="text-align:left;">low</td>
+      <td style="text-align:center;"><b>67.8</b></td>
+    </tr>
     <tr>
-      <td style="text-align:left;">Gemini-2.5-flash-preview-04-17</td>
-      <td style="text-align:left;">GPT-4.1</td>
-      <td style="text-align:center; color: #1E8449;"><b>54.6%</b></td> <td style="text-align:center; color: #D8000C;"><b>45.4%</b></td> </tr>
+      <td style="text-align:left;">GPT-5</td>
+      <td style="text-align:left;">2025-08-07</td>
+      <td style="text-align:left;">minimal</td>
+      <td style="text-align:center;"><b>62.7</b></td>
+    </tr>
     <tr>
-      <td style="text-align:left;">Gemini-2.5-flash-preview-04-17</td>
-      <td style="text-align:left;">Sonnet 3.7</td>
-      <td style="text-align:center; color: #1E8449;"><b>60.6%</b></td> <td style="text-align:center; color: #D8000C;"><b>39.4%</b></td> </tr>
+      <td style="text-align:left;">o3</td>
+      <td style="text-align:left;">2025-04-16</td>
+      <td style="text-align:left;">'medium' (<a href="https://ai.google.dev/gemini-api/docs/openai">8000</a>)</td>
+      <td style="text-align:center;"><b>62.5</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">o4-mini</td>
+      <td style="text-align:left;">2025-04-16</td>
+      <td style="text-align:left;">'medium' (<a href="https://ai.google.dev/gemini-api/docs/openai">8000</a>)</td>
+      <td style="text-align:center;"><b>57.7</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Gemini-3-pro-review</td>
+      <td style="text-align:left;">2025-11-18</td>
+      <td style="text-align:left;">high</td>
+      <td style="text-align:center;"><b>57.3</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Gemini-2.5-pro</td>
+      <td style="text-align:left;">2025-06-05</td>
+      <td style="text-align:left;">4096</td>
+      <td style="text-align:center;"><b>56.3</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Gemini-3-pro-review</td>
+      <td style="text-align:left;">2025-11-18</td>
+      <td style="text-align:left;">low</td>
+      <td style="text-align:center;"><b>55.6</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-haiku-4.5</td>
+      <td style="text-align:left;">2025-10-01</td>
+      <td style="text-align:left;">4096</td>
+      <td style="text-align:center;"><b>48.8</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">GPT-5.1</td>
+      <td style="text-align:left;">2025-11-13</td>
+      <td style="text-align:left;">medium</td>
+      <td style="text-align:center;"><b>44.9</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Gemini-2.5-pro</td>
+      <td style="text-align:left;">2025-06-05</td>
+      <td style="text-align:left;">1024</td>
+      <td style="text-align:center;"><b>44.3</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-sonnet-4.5</td>
+      <td style="text-align:left;">2025-09-29</td>
+      <td style="text-align:left;">4096</td>
+      <td style="text-align:center;"><b>44.2</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-haiku-4.5</td>
+      <td style="text-align:left;">2025-10-01</td>
+      <td style="text-align:left;"></td>
+      <td style="text-align:center;"><b>40.7</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-sonnet-4.5</td>
+      <td style="text-align:left;">2025-09-29</td>
+      <td style="text-align:left;"></td>
+      <td style="text-align:center;"><b>40.7</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-4-sonnet</td>
+      <td style="text-align:left;">2025-05-14</td>
+      <td style="text-align:left;">4096</td>
+      <td style="text-align:center;"><b>39.7</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-4-sonnet</td>
+      <td style="text-align:left;">2025-05-14</td>
+      <td style="text-align:left;"></td>
+      <td style="text-align:center;"><b>39.0</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Codex-mini</td>
+      <td style="text-align:left;">2025-06-20</td>
+      <td style="text-align:left;"><a href="https://platform.openai.com/docs/models/codex-mini-latest">unknown</a></td>
+      <td style="text-align:center;"><b>37.2</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Gemini-2.5-flash</td>
+      <td style="text-align:left;">2025-04-17</td>
+      <td style="text-align:left;"></td>
+      <td style="text-align:center;"><b>33.5</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Grok-4</td>
+      <td style="text-align:left;">2025-07-09</td>
+      <td style="text-align:left;">unknown</td>
+      <td style="text-align:center;"><b>32.8</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-4-opus-20250514</td>
+      <td style="text-align:left;">2025-05-14</td>
+      <td style="text-align:left;"></td>
+      <td style="text-align:center;"><b>32.8</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-3.7-sonnet</td>
+      <td style="text-align:left;">2025-02-19</td>
+      <td style="text-align:left;"></td>
+      <td style="text-align:center;"><b>32.4</b></td>
+    </tr>
+    <tr>
+      <td style="text-align:left;">Claude-opus-4.5</td>
+      <td style="text-align:left;">2025-11-01</td>
+      <td style="text-align:left;">high</td>
+      <td style="text-align:center;"><b>30.3</b></td>
+    </tr>
     <tr>
       <td style="text-align:left;">GPT-4.1</td>
-      <td style="text-align:left;">Sonnet 3.7</td>
-      <td style="text-align:center; color: #1E8449;"><b>61.0%</b></td> <td style="text-align:center; color: #D8000C;"><b>39.0%</b></td> </tr>
+      <td style="text-align:left;">2025-04-14</td>
+      <td style="text-align:left;"></td>
+      <td style="text-align:center;"><b>26.5</b></td>
+    </tr>
   </tbody>
 </table>
 
+## Results Analysis (Latest Additions)
 
-## Gemini-2.5-pro-preview-05-06 - Model Card
+### GPT-5-pro
 
-### Comparison against GPT-4.1
+Final score: **73.4**
 
-![Comparison](https://codium.ai/images/qodo_merge_benchmark/gpt-4.1_vs_gemini-2.5-pro-preview-05-06_judge_o3.png){width=768}
+Strengths:
 
-#### Analysis Summary
+- **High bug‐finding accuracy and depth:** In many cases the model uncovers the core compile-time or run-time regression that other answers miss and frequently combines several distinct critical issues into one reply.
+- **Actionable, minimal patches:** Suggestions almost always include clear before/after code blocks that touch only the added lines and respect the ≤3-suggestion limit, making them easy to apply.
+- **Good guideline compliance:** The model generally honours the task rules—no edits to unchanged code, no version bumps, no more than three items—and shows solid judgment about when an empty list is appropriate.
+- **Concise, impact-oriented reasoning:** Explanations focus on severity, crash potential and build breakage rather than style, helping reviewers prioritise fixes.
 
-Model 'Gemini-2.5-pro-preview-05-06' is generally more useful thanks to wider and more accurate bug detection and concrete patches, but it sacrifices compliance discipline and sometimes oversteps the task rules. Model 'GPT-4.1' is safer and highly rule-abiding, yet often too timid—missing many genuine issues and providing limited insight. An ideal reviewer would combine 'GPT-4.1’ restraint with 'Gemini-2.5-pro-preview-05-06' thoroughness.
+Weaknesses:
 
-#### Detailed Analysis
+- **Coverage gaps:** In a noticeable minority of examples the model misses a higher-impact defect that several other answers catch, or returns an empty list despite clear bugs.
+- **Occasional incorrect or harmful fixes:** A few replies introduce new errors or rest on wrong assumptions about functionality or language-specific behavior.
+- **Formatting / guideline slips:** Sporadic duplication of suggestions, missing or empty `improved_code` blocks, or YAML mishaps undermine otherwise good answers.
+- **Uneven criticality judgement:** Some suggestions drift into low-impact territory while overlooking more severe problems, indicating inconsistent prioritisation.
 
-Gemini-2.5-pro-preview-05-06 strengths:  
+### O3
 
-- better_bug_coverage: Detects and explains more critical issues, winning in ~70 % of comparisons and achieving a higher average score.  
-- actionable_fixes: Supplies clear code snippets, correct language labels, and often multiple coherent suggestions per diff.  
-- deeper_reasoning: Shows stronger grasp of logic, edge cases, and cross-file implications, leading to broader, high-impact reviews.  
+Final score: **62.5**
 
-Gemini-2.5-pro-preview-05-06 weaknesses:  
+Strengths:
 
-- guideline_violations: More prone to over-eager advice—non-critical tweaks, touching unchanged code, suggesting new imports, or minor format errors.  
-- occasional_overreach: Some fixes are speculative or risky, potentially introducing new bugs.  
-- redundant_or_duplicate: At times repeats the same point or exceeds the required brevity.  
+- **High precision & compliance:** Generally respects task rules (limits, “added lines” scope, YAML schema) and avoids false-positive advice, often returning an empty list when appropriate.  
+- **Clear, actionable output:** Suggestions are concise, well-explained and include correct before/after patches, so reviewers can apply them directly.  
+- **Good critical-bug detection rate:** Frequently spots compile-breakers or obvious runtime faults (nil / NPE, overflow, race, wrong selector, etc.), putting it at least on par with many peers.  
+- **Consistent formatting:** Produces syntactically valid YAML with correct labels, making automated consumption easy.
+
+Weaknesses:
+
+- **Narrow coverage:** Tends to stop after 1-2 issues; regularly misses additional critical defects that better answers catch, so it is seldom the top-ranked review.  
+- **Occasional inaccuracies:** A few replies introduce new bugs, give partial/duplicate fixes, or (rarely) violate rules (e.g., import suggestions), hurting trust.  
+- **Conservative bias:** Prefers silence over risk; while this keeps precision high, it lowers recall and overall usefulness on larger diffs.  
+- **Little added insight:** Rarely offers broader context, optimisations or holistic improvements, causing it to rank only mid-tier in many comparisons.
+
+### O4 Mini ('medium' thinking tokens)
+
+Final score: **57.7**
+
+Strengths:
+
+- **Good rule adherence:** Most answers respect the “new-lines only”, 3-suggestion, and YAML-schema limits, and frequently choose the safe empty list when the diff truly adds no critical bug.
+- **Clear, minimal patches:** When the model does spot a defect it usually supplies terse, valid before/after snippets and short, targeted explanations, making fixes easy to read and apply.
+- **Language & domain breadth:** Demonstrates competence across many ecosystems (C/C++, Java, TS/JS, Go, Rust, Python, Bash, Markdown, YAML, SQL, CSS, translation files, etc.) and can detect both compile-time and runtime mistakes.
+- **Often competitive:** In a sizeable minority of cases the model ties for best or near-best answer, occasionally being the only response to catch a subtle crash or build blocker.
+
+Weaknesses:
+
+- **High miss rate:** A large share of examples show the model returning an empty list or only minor advice while other reviewers catch clear, high-impact bugs—indicative of weak defect-detection recall.
+- **False or harmful fixes:** Several answers introduce new compilation errors, propose out-of-scope changes, or violate explicit rules (e.g., adding imports, version bumps, touching untouched lines), reducing trustworthiness.
+- **Shallow coverage:** Even when it identifies one real issue it often stops there, missing additional critical problems found by stronger peers; breadth and depth are inconsistent.
+
+### Gemini-3-pro-review (high thinking budget)
+
+Final score: **57.3**
+
+Strengths:
+
+- **Good schema & format discipline:** Consistently returns well-formed YAML with correct fields and respects the 3-suggestion limit; rarely breaks the required output structure.
+- **Reasonable guideline awareness:** Often recognises when a diff contains only data / translations and properly emits an empty list, avoiding over-reporting.
+- **Clear, actionable patches when correct:** When it does find a bug it usually supplies minimal-diff, compilable code snippets with concise explanations, and occasionally surfaces issues no other model spotted.
+
+Weaknesses:
+
+- **Spot-coverage gaps on critical defects:** In a large share of cases it overlooks the principal regression the tests were written for, while fixating on minor style or performance nits.
+- **False or speculative fixes:** A noticeable number of answers invent non-existent problems or propose changes that would not compile or would re-introduce removed behaviour.
+- **Guideline violations creep in:** Sometimes touches unchanged lines, adds forbidden imports / labels, or supplies more than "critical" advice, showing imperfect rule adherence.
+- **High variance / inconsistency:** Quality swings from best-in-class to harmful within consecutive examples, indicating unstable defect-prioritisation and review depth.
+
+### Gemini-2.5 Pro (4096 thinking tokens)
+
+Final score: **56.3**
+
+Strengths:
+
+- **High formatting compliance:** The model almost always produces valid YAML, respects the three-suggestion limit, and supplies clear before/after code snippets and short rationales.
+- **Good “first-bug” detection:** It frequently notices the single most obvious regression (crash, compile error, nil/NPE risk, wrong path, etc.) and gives a minimal, correct patch—often judged “on-par” with other solid answers.
+- **Clear, concise writing:** Explanations are brief yet understandable for reviewers; fixes are scoped to the changed lines and rarely include extraneous context.
+- **Low rate of harmful fixes:** Truly dangerous or build-breaking advice is rare; most mistakes are omissions rather than wrong code.
+
+Weaknesses:
+
+- **Limited breadth of review:** The model regularly stops after the first or second issue, missing additional critical problems that stronger answers surface, so it is often out-ranked by more comprehensive peers.
+- **Occasional guideline violations:** A noticeable minority of answers touch unchanged lines, exceed the 3-item cap, suggest adding imports, or drop the required YAML wrapper, leading to automatic downgrades.
+- **False positives / speculative fixes:** In several cases it flags non-issues (style, performance, redundant code) or supplies debatable “improvements”, lowering precision and sometimes breaching the “critical bugs only” rule.
+- **Inconsistent error coverage:** For certain domains (build scripts, schema files, test code) it either returns an empty list when real regressions exist or proposes cosmetic edits, indicating gaps in specialised knowledge.
+
+### Gemini-3-pro-review (low thinking budget)
+
+Final score: **55.6**
+
+Strengths:
+
+- **Concise, well-structured patches:** Suggestions are usually expressed in short, self-contained YAML items with clear before/after code blocks and just enough rationale, making them easy for reviewers to apply.
+- **Good eye for crash-level defects:** When the model does spot a problem it often focuses on high-impact issues such as compile-time errors, NPEs, nil-pointer races, buffer overflows, etc., and supplies a minimal, correct fix.
+- **High guideline compliance (format & scope):** In most cases it respects the 1-3-item limit and the "new lines only" rule, avoids changing imports, and keeps snippets syntactically valid.
+
+Weaknesses:
+
+- **Coverage inconsistency:** Many answers miss other obvious or even more critical regressions spotted by peers; breadth fluctuates from excellent to empty, leaving reviewers with partial insight.
+- **False positives & speculative advice:** A noticeable share of suggestions target stylistic or non-critical tweaks, or even introduce wrong changes, betraying occasional mis-reading of the diff and hurting trust.
+- **Rule violations still occur:** There are repeated instances of touching unchanged code, recommending version bumps/imports, mis-labelling severities, or outputting malformed snippets—showing lapses in instruction adherence.
+- **Quality variance / empty outputs:** Some responses provide no suggestions despite real bugs, while others supply harmful fixes; this volatility lowers overall reliability.
+
+### Claude-haiku-4.5 (4096 thinking tokens)
+
+Final score: **48.8**
+
+Strengths:
+
+- **High precision on detected issues:** When the model does flag a problem it is usually a real, high-impact bug; many answers are judged equal or better than strong baselines because the proposed fix is correct, minimal and easy to apply.
+- **Language- and domain-agnostic competence:** It successfully diagnoses defects across a wide range of languages (Python, Go, C/C++, Rust, JS/TS, CSS, SQL, Markdown, etc.) and domains (backend logic, build files, tests, docs).
+- **Clear, actionable patches:** Suggested code is typically concise, well-explained and scoped exactly to the added lines, making it practical for reviewers to adopt.
+
+Weaknesses:
+
+- **Low recall / narrow coverage:** The model often stops after one or two findings, leaving other obvious critical bugs unmentioned; in many examples stronger answers simply covered more ground.
+- **Occasional faulty or speculative fixes:** A non-trivial number of responses either mis-diagnose the issue or introduce new errors (e.g., wrong logic, undeclared imports), dropping them below baseline quality.
+- **Inconsistent output robustness:** Several cases show truncated or malformed responses, reducing value despite correct analysis elsewhere.
+- **Frequent false negatives:** The model sometimes returns an empty list even when clear regressions exist, indicating conservative behaviour that misses mandatory fixes.
+
+### GPT-5.1 ('medium' thinking budget)
+
+Final score: **44.9**
+
+Strengths:
+
+- **High precision & guideline compliance:** When the model does emit suggestions they are almost always technically sound, respect the "new-lines-only / ≤3 suggestions / no-imports" rules, and are formatted correctly. It rarely introduces harmful changes and often provides clear, runnable patches.
+- **Ability to spot subtle or unique defects:** In several cases the model caught a critical issue that most or all baselines missed, showing good deep-code reasoning when it does engage.
+- **Good judgment on noise-free diffs:** On purely data or documentation changes the model frequently (and correctly) returns an empty list, avoiding false-positive "nit" feedback.
+
+Weaknesses:
+
+- **Very low recall / over-conservatism:** In a large fraction of examples it outputs an empty suggestion list while clear critical bugs exist (well over 50 % of cases), making it inferior to almost every baseline answer that offered any fix.
+- **Narrow coverage when it speaks:** Even when it flags one bug, it often stops there and ignores other equally critical problems present in the same diff, leaving reviewers with partial insight.
+- **Occasional misdiagnosis or harmful fix:** A minority of suggestions are wrong or counter-productive, showing that precision, while good, is not perfect.
+
+### Claude-sonnet-4.5 (4096 thinking tokens)
+
+Final score: **44.2**
+
+Strengths:
+
+- **High precision / low noise:** When the model does offer fixes they are usually correct, concise and confined to the new '+' lines, rarely introducing spurious or off-scope changes.
+- **Clear, actionable patches:** Suggestions come with well-explained reasoning and minimal but valid code snippets, making them easy for a reviewer to apply.
+- **Good rule compliance:** It almost always respects the 1-3 suggestion limit, avoids touching unchanged code and seldom violates formatting or other task guidelines.
+
+Weaknesses:
+
+- **Low recall / frequent omissions:** In a large share of cases the model returns an empty list or only one minor tip while overlooking obvious, higher-impact regressions found by peers.
+- **Narrow coverage when it does respond:** Even in non-empty outputs it typically fixes a single issue and ignores related defects in the same diff, indicating shallow analysis.
+- **Occasional harmful or incomplete fixes:** A few suggestions introduce new errors (e.g., wrong logic, missing imports, malformed snippets) or mark non-critical style nits as "critical", reducing trust.
+
+### Claude-sonnet-4.5
+
+Final score: **40.7**
+
+Strengths:
+
+- **Concise & well-formatted output:** Most replies strictly follow the schema, stay within the 3-suggestion limit, and include clear, copy-paste-ready patches, making them easy to apply.
+- **Can spot headline bugs:** When a single, obvious regression is present (e.g. duplicated regex block, missing null-check, wrong macro name) the model often detects it and proposes an accurate, minimal fix.
+- **Scope discipline (usually):** It frequently restricts changes to newly-added lines and avoids broad refactors, so many answers comply with the “new code only / critical bugs only” rule.
+- **Reasonable explanations:** The accompanying rationales are typically short but precise, helping reviewers understand why the change is needed.
+
+Weaknesses:
+
+- **Low recall of critical issues:** In a large fraction of examples the model misses the primary bug or flags nothing at all while other reviewers find clear problems. Coverage is therefore unreliable.
+- **False or harmful fixes:** A notable number of suggestions mis-diagnose the code, touch unchanged lines, violate task rules, or would break compilation/runtime (wrong paths, bad types, guideline-forbidden advice).
+- **Priority mistakes:** The model often downgrades severe defects to “general” or upgrades cosmetic nits to “critical”, showing weak bug-severity judgment.
+- **Inconsistent quality:** Performance swings widely between excellent and poor; reviewers cannot predict whether a given answer will be thorough, partial, or incorrect.
+
+### Claude-haiku-4.5
+
+Final score: 40.7
+
+Strengths:
+
+- **Good format & clarity: Consistently produces valid YAML and readable, minimally-intrusive patches with clear before/after snippets, so its outputs are easy to apply.
+- **Basic bug-spotting ability: Often detects the most obvious new-line defect (e.g., syntax error, missing guard, wrong constant) and supplies a correct, concise fix; rarely ranks last in the set.
+- **Rule compliance in many cases: Usually stays within the 3-suggestion limit, touches only '+' lines, and avoids speculative refactors—returning an empty list when no code was added.
+
+Weaknesses:
+
+- **Shallow coverage: Frequently fixes just one surface-level issue and misses additional, higher-impact bugs that stronger reviewers catch, leaving regressions in place.
+- **Occasional incorrect or no-op patches: A noticeable share of suggestions either leave code unchanged, contain invalid code, or introduce new errors, lowering trust.
+- **Guideline slips: In several examples it edits unchanged lines, adds forbidden imports/version bumps, mis-labels severities, or supplies non-critical stylistic advice.
+- **Inconsistent diligence: Roughly a quarter of the cases return an empty list despite real problems, while others duplicate existing PR changes, indicating weak diff comprehension.
 
 
-### Comparison against Sonnet 3.7
+### OpenAI codex-mini
 
-![Comparison](https://codium.ai/images/qodo_merge_benchmark/sonnet_37_vs_gemini-2.5-pro-preview-05-06_judge_o3.png){width=768}
+Final score: **37.2**
 
-#### Analysis Summary
+Strengths:
 
-Model 'Gemini-2.5-pro-preview-05-06' is the stronger reviewer—more frequently identifies genuine, high-impact bugs and provides well-formed, actionable fixes. Model 'Sonnet 3.7' is safer against false positives and tends to be concise but often misses important defects or offers low-value or incorrect suggestions.
+- **Can spot high-impact defects:** When it "locks on", codex-mini often identifies the main runtime or security regression (e.g., race-conditions, logic inversions, blocking I/O, resource leaks) and proposes a minimal, direct patch that compiles and respects neighbouring style.
+- **Produces concise, scoped fixes:** Valid answers usually stay within the allowed 3-suggestion limit, reference only the added lines, and contain clear before/after snippets that reviewers can apply verbatim.
+- **Occasional broad coverage:** In a minority of cases the model catches multiple independent issues (logic + tests + docs) and outperforms every baseline answer, showing good contextual understanding of heterogeneous diffs.
 
-See raw results [here](https://github.com/Codium-ai/pr-agent-settings/blob/main/benchmark/sonnet_37_vs_gemini-2.5-pro-preview-05-06.md)
+Weaknesses:
 
+- **Output instability / format errors:** A very large share of responses are unusable—plain refusals, shell commands, or malformed/empty YAML—indicating brittle adherence to the required schema and tanking overall usefulness.
+- **Critical-miss rate:** Even when the format is correct the model frequently overlooks the single most serious bug the diff introduces, instead focusing on stylistic nits or speculative refactors.
+- **Introduces new problems:** Several suggestions add unsupported APIs, undeclared variables, wrong types, or break compilation, hurting trust in the recommendations.
+- **Rule violations:** It often edits lines outside the diff, exceeds the 3-suggestion cap, or labels cosmetic tweaks as "critical", showing inconsistent guideline compliance.
 
-#### Detailed Analysis
+### Gemini-2.5 Flash
 
-Gemini-2.5-pro-preview-05-06 strengths:  
+Final score: **33.5**
 
-- higher_accuracy_and_coverage: finds real critical bugs and supplies actionable patches in most examples (better in 78 % of cases).  
-- guideline_awareness: usually respects new-lines-only scope, ≤3 suggestions, proper YAML, and stays silent when no issues exist.  
-- detailed_reasoning_and_patches: explanations tie directly to the diff and fixes are concrete, often catching multiple related defects that 'Sonnet 3.7' overlooks.
+Strengths:
 
-Gemini-2.5-pro-preview-05-06 weaknesses:  
+- **High precision / low false-positive rate:** The model often stays silent or gives a single, well-justified fix, so when it does speak the suggestion is usually correct and seldom touches unchanged lines, keeping guideline compliance high.  
+- **Good guideline awareness:** YAML structure is consistently valid; suggestions rarely exceed the 3-item limit and generally restrict themselves to newly-added lines.  
+- **Clear, concise patches:** When a defect is found, the model produces short rationales and tidy “improved_code” blocks that reviewers can apply directly.  
+- **Risk-averse behaviour pays off in “no-bug” PRs:** In examples where the diff truly contained no critical issue, the model’s empty output ranked above peers that offered speculative or stylistic advice.
 
-- occasional_rule_violations: sometimes proposes new imports, package-version changes, or edits outside the added lines.  
-- overzealous_suggestions: may add speculative or stylistic fixes that exceed the “critical” scope, or mis-label severity.  
-- sporadic_technical_slips: a few patches contain minor coding errors, oversized snippets, or duplicate/contradicting advice.
+Weaknesses:
 
-## GPT-4.1 - Model Card
+- **Very low recall / shallow coverage:** In a large majority of cases it gives 0-1 suggestions and misses other evident, critical bugs highlighted by peer models, leading to inferior rankings.  
+- **Occasional incorrect or harmful fixes:** A noticeable subset of answers propose changes that break functionality or misunderstand the code (e.g. bad constant, wrong header logic, speculative rollbacks).  
+- **Non-actionable placeholders:** Some “improved_code” sections contain comments or “…” rather than real patches, reducing practical value.  
 
-### Comparison against Sonnet 3.7
+### Claude-4 Opus
 
-![Comparison](https://codium.ai/images/qodo_merge_benchmark/gpt-4.1_vs_sonnet_3.7_judge_o3.png){width=768}
+Final score: **32.8**
 
-#### Analysis Summary
+Strengths:
 
-Model 'GPT-4.1' is safer and more compliant, preferring silence over speculation, which yields fewer rule breaches and false positives but misses some real bugs.  
-Model 'Sonnet 3.7' is more adventurous and often uncovers important issues that 'GPT-4.1' ignores, yet its aggressive style leads to frequent guideline violations and a higher proportion of incorrect or non-critical advice. 
+- **Format & rule adherence:** Almost always returns valid YAML, stays within the ≤3-suggestion limit, and usually restricts edits to newly-added lines, so its output is easy to apply automatically.
+- **Concise, focused patches:** When it does find a real bug it gives short, well-scoped explanations plus minimal diff snippets, often outperforming verbose baselines in clarity.
+- **Able to catch subtle edge-cases:** In several examples it detected overflow, race-condition or enum-mismatch issues that many other models missed, showing solid code‐analysis capability.
 
-See raw results [here](https://github.com/Codium-ai/pr-agent-settings/blob/main/benchmark/gpt-4.1_vs_sonnet_3.7_judge_o3.md)
+Weaknesses:
 
+- **Low recall / narrow coverage:** In a large share of the 399 examples the model produced an empty list or only one minor tip while more serious defects were present, causing it to be rated inferior to most baselines.
+- **Frequent incorrect or no-op fixes:** It sometimes supplies identical “before/after” code, flags non-issues, or suggests changes that would break compilation or logic, reducing reviewer trust.
+- **Shaky guideline consistency:** Although generally compliant, it still occasionally violates rules (touches unchanged lines, offers stylistic advice, adds imports) and duplicates suggestions, indicating unstable internal checks.
 
-#### Detailed Analysis
+### Grok-4
 
-GPT-4.1 strengths:  
-- Strong guideline adherence: usually stays strictly on `+` lines, avoids non-critical or stylistic advice, and rarely suggests forbidden imports; often outputs an empty list when no real bug exists.  
-- Lower false-positive rate: suggestions are more accurate and seldom introduce new bugs; fixes compile more reliably.  
-- Good schema discipline: YAML is almost always well-formed and fields are populated correctly.  
+Final score: **32.8**
 
-GPT-4.1 weaknesses:  
-- Misses bugs: often returns an empty list even when a clear critical issue is present, so coverage is narrower.  
-- Sparse feedback: when it does comment, it tends to give fewer suggestions and sometimes lacks depth or completeness.  
-- Occasional metadata/slip-ups (wrong language tags, overly broad code spans), though less harmful than Sonnet 3.7 errors.  
+Strengths:
 
-### Comparison against Gemini-2.5-pro-preview-05-06
+- **Focused and concise fixes:** When the model does detect a problem it usually proposes a minimal, well-scoped patch that compiles and directly addresses the defect without unnecessary noise.
+- **Good critical-bug instinct:** It often prioritises show-stoppers (compile failures, crashes, security issues) over cosmetic matters and occasionally spots subtle issues that all other reviewers miss.
+- **Clear explanations & snippets:** Explanations are short, readable and paired with ready-to-paste code, making the advice easy to apply.
 
-![Comparison](https://codium.ai/images/qodo_merge_benchmark/gpt-4.1_vs_gemini-2.5-pro-preview-05-06_judge_o3.png){width=768}
+Weaknesses:
 
-#### Analysis Summary
+- **High miss rate:** In a large fraction of examples the model returned an empty list or covered only one minor issue while overlooking more serious newly-introduced bugs.
+- **Inconsistent accuracy:** A noticeable subset of answers contain wrong or even harmful fixes (e.g., removing valid flags, creating compile errors, re-introducing bugs).
+- **Limited breadth:** Even when it finds a real defect it rarely reports additional related problems that peers catch, leading to partial reviews.
+- **Occasional guideline slips:** A few replies modify unchanged lines, suggest new imports, or duplicate suggestions, showing imperfect compliance with instructions.
 
-Model 'Gemini-2.5-pro-preview-05-06' is generally more useful thanks to wider and more accurate bug detection and concrete patches, but it sacrifices compliance discipline and sometimes oversteps the task rules. Model 'GPT-4.1' is safer and highly rule-abiding, yet often too timid—missing many genuine issues and providing limited insight. An ideal reviewer would combine 'GPT-4.1’ restraint with 'Gemini-2.5-pro-preview-05-06' thoroughness.
+### Claude-Opus-4.5 (high thinking budget)
 
-#### Detailed Analysis
+Final score: **30.3**
 
-GPT-4.1 strengths: 
-- strict_compliance: Usually sticks to the “critical bugs only / new ‘+’ lines only” rule, so outputs rarely violate task constraints.  
-- low_risk: Conservative behaviour avoids harmful or speculative fixes; safer when no obvious issue exists.  
-- concise_formatting: Tends to produce minimal, correctly-structured YAML without extra noise.  
+Strengths:
 
-GPT-4.1 weaknesses:
-- under_detection: Frequently returns an empty list even when real bugs are present, missing ~70 % of the time.  
-- shallow_analysis: When it does suggest fixes, coverage is narrow and technical depth is limited, sometimes with wrong language tags or minor format slips.  
-- occasional_inaccuracy: A few suggestions are unfounded or duplicate, and rare guideline breaches (e.g., import advice) still occur.  
+- **High rule compliance & formatting:** Consistently produces valid YAML, respects the ≤3-suggestion limit, and usually confines edits to added lines, avoiding many guideline violations seen in peers.
+- **Low false-positive rate:** Tends to stay silent unless convinced of a real problem; when the diff is a pure version bump / docs tweak it often (correctly) returns an empty list, beating noisier baselines.
+- **Clear, focused patches when it fires:** In the minority of cases where it does spot a bug, it explains the issue crisply and supplies concise, copy-paste-able code snippets.
 
+Weaknesses:
 
-## Sonnet 3.7 - Model Card
+- **Very low recall:** In the vast majority of examples it misses obvious critical issues or suggests only a subset, frequently returning an empty list; this places it below most baselines on overall usefulness.
+- **Shallow coverage:** Even when it catches a defect it typically lists a single point and overlooks other high-impact problems present in the same diff.
+- **Occasional incorrect or incomplete fixes:** A non-trivial number of suggestions are wrong, compile-breaking, duplicate unchanged code, or touch out-of-scope lines, reducing trust.
+- **Inconsistent severity tagging & duplication:** Sometimes mis-labels critical vs general, repeats the same suggestion, or leaves `improved_code` blocks empty.
 
-### Comparison against GPT-4.1
+## Appendix - Example Results
 
-![Comparison](https://codium.ai/images/qodo_merge_benchmark/gpt-4.1_vs_sonnet_3.7_judge_o3.png){width=768}
+Some examples of benchmarked PRs and their results:
 
-#### Analysis Summary
+- [Example 1](https://www.qodo.ai/images/qodo_merge_benchmark/example_results1.html)
+- [Example 2](https://www.qodo.ai/images/qodo_merge_benchmark/example_results2.html)
+- [Example 3](https://www.qodo.ai/images/qodo_merge_benchmark/example_results3.html)
+- [Example 4](https://www.qodo.ai/images/qodo_merge_benchmark/example_results4.html)
 
-Model 'GPT-4.1' is safer and more compliant, preferring silence over speculation, which yields fewer rule breaches and false positives but misses some real bugs.  
-Model 'Sonnet 3.7' is more adventurous and often uncovers important issues that 'GPT-4.1' ignores, yet its aggressive style leads to frequent guideline violations and a higher proportion of incorrect or non-critical advice. 
+### Models Used for Benchmarking
 
-See raw results [here](https://github.com/Codium-ai/pr-agent-settings/blob/main/benchmark/gpt-4.1_vs_sonnet_3.7_judge_o3.md)
+The following models were used for generating the benchmark baseline:
 
-#### Detailed Analysis
+```markdown
+(1) anthropic_sonnet_3.7_v1:0
 
-'Sonnet 3.7' strengths:
-- Better bug discovery breadth: more willing to dive into logic and spot critical problems that 'GPT-4.1' overlooks; often supplies multiple, detailed fixes.  
-- Richer explanations & patches: gives fuller context and, when correct, proposes more functional or user-friendly solutions.  
-- Generally correct language/context tagging and targeted code snippets.  
+(2) claude-4-opus-20250514
 
-'Sonnet 3.7' weaknesses:
-- Guideline violations: frequently flags non-critical issues, edits untouched code, or recommends adding imports, breaching task rules.  
-- Higher error rate: suggestions are more speculative and sometimes introduce new defects or duplicate work already done.  
-- Occasional schema or formatting mistakes (missing list value, duplicated suggestions), reducing reliability.  
+(3) claude-4-sonnet-20250514
 
+(4) claude-4-sonnet-20250514_thinking_2048
 
-### Comparison against Gemini-2.5-pro-preview-05-06
+(5) gemini-2.5-flash-preview-04-17
 
-![Comparison](https://codium.ai/images/qodo_merge_benchmark/sonnet_37_vs_gemini-2.5-pro-preview-05-06_judge_o3.png){width=768}
+(6) gemini-2.5-pro-preview-05-06
 
-#### Analysis Summary
+(7) gemini-2.5-pro-preview-06-05_1024
 
-Model 'Gemini-2.5-pro-preview-05-06' is the stronger reviewer—more frequently identifies genuine, high-impact bugs and provides well-formed, actionable fixes. Model 'Sonnet 3.7' is safer against false positives and tends to be concise but often misses important defects or offers low-value or incorrect suggestions.
+(8) gemini-2.5-pro-preview-06-05_4096
 
-See raw results [here](https://github.com/Codium-ai/pr-agent-settings/blob/main/benchmark/sonnet_37_vs_gemini-2.5-pro-preview-05-06.md)
+(9) gpt-4.1
+
+(10) o3
+
+(11) o4-mini_medium
+```
+
+### Programming Languages
+
+The PR benchmark dataset includes pull requests containing code in the following programming languages:
+
+```markdown
+["Python", "JavaScript", "TypeScript", "Java", "CSharp", "PHP", "C++", "Go", "Rust", "Swift", "Kotlin", "Ruby", "Dart", "Scala"
+```
+
+Pull requests may also include non-code files such as `YAML`, `JSON`, `Markdown`, `Dockerfile` ,`Shell`, etc. 
+The benchmarked models should also analyze these files, as they commonly appear in real-world pull requests.

docs/docs/qodo-merge-cli/index.md

@@ -0,0 +1,34 @@
+# Review and Implement AI Suggestions from Your Terminal
+
+**Qodo Merge CLI** utilizes [Qodo Command](https://docs.qodo.ai/qodo-documentation/qodo-command) to bring AI-powered code suggestions directly to your terminal.
+Review, implement, and manage Qodo Merge suggestions without leaving your development environment.
+
+![Qodo Merge CLI Main Interface](https://www.qodo.ai/images/pr_agent/qm_cli_main_table_fix_all.png){width=768}
+
+## Mission
+
+The CLI can bridge the gap between Qodo Merge feedback and code implementation in your local enviroment:
+
+- **Seamlessly generate and manage PR suggestions** without context switching
+    - Remote Suggestions: Fetches Qodo Merge suggestions from your Git Environment
+    - Local Suggestions: Get real-time suggestions against your local changes
+- **Interactive review and implementation** of AI feedback directly in your terminal
+- **Track implementation status** of each suggestion (pending/implemented/declined)
+
+## Remote Suggestions Flow 
+1. Open a Pull Request on your Git environment and receive Qodo Merge feedback
+2. Pull the remote suggestions into your terminal with Qodo Merge CLI
+3. Explore, Review, and implement suggestions interactively
+4. Commit changes back to your branch seamlessly
+
+## Local Suggestions Flow
+Work in progress - coming soon!
+
+## Quick Start
+
+1. **[Install](installation.md)** Qodo Merge CLI
+2. **[Usage](usage.md)** - Navigate, explore, and implement suggestions
+
+---
+
+*Part of the Qodo Merge ecosystem - closing the loop between AI feedback and code implementation.*

docs/docs/qodo-merge-cli/installation.md

@@ -0,0 +1,70 @@
+# Installation
+
+> For remote suggestions, Qodo Merge needs to be installed and active on your Git repository (GitHub / GitLab), and provide code suggestions in a table format for your Pull Requests (PRs).
+
+## Install Qodo Command
+
+Qodo Merge CLI is a review tool within [Qodo Command](https://docs.qodo.ai/qodo-documentation/qodo-command), a command-line interface for running and managing AI agents.
+
+To use Qodo Command, you'll need first Node.js and npm installed.
+Then, to install Qodo Command, run:
+
+```bash
+npm install -g @qodo/command
+```
+
+**Login and Setup**
+
+To start using Qodo Command, you need to log in first:
+
+```bash
+qodo login
+```
+
+Once login is completed, you'll receive an API key in the terminal.
+The API key is also saved locally in the .qodo folder in your home directory, and can be reused (e.g., in CI).
+The key is tied to your user account and subject to the same usage limits.
+
+
+## Using Qodo Merge CLI
+
+After you set up Qodo Command, you can start using Qodo Merge CLI by running:
+
+```bash
+qodo merge
+```
+### Set Up Git Client
+On first run, the CLI will check for your Git client (GitHub CLI or GitLab CLI).
+If not found, it will guide you through the installation process.
+
+![GH Installation](https://www.qodo.ai/images/pr_agent/qm_cli_gh_install_prompt.png){width=384}
+
+
+## Quick Usage
+
+There are two ways to specify which PR to review:
+
+(1) **Auto Detect PR from current branch**
+run this command in your CLI:
+
+```bash
+qodo merge
+```
+
+(2) **Specify PR number or URL**
+
+```bash
+qodo merge 303
+
+qodo merge https://github.com/owner/repo/pull/303
+```
+
+Then the tool will automatically fetch the suggestions from the PR and display them in an interactive table.
+
+![Fix All Mode](https://www.qodo.ai/images/pr_agent/qm_cli_main_table_fix_all.png){width=768}
+
+
+## Next Steps
+
+**[Usage](usage.md)** - Navigate, explore, and implement suggestions
+

docs/docs/qodo-merge-cli/usage.md

@@ -0,0 +1,211 @@
+# Usage Guide for Qodo Merge CLI
+
+
+## Understanding the Interface
+
+### Why a Structured Table?
+
+The suggestions table serves as the core interface for reviewing and managing AI feedback.
+
+The table provides a structured overview of all suggestions with key metadata.
+Users can efficiently prioritize, explore, and implement suggestions through an intuitive workflow.
+
+The interface guides you from high-level overviews to detailed implementation context.
+This consistent user-friendly structure streamlines the review process, reducing time from feedback to implementation.
+
+![Fix All Mode](https://www.qodo.ai/images/pr_agent/qm_cli_main_table_fix_all.png){width=768}
+
+
+
+### Navigation Instructions
+Use `↑`/`↓` to navigate suggestions, `Enter` to implement, `Space` for multi-select, and `ESC` to exit.
+
+The table includes:
+
+- **Selection** (`○`/`◉`): Multi-selection mode
+- **Category**: Security, Performance, General, etc.
+- **Impact**: High, Medium, Low importance
+- **Suggestion**: Brief description
+- **Status**: `✓` implemented, `✗` declined, blank = pending
+- **Detail Panel** (if wide enough): Full suggestion text, affected files, impact analysis
+
+## Flow
+
+### Explore the suggestions
+
+You can explore the suggestions in detail before implementing them.
+You can view the proposed code changes in a diff format, jump to the relevant code in your IDE, or chat about any suggestion for clarification.
+
+!!! note "Exploring the suggestions"
+
+[//]: # (    === "Details Panel")
+
+[//]: # ()
+[//]: # (        ![Detail Panel](https://www.qodo.ai/images/pr_agent/qm_cli_tabl_detail_view.png){width=768})
+
+[//]: # (        )
+[//]: # (        **Enhanced Layout (≥120 columns)**)
+
+[//]: # (        )
+[//]: # (        - **Detail Panel**: Extended information for selected suggestions)
+
+[//]: # (        - **File Information**: Affected files and line ranges)
+
+[//]: # (        - **Complete Description**: Full suggestion explanation)
+
+[//]: # (        - **Impact Assessment**: Detailed importance analysis)
+
+    === "Diff View (`D/S`)"
+        === "Unified Diff View (`D`)"
+
+            ![Unified Diff](https://www.qodo.ai/images/pr_agent/qm_cli_unified_diffview.png){width=768}
+            
+            - Press `D` to view proposed code changes
+            - Standard unified diff format with line numbers
+            - Syntax highlighting for additions/removals
+            - `↑`/`↓` to scroll through changes
+
+        === "Side-by-Side View (`S`)"
+
+            ![Side-by-Side Diff](https://www.qodo.ai/images/pr_agent/qm_cli_side_by_side_diffview.png){width=768}
+            
+            - Press `S` for side-by-side diff view
+            - Enhanced layout for complex changes
+            - Better context understanding
+            - Clear before/after comparison
+
+    === "Jump to Code (`O`)"
+
+        **IDE Integration**
+        
+        - Press `O` to open the suggestion's source file in your IDE
+        - Supports all major IDEs when terminal is running inside them
+        - Direct navigation to relevant code location
+        - Seamless transition between CLI and editor
+
+    === "Chat (`C`)"
+
+        **Suggestion-Specific Discussion**
+        
+        ![Chat Interface](https://www.qodo.ai/images/pr_agent/qm_cli_suggestion_chat_pre_impl.png){width=768}
+        
+        - Press `C` to discuss the current suggestion
+        - Context automatically included (files, lines, description)
+        - Ask questions, request modifications
+        - `Ctrl+J` for new lines, `ESC` to return
+
+
+### Implement
+
+You can implement a single suggestion, multiple selected suggestions, or all suggestions at once. You can also chat about any suggestion before implementing it.
+
+!!! note "Multiple implementation modes available"
+
+    === "1. Single Suggestion"
+        ![Main Table](https://www.qodo.ai/images/pr_agent/qm_cli_tabl_detail_view.png){width=768}
+        
+        **Direct individual implementation**
+    
+        1. Navigate to any specific suggestion
+        2. Press `Enter` to implement just that suggestion
+
+    === "2. Multi-Select"
+        ![Multi-Selection](https://www.qodo.ai/images/pr_agent/qm_cli_multi_select.png){width=768}
+        
+        **Select multiple related suggestions**
+        
+        1. Use `Space` to select specific suggestions (◉)
+        2. Navigate and select multiple related suggestions
+        3. Press `Enter` on any selected suggestion to start implementation
+        4. AI implements selected suggestions together
+    
+    === "3. Address All"
+        ![Fix All Mode](https://www.qodo.ai/images/pr_agent/qm_cli_main_table_fix_all.png){width=768}
+        
+        **Reflect and address all suggestions (Always available as first row)**
+        
+        1. Press `Enter` on the first row "Reflect and address all suggestions"
+        2. AI implements all suggestions simultaneously and intelligently
+        3. Handles conflicts and dependencies automatically
+        4. Review the comprehensive summary
+    
+    === "4. Chat then Implement"
+    
+        ![Chat Interface](https://www.qodo.ai/images/pr_agent/qm_cli_suggestion_chat_pre_impl.png){width=768}
+    
+        **Discuss then implement**
+    
+        1. Press `C` on any suggestion to start a chat
+        2. Ask questions, request modifications, get clarifications
+        3. Once satisfied, request implementation via chat
+        4. AI implements based on your discussion
+
+___
+
+#### Implementation Summary
+
+After the AI completes the implementation, you receive a **structured output** showing detailed results for each suggestion:
+
+- **Status**: `✓ IMPLEMENTED`, `SKIPPED`, or `✗ REJECTED`
+- **Suggestion**: Brief description of what was addressed
+- **Reasoning**: Explanation of the implementation approach
+- **Changes**: Summary of code modifications made
+
+![Next Actions](https://www.qodo.ai/images/pr_agent/qm_cli_impl_success_next_actions.png){width=768}
+
+Each suggestion gets its own implementation summary, providing full transparency into what was done and why.
+
+### Finalize
+
+After implementing the suggestions, you have several options to proceed:
+
+!!! note "Post Implementation Actions"
+    === "Return to Table (`ESC`)"
+    
+        ![Status Updates](https://www.qodo.ai/images/pr_agent/qm_cli_suggestion_status_update_add_v_sign.png){width=768}
+        
+        The first option returns you to the main table where you can see:
+        
+        - **Updated Status**: Implemented suggestions now show `✓` green checkmark
+          - **Real-time Updates**: Status changes reflect immediately
+          - **Continue Workflow**: Handle remaining pending suggestions
+    
+    === "Continue Chatting (`C`)"
+    
+        ![Continue Chat](https://www.qodo.ai/images/pr_agent/qm_cli_continue_chat.png){width=768}
+        
+        Discuss the implementation details:
+        
+        - Review changes made by the AI
+        - Request refinements or modifications
+        - Get explanations of implementation approach
+        - Continuous improvement cycle
+    
+    === "Commit Changes (`M`)"
+    
+        ![Commit Message](https://www.qodo.ai/images/pr_agent/qm_cli_commit_message.png){width=512}
+        
+        Auto-generate commit messages:
+        
+        - AI-generated commit messages based on changes
+        - Editable before committing
+        - Standard git conventions
+        - Seamless workflow integration
+    
+    === "Open Edited File (`O`)"
+    
+        Open the implemented code directly in your IDE:
+        
+        - View the exact changes made
+        - See implementation in full context
+        - Continue development seamlessly
+        - Integrated with your existing workflow
+
+## Tips for Success
+
+- **Start with "Fix All"** to let AI handle everything intelligently
+- **Use Chat liberally** - ask questions about unclear suggestions
+- **Decline appropriately** - press `X` and provide reasons for inappropriate suggestions
+- **Multi-select strategically** - group related suggestions together
+
+---

docs/docs/recent_updates/index.md

@@ -1,21 +1,24 @@
 # Recent Updates and Future Roadmap
 
-`Page last updated: 2025-05-11`
 
-This page summarizes recent enhancements to Qodo Merge (last three months).
+This page summarizes recent enhancements to Qodo Merge.
 
 It also outlines our development roadmap for the upcoming three months. Please note that the roadmap is subject to change, and features may be adjusted, added, or reprioritized.
 
 === "Recent Updates"
-    - **Chat on Suggestions**:  Users can now chat with Qodo Merge code suggestions ([Learn more](https://qodo-merge-docs.qodo.ai/tools/improve/#chat-on-code-suggestions))
-    - **Scan Repo Discussions Tool**: A new tool that analyzes past code discussions to generate a `best_practices.md` file, distilling key insights and recommendations. ([Learn more](https://qodo-merge-docs.qodo.ai/tools/scan_repo_discussions/))
-    - **Enhanced Models**: Qodo Merge now defaults to a combination of top models (Claude Sonnet 3.7 and Gemini 2.5 Pro) and incorporates dedicated code validation logic for improved results. ([Details 1](https://qodo-merge-docs.qodo.ai/usage-guide/qodo_merge_models/), [Details 2](https://qodo-merge-docs.qodo.ai/core-abilities/code_validation/))
-    - **Chrome Extension Update**: Qodo Merge Chrome extension now supports single-tenant users. ([Learn more](https://qodo-merge-docs.qodo.ai/chrome-extension/options/#configuration-options/))
-    - **Help Docs Tool**: The help_docs tool can answer free-text questions based on any git documentation folder. ([Learn more](https://qodo-merge-docs.qodo.ai/tools/help_docs/))
+    | Date | Feature | Description |
+    |---|---|---|
+    | 2025-09-17 | **Qodo Merge CLI** | A new command-line interface for Qodo Merge, enabling developers to implement code suggestions directly in your terminal. ([Learn more](https://qodo-merge-docs.qodo.ai/qodo-merge-cli/)) |
+    | 2025-09-12 | **Repo Metadata** | You can now add metadata from files like `AGENTS.md`, which will be applied to all PRs in that repository. ([Learn more](https://qodo-merge-docs.qodo.ai/usage-guide/additional_configurations/#bringing-additional-repository-metadata-to-qodo-merge)) |
+    | 2025-08-11 | **RAG support for GitLab** | All Qodo Merge RAG features are now available in GitLab. ([Learn more](https://qodo-merge-docs.qodo.ai/core-abilities/rag_context_enrichment/)) |
+    | 2025-07-29 | **High-level Suggestions** | Qodo Merge now also provides high-level code suggestion for PRs. ([Learn more](https://qodo-merge-docs.qodo.ai/core-abilities/high_level_suggestions/)) |
+    | 2025-07-20 | **PR to Ticket** | Generate tickets in your tracking systems based on PR content. ([Learn more](https://qodo-merge-docs.qodo.ai/tools/pr_to_ticket/)) |
+    | 2025-07-17 | **Compliance** | Comprehensive compliance checks for security, ticket requirements, and custom organizational rules. ([Learn more](https://qodo-merge-docs.qodo.ai/tools/compliance/)) |
+    | 2025-06-21 | **Mermaid Diagrams** | Qodo Merge now generates by default Mermaid diagrams for PRs, providing a visual representation of code changes. ([Learn more](https://qodo-merge-docs.qodo.ai/tools/describe/#sequence-diagram-support)) |
+    | 2025-06-11 | **Best Practices Hierarchy** | Introducing support for structured best practices, such as for folders in monorepos or a unified best practice file for a group of repositories. ([Learn more](https://qodo-merge-docs.qodo.ai/tools/improve/#global-hierarchical-best-practices)) |
+    | 2025-06-01 | **CLI Endpoint** | A new Qodo Merge endpoint that accepts a lists of before/after code changes, executes Qodo Merge commands, and return the results. Currently available for enterprise customers. Contact [Qodo](https://www.qodo.ai/contact/) for more information. |
 
 === "Future Roadmap"
-    - **Smart Update**: Upon PR updates, Qodo Merge will offer tailored code suggestions, addressing both the entire PR and the specific incremental changes since the last feedback.
-    - **CLI Endpoint**: A new Qodo Merge endpoint will accept lists of before/after code changes, execute Qodo Merge commands, and return the results.
-    - **Simplified Free Tier**: We plan to transition from a two-week free trial to a free tier offering a limited number of suggestions per month per organization.
-    - **Best Practices Hierarchy**: Introducing support for structured best practices, such as for folders in monorepos or a unified best practice file for a group of repositories.
-    - **Installation Metrics**: Upon installation, Qodo Merge will analyze past PRs for key metrics (e.g., time to merge, time to first reviewer feedback), enabling pre/post-installation comparison to calculate ROI.
+    - **`Compliance` tool to replace `review` as default**: Planning to make the `compliance` tool the default automatic command instead of the current `review` tool.
+    - **Smarter context retrieval**: Leverage AST and LSP analysis to gather relevant context from across the entire repository.
+    - **Enhanced portal experience**: Improved user experience in the Qodo Merge portal with new options and capabilities.

docs/docs/summary.md

@@ -0,0 +1,84 @@
+# Table of contents
+
+* [Overview](index.md)
+  * [💎 Qodo Merge](overview/pr_agent_pro.md)
+  * [Data Privacy](overview/data_privacy.md)
+
+## Installation
+
+* [Installation](installation/index.md)
+* [PR-Agent](installation/pr_agent.md)
+* [💎 Qodo Merge](installation/qodo_merge.md)
+
+## Usage Guide
+
+* [Usage Guide](usage-guide/index.md)
+* [Introduction](usage-guide/introduction.md)
+* [Enabling a Wiki](usage-guide/enabling_a_wiki.md)
+* [Configuration File](usage-guide/configuration_options.md)
+* [Usage and Automation](usage-guide/automations_and_usage.md)
+* [Managing Mail Notifications](usage-guide/mail_notifications.md)
+* [Changing a Model](usage-guide/changing_a_model.md)
+* [Additional Configurations](usage-guide/additional_configurations.md)
+* [Frequently Asked Questions](faq/index.md)
+* [Qodo Merge Models](usage-guide/qodo_merge_models.md)
+
+## Tools
+
+* [Tools](tools/index.md)
+* [Describe](tools/describe.md)
+* [Review](tools/review.md)
+* [Improve](tools/improve.md)
+* [Ask](tools/ask.md)
+* [Help](tools/help.md)
+* [Help Docs](tools/help_docs.md)
+* [Update Changelog](tools/update_changelog.md)
+* [💎 Add Documentation](tools/documentation.md)
+* [💎 Analyze](tools/analyze.md)
+* [💎 CI Feedback](tools/ci_feedback.md)
+* [💎 Compliance](tools/compliance.md)
+* [💎 Custom Prompt](tools/custom_prompt.md)
+* [💎 Generate Labels](tools/custom_labels.md)
+* [💎 Generate Tests](tools/test.md)
+* [💎 Implement](tools/implement.md)
+* [💎 Improve Components](tools/improve_component.md)
+* [💎 PR to Ticket](tools/pr_to_ticket.md)
+* [💎 Scan Repo Discussions](tools/scan_repo_discussions.md)
+* [💎 Similar Code](tools/similar_code.md)
+
+## Core Abilities
+
+* [Core Abilities](core-abilities/index.md)
+* [Auto approval](core-abilities/auto_approval.md)
+* [Auto best practices](core-abilities/auto_best_practices.md)
+* [Chat on code suggestions](core-abilities/chat_on_code_suggestions.md)
+* [Chrome extension](chrome-extension/index.md)
+* [Code validation](core-abilities/code_validation.md)
+* [Dynamic context](core-abilities/dynamic_context.md)
+* [Fetching ticket context](core-abilities/fetching_ticket_context.md)
+* [High-level Suggestions](core-abilities/high_level_suggestions.md)
+* [Impact evaluation](core-abilities/impact_evaluation.md)
+* [Incremental Update](core-abilities/incremental_update.md)
+* [Interactivity](core-abilities/interactivity.md)
+* [Local and global metadata](core-abilities/metadata.md)
+* [RAG context enrichment](core-abilities/rag_context_enrichment.md)
+* [Self-reflection](core-abilities/self_reflection.md)
+* [Static code analysis](core-abilities/static_code_analysis.md)
+
+## Qodo Merge CLI
+
+* [Overview](qodo-merge-cli/index.md)
+* [Installation](qodo-merge-cli/installation.md)
+* [Usage](qodo-merge-cli/usage.md)
+
+## PR Benchmark
+
+* [PR Benchmark](pr_benchmark/index.md)
+
+## Recent Updates
+
+* [Recent Updates](recent_updates/index.md)
+
+## AI Docs Search
+
+* [AI Docs Search](ai_search/index.md)

docs/docs/tools/analyze.md

@@ -16,5 +16,5 @@ An example result:
 
 ![Analyze 1](https://codium.ai/images/pr_agent/analyze_1.png){width=750}
 
-!!! note "Language that are currently supported:"
-    Python, Java, C++, JavaScript, TypeScript, C#.
+!!! note "Languages that are currently supported:"
+    Python, Java, C++, JavaScript, TypeScript, C#, Go, Kotlin

docs/docs/tools/compliance.md

@@ -0,0 +1,375 @@
+`Platforms supported: GitHub, GitLab, Bitbucket`
+
+## Overview
+
+The `compliance` tool performs comprehensive compliance checks on PR code changes, validating them against security standards, ticket requirements, and custom organizational compliance checklists, thereby helping teams, enterprises, and agents maintain consistent code quality and security practices while ensuring that development work aligns with business requirements.
+
+=== "Fully Compliant"
+    ![compliance_overview](https://codium.ai/images/pr_agent/compliance_full.png){width=512}
+
+=== "Partially Compliant"
+    ![compliance_overview](https://codium.ai/images/pr_agent/compliance_partial.png){width=512}
+
+___
+
+[//]: # (???+ note "The following features are available only for Qodo Merge 💎 users:")
+
+[//]: # (    - Custom compliance checklists and hierarchical compliance checklists)
+
+[//]: # (    - Ticket compliance validation with Jira/Linear integration)
+
+[//]: # (    - Auto-approval based on compliance status)
+
+[//]: # (    - Compliance labels and automated enforcement)
+
+## Example Usage
+
+### Manual Triggering
+
+Invoke the tool manually by commenting `/compliance` on any PR. The compliance results are presented in a comprehensive table:
+
+To edit [configurations](#configuration-options) related to the `compliance` tool, use the following template:
+
+```toml
+/compliance --pr_compliance.some_config1=... --pr_compliance.some_config2=...
+```
+
+For example, you can enable ticket compliance labels by running:
+
+```toml
+/compliance --pr_compliance.enable_ticket_labels=true
+```
+
+### Automatic Triggering
+
+
+The tool can be triggered automatically every time a new PR is [opened](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/#github-app-automatic-tools-when-a-new-pr-is-opened), or in a [push](https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage/?h=push#github-app-automatic-tools-for-push-actions-commits-to-an-open-pr) event to an existing PR.
+
+To run the `compliance` tool automatically when a PR is opened, define the following in the [configuration file](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/):
+
+```toml
+[github_app]  # for example
+pr_commands = [
+    "/compliance",
+    ...
+]
+
+```
+
+## Compliance Categories
+
+The compliance tool evaluates three main categories:
+
+
+### 1. Security Compliance
+
+Scans for security vulnerabilities and potential exploits in the PR code changes:
+
+- **Verified Security Concerns** 🔴: Clear security vulnerabilities that require immediate attention
+- **Possible Security Risks** ⚪: Potential security issues that need human verification
+- **No Security Concerns** 🟢: No security vulnerabilities detected
+
+Examples of security issues:
+
+- Exposure of sensitive information (API keys, passwords, secrets)
+- SQL injection vulnerabilities
+- Cross-site scripting (XSS) risks
+- Cross-site request forgery (CSRF) vulnerabilities
+- Insecure data handling patterns
+
+
+### 2. Ticket Compliance
+
+???+ tip "How to set up ticket compliance"
+    Follow the guide on how to set up [ticket compliance](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/) with Qodo Merge.
+
+???+ tip "Auto-create ticket"
+    Follow this [guide](https://qodo-merge-docs.qodo.ai/tools/pr_to_ticket/) to learn how to enable triggering `create tickets` based on PR content.
+    
+    ![ticket creation via compliance tool](https://codium.ai/images/pr_agent/ticket_creation_from_compliance1.png){width=256}
+ 
+
+Validates that PR changes fulfill the requirements specified in linked tickets:
+
+- **Fully Compliant** 🟢: All ticket requirements are satisfied
+- **Partially Compliant** 🟡: Some requirements are met, others need attention
+- **Not Compliant** 🔴: Clear violations of ticket requirements
+- **Requires Verification** ⚪: Requirements that need human review
+
+
+### 3. RAG Code Duplication Compliance
+
+???+ tip "Learn more about RAG"
+    For detailed information about RAG context enrichment, see the [RAG Context Enrichment guide](../core-abilities/rag_context_enrichment.md).
+
+Analyzes code changes using RAG endpoint to detect potential code duplication from the codebase:
+
+- **Fully Compliant** 🟢: No code duplication found
+- **Not Compliant** 🔴: Full code duplication found
+- **Requires Verification** ⚪: Near code duplication 
+
+
+### 4. Custom Compliance
+
+Validates against an organization-specific compliance checklist:
+
+- **Fully Compliant** 🟢: All custom compliance are satisfied
+- **Not Compliant** 🔴: Violations of custom compliance
+- **Requires Verification** ⚪: Compliance that need human assessment
+
+## Custom Compliance
+
+### Setting Up Custom Compliance
+
+Each compliance is defined in a YAML file as follows:
+
+- `title` (required): A clear, descriptive title that identifies what is being checked
+- `compliance_label` (required): Determines whether this compliance generates labels for non-compliance issues (set to `true` or `false`)
+- `objective` (required): A detailed description of the goal or purpose this compliance aims to achieve
+- `success_criteria` and `failure_criteria` (at least one required; both recommended): Define the conditions for compliance
+
+
+???+ tip "Example of a compliance checklist"
+
+    ```yaml
+    # pr_compliance_checklist.yaml
+    pr_compliances:
+      - title: "Error Handling"
+        compliance_label: true
+        objective: "All external API calls must have proper error handling"
+        success_criteria: "Try-catch blocks around external calls with appropriate logging"
+        failure_criteria: "External API calls without error handling or logging"
+      
+    ...
+    ```
+
+???+ tip "Writing effective compliance checklists"
+    - Avoid overly complex or subjective compliances that are hard to verify
+    - Keep compliances focused on security, business requirements, and critical standards
+    - Use clear, actionable language that developers can understand
+    - Focus on meaningful compliance requirements, not style preferences
+
+???+ tip "Ready-to-use compliance templates"
+    For production-ready compliance checklist templates organized by programming languages and technology stacks, check out the [PR Compliance Templates repository](https://github.com/qodo-ai/pr-compliance-templates).
+
+### Local Compliance Checklists
+
+For basic usage, create a `pr_compliance_checklist.yaml` file in your repository's root directory containing the compliance requirements specific to your repository.
+
+The AI model will use this `pr_compliance_checklist.yaml` file as a reference, and if the PR code violates any of the compliance requirements, it will be shown in the compliance tool's comment.
+
+### Global Hierarchical Compliance
+
+Qodo Merge supports hierarchical compliance checklists using a dedicated global configuration repository.
+
+#### Setting up global hierarchical compliance
+
+1\. Create a new repository named `pr-agent-settings` in your organization or workspace.
+
+2\. Build the folder hierarchy in your `pr-agent-settings` repository:
+
+```bash
+pr-agent-settings/
+├── metadata.yaml                              # Maps repos/folders to compliance paths
+└── codebase_standards/                        # Root for all compliance definitions
+    ├── global/                                # Global compliance, inherited widely
+    │   └── pr_compliance_checklist.yaml
+    ├── groups/                                # For groups of repositories
+    │   ├── frontend_repos/
+    │   │   └── pr_compliance_checklist.yaml
+    │   ├── backend_repos/
+    │   │   └── pr_compliance_checklist.yaml
+    │   ├── python_repos/
+    │   │   └── pr_compliance_checklist.yaml
+    │   ├── cpp_repos/
+    │   │   └── pr_compliance_checklist.yaml
+    │   └── ...
+    ├── repo_a/                                # For standalone repositories
+    │   └── pr_compliance_checklist.yaml
+    ├── monorepo-name/                         # For monorepo-specific compliance
+    │   ├── pr_compliance_checklist.yaml       # Root-level monorepo compliance
+    │   ├── service-a/                         # Subproject compliance
+    │   │   └── pr_compliance_checklist.yaml
+    │   └── service-b/                         # Another subproject
+    │       └── pr_compliance_checklist.yaml
+    └── ...                                    # More repositories
+```
+
+> **Note:** In this structure, `pr-agent-settings`, `codebase_standards`, `global`, `groups`, `metadata.yaml`, and `pr_compliance_checklist.yaml` are hardcoded names that must be used exactly as shown. All other names (such as `frontend_repos`, `backend_repos`, `repo_a`, `monorepo-name`, `service-a`, etc.) are examples and should be replaced with your actual repository and service names.
+
+???+ tip "Grouping and categorizing compliance checklists"
+    - Each folder (including the global folder) can contain a single `pr_compliance_checklist.yaml` file
+    - Organize repository compliance checklists by creating subfolders within the `groups` folder. Group them by purpose, programming languages, or other categories
+
+3\. Define the metadata file `metadata.yaml` in the root of `pr-agent-settings`:
+
+```yaml
+# Standalone repos
+repo_a:
+  pr_compliance_checklist_paths:
+    - "repo_a"
+
+# Group-associated repos
+repo_b:
+  pr_compliance_checklist_paths:
+    - "groups/backend_repos"
+
+# Multi-group repos
+repo_c:
+  pr_compliance_checklist_paths:
+    - "groups/frontend_repos"
+    - "groups/backend_repos"
+
+# Monorepo with subprojects
+monorepo-name:
+  pr_compliance_checklist_paths:
+    - "monorepo-name"
+  monorepo_subprojects:
+    service-a:
+      pr_compliance_checklist_paths:
+        - "monorepo-name/service-a"
+    service-b:
+      pr_compliance_checklist_paths:
+        - "monorepo-name/service-b"
+```
+
+4\. Set the following configuration:
+
+```toml
+[pr_compliance]
+enable_global_pr_compliance = true
+```
+
+???- info "Compliance checklist loading strategy"
+
+    1. **Global Checklists**: Hierarchical compliance from `pr-agent-settings` repository
+    
+        1.1 If the repository is mapped in `metadata.yaml`, it uses the specified paths and the global compliance checklist
+        
+        1.2 For monorepos, it automatically collects compliance checklists matching PR file paths
+        
+        1.3 If the repository is not mapped in `metadata.yaml`, global checklists are not loaded
+
+    2. **Local Repository Checklist**: `pr_compliance_checklist.yaml` file in the repository
+    
+        2.1 Loaded if present in the repository
+        
+        2.2 Content is merged with global checklists (if loaded) to create the final compliance checklist
+
+
+## Configuration Options
+
+???+ example "General options"
+
+    <table>
+      <tr>
+        <td><b>extra_instructions</b></td>
+        <td>Optional extra instructions for the tool. For example: "Ensure that all error-handling paths in the code contain appropriate logging statements". Default is empty string.</td>
+      </tr>
+      <tr>
+        <td><b>persistent_comment</b></td>
+        <td>If set to true, the compliance comment will be persistent, meaning that every new compliance request will edit the previous one. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_user_defined_compliance_labels</b></td>
+        <td>If set to true, the tool will add the label `Failed compliance check` for custom compliance violations. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_estimate_effort_to_review</b></td>
+        <td>If set to true, the tool will estimate the effort required to review the PR (1-5 scale) as a label. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_todo_scan</b></td>
+        <td>If set to true, the tool will scan for TODO comments in the PR code. Default is false.</td>
+      </tr>
+      <tr>
+        <td><b>enable_update_pr_compliance_checkbox</b></td>
+        <td>If set to true, the tool will add an update checkbox to refresh compliance status following push events. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_help_text</b></td>
+        <td>If set to true, the tool will display help text in the comment. Default is false.</td>
+      </tr>
+    </table>
+
+???+ example "Section visibility options"
+
+    <table>
+      <tr>
+        <td><b>enable_security_section</b></td>
+        <td>If set to true, the security compliance section will be displayed in the output. When false, the entire security section is hidden. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_ticket_section</b></td>
+        <td>If set to true, the ticket compliance section will be displayed in the output. When false, the entire ticket section is hidden. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_codebase_duplication_section</b></td>
+        <td>If set to true, the codebase duplication compliance section will be displayed in the output. When false, the entire codebase duplication section is hidden. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_custom_compliance_section</b></td>
+        <td>If set to true, the custom compliance section will be displayed in the output. When false, the entire custom section is hidden. Default is true.</td>
+      </tr>
+    </table>
+
+???+ example "Security compliance options"
+
+    <table>
+      <tr>
+        <td><b>enable_security_compliance</b></td>
+        <td>If set to true, the tool will check for security vulnerabilities. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_compliance_labels_security</b></td>
+        <td>If set to true, the tool will add a `Possible security concern` label to the PR when security-related concerns are detected. Default is true.</td>
+      </tr>
+    </table>
+
+???+ example "Ticket compliance options"
+
+    <table>
+      <tr>
+        <td><b>require_ticket_analysis_review</b></td>
+        <td>If set to true, the tool will fetch and analyze ticket context for compliance validation. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>enable_ticket_labels</b></td>
+        <td>If set to true, the tool will add ticket compliance labels to the PR. Default is false.</td>
+      </tr>
+      <tr>
+        <td><b>enable_no_ticket_labels</b></td>
+        <td>If set to true, the tool will add a label when no ticket is found. Default is false.</td>
+      </tr>
+      <tr>
+        <td><b>check_pr_additional_content</b></td>
+        <td>If set to true, the tool will check if the PR contains content not related to the ticket. Default is false.</td>
+      </tr>
+    </table>
+
+???+ example "Generic custom compliance checklist options"
+
+    <table>
+      <tr>
+        <td><b>enable_generic_custom_compliance_checklist</b></td>
+        <td>If set to true, the tool will apply generic custom compliance checklist rules. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>persist_generic_custom_compliance_checklist</b></td>
+        <td>If set to false, generic compliance checklist will not be kept with custom compliance. Default is false.</td>
+      </tr>
+    </table>
+
+
+## Usage Tips
+
+### Blocking PRs Based on Compliance
+
+!!! tip ""
+    You can configure CI/CD Actions to prevent merging PRs with specific compliance labels:
+    
+    - `Possible security concern` - Block PRs with potential security issues
+    - `Failed compliance check` - Block PRs that violate custom compliance checklists
+    
+    Implement a dedicated [GitHub Action](https://medium.com/sequra-tech/quick-tip-block-pull-request-merge-using-labels-6cc326936221) to enforce these checklists.
+

docs/docs/tools/custom_labels.md

@@ -1,3 +1,5 @@
+`Platforms supported: GitHub, GitLab`
+
 ## Overview
 
 The `generate_labels` tool scans the PR code changes, and given a list of labels and their descriptions, it automatically suggests labels that match the PR code changes.
@@ -66,3 +68,7 @@ description = "Description of when AI should suggest this label"
 [custom_labels."Custom Label 2"]
 description = "Description of when AI should suggest this label 2"
 ```
+
+???+ tip "Auto-remove custom label when no longer relevant"
+    If the custom label is no longer relevant, it will be automatically removed from the PR by running the `generate_labels` tool or the `describe` tool.
+

docs/docs/tools/describe.md

@@ -47,18 +47,45 @@ publish_labels = true
 
 ## Preserving the original user description
 
-By default, Qodo Merge preserves your original PR description by placing it above the generated content.
+By default, Qodo Merge tries to preserve your original PR description by placing it above the generated content.
 This requires including your description during the initial PR creation.
-Be aware that if you edit the description while the automated tool is running, a race condition may occur, potentially causing your original description to be lost.
 
-When updating PR descriptions, the `/describe` tool considers everything above the "PR Type" field as user content and will preserve it.
+"Qodo removed the original description from the PR. Why"?
+
+From our experience, there are two possible reasons:
+
+- If you edit the description _while_ the automated tool is running, a race condition may occur, potentially causing your original description to be lost. Hence, create a description before launching the PR.
+
+- When _updating_ PR descriptions, the `/describe` tool considers everything above the "PR Type" field as user content and will preserve it.
 Everything below this marker is treated as previously auto-generated content and will be replaced.
 
 ![Describe comment](https://codium.ai/images/pr_agent/pr_description_user_description.png){width=512}
 
+## Sequence Diagram Support 
+The `/describe` tool includes a Mermaid sequence diagram showing component/function interactions. 
+
+This option is enabled by default via the `pr_description.enable_pr_diagram` param.
+
+
+[//]: # (### How to enable\disable)
+
+[//]: # ()
+[//]: # (In your configuration:)
+
+[//]: # ()
+[//]: # (```)
+
+[//]: # (toml)
+
+[//]: # ([pr_description])
+
+[//]: # (enable_pr_diagram = true)
+
+[//]: # (```)
+
 ## Configuration options
 
-!!! example "Possible configurations"
+???+ example "Possible configurations"
 
     <table>
       <tr>
@@ -91,24 +118,36 @@ Everything below this marker is treated as previously auto-generated content and
       </tr>
       <tr>
         <td><b>final_update_message</b></td>
-        <td>If set to true, it will add a comment message [`PR Description updated to latest commit...`](https://github.com/Codium-ai/pr-agent/pull/499#issuecomment-1837412176) after finishing calling `/describe`. Default is false.</td>
+        <td>If set to true, it will add a comment message [`PR Description updated to latest commit...`](https://github.com/Codium-ai/pr-agent/pull/499#issuecomment-1837412176) after finishing calling `/describe`. Default is true.</td>
       </tr>
       <tr>
         <td><b>enable_semantic_files_types</b></td>
         <td>If set to true, "Changes walkthrough" section will be generated. Default is true.</td>
       </tr>
+      <tr>
+            <td><b>file_table_collapsible_open_by_default</b></td>
+            <td>If set to true, the file list in the "Changes walkthrough" section will be open by default. If set to false, it will be closed by default. Default is false.</td>
+      </tr>
       <tr>
         <td><b>collapsible_file_list</b></td>
         <td>If set to true, the file list in the "Changes walkthrough" section will be collapsible. If set to "adaptive", the file list will be collapsible only if there are more than 8 files. Default is "adaptive".</td>
       </tr>
       <tr>
-        <td><b>enable_large_pr_handling</b></td>
-        <td>Pro feature. If set to true, in case of a large PR the tool will make several calls to the AI and combine them to be able to cover more files. Default is true.</td>
+        <td><b>enable_large_pr_handling 💎</b></td>
+        <td>If set to true, in case of a large PR the tool will make several calls to the AI and combine them to be able to cover more files. Default is true.</td>
       </tr>
       <tr>
         <td><b>enable_help_text</b></td>
         <td>If set to true, the tool will display a help text in the comment. Default is false.</td>
       </tr>
+      <tr>
+        <td><b>enable_pr_diagram</b></td>
+        <td>If set to true, the tool will generate a horizontal Mermaid flowchart summarizing the main pull request changes. This field remains empty if not applicable. Default is true.</td>
+      </tr>
+      <tr>
+        <td><b>auto_create_ticket</b></td>
+        <td>If set to true, this will <a href="https://qodo-merge-docs.qodo.ai/tools/pr_to_ticket/">automatically create a ticket</a> in the ticketing system when a PR is opened. Default is false.</td>
+      </tr>
     </table>
 
 ## Inline file summary 💎
@@ -151,9 +190,12 @@ pr_agent:summary
 
 ## PR Walkthrough:
 pr_agent:walkthrough
+
+## PR Diagram:
+pr_agent:diagram
 ```
 
-The marker `pr_agent:type` will be replaced with the PR type, `pr_agent:summary` will be replaced with the PR summary, and `pr_agent:walkthrough` will be replaced with the PR walkthrough.
+The marker `pr_agent:type` will be replaced with the PR type, `pr_agent:summary` will be replaced with the PR summary, `pr_agent:walkthrough` will be replaced with the PR walkthrough, and `pr_agent:diagram` will be replaced with the sequence diagram (if enabled).
 
 ![Describe markers before](https://codium.ai/images/pr_agent/describe_markers_before.png){width=512}
 
@@ -165,6 +207,7 @@ becomes
 
 - `use_description_markers`: if set to true, the tool will use markers template. It replaces every marker of the form `pr_agent:marker_name` with the relevant content. Default is false.
 - `include_generated_by_header`: if set to true, the tool will add a dedicated header: 'Generated by PR Agent at ...' to any automatic content. Default is true.
+- `diagram`: if present as a marker, will be replaced by the PR sequence diagram (if enabled).
 
 ## Custom labels
 
@@ -176,6 +219,10 @@ Custom labels can be defined in a [configuration file](https://qodo-merge-docs.q
 Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.
 Each label description should be a **conditional statement**, that indicates if to add the label to the PR or not, according to the PR content.
 
+???+ tip "Auto-remove custom label when no longer relevant"
+    If the custom label is no longer relevant, it will be automatically removed from the PR by running the `generate_labels` tool or the `describe` tool.
+
+
 ### Handle custom labels from a configuration file
 
 Example for a custom labels configuration setup in a configuration file:

docs/docs/tools/documentation.md

@@ -26,11 +26,31 @@ You can state a name of a specific component in the PR to get documentation only
 /add_docs component_name
 ```
 
+## Manual triggering
+
+Comment `/add_docs` on a PR to invoke it manually.
+
+## Automatic triggering
+
+To automatically run the `add_docs` tool when a pull request is opened, define in a [configuration file](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/):
+
+
+```toml
+[github_app]
+pr_commands = [
+    "/add_docs",
+    ...
+]
+```
+
+The `pr_commands` list defines commands that run automatically when a PR is opened.
+Since this is under the [github_app] section, it only applies when using the Qodo Merge GitHub App in GitHub environments.
+
 ## Configuration options
 
 - `docs_style`: The exact style of the documentation (for python docstring). you can choose between: `google`, `numpy`, `sphinx`, `restructuredtext`, `plain`. Default is `sphinx`.
 - `extra_instructions`: Optional extra instructions to the tool. For example: "focus on the changes in the file X. Ignore change in ...".
 
 !!! note "Notes"
-    - The following languages are currently supported: Python, Java, C++, JavaScript, TypeScript, C#.
+    - The following languages are currently supported: `Python, Java, C++, JavaScript, TypeScript, C#, Go, Ruby, PHP, Rust, Kotlin, Scala`
     - This tool can also be triggered interactively by using the [`analyze`](./analyze.md) tool.

docs/docs/tools/help.md

@@ -11,10 +11,11 @@ It can be invoked manually by commenting on any PR:
 
 ## Example usage
 
-An example [result](https://github.com/Codium-ai/pr-agent/pull/546#issuecomment-1868524805):
+Invoke the `help` tool by commenting on a PR with:
 
-![Help 1](https://codium.ai/images/pr_agent/help1.png){width=750}
+![Help tool input](https://codium.ai/images/pr_agent/help1.png){width=750}
 
-→
 
-![Analyze 2](https://codium.ai/images/pr_agent/help2.png){width=750}
+Response will include a list of available tools:
+
+![Help tool output](https://codium.ai/images/pr_agent/help2.png){width=750}

docs/docs/tools/help_docs.md

@@ -86,10 +86,11 @@ jobs:
             -c "cd /app && \
             echo 'Running Issue Agent action step on ISSUE_URL=$ISSUE_URL' && \
             export config__git_provider='github' && \
-            export github__user_token=$GITHUB_TOKEN && \            
+                        export github__user_token=$GITHUB_TOKEN && \
             export github__base_url=$GITHUB_API_URL && \
             export openai__key=$OPENAI_KEY && \
-            python -m pr_agent.cli --issue_url=$ISSUE_URL --pr_help_docs.repo_url="..." --pr_help_docs.docs_path="..." --pr_help_docs.openai_key=$OPENAI_KEY && \help_docs \"$ISSUE_BODY\""
+            python -m pr_agent.cli --issue_url=$ISSUE_URL --pr_help_docs.repo_url="..." --pr_help_docs.docs_path="..." --pr_help_docs.openai_key=$OPENAI_KEY && \
+            help_docs "$ISSUE_BODY"
 ```
 
 3) Following completion of the remaining steps (such as adding secrets and relevant configurations, such as `repo_url` and `docs_path`) merge this change to your main branch.

docs/docs/tools/implement.md

@@ -7,51 +7,51 @@ It leverages LLM technology to transform PR comments and review suggestions into
 
 ## Usage Scenarios
 
-### For Reviewers
+=== "For Reviewers"
 
-Reviewers can request code changes by:
+    Reviewers can request code changes by:
 
-1. Selecting the code block to be modified.
-2. Adding a comment with the syntax:
+    1. Selecting the code block to be modified.
+    2. Adding a comment with the syntax:
 
-```
-/implement <code-change-description>
-```
+    ```
+    /implement <code-change-description>
+    ```
 
-![implement1](https://codium.ai/images/pr_agent/implement1.png){width=640}
+    ![implement1](https://codium.ai/images/pr_agent/implement1.png){width=640}
 
-### For PR Authors
+=== "For PR Authors"
 
-PR authors can implement suggested changes by replying to a review comment using either: <br>
+    PR authors can implement suggested changes by replying to a review comment using either:
 
-1. Add specific implementation details as described above
+    1. Add specific implementation details as described above
 
-```
-/implement <code-change-description>
-```
+    ```
+    /implement <code-change-description>
+    ```
 
-2. Use the original review comment as instructions
+    2. Use the original review comment as instructions
 
-```
-/implement
-```
+    ```
+    /implement
+    ```
 
-![implement2](https://codium.ai/images/pr_agent/implement2.png){width=640}
+    ![implement2](https://codium.ai/images/pr_agent/implement2.png){width=640}
 
-### For Referencing Comments
+=== "For Referencing Comments"
 
-You can reference and implement changes from any comment by:
+    You can reference and implement changes from any comment by:
 
-```
-/implement <link-to-review-comment>
-```
+    ```
+    /implement <link-to-an-inline-comment>
+    ```
 
-![implement3](https://codium.ai/images/pr_agent/implement3.png){width=640}
+    ![implement3](https://codium.ai/images/pr_agent/implement3.png){width=640}
 
-Note that the implementation will occur within the review discussion thread.
+    Note that the implementation will occur within the review discussion thread.
 
-**Configuration options**
+## Configuration options
 
 - Use `/implement` to implement code change within and based on the review discussion.
 - Use `/implement <code-change-description>` inside a review discussion to implement specific instructions.
-- Use `/implement <link-to-review-comment>` to indirectly call the tool from any comment.
+- Use `/implement <link-to-an-inline-comment>` to respond to an inline comment by triggering the tool from anywhere in the thread.

docs/docs/tools/improve.md

@@ -42,8 +42,6 @@ For example, you can choose to present all the suggestions as committable code c
 
 ![improve](https://codium.ai/images/pr_agent/improve.png){width=512}
 
-As can be seen, a single table comment has a significantly smaller PR footprint. We recommend this mode for most cases.
-Also note that collapsible are not supported in _Bitbucket_. Hence, the suggestions can only be presented in Bitbucket as code comments.
 
 #### Manual more suggestions
 To generate more suggestions (distinct from the ones already generated), for git-providers that don't support interactive checkbox option, you can manually run:
@@ -71,6 +69,32 @@ num_code_suggestions_per_chunk = ...
 - The `pr_commands` lists commands that will be executed automatically when a PR is opened.
 - The `[pr_code_suggestions]` section contains the configurations for the `improve` tool you want to edit (if any)
 
+### Table vs Committable code comments
+
+Qodo Merge supports two modes for presenting code suggestions: 
+
+1) [Table](https://codium.ai/images/pr_agent/code_suggestions_as_comment_closed.png) mode 
+
+2) [Inline Committable](https://codium.ai/images/pr_agent/improve.png) code comments mode.
+
+The table format offers several key advantages:
+
+- **Reduced noise**: Creates a cleaner PR experience with less clutter
+- **Quick overview and prioritization**: Enables quick review of one-liner summaries, impact levels, and easy prioritization
+- **High-level suggestions**: High-level suggestions that aren't tied to specific code chunks are presented only in the table mode
+- **Interactive features**: Provides 'more' and 'update' functionality via clickable buttons
+- **Centralized tracking**: Shows suggestion implementation status in one place
+- **IDE integration**: Allows applying suggestions directly in your IDE via [Qodo Command](https://github.com/qodo-ai/agents)
+
+Table mode is the default of Qodo Merge, and is recommended approach for most users due to these benefits. 
+
+![code_suggestions_as_comment_closed.png](https://codium.ai/images/pr_agent/code_suggestions_as_comment_closed.png){width=512}
+
+Teams with specific preferences can enable committable code comments mode in their local configuration, or use [dual publishing mode](#dual-publishing-mode).
+
+> `Note - due to platform limitations, Bitbucket cloud and server supports only committable code comments mode.`
+
+
 ### Assessing Impact
 
 >`💎 feature`
@@ -144,84 +168,227 @@ Use triple quotes to write multi-line instructions. Use bullet points or numbers
 
 > `💎 feature. Platforms supported: GitHub, GitLab, Bitbucket`
 
-Another option to give additional guidance to the AI model is by creating a `best_practices.md` file in your repository's root directory.
-This page can contain a list of best practices, coding standards, and guidelines that are specific to your repo/organization.
+Qodo Merge supports both simple and hierarchical best practices configurations to provide guidance to the AI model for generating relevant code suggestions.
 
-The AI model will use this `best_practices.md` file as a reference, and in case the PR code violates any of the guidelines, it will create additional suggestions, with a dedicated label: `Organization
-best practice`.
+???- tip "Writing effective best practices files"
+    
+    The following guidelines apply to all best practices files:
+    
+    - Write clearly and concisely
+    - Include brief code examples when helpful with before/after patterns
+    - Focus on project-specific guidelines that will result in relevant suggestions you actually want to get
+    - Keep each file relatively short, under 800 lines, since:
+        - AI models may not process effectively very long documents
+        - Long files tend to contain generic guidelines already known to AI
+        - Maximum multiple file accumulated content is limited to 2000 lines.
+    - Use pattern-based structure rather than simple bullet points for better clarity
 
-Example for a Python `best_practices.md` content:
+???- tip "Example of a best practices file"
+ 
+    Pattern 1: Add proper error handling with try-except blocks around external function calls.
+    
+    Example code before:
 
-```markdown
-## Project best practices
-- Make sure that I/O operations are encapsulated in a try-except block
-- Use the `logging` module for logging instead of `print` statements
-- Use `is` and `is not` to compare with `None`
-- Use `if __name__ == '__main__':` to run the code only when the script is executed
-- Use `with` statement to open files
-...
-```
+    ```python
+    # Some code that might raise an exception
+    return process_pr_data(data)
+    ```
 
-Tips for writing an effective `best_practices.md` file:
+    Example code after:
 
-- Write clearly and concisely
-- Include brief code examples when helpful
-- Focus on project-specific guidelines, that will result in relevant suggestions you actually want to get
-- Keep the file relatively short, under 800 lines, since:
-  - AI models may not process effectively very long documents
-  - Long files tend to contain generic guidelines already known to AI
+    ```python
+    try:
+        # Some code that might raise an exception
+        return process_pr_data(data)
+    except Exception as e:
+        logger.exception("Failed to process request", extra={"error": e})
+    ```
 
-To control the number of best practices suggestions generated by the `improve` tool, give the following configuration:
+    Pattern 2: Add defensive null/empty checks before accessing object properties or performing operations on potentially null variables to prevent runtime errors.
+    
+    Example code before:
 
-```toml
-[best_practices]
-num_best_practice_suggestions = 2
-```
+    ```python
+    def get_pr_code(pr_data):
+        if "changed_code" in pr_data:
+            return pr_data.get("changed_code", "")
+        return ""
+    ```
 
-#### Local and global best practices
+    Example code after:
 
-By default, Qodo Merge will look for a local `best_practices.md` in the root of the relevant local repo.
+    ```python
+    def get_pr_code(pr_data):
+        if pr_data is None:
+            return ""
+        if "changed_code" in pr_data:
+            return pr_data.get("changed_code", "")
+        return ""
+    ```
 
-If you want to enable also a global `best_practices.md` file, set first in the global configuration file:
+#### Local best practices
 
-```toml
-[best_practices]
-enable_global_best_practices = true
-```
+For basic usage, create a `best_practices.md` file in your repository's root directory containing a list of best practices, coding standards, and guidelines specific to your repository.
 
-Then, create a `best_practices.md` file in the root of [global](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/#global-configuration-file) configuration repository,  `pr-agent-settings`.
+The AI model will use this `best_practices.md` file as a reference, and in case the PR code violates any of the guidelines, it will create additional suggestions, with a dedicated label: `Organization best practice`.
 
-#### Best practices for multiple languages
+#### Global hierarchical best practices
 
-For a git organization working with multiple programming languages, you can maintain a centralized global `best_practices.md` file containing language-specific guidelines.
-When reviewing pull requests, Qodo Merge automatically identifies the programming language and applies the relevant best practices from this file.
 
-To do this, structure your `best_practices.md` file using the following format:
+For organizations managing multiple repositories with different requirements, Qodo Merge supports a hierarchical best practices system using a dedicated global configuration repository.
 
-```
-# [Python]
-...
-# [Java]
-...
-# [JavaScript]
-...
-```
+**Supported scenarios:**
 
-#### Dedicated label for best practices suggestions
+1. **Standalone repositories**: Individual repositories can have their own specific best practices tailored to their unique requirements
+2. **Groups of repositories**: Repositories can be mapped to shared group-level best practices for consistent standards across similar projects
+3. **Monorepos with subprojects**: Large monorepos can have both repository-level and subproject-level best practices, with automatic path-based matching
 
-Best practice suggestions are labeled as `Organization best practice` by default.
-To customize this label, modify it in your configuration file:
+#### Setting up global hierarchical best practices
+    
+1\. Create a new repository named `pr-agent-settings` in your organization/workspace.
 
-```toml
-[best_practices]
-organization_name = "..."
-```
+2\. Build the folder hierarchy in your `pr-agent-settings` repository, for example:
 
-And the label will be: `{organization_name} best practice`.
+   ```bash
+   pr-agent-settings/
+   ├── metadata.yaml                    # Maps repos/folders to best practice paths
+   └── codebase_standards/              # Root for all best practice definitions
+       ├── global/                      # Global rules, inherited widely
+       │   └── best_practices.md
+       ├── groups/                      # For groups of repositories
+       │   ├── frontend_repos/
+       │   │   └── best_practices.md
+       │   ├── backend_repos/
+       │   │   └── best_practices.md
+       │   ├── python_repos/
+       │   │   └── best_practices.md
+       │   ├── cpp_repos/
+       │   │   └── best_practices.md
+       │   └── ...
+       ├── repo_a/                      # For standalone repositories
+       │   └── best_practices.md
+       ├── monorepo-name/               # For monorepo-specific rules 
+       │   ├── best_practices.md        # Root level monorepo rules
+       │   ├── service-a/               # Subproject best practices
+       │   │   └── best_practices.md
+       │   └── service-b/               # Another subproject
+       │       └── best_practices.md
+       └── ...                          # More repositories
+   ```
 
-#### Example results
+> **Note:** In this structure, `pr-agent-settings`, `codebase_standards`, `global`, `groups`, `metadata.yaml`, and `best_practices.md` are hardcoded names that must be used exactly as shown. All other names (such as `frontend_repos`, `backend_repos`, `repo_a`, `monorepo-name`, `service-a`, etc.) are examples and should be replaced with your actual repository and service names.
 
-![best_practice](https://codium.ai/images/pr_agent/org_best_practice.png){width=512}
+???+ tip "Grouping and categorizing best practices"
+    - Each folder (including the global folder) can contain a single `best_practices.md` file
+    - Organize repository best practices by creating subfolders within the `groups` folder. Group them by purpose, programming languages, or other categories
+
+3\. Define the metadata file `metadata.yaml` that maps your repositories to their relevant best practices paths, for example:
+
+   ```yaml
+   # Standalone repos
+   repo_a:
+     best_practices_paths:
+       - "repo_a"
+
+   # Group-associated repos
+   repo_b:
+     best_practices_paths:
+       - "groups/backend_repos"
+
+   # Multi-group repos
+   repo_c:
+     best_practices_paths:
+       - "groups/frontend_repos"
+       - "groups/backend_repos"
+
+   # Monorepo with subprojects
+   monorepo-name:
+     best_practices_paths:
+       - "monorepo-name"
+     monorepo_subprojects:
+       service-a:
+         best_practices_paths:
+           - "monorepo-name/service-a"
+       service-b:
+         best_practices_paths:
+           - "monorepo-name/service-b"
+   ```
+
+4\. Set the following configuration in your global configuration file:
+
+   ```toml
+   [best_practices]
+   enable_global_best_practices = true
+   ```
+
+???- info "Best practices priority and fallback behavior"
+
+    When global best practices are enabled, Qodo Merge follows this priority order:
+    
+    1\. **Primary**: Global hierarchical best practices from `pr-agent-settings` repository:
+    
+        1.1 If the repository is mapped in `metadata.yaml`, it uses the specified paths
+    
+        1.2 For monorepos, it automatically collects best practices matching PR file paths
+    
+        1.3 If no mapping exists, it falls back to the global best practices
+
+    2\. **Fallback**: Local repository `best_practices.md` file:
+
+        2.1 Used when global best practices are not found or configured
+
+        2.2 Acts as a safety net for repositories not yet configured in the global system
+
+        2.3 Local best practices are completely ignored when global best practices are successfully loaded
+
+???- info "Edge cases and behavior"
+
+    - **Missing paths**: If specified paths in `metadata.yaml` don't exist in the file system, those paths are skipped
+    - **Monorepo subproject matching**: For monorepos, Qodo Merge automatically matches PR file paths against subproject paths to apply relevant best practices
+    - **Multiple group inheritance**: Repositories can inherit from multiple groups, and all applicable best practices are combined
+
+[//]: # (#### Best practices for multiple languages)
+
+[//]: # ()
+[//]: # (For a git organization working with multiple programming languages, you can maintain a centralized global `best_practices.md` file containing language-specific guidelines.)
+
+[//]: # (When reviewing pull requests, Qodo Merge automatically identifies the programming language and applies the relevant best practices from this file.)
+
+[//]: # ()
+[//]: # (To do this, structure your `best_practices.md` file using the following format:)
+
+[//]: # ()
+[//]: # (```)
+
+[//]: # (# [Python])
+
+[//]: # (...)
+
+[//]: # (# [Java])
+
+[//]: # (...)
+
+[//]: # (# [JavaScript])
+
+[//]: # (...)
+
+[//]: # (```)
+
+???- info "Dedicated label for best practices suggestions"
+
+    Best practice suggestions are labeled as `Organization best practice` by default.
+    To customize this label, modify it in your configuration file:
+    
+    ```toml
+    [best_practices]
+    organization_name = "..."
+    ```
+    
+    And the label will be: `{organization_name} best practice`.
+    
+    #### Example results
+    
+    ![best_practice](https://codium.ai/images/pr_agent/org_best_practice.png){width=512}
 
 ### Auto best practices
 
@@ -288,45 +455,6 @@ We advise users to apply critical analysis and judgment when implementing the pr
 In addition to mistakes (which may happen, but are rare), sometimes the presented code modification may serve more as an _illustrative example_ than a directly applicable solution.
 In such cases, we recommend prioritizing the suggestion's detailed description, using the diff snippet primarily as a supporting reference.
 
-
-### Chat on code suggestions 
-
-> `💎 feature` Platforms supported: GitHub, GitLab
-
-Qodo Merge implements an orchestrator agent that enables interactive code discussions, listening and responding to comments without requiring explicit tool calls.
-The orchestrator intelligently analyzes your responses to determine if you want to implement a suggestion, ask a question, or request help, then delegates to the appropriate specialized tool.
-
-#### Setup and Activation
-
-Enable interactive code discussions by adding the following to your configuration file (default is `True`):
-
-```toml
-[pr_code_suggestions]
-enable_chat_in_code_suggestions = true
-```
-
-!!! info "Activating Dynamic Responses"
-    To obtain dynamic responses, the following steps are required:
-
-    1. Run the `/improve` command (mostly automatic)
-    2. Tick the `/improve` recommendation checkboxes (_Apply this suggestion_) to have Qodo Merge generate a new inline code suggestion discussion
-    3. The orchestrator agent will then automatically listen and reply to comments within the discussion without requiring additional commands
-
-#### Explore the available interaction patterns:
-
-!!! tip "Tip: Direct the agent with keywords"
-    Use "implement" or "apply" for code generation. Use "explain", "why", or "how" for information and help.
-
-=== "Asking for Details"
-    ![Chat on code suggestions ask](https://codium.ai/images/pr_agent/improve_chat_on_code_suggestions_ask.png){width=512}
-
-=== "Implementing Suggestions"
-    ![Chat on code suggestions implement](https://codium.ai/images/pr_agent/improve_chat_on_code_suggestions_implement.png){width=512}
-
-=== "Providing Additional Help"
-    ![Chat on code suggestions help](https://codium.ai/images/pr_agent/improve_chat_on_code_suggestions_help.png){width=512}
-
-
 ### Dual publishing mode
 
 Our recommended approach for presenting code suggestions is through a [table](https://qodo-merge-docs.qodo.ai/tools/improve/#overview) (`--pr_code_suggestions.commitable_code_suggestions=false`).
@@ -344,9 +472,25 @@ dual_publishing_score_threshold = x
 
 Where x represents the minimum score threshold (>=) for suggestions to be presented as committable PR comments in addition to the table. Default is -1 (disabled).
 
+### Controlling suggestions depth
+
+> `💎 feature`
+
+You can control the depth and comprehensiveness of the code suggestions by using the `pr_code_suggestions.suggestions_depth` parameter.
+
+Available options:
+
+- `selective` - Shows only suggestions above a score threshold of 6
+- `regular` - Default mode with balanced suggestion coverage  
+- `exhaustive` - Provides maximum suggestion comprehensiveness
+
+(Alternatively, use numeric values: 1, 2, or 3 respectively)
+
+We recommend starting with `regular` mode, then exploring `exhaustive` mode, which can provide more comprehensive suggestions and enhanced bug detection.
+
 ### Self-review
 
-> `💎 feature` Platforms supported: GitHub, GitLab
+> `💎 feature. Platforms supported: GitHub, GitLab`
 
 If you set in a configuration file:
 
@@ -390,74 +534,6 @@ code_suggestions_self_review_text = "... (your text here) ..."
 
         To prevent unauthorized approvals, this configuration defaults to false, and cannot be altered through online comments; enabling requires a direct update to the configuration file and a commit to the repository. This ensures that utilizing the feature demands a deliberate documented decision by the repository owner.
 
-### Auto-approval
-
-> `💎 feature. Platforms supported: GitHub, GitLab, Bitbucket`
-
-Under specific conditions, Qodo Merge can auto-approve a PR when a specific comment is invoked, or when the PR meets certain criteria.
-
-**To ensure safety, the auto-approval feature is disabled by default.**
-To enable auto-approval features, you need to actively set one or both of the following options in a pre-defined _configuration file_:
-
-```toml
-[config]
-enable_comment_approval = true # For approval via comments
-enable_auto_approval = true   # For criteria-based auto-approval
-```
-
-!!! note "Notes"
-    - Note that this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository.
-    - Enabling auto-approval must be a deliberate decision by the repository owner.
-
-1\. **Auto-approval by commenting**
-
-To enable auto-approval by commenting, set in the configuration file:
-
-```toml
-[config]
-enable_comment_approval = true
-```
-
-After enabling, by commenting on a PR:
-
-```
-/review auto_approve
-```
-
-Qodo Merge will automatically approve the PR, and add a comment with the approval.
-
-2\. **Auto-approval when the PR meets certain criteria**
-
-To enable auto-approval based on specific criteria, first, you need to enable the top-level flag:
-
-```toml
-[config]
-enable_auto_approval = true
-```
-
-There are two criteria that can be set for auto-approval:
-
-- **Review effort score**
-
-```toml
-[config]
-enable_auto_approval = true
-auto_approve_for_low_review_effort = X # X is a number between 1 to 5
-```
-
-When the [review effort score](https://www.qodo.ai/images/pr_agent/review3.png) is lower or equal to X, the PR will be auto-approved.
-
-___
-
-- **No code suggestions**
-
-```toml
-[config]
-enable_auto_approval = true
-auto_approve_for_no_suggestions = true
-```
-
-When no [code suggestion](https://www.qodo.ai/images/pr_agent/code_suggestions_as_comment_closed.png) were found for the PR, the PR will be auto-approved.
 
 ### How many code suggestions are generated?
 
@@ -466,11 +542,11 @@ Qodo Merge uses a dynamic strategy to generate code suggestions based on the siz
 #### 1. Chunking large PRs
 
 - Qodo Merge divides large PRs into 'chunks'.
-- Each chunk contains up to `pr_code_suggestions.max_context_tokens` tokens (default: 24,000).
+- Each chunk contains up to `config.max_model_tokens` tokens (default: 32,000).
 
 #### 2. Generating suggestions
 
-- For each chunk, Qodo Merge generates up to `pr_code_suggestions.num_code_suggestions_per_chunk` suggestions (default: 4).
+- For each chunk, Qodo Merge generates up to `pr_code_suggestions.num_code_suggestions_per_chunk` suggestions (default: 3).
 
 This approach has two main benefits:
 
@@ -479,9 +555,39 @@ This approach has two main benefits:
 
 Note: Chunking is primarily relevant for large PRs. For most PRs (up to 600 lines of code), Qodo Merge will be able to process the entire code in a single call.
 
+#### Maximum coverage configuration
+> `💎 feature`
+
+For critical code reviews requiring maximum coverage, you can combine several settings to achieve a "super exhaustive" analysis. This is not a built-in mode, but a configuration recipe for advanced use cases.
+
+```toml
+# Recipe for maximum suggestion comprehensiveness
+[pr_code_suggestions]
+suggestions_depth = "exhaustive"
+enable_suggestion_type_reuse = true
+num_code_suggestions_per_chunk = 100
+num_best_practice_suggestions = 100
+```
+
+This configuration is recommended for:
+
+- Critical code reviews requiring maximum coverage
+- Final reviews before major releases
+- Code quality audits
+
+???- warning "Performance considerations"
+
+    This configuration will significantly increase:
+
+    - Analysis time and API costs
+    - Number of suggestions generated (potentially overwhelming)
+    - Comment volume in your PR
+    
+    Use this configuration judiciously and consider your team's review capacity.
+
 ## Configuration options
 
-??? example "General options"
+???+ example "General options"
 
     <table>
       <tr>
@@ -496,6 +602,10 @@ Note: Chunking is primarily relevant for large PRs. For most PRs (up to 600 line
         <td><b>enable_chat_in_code_suggestions</b></td>
         <td>If set to true, QM bot will interact with comments made on code changes it has proposed. Default is true.</td>
       </tr>
+      <tr>
+        <td><b>suggestions_depth 💎</b></td>
+        <td> Controls the depth of the suggestions. Can be set to 'selective', 'regular', or 'exhaustive'. Default is 'regular'.</td>
+      </tr>
       <tr>
         <td><b>dual_publishing_score_threshold</b></td>
         <td>Minimum score threshold for suggestions to be presented as committable PR comments in addition to the table. Default is -1 (disabled).</td>
@@ -522,11 +632,11 @@ Note: Chunking is primarily relevant for large PRs. For most PRs (up to 600 line
       </tr>
       <tr>
         <td><b>enable_help_text</b></td>
-        <td>If set to true, the tool will display a help text in the comment. Default is true.</td>
+        <td>If set to true, the tool will display a help text in the comment. Default is false.</td>
       </tr>
       <tr>
         <td><b>enable_chat_text</b></td>
-        <td>If set to true, the tool will display a reference to the PR chat in the comment. Default is true.</td>
+        <td>If set to true, the tool will display a reference to the PR chat in the comment. Default is false.</td>
       </tr>
       <tr>
         <td><b>publish_output_no_suggestions</b></td>
@@ -541,7 +651,7 @@ Note: Chunking is primarily relevant for large PRs. For most PRs (up to 600 line
       </tr>
     </table>
 
-??? example "Params for number of suggestions and AI calls"
+???+ example "Params for number of suggestions and AI calls"
 
     <table>
       <tr>
@@ -552,6 +662,10 @@ Note: Chunking is primarily relevant for large PRs. For most PRs (up to 600 line
         <td><b>num_code_suggestions_per_chunk</b></td>
         <td>Number of code suggestions provided by the 'improve' tool, per chunk. Default is 3.</td>
       </tr>
+      <tr>
+        <td><b>num_best_practice_suggestions 💎</b></td>
+        <td>Number of code suggestions provided by the 'improve' tool for best practices. Default is 1.</td>
+      </tr>
       <tr>
         <td><b>max_number_of_calls</b></td>
         <td>Maximum number of chunks. Default is 3.</td>

docs/docs/tools/improve_component.md

@@ -1,6 +1,6 @@
 ## Overview
 
-The `improve_component` tool generates code suggestions for a specific code component that changed in the PR.
+The `improve_component` tool generates code suggestions for a specific code component that has changed in the PR.
 it can be invoked manually by commenting on any PR:
 
 ```
@@ -20,7 +20,7 @@ The tool will generate code suggestions for the selected component (if no compon
 ![improve_component2](https://codium.ai/images/pr_agent/improve_component2.png){width=768}
 
 !!! note "Notes"
-    - Language that are currently supported by the tool: Python, Java, C++, JavaScript, TypeScript, C#.
+    - Languages that are currently supported by the tool: `Python, Java, C++, JavaScript, TypeScript, C#, Go, Kotlin`
     - This tool can also be triggered interactively by using the [`analyze`](./analyze.md) tool.
 
 ## Configuration options

docs/docs/tools/index.md

@@ -3,22 +3,25 @@
 Here is a list of Qodo Merge tools, each with a dedicated page that explains how to use it:
 
 | Tool                                                                                     | Description                                                                                                                                 |
-| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
 | **[PR Description (`/describe`](./describe.md))**                                        | Automatically generating PR description - title, type, summary, code walkthrough and labels                                                 |
 | **[PR Review (`/review`](./review.md))**                                                 | Adjustable feedback about the PR, possible issues, security concerns, review effort and more                                                |
 | **[Code Suggestions (`/improve`](./improve.md))**                                        | Code suggestions for improving the PR                                                                                                       |
 | **[Question Answering (`/ask ...`](./ask.md))**                                          | Answering free-text questions about the PR, or on specific code lines                                                                       |
-| **[Update Changelog (`/update_changelog`](./update_changelog.md))**                      | Automatically updating the CHANGELOG.md file with the PR changes                                                                            |
 | **[Help (`/help`](./help.md))**                                                          | Provides a list of all the available tools. Also enables to trigger them interactively (💎)                                                 |
+| **[Help Docs (`/help_docs`](./help_docs.md))**                                           | Answer a free-text question based on a git documentation folder.                                                                            |
+| **[Update Changelog (`/update_changelog`](./update_changelog.md))**                      | Automatically updating the CHANGELOG.md file with the PR changes                                                                            |
 | **💎 [Add Documentation (`/add_docs`](./documentation.md))**                             | Generates documentation to methods/functions/classes that changed in the PR                                                                 |
-| **💎 [Generate Custom Labels (`/generate_labels`](./custom_labels.md))**                 | Generates custom labels for the PR, based on specific guidelines defined by the user                                                        |
 | **💎 [Analyze (`/analyze`](./analyze.md))**                                              | Identify code components that changed in the PR, and enables to interactively generate tests, docs, and code suggestions for each component |
-| **💎 [Test (`/test`](./test.md))**                                                       | generate tests for a selected component, based on the PR code changes                                                                       |
-| **💎 [Custom Prompt (`/custom_prompt`](./custom_prompt.md))**                            | Automatically generates custom suggestions for improving the PR code, based on specific guidelines defined by the user                      |
-| **💎 [Generate Tests (`/test component_name`](./test.md))**                              | Automatically generates unit tests for a selected component, based on the PR code changes                                                   |
-| **💎 [Improve Component (`/improve_component component_name`](./improve_component.md))** | Generates code suggestions for a specific code component that changed in the PR                                                             |
 | **💎 [CI Feedback (`/checks ci_job`](./ci_feedback.md))**                                | Automatically generates feedback and analysis for a failed CI job                                                                           |
+| **💎 [Compliance (`/compliance`](./compliance.md))**                                  | Comprehensive compliance checks for security, ticket requirements, and custom organizational rules                                          |
+| **💎 [Custom Prompt (`/custom_prompt`](./custom_prompt.md))**                            | Automatically generates custom suggestions for improving the PR code, based on specific guidelines defined by the user                      |
+| **💎 [Generate Custom Labels (`/generate_labels`](./custom_labels.md))**                 | Generates custom labels for the PR, based on specific guidelines defined by the user                                                        |
+| **💎 [Generate Tests (`/test`](./test.md))**                                             | Automatically generates unit tests for a selected component, based on the PR code changes                                                   |
 | **💎 [Implement (`/implement`](./implement.md))**                                        | Generates implementation code from review suggestions                                                                                       |
+| **💎 [Improve Component (`/improve_component component_name`](./improve_component.md))** | Generates code suggestions for a specific code component that changed in the PR                                                             |
+| **💎 [PR to Ticket (`/create_ticket`](./pr_to_ticket.md))**                          | Generates ticket in the ticket tracking systems (Jira, Linear, or Git provider issues) based on PR content                                  |
 | **💎 [Scan Repo Discussions (`/scan_repo_discussions`](./scan_repo_discussions.md))**    | Generates `best_practices.md` file based on previous discussions in the repository                                                          |
+| **💎 [Similar Code (`/similar_code`](./similar_code.md))**                               | Retrieves the most similar code components from inside the organization's codebase, or from open-source code.                               |
 
-Note that the tools marked with 💎 are available only for Qodo Merge users.
+Note that the tools marked with 💎 are available only for Qodo Merge users.

docs/docs/tools/pr_to_ticket.md

@@ -0,0 +1,89 @@
+`Platforms supported: GitHub, GitLab, Bitbucket`
+
+`Supported Ticket providers: Jira, Linear, GitHub Issues, Gitlab Issues`
+
+## Overview
+The `create_ticket` tool automatically generates tickets in ticket tracking systems (`Jira`, `Linear`, or `GitHub Issues` and `Gitlab issues`) based on PR content.
+
+It analyzes the PR's data (code changes, commit messages, and description) to create well-structured tickets that capture the essence of the development work, helping teams maintain traceability between code changes and project management systems.
+
+When a ticket is created, it appears in the PR description under an `Auto-created Ticket` section, complete with a link to the generated ticket.
+
+![auto_created_ticket_in_description](https://codium.ai/images/pr_agent/auto_created_ticket_in_description.png){width=512}
+
+!!! info "Pre-requisites"
+    - To use this tool you need to integrate your ticketing system with Qodo-merge, follow the [Ticket Compliance Documentation](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/).
+    - For Jira Cloud users, please re-integrate your connection through the [qodo merge integration page](https://app.qodo.ai/qodo-merge/integrations) to enable the `update` permission required for ticket creation
+    - You need to configure the project key in ticket corresponding to the repository where the PR is created. This is done by adding the `default_project_key`.
+
+    ```toml
+    [pr_to_ticket]
+    default_project_key = "PROJECT_KEY" # e.g., "SCRUM"
+    ```
+
+## Usage
+there are 3 ways to use the `create_ticket` tool:
+
+1. [**Automatic Ticket Creation**](#automatic-ticket-creation)
+2. [**Interactive Triggering via Compliance Tool**](#interactive-triggering-via-compliance-tool)
+3. [**Manual Ticket Creation**](#manual-ticket-creation)
+
+### Automatic Ticket Creation
+The tool can be configured to automatically create tickets when a PR is opened or updated and the PR does not already have a ticket associated with it. 
+This ensures that every code change is documented in the ticketing system without manual intervention.
+
+To configure automatic ticket creation, add the following to `.pr_agent.toml`:
+
+```toml
+[pr_description]
+auto_create_ticket = true
+```
+
+### Interactive Triggering via Compliance Tool
+`Supported only in Github and Gitlab`
+
+The tool can be triggered interactively through a checkbox in the compliance tool. This allows users to create tickets as part of their PR Compliance Review workflow.
+
+![ticket creation via compliance tool](https://codium.ai/images/pr_agent/ticket_creation_from_compliance1.png){width=512}
+
+- After clicking the checkbox, the tool will create a ticket and will add/update the `PR Description` with a section called `Auto-created Ticket` with the link to the created ticket.
+- Then you can click `update` in the `Ticket compliance` section in the `Compliance` tool 
+
+![compliance_auto_created_ticket_final](https://codium.ai/images/pr_agent/compliance_auto_created_ticket_final.png){width=512}
+
+### Manual Ticket Creation
+Users can manually trigger the ticket creation process from the PR interface.
+
+To trigger ticket creation manually, the user can call this tool from the PR comment:
+
+```
+/create_ticket
+```
+
+After triggering, the tool will create a ticket and will add/update the `PR Description` with a section called `Auto-created Ticket` with the link to the created ticket.
+
+
+## Configuration
+
+## Configuration Options
+
+???+ example "Configuration"
+
+    <table>
+      <tr>
+        <td><b>default_project_key</b></td>
+        <td>The default project key for your ticketing system (e.g., `SCRUM`). This is required unless `fallback_to_git_provider_issues` is set to `true`.</td>
+      </tr>
+      <tr>
+        <td><b>default_base_url</b></td>
+        <td>If your organization have integrated to multiple ticketing systems, you can set the default base URL for the ticketing system. This will be used to create tickets in the default system. Example: `https://YOUR-ORG.atlassian.net`.</td>
+      </tr>
+      <tr>
+        <td><b>fallback_to_git_provider_issues</b></td>
+        <td>If set to `true`, the tool will create issues in the Git provider's issue tracker (GitHub, Gitlab) if the `default_project_key` is not configured in the repository configuration. Default is `false`.</td>
+      </tr>
+    </table>
+
+
+## Helping Your Organization Meet SOC-2 Requirements
+The `create_ticket` tool helps your organization satisfy SOC-2 compliance. By automatically creating tickets from PRs and establishing bidirectional links between them, it ensures every code change is traceable to its corresponding business requirement or task.

docs/docs/tools/review.md

@@ -1,6 +1,6 @@
 ## Overview
 
-The `review` tool scans the PR code changes, and generates a list of feedbacks about the PR, aiming to aid the reviewing process.
+The `review` tool scans the PR code changes, and generates feedback about the PR, aiming to aid the reviewing process.
 <br>
 The tool can be triggered automatically every time a new PR is [opened](../usage-guide/automations_and_usage.md#github-app-automatic-tools-when-a-new-pr-is-opened), or can be invoked manually by commenting on any PR:
 
@@ -8,7 +8,7 @@ The tool can be triggered automatically every time a new PR is [opened](../usage
 /review
 ```
 
-Note that the main purpose of the `review` tool is to provide the **PR reviewer** with useful feedbacks and insights. The PR author, in contrast, may prefer to save time and focus on the output of the [improve](./improve.md) tool, which provides actionable code suggestions.
+Note that the main purpose of the `review` tool is to provide the **PR reviewer** with useful feedback and insights. The PR author, in contrast, may prefer to save time and focus on the output of the [improve](./improve.md) tool, which provides actionable code suggestions.
 
 (Read more about the different personas in the PR process and how Qodo Merge aims to assist them in our [blog](https://www.codium.ai/blog/understanding-the-challenges-and-pain-points-of-the-pull-request-cycle/))
 
@@ -51,7 +51,7 @@ extra_instructions = "..."
 
 ## Configuration options
 
-!!! example "General options"
+???+ example "General options"
 
     <table>
       <tr>
@@ -68,11 +68,15 @@ extra_instructions = "..."
       </tr>
       <tr>
         <td><b>enable_help_text</b></td>
-        <td>If set to true, the tool will display a help text in the comment. Default is true.</td>
+        <td>If set to true, the tool will display a help text in the comment. Default is false.</td>
+      </tr>
+      <tr>
+        <td><b>num_max_findings</b></td>
+        <td>Number of maximum returned findings. Default is 3.</td>
       </tr>
     </table>
 
-!!! example "Enable\\disable specific sub-sections"
+???+ example "Enable\\disable specific sub-sections"
 
     <table>
       <tr>
@@ -87,6 +91,10 @@ extra_instructions = "..."
         <td><b>require_estimate_effort_to_review</b></td>
         <td>If set to true, the tool will add a section that estimates the effort needed to review the PR. Default is true.</td>
       </tr>
+      <tr>
+        <td><b>require_estimate_contribution_time_cost</b></td>
+        <td>If set to true, the tool will add a section that estimates the time required for a senior developer to create and submit such changes. Default is false.</td>
+      </tr>
       <tr>
         <td><b>require_can_be_split_review</b></td>
         <td>If set to true, the tool will add a section that checks if the PR contains several themes, and can be split into smaller PRs. Default is false.</td>
@@ -94,6 +102,11 @@ extra_instructions = "..."
       <tr>
         <td><b>require_security_review</b></td>
         <td>If set to true, the tool will add a section that checks if the PR contains a possible security or vulnerability issue. Default is true.</td>
+      </tr>
+        <tr>
+        <td><b>require_todo_scan</b></td>
+        <td>If set to true, the tool will add a section that lists TODO comments found in the PR code changes. Default is false.
+        </td>
       </tr>
       <tr>
         <td><b>require_ticket_analysis_review</b></td>
@@ -101,7 +114,7 @@ extra_instructions = "..."
       </tr>
     </table>
 
-!!! example "Adding PR labels"
+???+ example "Adding PR labels"
 
     You can enable\disable the `review` tool to add specific labels to the PR:
 
@@ -112,13 +125,15 @@ extra_instructions = "..."
       </tr>
       <tr>
         <td><b>enable_review_labels_effort</b></td>
-        <td>If set to true, the tool will publish a 'Review effort [1-5]: x' label. Default is true.</td>
+        <td>If set to true, the tool will publish a 'Review effort x/5' label (1–5 scale). Default is true.</td>
       </tr>
     </table>
 
 ## Usage Tips
 
-!!! tip "General guidelines"
+### General guidelines
+
+!!! tip ""
 
     The `review` tool provides a collection of configurable feedbacks about a PR.
     It is recommended to review the [Configuration options](#configuration-options) section, and choose the relevant options for your use case.
@@ -128,7 +143,9 @@ extra_instructions = "..."
 
     On the other hand, if you find one of the enabled features to be irrelevant for your use case, disable it. No default configuration can fit all use cases.
 
-!!! tip "Automation"
+### Automation
+
+!!! tip ""
     When you first install Qodo Merge app, the [default mode](../usage-guide/automations_and_usage.md#github-app-automatic-tools-when-a-new-pr-is-opened) for the `review` tool is:
     ```
     pr_commands = ["/review", ...]
@@ -136,16 +153,30 @@ extra_instructions = "..."
     Meaning the `review` tool will run automatically on every PR, without any additional configurations.
     Edit this field to enable/disable the tool, or to change the configurations used.
 
-!!! tip "Possible labels from the review tool"
+### Auto-generated PR labels by the Review Tool
 
-    The `review` tool can auto-generate two specific types of labels for a PR:
+!!! tip ""
 
-    - a `possible security issue` label that detects if a possible [security issue](https://github.com/Codium-ai/pr-agent/blob/tr/user_description/pr_agent/settings/pr_reviewer_prompts.toml#L136) exists in the PR code (`enable_review_labels_security` flag)
-    - a `Review effort [1-5]: x` label, where x is the estimated effort to review the PR (`enable_review_labels_effort` flag)
+    The `review` can tool automatically add labels to your Pull Requests:
 
-    Both modes are useful, and we recommended to enable them.
+    - **`possible security issue`**: This label is applied if the tool detects a potential [security vulnerability](https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/pr_reviewer_prompts.toml#L103) in the PR's code. This feedback is controlled by the 'enable_review_labels_security' flag (default is true).
+    - **`review effort [x/5]`**: This label estimates the [effort](https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/pr_reviewer_prompts.toml#L90) required to review the PR on a relative scale of 1 to 5, where 'x' represents the assessed effort. This feedback is controlled by the 'enable_review_labels_effort' flag (default is true).
+    - **`ticket compliance`**: Adds a label indicating code compliance level ("Fully compliant" | "PR Code Verified" | "Partially compliant" | "Not compliant") to any GitHub/Jira/Linea ticket linked in the PR. Controlled by the 'require_ticket_labels' flag (default: false). If 'require_no_ticket_labels' is also enabled, PRs without ticket links will receive a "No ticket found" label.
 
-!!! tip "Extra instructions"
+
+### Auto-blocking PRs from being merged based on the generated labels
+
+!!! tip ""
+
+    You can configure a CI/CD Action to prevent merging PRs with specific labels. For example, implement a dedicated [GitHub Action](https://medium.com/sequra-tech/quick-tip-block-pull-request-merge-using-labels-6cc326936221).
+
+    This approach helps ensure PRs with potential security issues or ticket compliance problems will not be merged without further review.
+
+    Since AI may make mistakes or lack complete context, use this feature judiciously. For flexibility, users with appropriate permissions can remove generated labels when necessary. When a label is removed, this action will be automatically documented in the PR discussion, clearly indicating it was a deliberate override by an authorized user to allow the merge.
+
+### Extra instructions
+
+!!! tip "" 
 
     Extra instructions are important.
     The `review` tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project.
@@ -164,7 +195,3 @@ extra_instructions = "..."
     """
     ```
     Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.
-
-!!! tip  "Code suggestions"
-
-    The `review` tool previously included a legacy feature for providing code suggestions (controlled by `--pr_reviewer.num_code_suggestion`). This functionality has been deprecated and replaced by the [`improve`](./improve.md) tool, which offers higher quality and more actionable code suggestions.

docs/docs/tools/similar_code.md

@@ -1,10 +1,12 @@
+`Platforms supported: GitHub`
+
 ## Overview
 
 The similar code tool retrieves the most similar code components from inside the organization's codebase, or from open-source code.
 
 For example:
 
-`Global Search` for a method called `chat_completion`:
+A `Global Search` for a method called `chat_completion`:
 
 ![similar code global](https://codium.ai/images/pr_agent/similar_code_global2.png){width=768}
 
@@ -19,7 +21,7 @@ Search result link example:
 
 ![code search result single](https://codium.ai/images/pr_agent/code_search_result_single.png){width=768}
 
-`Organization Search`:
+An `Organization Search`:
 
 ![similar code org](https://codium.ai/images/pr_agent/similar_code_org.png){width=768}
 

docs/docs/tools/similar_issues.md

@@ -27,6 +27,7 @@ Choose from the following Vector Databases:
 
 1. LanceDB
 2. Pinecone
+3. Qdrant
 
 #### Pinecone Configuration
 
@@ -40,6 +41,25 @@ environment = "..."
 
 These parameters can be obtained by registering to [Pinecone](https://app.pinecone.io/?sessionType=signup/).
 
+#### Qdrant Configuration
+
+To use Qdrant with the `similar issue` tool, add these credentials to `.secrets.toml` (or set as environment variables):
+
+```
+[qdrant]
+url = "https://YOUR-QDRANT-URL" # e.g., https://xxxxxxxx-xxxxxxxx.eu-central-1-0.aws.cloud.qdrant.io
+api_key = "..."
+```
+
+Then select Qdrant in `configuration.toml`:
+
+```
+[pr_similar_issue]
+vectordb = "qdrant"
+```
+
+You can get a free managed Qdrant instance from [Qdrant Cloud](https://cloud.qdrant.io/).
+
 ## How to use
 
 - To invoke the 'similar issue' tool from **CLI**, run:

docs/docs/tools/test.md

@@ -1,6 +1,6 @@
 ## Overview
 
-By combining LLM abilities with static code analysis, the `test` tool  generate tests for a selected component, based on the PR code changes.
+By combining LLM abilities with static code analysis, the `test` tool generates tests for a selected component, based on the PR code changes.
 It can be invoked manually by commenting on any PR:
 
 ```
@@ -20,7 +20,7 @@ The tool will generate tests for the selected component (if no component is stat
 (Example taken from [here](https://github.com/Codium-ai/pr-agent/pull/598#issuecomment-1913679429)):
 
 !!! note "Notes"
-    - The following languages are currently supported: Python, Java, C++, JavaScript, TypeScript, C#.
+    - The following languages are currently supported: `Python, Java, C++, JavaScript, TypeScript, C#, Go, Kotlin`
     - This tool can also be triggered interactively by using the [`analyze`](./analyze.md) tool.
 
 ## Configuration options

docs/docs/usage-guide/additional_configurations.md

@@ -50,7 +50,7 @@ glob = ['*.py']
 And to ignore Python files in all PRs using `regex` pattern, set in a configuration file:
 
 ```
-[regex]
+[ignore]
 regex = ['.*\.py$']
 ```
 
@@ -64,9 +64,9 @@ All Qodo Merge tools have a parameter called `extra_instructions`, that enables
 
 ## Language Settings
 
-The default response language for Qodo Merge is **U.S. English**. However, some development teams may prefer to display information in a different language. For example, your team's workflow might improve if PR descriptions and code suggestions are set to your country's native language.  
+The default response language for Qodo Merge is **U.S. English**. However, some development teams may prefer to display information in a different language. For example, your team's workflow might improve if PR descriptions and code suggestions are set to your country's native language.
 
-To configure this, set the `response_language` parameter in the configuration file. This will prompt the model to respond in the specified language. Use a **standard locale code** based on [ISO 3166](https://en.wikipedia.org/wiki/ISO_3166) (country codes) and [ISO 639](https://en.wikipedia.org/wiki/ISO_639) (language codes) to define a language-country pair. See this [comprehensive list of locale codes](https://simplelocalize.io/data/locales/).  
+To configure this, set the `response_language` parameter in the configuration file. This will prompt the model to respond in the specified language. Use a **standard locale code** based on [ISO 3166](https://en.wikipedia.org/wiki/ISO_3166) (country codes) and [ISO 639](https://en.wikipedia.org/wiki/ISO_639) (language codes) to define a language-country pair. See this [comprehensive list of locale codes](https://simplelocalize.io/data/locales/).
 
 Example:
 
@@ -97,33 +97,17 @@ This will set the response language globally for all the commands to Italian.
 
 [//]: # (which divides the PR into chunks, and processes each chunk separately. With this mode, regardless of the model, no compression will be done (but for large PRs, multiple model calls may occur))
 
-## Patch Extra Lines
 
-By default, around any change in your PR, git patch provides three lines of context above and below the change.
+## Expand GitLab submodule diffs
 
-```
-@@ -12,5 +12,5 @@ def func1():
- code line that already existed in the file...
- code line that already existed in the file...
- code line that already existed in the file....
--code line that was removed in the PR
-+new code line added in the PR
- code line that already existed in the file...
- code line that already existed in the file...
- code line that already existed in the file...
+By default, GitLab merge requests show submodule updates as `Subproject commit` lines. To include the actual file-level changes from those submodules in Qodo Merge analysis, enable:
+
+```toml
+[gitlab]
+expand_submodule_diffs = true
 ```
 
-Qodo Merge will try to increase the number of lines of context, via the parameter:
-
-```
-[config]
-patch_extra_lines_before=3
-patch_extra_lines_after=1
-```
-
-Increasing this number provides more context to the model, but will also increase the token budget, and may overwhelm the model with too much information, unrelated to the actual PR code changes.
-
-If the PR is too large (see [PR Compression strategy](https://github.com/Codium-ai/pr-agent/blob/main/PR_COMPRESSION.md)), Qodo Merge may automatically set this number to 0, and will use the original git patch.
+When enabled, Qodo Merge will fetch and attach diffs from the submodule repositories. The default is `false` to avoid extra GitLab API calls.
 
 ## Log Level
 
@@ -158,6 +142,27 @@ LANGSMITH_PROJECT=<project>
 LANGSMITH_BASE_URL=<url>
 ```
 
+## Bringing additional repository metadata to Qodo Merge 💎
+
+To provide Qodo Merge tools with additional context about your project, you can enable automatic repository metadata detection. 
+
+If you set:
+
+```toml
+[config]
+add_repo_metadata = true
+```
+
+Qodo Merge automatically searches for repository metadata files in your PR's head branch root directory. By default, it looks for:
+[AGENTS.MD](https://agents.md/), [QODO.MD](https://docs.qodo.ai/qodo-documentation/qodo-command/getting-started/setup-and-quickstart), [CLAUDE.MD](https://www.anthropic.com/engineering/claude-code-best-practices).
+
+You can also specify custom filenames to search for:
+
+```toml
+[config]
+add_repo_metadata_file_list= ["file1.md", "file2.md", ...]
+```
+
 ## Ignoring automatic commands in PRs
 
 Qodo Merge allows you to automatically ignore certain PRs based on various criteria:
@@ -246,7 +251,32 @@ To supplement the automatic bot detection, you can manually specify users to ign
 ignore_pr_authors = ["my-special-bot-user", ...]
 ```
 
-Where the `ignore_pr_authors` is a list of usernames that you want to ignore.
+Where the `ignore_pr_authors` is a regex list of usernames that you want to ignore.
 
 !!! note
-    There is one specific case where bots will receive an automatic response - when they generated a PR with a _failed test_. In that case, the [`ci_feedback`](https://qodo-merge-docs.qodo.ai/tools/ci_feedback/) tool will be invoked.
+    There is one specific case where bots will receive an automatic response - when they generated a PR with a _failed test_. In that case, the [`ci_feedback`](https://qodo-merge-docs.qodo.ai/tools/ci_feedback/) tool will be invoked.
+
+### Ignoring Generated Files by Language/Framework
+
+To automatically exclude files generated by specific languages or frameworks, you can add the following to your `configuration.toml` file:
+
+```
+[config]
+ignore_language_framework = ['protobuf', ...]
+```
+
+You can view the list of auto-generated file patterns in [`generated_code_ignore.toml`](https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/generated_code_ignore.toml).
+Files matching these glob patterns will be automatically excluded from PR Agent analysis.
+
+### Ignoring Tickets with Specific Labels
+
+When Qodo Merge analyzes tickets (JIRA, GitHub Issues, GitLab Issues, etc.) referenced in your PR, you may want to exclude tickets that have certain labels from the analysis. This is useful for filtering out tickets marked as "ignore-compliance", "skip-review", or other labels that indicate the ticket should not be considered during PR review.
+
+To ignore tickets with specific labels, add the following to your `configuration.toml` file:
+
+```toml
+[config]
+ignore_ticket_labels = ["ignore-compliance", "skip-review", "wont-fix"]
+```
+
+Where `ignore_ticket_labels` is a list of label names that should be ignored during ticket analysis.

docs/docs/usage-guide/automations_and_usage.md

@@ -30,7 +30,7 @@ verbosity_level=2
 This is useful for debugging or experimenting with different tools.
 
 3. **git provider**: The [git_provider](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L5) field in a configuration file determines the GIT provider that will be used by Qodo Merge. Currently, the following providers are supported:
-`github` **(default)**, `gitlab`, `bitbucket`, `azure`, `codecommit`, `local`, and `gerrit`.
+`github` **(default)**, `gitlab`, `bitbucket`, `azure`, `codecommit`, `local`, and `gitea`.
 
 ### CLI Health Check
 
@@ -202,6 +202,39 @@ publish_labels = false
 
 to prevent Qodo Merge from publishing labels when running the `describe` tool.
 
+#### Enable using commands in PR
+
+You can configure your GitHub Actions workflow to trigger on `issue_comment` [events](https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#issue_comment) (`created` and `edited`).
+
+Example GitHub Actions workflow configuration:
+
+```yaml
+on:
+  issue_comment:
+    types: [created, edited]
+```
+
+When this is configured, Qodo merge can be invoked by commenting on the PR.
+
+#### Quick Reference: Model Configuration in GitHub Actions
+
+For detailed step-by-step examples of configuring different models (Gemini, Claude, Azure OpenAI, etc.) in GitHub Actions, see the [Configuration Examples](../installation/github.md#configuration-examples) section in the installation guide.
+
+**Common Model Configuration Patterns:**
+
+- **OpenAI**: Set `config.model: "gpt-4o"` and `OPENAI_KEY`
+- **Gemini**: Set `config.model: "gemini/gemini-1.5-flash"` and `GOOGLE_AI_STUDIO.GEMINI_API_KEY` (no `OPENAI_KEY` needed)
+- **Claude**: Set `config.model: "anthropic/claude-3-opus-20240229"` and `ANTHROPIC.KEY` (no `OPENAI_KEY` needed)
+- **Azure OpenAI**: Set `OPENAI.API_TYPE: "azure"`, `OPENAI.API_BASE`, and `OPENAI.DEPLOYMENT_ID`
+- **Local Models**: Set `config.model: "ollama/model-name"` and `OLLAMA.API_BASE`
+
+**Environment Variable Format:**
+- Use dots (`.`) to separate sections and keys: `config.model`, `pr_reviewer.extra_instructions`
+- Boolean values as strings: `"true"` or `"false"`
+- Arrays as JSON strings: `'["item1", "item2"]'`
+
+For complete model configuration details, see [Changing a model in PR-Agent](changing_a_model.md).
+
 ### GitLab Webhook
 
 After setting up a GitLab webhook, to control which commands will run automatically when a new MR is opened, you can set the `pr_commands` parameter in the configuration file, similar to the GitHub App:
@@ -312,3 +345,16 @@ pr_commands = [
     "/improve",
 ]
 ```
+
+### Gitea Webhook
+
+After setting up a Gitea webhook, to control which commands will run automatically when a new MR is opened, you can set the `pr_commands` parameter in the configuration file, similar to the GitHub App:
+
+```toml
+[gitea]
+pr_commands = [
+    "/describe",
+    "/review",
+    "/improve",
+]
+```

docs/docs/usage-guide/changing_a_model.md

@@ -1,7 +1,8 @@
 ## Changing a model in PR-Agent
 
-See [here](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/algo/__init__.py) for a list of available models.
-To use a different model than the default (o4-mini), you need to edit in the [configuration file](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L2) the fields:
+See [here](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/algo/__init__.py) for a list of supported models in PR-Agent.
+The default model of PR-Agent is `GPT-5` from OpenAI.
+To use a different model than the default, you need to edit in the [configuration file](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L2) the fields:
 
 ```toml
 [config]
@@ -32,6 +33,16 @@ OPENAI__API_BASE=https://api.openai.com/v1
 OPENAI__KEY=sk-...
 ```
 
+### OpenAI Flex Processing
+
+To reduce costs for non-urgent/background tasks, enable Flex Processing:
+
+```toml
+[litellm]
+extra_body='{"processing_mode": "flex"}'
+```
+
+See [OpenAI Flex Processing docs](https://platform.openai.com/docs/guides/flex-processing) for details.
 
 ### Azure
 
@@ -90,14 +101,14 @@ duplicate_examples=true # will duplicate the examples in the prompt, to help the
 api_base = "http://localhost:11434" # or whatever port you're running Ollama on
 ```
 
-By default, Ollama uses a context window size of 2048 tokens. In most cases this is not enough to cover pr-agent promt and pull-request diff. Context window size can be overridden with the `OLLAMA_CONTEXT_LENGTH` environment variable. For example, to set the default context length to 8K, use: `OLLAMA_CONTEXT_LENGTH=8192 ollama serve`. More information you can find on the [official ollama faq](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-specify-the-context-window-size).
+By default, Ollama uses a context window size of 2048 tokens. In most cases this is not enough to cover pr-agent prompt and pull-request diff. Context window size can be overridden with the `OLLAMA_CONTEXT_LENGTH` environment variable. For example, to set the default context length to 8K, use: `OLLAMA_CONTEXT_LENGTH=8192 ollama serve`. More information you can find on the [official ollama faq](https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-specify-the-context-window-size).
 
 Please note that the `custom_model_max_tokens` setting should be configured in accordance with the `OLLAMA_CONTEXT_LENGTH`. Failure to do so may result in unexpected model output.
 
 !!! note "Local models vs commercial models"
     Qodo Merge is compatible with almost any AI model, but analyzing complex code repositories and pull requests requires a model specifically optimized for code analysis.
 
-    Commercial models such as GPT-4, Claude Sonnet, and Gemini have demonstrated robust capabilities in generating structured output for code analysis tasks with large input. In contrast, most open-source models currently available (as of January 2025) face challenges with these complex tasks.
+    Commercial models such as GPT-5, Claude Sonnet, and Gemini have demonstrated robust capabilities in generating structured output for code analysis tasks with large input. In contrast, most open-source models currently available (as of January 2025) face challenges with these complex tasks.
 
     Based on our testing, local open-source models are suitable for experimentation and learning purposes (mainly for the `ask` command), but they are not suitable for production-level code analysis tasks.
     
@@ -232,6 +243,34 @@ AWS_SECRET_ACCESS_KEY="..."
 AWS_REGION_NAME="..."
 ```
 
+You can also use the new Meta Llama 4 models available on Amazon Bedrock:
+
+```toml
+[config] # in configuration.toml
+model="bedrock/us.meta.llama4-scout-17b-instruct-v1:0"
+fallback_models=["bedrock/us.meta.llama4-maverick-17b-instruct-v1:0"]
+```
+
+#### Custom Inference Profiles
+
+To use a custom inference profile with Amazon Bedrock (for cost allocation tags and other configuration settings), add the `model_id` parameter to your configuration:
+
+```toml
+[config] # in configuration.toml
+model="bedrock/anthropic.claude-3-5-sonnet-20240620-v1:0"
+fallback_models=["bedrock/anthropic.claude-3-5-sonnet-20240620-v1:0"]
+
+[aws]
+AWS_ACCESS_KEY_ID="..."
+AWS_SECRET_ACCESS_KEY="..."
+AWS_REGION_NAME="..."
+
+[litellm]
+model_id = "your-custom-inference-profile-id"
+```
+
+The `model_id` parameter will be passed to all Bedrock completion calls, allowing you to use custom inference profiles for better cost allocation and reporting.
+
 See [litellm](https://docs.litellm.ai/docs/providers/bedrock#usage) documentation for more information about the environment variables required for Amazon Bedrock.
 
 ### DeepSeek
@@ -341,7 +380,7 @@ To bypass chat templates and temperature controls, set `config.custom_reasoning_
 
 ```toml
 [config]
-reasoning_efffort= = "medium" # "low", "medium", "high"
+reasoning_effort = "medium" # "low", "medium", "high"
 ```
 
 With the OpenAI models that support reasoning effort (eg: o4-mini), you can specify its reasoning effort via `config` section. The default value is `medium`. You can change it to `high` or `low` based on your usage.

docs/docs/usage-guide/configuration_options.md

@@ -1,20 +1,22 @@
-The different tools and sub-tools used by Qodo Merge are adjustable via the **[configuration file](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml)**.
+The different tools and sub-tools used by Qodo Merge are adjustable via a Git configuration file.
+There are three main ways to set persistent configurations:
 
-In addition to general configuration options, each tool has its own configurations. For example, the `review` tool will use parameters from the [pr_reviewer](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L16) section in the configuration file.
-See the [Tools Guide](https://qodo-merge-docs.qodo.ai/tools/) for a detailed description of the different tools and their configurations.
-
-There are three ways to set persistent configurations:
-
-1. Wiki configuration page 💎
-2. Local configuration file
-3. Global configuration file 💎
+1. [Wiki](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/#wiki-configuration-file) configuration page 💎
+2. [Local](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/#local-configuration-file) configuration file
+3. [Global](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/#global-configuration-file) configuration file 💎
 
 In terms of precedence, wiki configurations will override local configurations, and local configurations will override global configurations.
 
-!!! tip "Tip1: edit only what you need"
+
+For a list of all possible configurations, see the [configuration options](https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml/) page.
+In addition to general configuration options, each tool has its own configurations. For example, the `review` tool will use parameters from the [pr_reviewer](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L16) section in the configuration file.
+
+!!! tip "Tip1: Edit only what you need"
     Your configuration file should be minimal, and edit only the relevant values. Don't copy the entire configuration options, since it can lead to legacy problems when something changes.
-!!! tip "Tip2: show relevant configurations"
-    If you set `config.output_relevant_configurations=true`, each tool will also output in a collapsible section its relevant configurations. This can be useful for debugging, or getting to know the configurations better.
+!!! tip "Tip2: Show relevant configurations"
+    If you set `config.output_relevant_configurations` to True, each tool will also output in a collapsible section its relevant configurations. This can be useful for debugging, or getting to know the configurations better.
+
+
 
 ## Wiki configuration file 💎
 
@@ -56,7 +58,7 @@ Then you can give a list of extra instructions to the `review` tool.
 
 ## Global configuration file 💎
 
-`Platforms supported: GitHub, GitLab, Bitbucket`
+`Platforms supported: GitHub, GitLab (cloud), Bitbucket (cloud)`
 
 If you create a repo called `pr-agent-settings` in your **organization**, its configuration file `.pr_agent.toml` will be used as a global configuration file for any other repo that belongs to the same organization.
 Parameters from a local `.pr_agent.toml` file, in a specific repo, will override the global configuration parameters.
@@ -67,18 +69,21 @@ For example, in the GitHub organization `Codium-ai`:
 
 - The repo [`https://github.com/Codium-ai/pr-agent`](https://github.com/Codium-ai/pr-agent/blob/main/.pr_agent.toml) inherits the global configuration file from `pr-agent-settings`.
 
-### Bitbucket Organization level configuration file 💎
+## Project/Group level configuration file 💎
+
+`Platforms supported: GitLab, Bitbucket Data Center`
+
+Create a repository named `pr-agent-settings` within a specific project (Bitbucket) or a group/subgroup (Gitlab). 
+The configuration file in this repository will apply to all repositories directly under the same project/group/subgroup.
+
+!!! note "Note"
+    For Gitlab, in case of a repository nested in several sub groups, the lookup for a pr-agent-settings repo will be only on one level above such repository.
+
+
+## Organization level configuration file 💎
 
 `Relevant platforms: Bitbucket Data Center`
 
-In Bitbucket Data Center, there are two levels where you can define a global configuration file:
-
-- Project-level global configuration:
-
-Create a repository named `pr-agent-settings` within a specific project. The configuration file in this repository will apply to all repositories under the same project.
-
-- Organization-level global configuration:
-
 Create a dedicated project to hold a global configuration file that affects all repositories across all projects in your organization.
 
 **Setting up organization-level global configuration:**
@@ -86,7 +91,7 @@ Create a dedicated project to hold a global configuration file that affects all
 1. Create a new project with both the name and key: PR_AGENT_SETTINGS.
 2. Inside the PR_AGENT_SETTINGS project, create a repository named pr-agent-settings.
 3. In this repository, add a `.pr_agent.toml` configuration file—structured similarly to the global configuration file described above.
-4. Optionally, you can add organizational-level [global best practices file](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/#global-configuration-file).
+4. Optionally, you can add organizational-level [global best practices](https://qodo-merge-docs.qodo.ai/tools/improve/#global-hierarchical-best-practices).
 
 Repositories across your entire Bitbucket organization will inherit the configuration from this file.
 

docs/docs/usage-guide/index.md

@@ -12,6 +12,7 @@ It includes information on how to adjust Qodo Merge configurations, define which
     - [GitHub App](./automations_and_usage.md#github-app)
     - [GitHub Action](./automations_and_usage.md#github-action)
     - [GitLab Webhook](./automations_and_usage.md#gitlab-webhook)
+    - [Gitea Webhook](./automations_and_usage.md#gitea-webhook)
     - [BitBucket App](./automations_and_usage.md#bitbucket-app)
     - [Azure DevOps Provider](./automations_and_usage.md#azure-devops-provider)
 - [Managing Mail Notifications](./mail_notifications.md)
@@ -21,6 +22,5 @@ It includes information on how to adjust Qodo Merge configurations, define which
     - [Extra instructions](./additional_configurations.md#extra-instructions)
     - [Working with large PRs](./additional_configurations.md#working-with-large-prs)
     - [Changing a model](https://qodo-merge-docs.qodo.ai/usage-guide/changing_a_model/)
-    - [Patch Extra Lines](./additional_configurations.md#patch-extra-lines)
 - [FAQ](https://qodo-merge-docs.qodo.ai/faq/)
 - [Qodo Merge Models](./qodo_merge_models)

docs/docs/usage-guide/qodo_merge_models.md

@@ -1,15 +1,15 @@
 
-The default models used by Qodo Merge (April 2025) are a combination of Claude Sonnet 3.7 and Gemini 2.5 Pro.
+The default models used by Qodo Merge 💎 (October 2025) are a combination of GPT-5, Haiku-4.5, and Gemini 2.5 Pro.
 
 ### Selecting a Specific Model
 
 Users can configure Qodo Merge to use only a specific model by editing the [configuration](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/) file.
 The models supported by Qodo Merge are:
 
-- `claude-3-7-sonnet`
-- `o4-mini`
-- `gpt-4.1`
+- `gpt-5`
+- `claude-haiku-4.5`
 - `gemini-2.5-pro`
+- `o4-mini`
 - `deepseek/r1`
 
 To restrict Qodo Merge to using only `o4-mini`, add this setting:
@@ -19,11 +19,11 @@ To restrict Qodo Merge to using only `o4-mini`, add this setting:
 model="o4-mini"
 ```
 
-To restrict Qodo Merge to using only `GPT-4.1`, add this setting:
+To restrict Qodo Merge to using only `GPT-5`, add this setting:
 
 ```toml
 [config]
-model="gpt-4.1"
+model="gpt-5"
 ```
 
 To restrict Qodo Merge to using only `gemini-2.5-pro`, add this setting:
@@ -33,10 +33,9 @@ To restrict Qodo Merge to using only `gemini-2.5-pro`, add this setting:
 model="gemini-2.5-pro"
 ```
 
-
-To restrict Qodo Merge to using only `deepseek-r1` us-hosted, add this setting:
+To restrict Qodo Merge to using only `claude-4-sonnet`, add this setting:
 
 ```toml
 [config]
-model="deepseek/r1"
+model="claude-4-sonnet"
 ```

docs/mkdocs.yml

@@ -21,49 +21,63 @@ nav:
     - Changing a Model: 'usage-guide/changing_a_model.md'
     - Additional Configurations: 'usage-guide/additional_configurations.md'
     - Frequently Asked Questions: 'faq/index.md'
-    - 💎 Qodo Merge Models: 'usage-guide/qodo_merge_models.md'
+    - Qodo Merge Models: 'usage-guide/qodo_merge_models.md'
   - Tools:
-    - 'tools/index.md'
-    - Describe: 'tools/describe.md'
-    - Review: 'tools/review.md'
-    - Improve: 'tools/improve.md'
-    - Ask: 'tools/ask.md'
-    - Update Changelog: 'tools/update_changelog.md'
-    - Help Docs: 'tools/help_docs.md'
-    - Help: 'tools/help.md'
-    - 💎 Analyze: 'tools/analyze.md'
-    - 💎 Test: 'tools/test.md'
-    - 💎 Improve Component: 'tools/improve_component.md'
-    - 💎 Documentation: 'tools/documentation.md'
-    - 💎 Custom Labels: 'tools/custom_labels.md'
-    - 💎 Custom Prompt: 'tools/custom_prompt.md'
-    - 💎 CI Feedback: 'tools/ci_feedback.md'
-    - 💎 Similar Code: 'tools/similar_code.md'
-    - 💎 Implement: 'tools/implement.md'
-    - 💎 Scan Repo Discussions: 'tools/scan_repo_discussions.md'
+     - 'tools/index.md'
+     - Describe: 'tools/describe.md'
+     - Review: 'tools/review.md'
+     - Improve: 'tools/improve.md'
+     - Ask: 'tools/ask.md'
+     - Help: 'tools/help.md'
+     - Help Docs: 'tools/help_docs.md'
+     - Update Changelog: 'tools/update_changelog.md'
+     - 💎 Add Documentation: 'tools/documentation.md'
+     - 💎 Analyze: 'tools/analyze.md'
+     - 💎 CI Feedback: 'tools/ci_feedback.md'
+     - 💎 Compliance: 'tools/compliance.md'
+     - 💎 Custom Prompt: 'tools/custom_prompt.md'
+     - 💎 Generate Labels: 'tools/custom_labels.md'
+     - 💎 Generate Tests: 'tools/test.md'
+     - 💎 Implement: 'tools/implement.md'
+     - 💎 Improve Components: 'tools/improve_component.md'
+     - 💎 PR to Ticket: 'tools/pr_to_ticket.md'
+     - 💎 Scan Repo Discussions: 'tools/scan_repo_discussions.md'
+     - 💎 Similar Code: 'tools/similar_code.md'
   - Core Abilities:
       - 'core-abilities/index.md'
+      - Auto approval: 'core-abilities/auto_approval.md'
       - Auto best practices: 'core-abilities/auto_best_practices.md'
+      - Chat on code suggestions: 'core-abilities/chat_on_code_suggestions.md'
+      - Chrome extension: 'chrome-extension/index.md'
       - Code validation: 'core-abilities/code_validation.md'
-      - Compression strategy: 'core-abilities/compression_strategy.md'
+#      - Compression strategy: 'core-abilities/compression_strategy.md'
       - Dynamic context: 'core-abilities/dynamic_context.md'
       - Fetching ticket context: 'core-abilities/fetching_ticket_context.md'
+      - High-level Suggestions: 'core-abilities/high_level_suggestions.md'
       - Impact evaluation: 'core-abilities/impact_evaluation.md'
+      - Incremental Update: 'core-abilities/incremental_update.md'
       - Interactivity: 'core-abilities/interactivity.md'
       - Local and global metadata: 'core-abilities/metadata.md'
       - RAG context enrichment: 'core-abilities/rag_context_enrichment.md'
       - Self-reflection: 'core-abilities/self_reflection.md'
       - Static code analysis: 'core-abilities/static_code_analysis.md'
-  - Chrome Extension:
-      - Qodo Merge Chrome Extension: 'chrome-extension/index.md'
-      - Features: 'chrome-extension/features.md'
-      - Data Privacy: 'chrome-extension/data_privacy.md'
-      - Options: 'chrome-extension/options.md'
+#  - Chrome Extension:
+#      - Qodo Merge Chrome Extension: 'chrome-extension/index.md'
+#      - Features: 'chrome-extension/features.md'
+#      - Data Privacy: 'chrome-extension/data_privacy.md'
+#      - Options: 'chrome-extension/options.md'
+  - Qodo Merge CLI:
+      - Overview: 'qodo-merge-cli/index.md'
+      - Installation: 'qodo-merge-cli/installation.md'
+      - Usage: 'qodo-merge-cli/usage.md'
+      #- Features & Usage: 'qodo-merge-cli/features.md'
+  #      - Troubleshooting: 'qodo-merge-cli/troubleshooting.md'
   - PR Benchmark:
       - PR Benchmark: 'pr_benchmark/index.md'
   - Recent Updates:
       - Recent Updates: 'recent_updates/index.md'
   - AI Docs Search: 'ai_search/index.md'
+
 #  - Code Fine-tuning Benchmark: 'finetuning_benchmark/index.md'
 
 theme:

docs/overrides/partials/integrations/analytics/custom.html

@@ -3,5 +3,5 @@
     new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
     j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
     'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
-    })(window,document,'script','dataLayer','GTM-M6PJSFV');</script>
+    })(window,document,'script','dataLayer','GTM-5C9KZBM3');</script>
     <!-- End Google Tag Manager -->

pr_agent/agent/pr_agent.py

@@ -51,7 +51,7 @@ class PRAgent:
     def __init__(self, ai_handler: partial[BaseAiHandler,] = LiteLLMAIHandler):
         self.ai_handler = ai_handler  # will be initialized in run_action
 
-    async def handle_request(self, pr_url, request, notify=None) -> bool:
+    async def _handle_request(self, pr_url, request, notify=None) -> bool:
         # First, apply repo specific settings if exists
         apply_repo_settings(pr_url)
 
@@ -117,3 +117,10 @@ class PRAgent:
             else:
                 return False
             return True
+
+    async def handle_request(self, pr_url, request, notify=None) -> bool:
+        try:
+            return await self._handle_request(pr_url, request, notify)
+        except:
+            get_logger().exception("Failed to process the command.")
+            return False

pr_agent/algo/__init__.py

@@ -28,6 +28,15 @@ MAX_TOKENS = {
     'gpt-4.1-mini-2025-04-14': 1047576,
     'gpt-4.1-nano': 1047576,
     'gpt-4.1-nano-2025-04-14': 1047576,
+    'gpt-5-nano': 200000,  # 200K, but may be limited by config.max_model_tokens
+    'gpt-5-mini': 200000,  # 200K, but may be limited by config.max_model_tokens
+    'gpt-5': 200000,
+    'gpt-5-2025-08-07': 200000,
+    'gpt-5.1': 200000,
+    'gpt-5.1-2025-11-13': 200000,
+    'gpt-5.1-chat-latest': 200000,
+    'gpt-5.1-codex': 200000,
+    'gpt-5.1-codex-mini': 200000,
     'o1-mini': 128000,  # 128K, but may be limited by config.max_model_tokens
     'o1-mini-2024-09-12': 128000,  # 128K, but may be limited by config.max_model_tokens
     'o1-preview': 128000,  # 128K, but may be limited by config.max_model_tokens
@@ -45,6 +54,7 @@ MAX_TOKENS = {
     'command-nightly': 4096,
     'deepseek/deepseek-chat': 128000,  # 128K, but may be limited by config.max_model_tokens
     'deepseek/deepseek-reasoner': 64000,  # 64K, but may be limited by config.max_model_tokens
+    'openai/qwq-plus': 131072,  # 131K context length, but may be limited by config.max_model_tokens
     'replicate/llama-2-70b-chat:2c1608e18606fad2812020dc541930f2d0495ce32eee50074220b87300bc16e1': 4096,
     'meta-llama/Llama-2-7b-chat-hf': 4096,
     'vertex_ai/codechat-bison': 6144,
@@ -53,58 +63,91 @@ MAX_TOKENS = {
     'vertex_ai/claude-3-5-haiku@20241022': 100000,
     'vertex_ai/claude-3-sonnet@20240229': 100000,
     'vertex_ai/claude-3-opus@20240229': 100000,
+    'vertex_ai/claude-opus-4@20250514': 200000,
     'vertex_ai/claude-3-5-sonnet@20240620': 100000,
     'vertex_ai/claude-3-5-sonnet-v2@20241022': 100000,
     'vertex_ai/claude-3-7-sonnet@20250219': 200000,
+    'vertex_ai/claude-sonnet-4@20250514': 200000,
+    'vertex_ai/claude-sonnet-4-5@20250929': 200000,
     'vertex_ai/gemini-1.5-pro': 1048576,
     'vertex_ai/gemini-2.5-pro-preview-03-25': 1048576,
     'vertex_ai/gemini-2.5-pro-preview-05-06': 1048576,
+    'vertex_ai/gemini-2.5-pro-preview-06-05': 1048576,
+    'vertex_ai/gemini-2.5-pro': 1048576,
     'vertex_ai/gemini-1.5-flash': 1048576,
     'vertex_ai/gemini-2.0-flash': 1048576,
     'vertex_ai/gemini-2.5-flash-preview-04-17': 1048576,
+    'vertex_ai/gemini-2.5-flash-preview-05-20': 1048576,
+    'vertex_ai/gemini-2.5-flash': 1048576,
     'vertex_ai/gemma2': 8200,
     'gemini/gemini-1.5-pro': 1048576,
     'gemini/gemini-1.5-flash': 1048576,
     'gemini/gemini-2.0-flash': 1048576,
+    'gemini/gemini-2.5-flash-preview-04-17': 1048576,
+    'gemini/gemini-2.5-flash-preview-05-20': 1048576,
+    'gemini/gemini-2.5-flash': 1048576,
     'gemini/gemini-2.5-pro-preview-03-25': 1048576,
     'gemini/gemini-2.5-pro-preview-05-06': 1048576,
+    'gemini/gemini-2.5-pro-preview-06-05': 1048576,
+    'gemini/gemini-2.5-pro': 1048576,
     'codechat-bison': 6144,
     'codechat-bison-32k': 32000,
     'anthropic.claude-instant-v1': 100000,
     'anthropic.claude-v1': 100000,
     'anthropic.claude-v2': 100000,
     'anthropic/claude-3-opus-20240229': 100000,
+    'anthropic/claude-opus-4-20250514': 200000,
     'anthropic/claude-3-5-sonnet-20240620': 100000,
     'anthropic/claude-3-5-sonnet-20241022': 100000,
     'anthropic/claude-3-7-sonnet-20250219': 200000,
+    'anthropic/claude-sonnet-4-20250514': 200000,
+    'anthropic/claude-sonnet-4-5-20250929': 200000,
     'claude-3-7-sonnet-20250219': 200000,
     'anthropic/claude-3-5-haiku-20241022': 100000,
     'bedrock/anthropic.claude-instant-v1': 100000,
     'bedrock/anthropic.claude-v2': 100000,
     'bedrock/anthropic.claude-v2:1': 100000,
     'bedrock/anthropic.claude-3-sonnet-20240229-v1:0': 100000,
+    'bedrock/anthropic.claude-opus-4-20250514-v1:0': 200000,
     'bedrock/anthropic.claude-3-haiku-20240307-v1:0': 100000,
     'bedrock/anthropic.claude-3-5-haiku-20241022-v1:0': 100000,
     'bedrock/anthropic.claude-3-5-sonnet-20240620-v1:0': 100000,
     'bedrock/anthropic.claude-3-5-sonnet-20241022-v2:0': 100000,
     'bedrock/anthropic.claude-3-7-sonnet-20250219-v1:0': 200000,
+    'bedrock/anthropic.claude-sonnet-4-20250514-v1:0': 200000,
+    'bedrock/anthropic.claude-sonnet-4-5-20250929-v1:0': 200000,
+    "bedrock/us.anthropic.claude-opus-4-20250514-v1:0": 200000,
     "bedrock/us.anthropic.claude-3-5-sonnet-20241022-v2:0": 100000,
     "bedrock/us.anthropic.claude-3-7-sonnet-20250219-v1:0": 200000,
+    "bedrock/us.anthropic.claude-sonnet-4-20250514-v1:0": 200000,
+    "bedrock/us.anthropic.claude-sonnet-4-5-20250929-v1:0": 200000,
+    "bedrock/apac.anthropic.claude-3-5-sonnet-20241022-v2:0": 100000,
+    "bedrock/apac.anthropic.claude-3-7-sonnet-20250219-v1:0": 200000,
+    "bedrock/apac.anthropic.claude-sonnet-4-20250514-v1:0": 200000,
+    "bedrock/jp.anthropic.claude-sonnet-4-5-20250929-v1:0": 200000,
+    "bedrock/global.anthropic.claude-sonnet-4-5-20250929-v1:0": 200000,
     'claude-3-5-sonnet': 100000,
-    'groq/meta-llama/llama-4-scout-17b-16e-instruct': 131072,
+    'bedrock/us.meta.llama4-scout-17b-instruct-v1:0': 128000,
+    'bedrock/us.meta.llama4-maverick-17b-instruct-v1:0': 128000,
+    'groq/openai/gpt-oss-120b': 131072,
+    'groq/openai/gpt-oss-20b': 131072,
+    'groq/qwen/qwen3-32b': 131000,
+    'groq/moonshotai/kimi-k2-instruct': 131072,
+    'groq/deepseek-r1-distill-llama-70b': 128000,
     'groq/meta-llama/llama-4-maverick-17b-128e-instruct': 131072,
-    'groq/llama3-8b-8192': 8192,
-    'groq/llama3-70b-8192': 8192,
-    'groq/llama-3.1-8b-instant': 8192,
+    'groq/meta-llama/llama-4-scout-17b-16e-instruct': 131072,
     'groq/llama-3.3-70b-versatile': 128000,
-    'groq/mixtral-8x7b-32768': 32768,
-    'groq/gemma2-9b-it': 8192,
+    'groq/llama-3.1-8b-instant': 128000,
     'xai/grok-2': 131072,
     'xai/grok-2-1212': 131072,
     'xai/grok-2-latest': 131072,
+    'xai/grok-3': 131072,
     'xai/grok-3-beta': 131072,
+    'xai/grok-3-fast': 131072,
     'xai/grok-3-fast-beta': 131072,
+    'xai/grok-3-mini': 131072,
     'xai/grok-3-mini-beta': 131072,
+    'xai/grok-3-mini-fast': 131072,
     'xai/grok-3-mini-fast-beta': 131072,
     'ollama/llama3': 4096,
     'watsonx/meta-llama/llama-3-8b-instruct': 4096,
@@ -167,3 +210,8 @@ CLAUDE_EXTENDED_THINKING_MODELS = [
     "anthropic/claude-3-7-sonnet-20250219",
     "claude-3-7-sonnet-20250219"
 ]
+
+# Models that require streaming mode
+STREAMING_REQUIRED_MODELS = [
+    "openai/qwq-plus"
+]

pr_agent/algo/ai_handlers/langchain_ai_handler.py

@@ -1,13 +1,17 @@
+_LANGCHAIN_INSTALLED = False
+
 try:
     from langchain_core.messages import HumanMessage, SystemMessage
     from langchain_openai import AzureChatOpenAI, ChatOpenAI
+    _LANGCHAIN_INSTALLED = True
 except:  # we don't enforce langchain as a dependency, so if it's not installed, just move on
     pass
 
 import functools
 
-from openai import APIError, RateLimitError, Timeout
-from retry import retry
+import openai
+from tenacity import retry, retry_if_exception_type, retry_if_not_exception_type, stop_after_attempt
+from langchain_core.runnables import Runnable
 
 from pr_agent.algo.ai_handlers.base_ai_handler import BaseAiHandler
 from pr_agent.config_loader import get_settings
@@ -18,17 +22,14 @@ OPENAI_RETRIES = 5
 
 class LangChainOpenAIHandler(BaseAiHandler):
     def __init__(self):
-        # Initialize OpenAIHandler specific attributes here
+        if not _LANGCHAIN_INSTALLED:
+            error_msg = "LangChain is not installed. Please install it with `pip install langchain`."
+            get_logger().error(error_msg)
+            raise ImportError(error_msg)
+        
         super().__init__()
         self.azure = get_settings().get("OPENAI.API_TYPE", "").lower() == "azure"
 
-        # Create a default unused chat object to trigger early validation
-        self._create_chat(self.deployment_id)
-
-    def chat(self, messages: list, model: str, temperature: float):
-        chat = self._create_chat(self.deployment_id)
-        return chat.invoke(input=messages, model=model, temperature=temperature)
-
     @property
     def deployment_id(self):
         """
@@ -36,26 +37,10 @@ class LangChainOpenAIHandler(BaseAiHandler):
         """
         return get_settings().get("OPENAI.DEPLOYMENT_ID", None)
 
-    @retry(exceptions=(APIError, Timeout, AttributeError, RateLimitError),
-           tries=OPENAI_RETRIES, delay=2, backoff=2, jitter=(1, 3))
-    async def chat_completion(self, model: str, system: str, user: str, temperature: float = 0.2):
-        try:
-            messages = [SystemMessage(content=system), HumanMessage(content=user)]
-
-            # get a chat completion from the formatted messages
-            resp = self.chat(messages, model=model, temperature=temperature)
-            finish_reason = "completed"
-            return resp.content, finish_reason
-
-        except (Exception) as e:
-            get_logger().error("Unknown error during OpenAI inference: ", e)
-            raise e
-
-    def _create_chat(self, deployment_id=None):
+    async def _create_chat_async(self, deployment_id=None):
         try:
             if self.azure:
-                # using a partial function so we can set the deployment_id later to support fallback_deployments
-                # but still need to access the other settings now so we can raise a proper exception if they're missing
+                # Using Azure OpenAI service
                 return AzureChatOpenAI(
                     openai_api_key=get_settings().openai.key,
                     openai_api_version=get_settings().openai.api_version,
@@ -63,14 +48,64 @@ class LangChainOpenAIHandler(BaseAiHandler):
                     azure_endpoint=get_settings().openai.api_base,
                 )
             else:
-                # for llms that compatible with openai, should use custom api base
+                # Using standard OpenAI or other LLM services
                 openai_api_base = get_settings().get("OPENAI.API_BASE", None)
                 if openai_api_base is None or len(openai_api_base) == 0:
                     return ChatOpenAI(openai_api_key=get_settings().openai.key)
                 else:
-                    return ChatOpenAI(openai_api_key=get_settings().openai.key, openai_api_base=openai_api_base)
+                    return ChatOpenAI(
+                        openai_api_key=get_settings().openai.key, 
+                        openai_api_base=openai_api_base
+                    )
         except AttributeError as e:
-            if getattr(e, "name"):
-                raise ValueError(f"OpenAI {e.name} is required") from e
+            # Handle configuration errors
+            error_msg = f"OpenAI {e.name} is required" if getattr(e, "name") else str(e)
+            get_logger().error(error_msg)
+            raise ValueError(error_msg) from e
+
+    @retry(
+        retry=retry_if_exception_type(openai.APIError) & retry_if_not_exception_type(openai.RateLimitError),
+        stop=stop_after_attempt(OPENAI_RETRIES),
+    )
+    async def chat_completion(self, model: str, system: str, user: str, temperature: float = 0.2, img_path: str = None):
+        if img_path:
+            get_logger().warning(f"Image path is not supported for LangChainOpenAIHandler. Ignoring image path: {img_path}")
+        try:
+            messages = [SystemMessage(content=system), HumanMessage(content=user)]
+            llm = await self._create_chat_async(deployment_id=self.deployment_id)
+            
+            if not isinstance(llm, Runnable):
+                error_message = (
+                    f"The Langchain LLM object ({type(llm)}) does not implement the Runnable interface. "
+                    f"Please update your Langchain library to the latest version or "
+                    f"check your LLM configuration to support async calls. "
+                    f"PR-Agent is designed to utilize Langchain's async capabilities."
+                )
+                get_logger().error(error_message)
+                raise NotImplementedError(error_message)
+
+            # Handle parameters based on LLM type
+            if isinstance(llm, (ChatOpenAI, AzureChatOpenAI)):
+                # OpenAI models support all parameters
+                resp = await llm.ainvoke(
+                    input=messages,
+                    model=model,
+                    temperature=temperature
+                )
             else:
-                raise e
+                # Other LLMs (like Gemini) only support input parameter
+                get_logger().info(f"Using simplified ainvoke for {type(llm)}")
+                resp = await llm.ainvoke(input=messages)
+
+            finish_reason = "completed"
+            return resp.content, finish_reason
+
+        except openai.RateLimitError as e:
+            get_logger().error(f"Rate limit error during LLM inference: {e}")
+            raise
+        except openai.APIError as e:
+            get_logger().warning(f"Error during LLM inference: {e}")
+            raise
+        except Exception as e:
+            get_logger().warning(f"Unknown error during LLM inference: {e}")
+            raise openai.APIError from e

pr_agent/algo/ai_handlers/litellm_ai_handler.py

@@ -3,16 +3,18 @@ import litellm
 import openai
 import requests
 from litellm import acompletion
-from tenacity import retry, retry_if_exception_type, stop_after_attempt
+from tenacity import retry, retry_if_exception_type, retry_if_not_exception_type, stop_after_attempt
 
-from pr_agent.algo import CLAUDE_EXTENDED_THINKING_MODELS, NO_SUPPORT_TEMPERATURE_MODELS, SUPPORT_REASONING_EFFORT_MODELS, USER_MESSAGE_ONLY_MODELS
+from pr_agent.algo import CLAUDE_EXTENDED_THINKING_MODELS, NO_SUPPORT_TEMPERATURE_MODELS, SUPPORT_REASONING_EFFORT_MODELS, USER_MESSAGE_ONLY_MODELS, STREAMING_REQUIRED_MODELS
 from pr_agent.algo.ai_handlers.base_ai_handler import BaseAiHandler
+from pr_agent.algo.ai_handlers.litellm_helpers import _handle_streaming_response, MockResponse, _get_azure_ad_token, \
+    _process_litellm_extra_body
 from pr_agent.algo.utils import ReasoningEffort, get_version
 from pr_agent.config_loader import get_settings
 from pr_agent.log import get_logger
 import json
 
-OPENAI_RETRIES = 5
+MODEL_RETRIES = 2
 
 
 class LiteLLMAIHandler(BaseAiHandler):
@@ -30,7 +32,9 @@ class LiteLLMAIHandler(BaseAiHandler):
         self.azure = False
         self.api_base = None
         self.repetition_penalty = None
-        
+
+        if get_settings().get("LITELLM.DISABLE_AIOHTTP", False):
+            litellm.disable_aiohttp_transport = True
         if get_settings().get("OPENAI.KEY", None):
             openai.api_key = get_settings().openai.key
             litellm.openai_key = get_settings().openai.key
@@ -110,7 +114,7 @@ class LiteLLMAIHandler(BaseAiHandler):
         if get_settings().get("AZURE_AD.CLIENT_ID", None):
             self.azure = True
             # Generate access token using Azure AD credentials from settings
-            access_token = self._get_azure_ad_token()
+            access_token = _get_azure_ad_token()
             litellm.api_key = access_token
             openai.api_key = access_token
             
@@ -131,7 +135,7 @@ class LiteLLMAIHandler(BaseAiHandler):
             self.api_base = openrouter_api_base
             litellm.api_base = openrouter_api_base
 
-        # Models that only use user meessage
+        # Models that only use user message
         self.user_message_only_models = USER_MESSAGE_ONLY_MODELS
 
         # Model that doesn't support temperature argument
@@ -143,25 +147,8 @@ class LiteLLMAIHandler(BaseAiHandler):
         # Models that support extended thinking
         self.claude_extended_thinking_models = CLAUDE_EXTENDED_THINKING_MODELS
 
-    def _get_azure_ad_token(self):
-        """
-        Generates an access token using Azure AD credentials from settings.
-        Returns:
-            str: The access token
-        """
-        from azure.identity import ClientSecretCredential
-        try:
-            credential = ClientSecretCredential(
-                tenant_id=get_settings().azure_ad.tenant_id,
-                client_id=get_settings().azure_ad.client_id,
-                client_secret=get_settings().azure_ad.client_secret
-            )
-            # Get token for Azure OpenAI service
-            token = credential.get_token("https://cognitiveservices.azure.com/.default")
-            return token.token
-        except Exception as e:
-            get_logger().error(f"Failed to get Azure AD token: {e}")
-            raise
+        # Models that require streaming
+        self.streaming_required_models = STREAMING_REQUIRED_MODELS
 
     def prepare_logs(self, response, system, user, resp, finish_reason):
         response_log = response.dict().copy()
@@ -212,7 +199,7 @@ class LiteLLMAIHandler(BaseAiHandler):
 
         return kwargs
 
-    def add_litellm_callbacks(selfs, kwargs) -> dict:
+    def add_litellm_callbacks(self, kwargs) -> dict:
         captured_extra = []
 
         def capture_logs(message):
@@ -274,8 +261,8 @@ class LiteLLMAIHandler(BaseAiHandler):
         return get_settings().get("OPENAI.DEPLOYMENT_ID", None)
 
     @retry(
-        retry=retry_if_exception_type((openai.APIError, openai.APIConnectionError, openai.APITimeoutError)), # No retry on RateLimitError
-        stop=stop_after_attempt(OPENAI_RETRIES)
+        retry=retry_if_exception_type(openai.APIError) & retry_if_not_exception_type(openai.RateLimitError),
+        stop=stop_after_attempt(MODEL_RETRIES),
     )
     async def chat_completion(self, model: str, system: str, user: str, temperature: float = 0.2, img_path: str = None):
         try:
@@ -303,6 +290,21 @@ class LiteLLMAIHandler(BaseAiHandler):
                 messages[1]["content"] = [{"type": "text", "text": messages[1]["content"]},
                                           {"type": "image_url", "image_url": {"url": img_path}}]
 
+            thinking_kwargs_gpt5 = None
+            if model.startswith('gpt-5'):
+                if model.endswith('_thinking'):
+                    thinking_kwargs_gpt5 = {
+                        "reasoning_effort": 'low',
+                        "allowed_openai_params": ["reasoning_effort"],
+                    }
+                else:
+                    thinking_kwargs_gpt5 = {
+                        "reasoning_effort": 'minimal',
+                        "allowed_openai_params": ["reasoning_effort"],
+                    }
+                model = 'openai/'+model.replace('_thinking', '')  # remove _thinking suffix
+
+
             # Currently, some models do not support a separate system and user prompts
             if model in self.user_message_only_models or get_settings().config.custom_reasoning_model:
                 user = f"{system}\n\n\n{user}"
@@ -330,6 +332,11 @@ class LiteLLMAIHandler(BaseAiHandler):
                 # get_logger().info(f"Adding temperature with value {temperature} to model {model}.")
                 kwargs["temperature"] = temperature
 
+            if thinking_kwargs_gpt5:
+                kwargs.update(thinking_kwargs_gpt5)
+                if 'temperature' in kwargs:
+                    del kwargs['temperature']
+
             # Add reasoning_effort if model supports it
             if (model in self.support_reasoning_models):
                 supported_reasoning_efforts = [ReasoningEffort.HIGH.value, ReasoningEffort.MEDIUM.value, ReasoningEffort.LOW.value]
@@ -364,35 +371,63 @@ class LiteLLMAIHandler(BaseAiHandler):
                     raise ValueError(f"LITELLM.EXTRA_HEADERS contains invalid JSON: {str(e)}")
                 kwargs["extra_headers"] = litellm_extra_headers
 
+            # Support for custom OpenAI body fields (e.g., Flex Processing)
+            kwargs = _process_litellm_extra_body(kwargs)
+
+            # Support for Bedrock custom inference profile via model_id
+            model_id = get_settings().get("litellm.model_id")
+            if model_id and 'bedrock/' in model:
+                kwargs["model_id"] = model_id
+                get_logger().info(f"Using Bedrock custom inference profile: {model_id}")
+
             get_logger().debug("Prompts", artifact={"system": system, "user": user})
 
             if get_settings().config.verbosity_level >= 2:
                 get_logger().info(f"\nSystem prompt:\n{system}")
                 get_logger().info(f"\nUser prompt:\n{user}")
 
-            response = await acompletion(**kwargs)
-        except (openai.APIError, openai.APITimeoutError) as e:
-            get_logger().warning(f"Error during LLM inference: {e}")
-            raise
-        except (openai.RateLimitError) as e:
+            # Get completion with automatic streaming detection
+            resp, finish_reason, response_obj = await self._get_completion(**kwargs)
+
+        except openai.RateLimitError as e:
             get_logger().error(f"Rate limit error during LLM inference: {e}")
             raise
-        except (Exception) as e:
+        except openai.APIError as e:
+            get_logger().warning(f"Error during LLM inference: {e}")
+            raise
+        except Exception as e:
             get_logger().warning(f"Unknown error during LLM inference: {e}")
             raise openai.APIError from e
-        if response is None or len(response["choices"]) == 0:
-            raise openai.APIError
-        else:
-            resp = response["choices"][0]['message']['content']
-            finish_reason = response["choices"][0]["finish_reason"]
-            get_logger().debug(f"\nAI response:\n{resp}")
 
-            # log the full response for debugging
-            response_log = self.prepare_logs(response, system, user, resp, finish_reason)
-            get_logger().debug("Full_response", artifact=response_log)
+        get_logger().debug(f"\nAI response:\n{resp}")
 
-            # for CLI debugging
-            if get_settings().config.verbosity_level >= 2:
-                get_logger().info(f"\nAI response:\n{resp}")
+        # log the full response for debugging
+        response_log = self.prepare_logs(response_obj, system, user, resp, finish_reason)
+        get_logger().debug("Full_response", artifact=response_log)
+
+        # for CLI debugging
+        if get_settings().config.verbosity_level >= 2:
+            get_logger().info(f"\nAI response:\n{resp}")
 
         return resp, finish_reason
+
+    async def _get_completion(self, **kwargs):
+        """
+        Wrapper that automatically handles streaming for required models.
+        """
+        model = kwargs["model"]
+        if model in self.streaming_required_models:
+            kwargs["stream"] = True
+            get_logger().info(f"Using streaming mode for model {model}")
+            response = await acompletion(**kwargs)
+            resp, finish_reason = await _handle_streaming_response(response)
+            # Create MockResponse for streaming since we don't have the full response object
+            mock_response = MockResponse(resp, finish_reason)
+            return resp, finish_reason, mock_response
+        else:
+            response = await acompletion(**kwargs)
+            if response is None or len(response["choices"]) == 0:
+                raise openai.APIError
+            return (response["choices"][0]['message']['content'],
+                    response["choices"][0]["finish_reason"],
+                    response)

pr_agent/algo/ai_handlers/litellm_helpers.py

@@ -0,0 +1,112 @@
+import json
+
+import openai
+
+from pr_agent.config_loader import get_settings
+from pr_agent.log import get_logger
+
+
+async def _handle_streaming_response(response):
+    """
+    Handle streaming response from acompletion and collect the full response.
+
+    Args:
+        response: The streaming response object from acompletion
+
+    Returns:
+        tuple: (full_response_content, finish_reason)
+    """
+    full_response = ""
+    finish_reason = None
+
+    try:
+        async for chunk in response:
+            if chunk.choices and len(chunk.choices) > 0:
+                choice = chunk.choices[0]
+                delta = choice.delta
+                content = getattr(delta, 'content', None)
+                if content:
+                    full_response += content
+                if choice.finish_reason:
+                    finish_reason = choice.finish_reason
+    except Exception as e:
+        get_logger().error(f"Error handling streaming response: {e}")
+        raise
+
+    if not full_response and finish_reason is None:
+        get_logger().warning("Streaming response resulted in empty content with no finish reason")
+        raise openai.APIError("Empty streaming response received without proper completion")
+    elif not full_response and finish_reason:
+        get_logger().debug(f"Streaming response resulted in empty content but completed with finish_reason: {finish_reason}")
+        raise openai.APIError(f"Streaming response completed with finish_reason '{finish_reason}' but no content received")
+    return full_response, finish_reason
+
+
+class MockResponse:
+    """Mock response object for streaming models to enable consistent logging."""
+
+    def __init__(self, resp, finish_reason):
+        self._data = {
+            "choices": [
+                {
+                    "message": {"content": resp},
+                    "finish_reason": finish_reason
+                }
+            ]
+        }
+
+    def dict(self):
+        return self._data
+
+
+def _get_azure_ad_token():
+    """
+    Generates an access token using Azure AD credentials from settings.
+    Returns:
+        str: The access token
+    """
+    from azure.identity import ClientSecretCredential
+    try:
+        credential = ClientSecretCredential(
+            tenant_id=get_settings().azure_ad.tenant_id,
+            client_id=get_settings().azure_ad.client_id,
+            client_secret=get_settings().azure_ad.client_secret
+        )
+        # Get token for Azure OpenAI service
+        token = credential.get_token("https://cognitiveservices.azure.com/.default")
+        return token.token
+    except Exception as e:
+        get_logger().error(f"Failed to get Azure AD token: {e}")
+        raise
+
+
+def _process_litellm_extra_body(kwargs: dict) -> dict:
+    """
+    Process LITELLM.EXTRA_BODY configuration and update kwargs accordingly.
+
+    Args:
+        kwargs: The current kwargs dictionary to update
+
+    Returns:
+        Updated kwargs dictionary
+
+    Raises:
+        ValueError: If extra_body contains invalid JSON, unsupported keys, or colliding keys
+    """
+    allowed_extra_body_keys = {"processing_mode", "service_tier"}
+    extra_body = getattr(getattr(get_settings(), "litellm", None), "extra_body", None)
+    if extra_body:
+        try:
+            litellm_extra_body = json.loads(extra_body)
+            if not isinstance(litellm_extra_body, dict):
+                raise ValueError("LITELLM.EXTRA_BODY must be a JSON object")
+            unsupported_keys = set(litellm_extra_body.keys()) - allowed_extra_body_keys
+            if unsupported_keys:
+                raise ValueError(f"LITELLM.EXTRA_BODY contains unsupported keys: {', '.join(unsupported_keys)}. Allowed keys: {', '.join(allowed_extra_body_keys)}")
+            colliding_keys = kwargs.keys() & litellm_extra_body.keys()
+            if colliding_keys:
+                raise ValueError(f"LITELLM.EXTRA_BODY cannot override existing parameters: {', '.join(colliding_keys)}")
+            kwargs.update(litellm_extra_body)
+        except json.JSONDecodeError as e:
+            raise ValueError(f"LITELLM.EXTRA_BODY contains invalid JSON: {str(e)}")
+    return kwargs

pr_agent/algo/ai_handlers/openai_ai_handler.py

@@ -1,8 +1,8 @@
 from os import environ
 from pr_agent.algo.ai_handlers.base_ai_handler import BaseAiHandler
 import openai
-from openai import APIError, AsyncOpenAI, RateLimitError, Timeout
-from retry import retry
+from openai import AsyncOpenAI
+from tenacity import retry, retry_if_exception_type, retry_if_not_exception_type, stop_after_attempt
 
 from pr_agent.algo.ai_handlers.base_ai_handler import BaseAiHandler
 from pr_agent.config_loader import get_settings
@@ -38,10 +38,14 @@ class OpenAIHandler(BaseAiHandler):
         """
         return get_settings().get("OPENAI.DEPLOYMENT_ID", None)
 
-    @retry(exceptions=(APIError, Timeout, AttributeError, RateLimitError),
-           tries=OPENAI_RETRIES, delay=2, backoff=2, jitter=(1, 3))
-    async def chat_completion(self, model: str, system: str, user: str, temperature: float = 0.2):
+    @retry(
+        retry=retry_if_exception_type(openai.APIError) & retry_if_not_exception_type(openai.RateLimitError),
+        stop=stop_after_attempt(OPENAI_RETRIES),
+    )
+    async def chat_completion(self, model: str, system: str, user: str, temperature: float = 0.2, img_path: str = None):
         try:
+            if img_path:
+                get_logger().warning(f"Image path is not supported for OpenAIHandler. Ignoring image path: {img_path}")
             get_logger().info("System: ", system)
             get_logger().info("User: ", user)
             messages = [{"role": "system", "content": system}, {"role": "user", "content": user}]
@@ -57,12 +61,12 @@ class OpenAIHandler(BaseAiHandler):
             get_logger().info("AI response", response=resp, messages=messages, finish_reason=finish_reason,
                               model=model, usage=usage)
             return resp, finish_reason
-        except (APIError, Timeout) as e:
-            get_logger().error("Error during OpenAI inference: ", e)
+        except openai.RateLimitError as e:
+            get_logger().error(f"Rate limit error during LLM inference: {e}")
             raise
-        except (RateLimitError) as e:
-            get_logger().error("Rate limit error during OpenAI inference: ", e)
-            raise
-        except (Exception) as e:
-            get_logger().error("Unknown error during OpenAI inference: ", e)
+        except openai.APIError as e:
+            get_logger().warning(f"Error during LLM inference: {e}")
             raise
+        except Exception as e:
+            get_logger().warning(f"Unknown error during LLM inference: {e}")
+            raise openai.APIError from e

pr_agent/algo/file_filter.py

@@ -2,6 +2,7 @@ import fnmatch
 import re
 
 from pr_agent.config_loader import get_settings
+from pr_agent.log import get_logger
 
 
 def filter_ignored(files, platform = 'github'):
@@ -17,7 +18,17 @@ def filter_ignored(files, platform = 'github'):
         glob_setting = get_settings().ignore.glob
         if isinstance(glob_setting, str):  # --ignore.glob=[.*utils.py], --ignore.glob=.*utils.py
             glob_setting = glob_setting.strip('[]').split(",")
-        patterns += [fnmatch.translate(glob) for glob in glob_setting]
+        patterns += translate_globs_to_regexes(glob_setting)
+
+        code_generators = get_settings().config.get('ignore_language_framework', [])
+        if isinstance(code_generators, str):
+            get_logger().warning("'ignore_language_framework' should be a list. Skipping language framework filtering.")
+            code_generators = []
+        for cg in code_generators:
+            glob_patterns = get_settings().generated_code.get(cg, [])
+            if isinstance(glob_patterns, str):
+                glob_patterns = [glob_patterns]
+            patterns += translate_globs_to_regexes(glob_patterns)
 
         # compile all valid patterns
         compiled_patterns = []
@@ -45,6 +56,8 @@ def filter_ignored(files, platform = 'github'):
                                 files_o.append(f)
                                 continue
                     files = files_o
+                elif platform == 'bitbucket_server':
+                    files = [f for f in files if f.get('path', {}).get('toString') and not r.match(f['path']['toString'])]
                 elif platform == 'gitlab':
                     # files = [f for f in files if (f['new_path'] and not r.match(f['new_path']))]
                     files_o = []
@@ -58,8 +71,19 @@ def filter_ignored(files, platform = 'github'):
                     files = files_o
                 elif platform == 'azure':
                     files = [f for f in files if not r.match(f)]
+                elif platform == 'gitea':
+                    files = [f for f in files if not r.match(f.get("filename", ""))]
+
 
     except Exception as e:
         print(f"Could not filter file list: {e}")
 
     return files
+
+def translate_globs_to_regexes(globs: list):
+    regexes = []
+    for pattern in globs:
+        regexes.append(fnmatch.translate(pattern))
+        if pattern.startswith("**/"): # cover root-level files
+            regexes.append(fnmatch.translate(pattern[3:]))
+    return regexes

pr_agent/algo/pr_processing.py

@@ -329,12 +329,13 @@ async def retry_with_fallback_models(f: Callable, model_type: ModelType = ModelT
             )
             get_settings().set("openai.deployment_id", deployment_id)
             return await f(model)
-        except:
+        except Exception as e:
             get_logger().warning(
-                f"Failed to generate prediction with {model}"
+                f"Failed to generate prediction with {model}",
+                artifact={"error": e},
             )
             if i == len(all_models) - 1:  # If it's the last iteration
-                raise Exception(f"Failed to generate prediction with any model of {all_models}")
+                raise Exception(f"Failed to generate prediction with any model of {all_models}") from e
 
 
 def _get_all_models(model_type: ModelType = ModelType.REGULAR) -> List[str]:
@@ -398,11 +399,6 @@ def get_pr_multi_diffs(git_provider: GitProvider,
     # Sort files by main language
     pr_languages = sort_files_by_main_languages(git_provider.get_languages(), diff_files)
 
-    # Sort files within each language group by tokens in descending order
-    sorted_files = []
-    for lang in pr_languages:
-        sorted_files.extend(sorted(lang['files'], key=lambda x: x.tokens, reverse=True))
-
     # Get the maximum number of extra lines before and after the patch
     PATCH_EXTRA_LINES_BEFORE = get_settings().config.patch_extra_lines_before
     PATCH_EXTRA_LINES_AFTER = get_settings().config.patch_extra_lines_after
@@ -420,6 +416,11 @@ def get_pr_multi_diffs(git_provider: GitProvider,
     if total_tokens + OUTPUT_BUFFER_TOKENS_SOFT_THRESHOLD < get_max_tokens(model):
         return ["\n".join(patches_extended)] if patches_extended else []
 
+    # Sort files within each language group by tokens in descending order
+    sorted_files = []
+    for lang in pr_languages:
+        sorted_files.extend(sorted(lang['files'], key=lambda x: x.tokens, reverse=True))
+
     patches = []
     final_diff_list = []
     total_tokens = token_handler.prompt_tokens

pr_agent/algo/token_handler.py

@@ -1,4 +1,6 @@
 from threading import Lock
+from math import ceil
+import re
 
 from jinja2 import Environment, StrictUndefined
 from tiktoken import encoding_for_model, get_encoding
@@ -7,6 +9,16 @@ from pr_agent.config_loader import get_settings
 from pr_agent.log import get_logger
 
 
+class ModelTypeValidator:
+    @staticmethod
+    def is_openai_model(model_name: str) -> bool:
+        return 'gpt' in model_name or re.match(r"^o[1-9](-mini|-preview)?$", model_name)
+    
+    @staticmethod
+    def is_anthropic_model(model_name: str) -> bool:
+        return 'claude' in model_name
+
+
 class TokenEncoder:
     _encoder_instance = None
     _model = None
@@ -40,6 +52,10 @@ class TokenHandler:
       method.
     """
 
+    # Constants
+    CLAUDE_MODEL = "claude-3-7-sonnet-20250219"
+    CLAUDE_MAX_CONTENT_SIZE = 9_000_000 # Maximum allowed content size (9MB) for Claude API
+
     def __init__(self, pr=None, vars: dict = {}, system="", user=""):
         """
         Initializes the TokenHandler object.
@@ -51,6 +67,7 @@ class TokenHandler:
         - user: The user string.
         """
         self.encoder = TokenEncoder.get_token_encoder()
+        
         if pr is not None:
             self.prompt_tokens = self._get_system_user_tokens(pr, self.encoder, vars, system, user)
 
@@ -79,22 +96,22 @@ class TokenHandler:
             get_logger().error(f"Error in _get_system_user_tokens: {e}")
             return 0
 
-    def calc_claude_tokens(self, patch):
+    def _calc_claude_tokens(self, patch: str) -> int:
         try:
             import anthropic
             from pr_agent.algo import MAX_TOKENS
+            
             client = anthropic.Anthropic(api_key=get_settings(use_context=False).get('anthropic.key'))
-            MaxTokens = MAX_TOKENS[get_settings().config.model]
+            max_tokens = MAX_TOKENS[get_settings().config.model]
 
-            # Check if the content size is too large (9MB limit)
-            if len(patch.encode('utf-8')) > 9_000_000:
+            if len(patch.encode('utf-8')) > self.CLAUDE_MAX_CONTENT_SIZE:
                 get_logger().warning(
                     "Content too large for Anthropic token counting API, falling back to local tokenizer"
                 )
-                return MaxTokens
+                return max_tokens
 
             response = client.messages.count_tokens(
-                model="claude-3-7-sonnet-20250219",
+                model=self.CLAUDE_MODEL,
                 system="system",
                 messages=[{
                     "role": "user",
@@ -104,42 +121,51 @@ class TokenHandler:
             return response.input_tokens
 
         except Exception as e:
-            get_logger().error( f"Error in Anthropic token counting: {e}")
-            return MaxTokens
+            get_logger().error(f"Error in Anthropic token counting: {e}")
+            return max_tokens
 
-    def estimate_token_count_for_non_anth_claude_models(self, model, default_encoder_estimate):
-        from math import ceil
-        import re
+    def _apply_estimation_factor(self, model_name: str, default_estimate: int) -> int:
+        factor = 1 + get_settings().get('config.model_token_count_estimate_factor', 0)
+        get_logger().warning(f"{model_name}'s token count cannot be accurately estimated. Using factor of {factor}")
+        
+        return ceil(factor * default_estimate)
 
-        model_is_from_o_series = re.match(r"^o[1-9](-mini|-preview)?$", model)
-        if ('gpt' in get_settings().config.model.lower() or model_is_from_o_series) and get_settings(use_context=False).get('openai.key'):
-            return default_encoder_estimate
-        #else: Model is not an OpenAI one - therefore, cannot provide an accurate token count and instead, return a higher number as best effort.
+    def _get_token_count_by_model_type(self, patch: str, default_estimate: int) -> int:
+        """
+        Get token count based on model type.
 
-        elbow_factor = 1 + get_settings().get('config.model_token_count_estimate_factor', 0)
-        get_logger().warning(f"{model}'s expected token count cannot be accurately estimated. Using {elbow_factor} of encoder output as best effort estimate")
-        return ceil(elbow_factor * default_encoder_estimate)
+        Args:
+            patch: The text to count tokens for.
+            default_estimate: The default token count estimate.
 
-    def count_tokens(self, patch: str, force_accurate=False) -> int:
+        Returns:
+            int: The calculated token count.
+        """
+        model_name = get_settings().config.model.lower()
+        
+        if ModelTypeValidator.is_openai_model(model_name) and get_settings(use_context=False).get('openai.key'):
+            return default_estimate
+
+        if ModelTypeValidator.is_anthropic_model(model_name) and get_settings(use_context=False).get('anthropic.key'):
+            return self._calc_claude_tokens(patch)
+        
+        return self._apply_estimation_factor(model_name, default_estimate)
+    
+    def count_tokens(self, patch: str, force_accurate: bool = False) -> int:
         """
         Counts the number of tokens in a given patch string.
 
         Args:
         - patch: The patch string.
+        - force_accurate: If True, uses a more precise calculation method.
 
         Returns:
         The number of tokens in the patch string.
         """
         encoder_estimate = len(self.encoder.encode(patch, disallowed_special=()))
 
-        #If an estimate is enough (for example, in cases where the maximal allowed tokens is way below the known limits), return it.
+        # If an estimate is enough (for example, in cases where the maximal allowed tokens is way below the known limits), return it.
         if not force_accurate:
             return encoder_estimate
 
-        #else, force_accurate==True: User requested providing an accurate estimation:
-        model = get_settings().config.model.lower()
-        if 'claude' in model and get_settings(use_context=False).get('anthropic.key'):
-            return self.calc_claude_tokens(patch) # API call to Anthropic for accurate token counting for Claude models
-
-        #else: Non Anthropic provided model:
-        return self.estimate_token_count_for_non_anth_claude_models(model, encoder_estimate)
+        return self._get_token_count_by_model_type(patch, encoder_estimate)

pr_agent/algo/utils.py

@@ -1,5 +1,6 @@
 from __future__ import annotations
 
+import ast
 import copy
 import difflib
 import hashlib
@@ -14,7 +15,7 @@ import traceback
 from datetime import datetime
 from enum import Enum
 from importlib.metadata import PackageNotFoundError, version
-from typing import Any, List, Tuple
+from typing import Any, List, Tuple, TypedDict
 
 import html2text
 import requests
@@ -37,21 +38,31 @@ def get_model(model_type: str = "model_weak") -> str:
         return get_settings().config.model_reasoning
     return get_settings().config.model
 
+
 class Range(BaseModel):
     line_start: int  # should be 0-indexed
     line_end: int
     column_start: int = -1
     column_end: int = -1
 
+
 class ModelType(str, Enum):
     REGULAR = "regular"
     WEAK = "weak"
     REASONING = "reasoning"
 
+
+class TodoItem(TypedDict):
+    relevant_file: str
+    line_range: Tuple[int, int]
+    content: str
+
+
 class PRReviewHeader(str, Enum):
     REGULAR = "## PR Reviewer Guide"
     INCREMENTAL = "## Incremental PR Reviewer Guide"
 
+
 class ReasoningEffort(str, Enum):
     HIGH = "high"
     MEDIUM = "medium"
@@ -59,7 +70,8 @@ class ReasoningEffort(str, Enum):
 
 
 class PRDescriptionHeader(str, Enum):
-    CHANGES_WALKTHROUGH = "### **Changes walkthrough** 📝"
+    DIAGRAM_WALKTHROUGH = "Diagram Walkthrough"
+    FILE_WALKTHROUGH = "File Walkthrough"
 
 
 def get_setting(key: str) -> Any:
@@ -109,6 +121,7 @@ def unique_strings(input_list: List[str]) -> List[str]:
             seen.add(item)
     return unique_list
 
+
 def convert_to_markdown_v2(output_data: dict,
                            gfm_supported: bool = True,
                            incremental_review=None,
@@ -131,9 +144,11 @@ def convert_to_markdown_v2(output_data: dict,
         "Focused PR": "✨",
         "Relevant ticket": "🎫",
         "Security concerns": "🔒",
+        "Todo sections": "📝",
         "Insights from user's answers": "📝",
         "Code feedback": "🤖",
         "Estimated effort to review [1-5]": "⏱️",
+        "Contribution time cost estimate": "⏳",
         "Ticket compliance check": "🎫",
     }
     markdown_text = ""
@@ -151,6 +166,7 @@ def convert_to_markdown_v2(output_data: dict,
     if gfm_supported:
         markdown_text += "<table>\n"
 
+    todo_summary = output_data['review'].pop('todo_summary', '')
     for key, value in output_data['review'].items():
         if value is None or value == '' or value == {} or value == []:
             if key.lower() not in ['can_be_split', 'key_issues_to_review']:
@@ -192,6 +208,14 @@ def convert_to_markdown_v2(output_data: dict,
                     markdown_text += f"### {emoji} PR contains tests\n\n"
         elif 'ticket compliance check' in key_nice.lower():
             markdown_text = ticket_markdown_logic(emoji, markdown_text, value, gfm_supported)
+        elif 'contribution time cost estimate' in key_nice.lower():
+            if gfm_supported:
+                markdown_text += f"<tr><td>{emoji}&nbsp;<strong>Contribution time estimate</strong> (best, average, worst case): "
+                markdown_text += f"{value['best_case'].replace('m', ' minutes')} | {value['average_case'].replace('m', ' minutes')} | {value['worst_case'].replace('m', ' minutes')}"
+                markdown_text += f"</td></tr>\n"
+            else:
+                markdown_text += f"### {emoji} Contribution time estimate (best, average, worst case): "
+                markdown_text += f"{value['best_case'].replace('m', ' minutes')} | {value['average_case'].replace('m', ' minutes')} | {value['worst_case'].replace('m', ' minutes')}\n\n"
         elif 'security concerns' in key_nice.lower():
             if gfm_supported:
                 markdown_text += f"<tr><td>"
@@ -209,6 +233,23 @@ def convert_to_markdown_v2(output_data: dict,
                     markdown_text += f"### {emoji} Security concerns\n\n"
                     value = emphasize_header(value.strip(), only_markdown=True)
                     markdown_text += f"{value}\n\n"
+        elif 'todo sections' in key_nice.lower():
+            if gfm_supported:
+                markdown_text += "<tr><td>"
+                if is_value_no(value):
+                    markdown_text += f"✅&nbsp;<strong>No TODO sections</strong>"
+                else:
+                    markdown_todo_items = format_todo_items(value, git_provider, gfm_supported)
+                    markdown_text += f"{emoji}&nbsp;<strong>TODO sections</strong>\n<br><br>\n"
+                    markdown_text += markdown_todo_items
+                markdown_text += "</td></tr>\n"
+            else:
+                if is_value_no(value):
+                    markdown_text += f"### ✅ No TODO sections\n\n"
+                else:
+                    markdown_todo_items = format_todo_items(value, git_provider, gfm_supported)
+                    markdown_text += f"### {emoji} TODO sections\n\n"
+                    markdown_text += markdown_todo_items
         elif 'can be split' in key_nice.lower():
             if gfm_supported:
                 markdown_text += f"<tr><td>"
@@ -707,7 +748,7 @@ def _fix_key_value(key: str, value: str):
 
 def load_yaml(response_text: str, keys_fix_yaml: List[str] = [], first_key="", last_key="") -> dict:
     response_text_original = copy.deepcopy(response_text)
-    response_text = response_text.strip('\n').removeprefix('```yaml').rstrip().removesuffix('```')
+    response_text = response_text.strip('\n').removeprefix('yaml').removeprefix('```yaml').rstrip().removesuffix('```')
     try:
         data = yaml.safe_load(response_text)
     except Exception as e:
@@ -731,7 +772,8 @@ def try_fix_yaml(response_text: str,
                  response_text_original="") -> dict:
     response_text_lines = response_text.split('\n')
 
-    keys_yaml = ['relevant line:', 'suggestion content:', 'relevant file:', 'existing code:', 'improved code:', 'label:']
+    keys_yaml = ['relevant line:', 'suggestion content:', 'relevant file:', 'existing code:',
+                 'improved code:', 'label:', 'why:', 'suggestion_summary:']
     keys_yaml = keys_yaml + keys_fix_yaml
 
     # first fallback - try to convert 'relevant line: ...' to relevant line: |-\n        ...'
@@ -806,12 +848,13 @@ def try_fix_yaml(response_text: str,
         if index_end == -1:
             index_end = len(response_text)
         response_text_copy = response_text[index_start:index_end].strip().strip('```yaml').strip('`').strip()
-        try:
-            data = yaml.safe_load(response_text_copy)
-            get_logger().info(f"Successfully parsed AI prediction after extracting yaml snippet")
-            return data
-        except:
-            pass
+        if response_text_copy:
+            try:
+                data = yaml.safe_load(response_text_copy)
+                get_logger().info(f"Successfully parsed AI prediction after extracting yaml snippet")
+                return data
+            except:
+                pass
 
     # fifth fallback - try to remove leading '+' (sometimes added by AI for 'existing code' and 'improved code')
     response_text_lines_copy = response_text_lines.copy()
@@ -840,14 +883,18 @@ def try_fix_yaml(response_text: str,
     response_text_copy = copy.deepcopy(response_text)
     response_text_copy_lines = response_text_copy.split('\n')
     start_line = -1
+    improve_sections = ['existing_code:', 'improved_code:', 'response:', 'why:']
+    describe_sections = ['description:', 'title:', 'changes_diagram:', 'pr_files:', 'pr_ticket:']
     for i, line in enumerate(response_text_copy_lines):
-        if 'existing_code:' in line or 'improved_code:' in line:
+        line_stripped = line.rstrip()
+        if any(key in line_stripped for key in (improve_sections+describe_sections)):
             start_line = i
-        elif line.endswith(': |') or line.endswith(': |-') or line.endswith(': |2') or line.endswith(':'):
+        elif line_stripped.endswith(': |') or line_stripped.endswith(': |-') or line_stripped.endswith(': |2') or any(line_stripped.endswith(key) for key in keys_yaml):
             start_line = -1
         elif start_line != -1:
             response_text_copy_lines[i] = '    ' + line
     response_text_copy = '\n'.join(response_text_copy_lines)
+    response_text_copy = response_text_copy.replace(' |\n', ' |2\n')
     try:
         data = yaml.safe_load(response_text_copy)
         get_logger().info(f"Successfully parsed AI prediction after adding indent for sections of code blocks")
@@ -855,6 +902,27 @@ def try_fix_yaml(response_text: str,
     except:
         pass
 
+    # eighth fallback - try to remove pipe chars at the root-level dicts
+    response_text_copy = copy.deepcopy(response_text)
+    response_text_copy = response_text_copy.lstrip('|\n')
+    try:
+        data = yaml.safe_load(response_text_copy)
+        get_logger().info(f"Successfully parsed AI prediction after removing pipe chars")
+        return data
+    except:
+        pass
+
+    # ninth fallback - try to decode the response text with different encodings. GPT-5 can return text that is not utf-8 encoded.
+    encodings_to_try = ['latin-1', 'utf-16']
+    for encoding in encodings_to_try:
+        try:
+            data = yaml.safe_load(response_text.encode(encoding).decode("utf-8"))
+            if data:
+                get_logger().info(f"Successfully parsed AI prediction after decoding with {encoding} encoding")
+                return data
+        except:
+            pass
+
     # # sixth fallback - try to remove last lines
     # for i in range(1, len(response_text_lines)):
     #     response_text_lines_tmp = '\n'.join(response_text_lines[:-i])
@@ -945,12 +1013,66 @@ def clip_tokens(text: str, max_tokens: int, add_three_dots=True, num_input_token
     """
     Clip the number of tokens in a string to a maximum number of tokens.
 
+    This function limits text to a specified token count by calculating the approximate
+    character-to-token ratio and truncating the text accordingly. A safety factor of 0.9
+    (10% reduction) is applied to ensure the result stays within the token limit.
+
     Args:
-        text (str): The string to clip.
+        text (str): The string to clip. If empty or None, returns the input unchanged.
         max_tokens (int): The maximum number of tokens allowed in the string.
-        add_three_dots (bool, optional): A boolean indicating whether to add three dots at the end of the clipped
+                         If negative, returns an empty string.
+        add_three_dots (bool, optional): Whether to add "\\n...(truncated)" at the end
+                                       of the clipped text to indicate truncation.
+                                       Defaults to True.
+        num_input_tokens (int, optional): Pre-computed number of tokens in the input text.
+                                        If provided, skips token encoding step for efficiency.
+                                        If None, tokens will be counted using TokenEncoder.
+                                        Defaults to None.
+        delete_last_line (bool, optional): Whether to remove the last line from the
+                                         clipped content before adding truncation indicator.
+                                         Useful for ensuring clean breaks at line boundaries.
+                                         Defaults to False.
+
     Returns:
-        str: The clipped string.
+        str: The clipped string. Returns original text if:
+             - Text is empty/None
+             - Token count is within limit
+             - An error occurs during processing
+
+             Returns empty string if max_tokens <= 0.
+
+    Examples:
+        Basic usage:
+        >>> text = "This is a sample text that might be too long"
+        >>> result = clip_tokens(text, max_tokens=10)
+        >>> print(result)
+        This is a sample...
+        (truncated)
+
+        Without truncation indicator:
+        >>> result = clip_tokens(text, max_tokens=10, add_three_dots=False)
+        >>> print(result)
+        This is a sample
+
+        With pre-computed token count:
+        >>> result = clip_tokens(text, max_tokens=5, num_input_tokens=15)
+        >>> print(result)
+        This...
+        (truncated)
+
+        With line deletion:
+        >>> multiline_text = "Line 1\\nLine 2\\nLine 3"
+        >>> result = clip_tokens(multiline_text, max_tokens=3, delete_last_line=True)
+        >>> print(result)
+        Line 1
+        Line 2
+        ...
+        (truncated)
+
+    Notes:
+        The function uses a safety factor of 0.9 (10% reduction) to ensure the
+        result stays within the token limit, as character-to-token ratios can vary.
+        If token encoding fails, the original text is returned with a warning logged.
     """
     if not text:
         return text
@@ -1199,14 +1321,35 @@ def process_description(description_full: str) -> Tuple[str, List]:
     if not description_full:
         return "", []
 
-    description_split = description_full.split(PRDescriptionHeader.CHANGES_WALKTHROUGH.value)
-    base_description_str = description_split[0]
-    changes_walkthrough_str = ""
-    files = []
-    if len(description_split) > 1:
-        changes_walkthrough_str = description_split[1]
+    # description_split = description_full.split(PRDescriptionHeader.FILE_WALKTHROUGH.value)
+    if PRDescriptionHeader.FILE_WALKTHROUGH.value in description_full:
+        try:
+            # FILE_WALKTHROUGH are presented in a collapsible section in the description
+            regex_pattern = r'<details.*?>\s*<summary>\s*<h3>\s*' + re.escape(PRDescriptionHeader.FILE_WALKTHROUGH.value) + r'\s*</h3>\s*</summary>'
+            description_split = re.split(regex_pattern, description_full, maxsplit=1, flags=re.DOTALL)
+
+            # If the regex pattern is not found, fallback to the previous method
+            if len(description_split) == 1:
+                get_logger().debug("Could not find regex pattern for file walkthrough, falling back to simple split")
+                description_split = description_full.split(PRDescriptionHeader.FILE_WALKTHROUGH.value, 1)
+        except Exception as e:
+            get_logger().warning(f"Failed to split description using regex, falling back to simple split: {e}")
+            description_split = description_full.split(PRDescriptionHeader.FILE_WALKTHROUGH.value, 1)
+
+        if len(description_split) < 2:
+            get_logger().error("Failed to split description into base and changes walkthrough", artifact={'description': description_full})
+            return description_full.strip(), []
+
+        base_description_str = description_split[0].strip()
+        changes_walkthrough_str = ""
+        files = []
+        if len(description_split) > 1:
+            changes_walkthrough_str = description_split[1]
+        else:
+            get_logger().debug("No changes walkthrough found")
     else:
-        get_logger().debug("No changes walkthrough found")
+        base_description_str = description_full.strip()
+        return base_description_str, []
 
     try:
         if changes_walkthrough_str:
@@ -1229,7 +1372,7 @@ def process_description(description_full: str) -> Tuple[str, List]:
                 try:
                     if isinstance(file_data, tuple):
                         file_data = file_data[0]
-                    pattern = r'<details>\s*<summary><strong>(.*?)</strong>\s*<dd><code>(.*?)</code>.*?</summary>\s*<hr>\s*(.*?)\s*<li>(.*?)</details>'
+                    pattern = r'<details>\s*<summary><strong>(.*?)</strong>\s*<dd><code>(.*?)</code>.*?</summary>\s*<hr>\s*(.*?)\s*(?:<li>|•)(.*?)</details>'
                     res = re.search(pattern, file_data, re.DOTALL)
                     if not res or res.lastindex != 4:
                         pattern_back = r'<details>\s*<summary><strong>(.*?)</strong><dd><code>(.*?)</code>.*?</summary>\s*<hr>\s*(.*?)\n\n\s*(.*?)</details>'
@@ -1241,6 +1384,8 @@ def process_description(description_full: str) -> Tuple[str, List]:
                         short_filename = res.group(1).strip()
                         short_summary = res.group(2).strip()
                         long_filename = res.group(3).strip()
+                        if long_filename.endswith('<ul>'):
+                            long_filename = long_filename[:-4].strip()
                         long_summary =  res.group(4).strip()
                         long_summary = long_summary.replace('<br> *', '\n*').replace('<br>','').replace('\n','<br>')
                         long_summary = h.handle(long_summary).strip()
@@ -1259,7 +1404,7 @@ def process_description(description_full: str) -> Tuple[str, List]:
                         if '<code>...</code>' in file_data:
                             pass # PR with many files. some did not get analyzed
                         else:
-                            get_logger().error(f"Failed to parse description", artifact={'description': file_data})
+                            get_logger().warning(f"Failed to parse description", artifact={'description': file_data})
                 except Exception as e:
                     get_logger().exception(f"Failed to process description: {e}", artifact={'description': file_data})
 
@@ -1313,3 +1458,47 @@ def set_file_languages(diff_files) -> List[FilePatchInfo]:
         get_logger().exception(f"Failed to set file languages: {e}")
 
     return diff_files
+
+def format_todo_item(todo_item: TodoItem, git_provider, gfm_supported) -> str:
+    relevant_file = todo_item.get('relevant_file', '').strip()
+    line_number = todo_item.get('line_number', '')
+    content = todo_item.get('content', '')
+    reference_link = git_provider.get_line_link(relevant_file, line_number, line_number)
+    file_ref = f"{relevant_file} [{line_number}]"
+    if reference_link:
+        if gfm_supported:
+            file_ref = f"<a href='{reference_link}'>{file_ref}</a>"
+        else:
+            file_ref = f"[{file_ref}]({reference_link})"
+
+    if content:
+        return f"{file_ref}: {content.strip()}"
+    else:
+        # if content is empty, return only the file reference
+        return file_ref
+
+
+def format_todo_items(value: list[TodoItem] | TodoItem, git_provider, gfm_supported) -> str:
+    markdown_text = ""
+    MAX_ITEMS = 5 # limit the number of items to display
+    if gfm_supported:
+        if isinstance(value, list):
+            markdown_text += "<ul>\n"
+            if len(value) > MAX_ITEMS:
+                get_logger().debug(f"Truncating todo items to {MAX_ITEMS} items")
+                value = value[:MAX_ITEMS]
+            for todo_item in value:
+                markdown_text += f"<li>{format_todo_item(todo_item, git_provider, gfm_supported)}</li>\n"
+            markdown_text += "</ul>\n"
+        else:
+            markdown_text += f"<p>{format_todo_item(value, git_provider, gfm_supported)}</p>\n"
+    else:
+        if isinstance(value, list):
+            if len(value) > MAX_ITEMS:
+                get_logger().debug(f"Truncating todo items to {MAX_ITEMS} items")
+                value = value[:MAX_ITEMS]
+            for todo_item in value:
+                markdown_text += f"- {format_todo_item(todo_item, git_provider, gfm_supported)}\n"
+        else:
+            markdown_text += f"- {format_todo_item(value, git_provider, gfm_supported)}\n"
+    return markdown_text

pr_agent/config_loader.py

@@ -8,12 +8,19 @@ from starlette_context import context
 PR_AGENT_TOML_KEY = 'pr-agent'
 
 current_dir = dirname(abspath(__file__))
+
+dynconf_kwargs = {'core_loaders': [], # DISABLE default loaders, otherwise will load toml files more than once.
+                           'loaders': ['pr_agent.custom_merge_loader', 'dynaconf.loaders.env_loader'], # Use a custom loader to merge sections, but overwrite their overlapping values. Also support ENV variables to take precedence.
+                           'root_path': join(current_dir, "settings"), #Used for Dynaconf.find_file() - So that root path points to settings folder, since we disabled all core loaders.
+                           'merge_enabled': True  # In case more than one file is sent, merge them. Must be set to True, otherwise, a .toml file with section [XYZ] overwrites the entire section of a previous .toml file's [XYZ] and we want it to only overwrite the overlapping fields under such section
+                           }
 global_settings = Dynaconf(
     envvar_prefix=False,
-    merge_enabled=True,
+    load_dotenv=False,  # Security: Don't load .env files
     settings_files=[join(current_dir, f) for f in [
         "settings/configuration.toml",
         "settings/ignore.toml",
+        "settings/generated_code_ignore.toml",
         "settings/language_extensions.toml",
         "settings/pr_reviewer_prompts.toml",
         "settings/pr_questions_prompts.toml",
@@ -32,7 +39,8 @@ global_settings = Dynaconf(
         "settings/pr_help_docs_headings_prompts.toml",
         "settings/.secrets.toml",
         "settings_prod/.secrets.toml",
-    ]]
+    ]],
+    **dynconf_kwargs
 )
 
 
@@ -81,3 +89,62 @@ def _find_pyproject() -> Optional[Path]:
 pyproject_path = _find_pyproject()
 if pyproject_path is not None:
     get_settings().load_file(pyproject_path, env=f'tool.{PR_AGENT_TOML_KEY}')
+
+
+def apply_secrets_manager_config():
+    """
+    Retrieve configuration from AWS Secrets Manager and override existing settings
+    """
+    try:
+        # Dynamic imports to avoid circular dependency (secret_providers imports config_loader)
+        from pr_agent.secret_providers import get_secret_provider
+        from pr_agent.log import get_logger
+
+        secret_provider = get_secret_provider()
+        if not secret_provider:
+            return
+
+        if (hasattr(secret_provider, 'get_all_secrets') and
+            get_settings().get("CONFIG.SECRET_PROVIDER") == 'aws_secrets_manager'):
+            try:
+                secrets = secret_provider.get_all_secrets()
+                if secrets:
+                    apply_secrets_to_config(secrets)
+                    get_logger().info("Applied AWS Secrets Manager configuration")
+            except Exception as e:
+                get_logger().error(f"Failed to apply AWS Secrets Manager config: {e}")
+    except Exception as e:
+        try:
+            from pr_agent.log import get_logger
+            get_logger().debug(f"Secret provider not configured: {e}")
+        except:
+            # Fail completely silently if log module is not available
+            pass
+
+
+def apply_secrets_to_config(secrets: dict):
+    """
+    Apply secret dictionary to configuration
+    """
+    try:
+        # Dynamic import to avoid potential circular dependency
+        from pr_agent.log import get_logger
+    except:
+        def get_logger():
+            class DummyLogger:
+                def debug(self, msg): pass
+            return DummyLogger()
+
+    for key, value in secrets.items():
+        if '.' in key:  # nested key like "openai.key"
+            parts = key.split('.')
+            if len(parts) == 2:
+                section, setting = parts
+                section_upper = section.upper()
+                setting_upper = setting.upper()
+
+                # Set only when no existing value (prioritize environment variables)
+                current_value = get_settings().get(f"{section_upper}.{setting_upper}")
+                if current_value is None or current_value == "":
+                    get_settings().set(f"{section_upper}.{setting_upper}", value)
+                    get_logger().debug(f"Set {section}.{setting} from AWS Secrets Manager")

pr_agent/custom_merge_loader.py

@@ -0,0 +1,167 @@
+from pathlib import Path
+import tomllib #tomllib should be used instead of Py toml for Python 3.11+
+
+from jinja2.exceptions import SecurityError
+
+from pr_agent.log import get_logger
+
+def load(obj, env=None, silent=True, key=None, filename=None):
+    """
+    Load and merge TOML configuration files into a Dynaconf settings object using a secure, in-house loader.
+    This loader:
+    - Replaces list and dict fields instead of appending/updating (non-default Dynaconf behavior).
+    - Enforces several security checks (e.g., disallows includes/preloads and enforces .toml files).
+    - Supports optional single-key loading.
+    Args:
+        obj: The Dynaconf settings instance to update.
+        env: The current environment name (upper case). Defaults to 'DEVELOPMENT'. Note: currently unused.
+        silent (bool): If True, suppress exceptions and log warnings/errors instead.
+        key (str | None): Load only this top-level key (section) if provided; otherwise, load all keys from the files.
+        filename (str | None): Custom filename for tests (not used when settings_files are provided).
+    Returns:
+        None
+    """
+
+    MAX_TOML_SIZE_IN_BYTES = 100 * 1024 * 1024 # Prevent out of mem. exceptions by limiting to 100 MBs which is sufficient for upto 1M lines
+
+    # Get the list of files to load
+    # TODO: hasattr(obj, 'settings_files') for some reason returns False. Need to use 'settings_file'
+    settings_files = obj.settings_files if hasattr(obj, 'settings_files') else (
+        obj.settings_file) if hasattr(obj, 'settings_file') else []
+    if not settings_files or not isinstance(settings_files, list):
+        get_logger().warning("No settings files specified, or missing keys "
+                             "(tried looking for 'settings_files' or 'settings_file'), or not a list. Skipping loading.",
+                             artifact={'toml_obj_attributes_names': dir(obj)})
+        return
+
+    # Storage for all loaded data
+    accumulated_data = {}
+
+    # Security: Check for forbidden configuration options
+    if hasattr(obj, 'includes') and obj.includes:
+        if not silent:
+            raise SecurityError("Configuration includes forbidden option: 'includes'. Skipping loading.")
+        get_logger().error("Configuration includes forbidden option: 'includes'. Skipping loading.")
+        return
+    if hasattr(obj, 'preload') and obj.preload:
+        if not silent:
+            raise SecurityError("Configuration includes forbidden option: 'preload'. Skipping loading.")
+        get_logger().error("Configuration includes forbidden option: 'preload'. Skipping loading.")
+        return
+
+    for settings_file in settings_files:
+        try:
+            # Load the TOML file
+            file_path = Path(settings_file)
+            # Security: Only allow .toml files
+            if file_path.suffix.lower() != '.toml':
+                get_logger().warning(f"Only .toml files are allowed. Skipping: {settings_file}")
+                continue
+
+            if not file_path.exists():
+                get_logger().warning(f"Settings file not found: {settings_file}. Skipping it.")
+                continue
+
+            if file_path.stat().st_size > MAX_TOML_SIZE_IN_BYTES:
+                get_logger().warning(f"Settings file too large (> {MAX_TOML_SIZE_IN_BYTES} bytes): {settings_file}. Skipping it.")
+                continue
+
+            with open(file_path, 'rb') as f:
+                file_data = tomllib.load(f)
+
+            # Handle sections (like [config], [default], etc.)
+            if not isinstance(file_data, dict):
+                get_logger().warning(f"TOML root is not a table in '{settings_file}'. Skipping.")
+                continue
+
+            # Security: Check file contents for forbidden directives
+            validate_file_security(file_data, settings_file)
+
+            for section_name, section_data in file_data.items():
+                if not isinstance(section_data, dict):
+                    get_logger().warning(f"Section '{section_name}' in '{settings_file}' is not a table. Skipping.")
+                    continue
+                for field, field_value in section_data.items():
+                    if section_name not in accumulated_data:
+                        accumulated_data[section_name] = {}
+                    accumulated_data[section_name][field] = field_value
+
+        except Exception as e:
+            if not silent:
+                raise e
+            get_logger().exception(f"Exception loading settings file: {settings_file}. Skipping.")
+
+    # Update the settings object
+    for k, v in accumulated_data.items():
+        if key is None or key == k:
+            obj.set(k, v)
+
+def validate_file_security(file_data, filename):
+    """
+    Validate that the config file does not contain security-sensitive directives.
+
+    Args:
+        file_data: Parsed TOML data representing the configuration contents.
+        filename: The name or path of the file being validated (used for error messages).
+
+    Raises:
+        SecurityError: If forbidden directives are found within the configuration, or if data too nested.
+    """
+    MAX_DEPTH = 50
+
+    # Check for forbidden keys
+    # Comprehensive list of forbidden keys with explanations
+    forbidden_keys_to_reasons = {
+        # Include mechanisms - allow loading arbitrary files
+        'dynaconf_include': 'allows including other config files dynamically',
+        'dynaconf_includes': 'allows including other config files dynamically',
+        'includes': 'allows including other config files dynamically',
+
+        # Preload mechanisms - allow loading files before main config
+        'preload': 'allows preloading files with potential code execution',
+        'preload_for_dynaconf': 'allows preloading files with potential code execution',
+        'preloads': 'allows preloading files with potential code execution',
+
+        # Merge controls - could be used to manipulate config behavior
+        'dynaconf_merge': 'allows manipulating merge behavior',
+        'dynaconf_merge_enabled': 'allows manipulating merge behavior',
+        'merge_enabled': 'allows manipulating merge behavior',
+
+        # Loader controls - allow changing how configs are loaded
+        'loaders_for_dynaconf': 'allows overriding loaders to execute arbitrary code',
+        'loaders': 'allows overriding loaders to execute arbitrary code',
+        'core_loaders': 'allows overriding core loaders',
+        'core_loaders_for_dynaconf': 'allows overriding core loaders',
+
+        # Settings module - allows loading Python modules
+        'settings_module': 'allows loading Python modules with code execution',
+        'settings_file_for_dynaconf': 'could override settings file location',
+        'settings_files_for_dynaconf': 'could override settings file location',
+
+        # Environment variable prefix manipulation
+        'envvar_prefix': 'allows changing environment variable prefix',
+        'envvar_prefix_for_dynaconf': 'allows changing environment variable prefix',
+    }
+
+    # Check at the top level and in all sections
+    def check_dict(data, path="", max_depth=MAX_DEPTH):
+        if max_depth <= 0:
+            raise SecurityError(
+                f"Maximum nesting depth exceeded at {path}. "
+                f"Possible attempt to cause stack overflow."
+            )
+
+        for key, value in data.items():
+            full_path = f"{path}.{key}" if path else key
+
+            if key.lower() in forbidden_keys_to_reasons:
+                raise SecurityError(
+                    f"Security error in {filename}: "
+                    f"Forbidden directive '{key}' found at {full_path}. Reason: {forbidden_keys_to_reasons[key.lower()]}"
+                )
+
+            # Recursively check nested dicts
+            if isinstance(value, dict):
+                check_dict(value, path=full_path, max_depth=(max_depth - 1))
+
+    check_dict(file_data, max_depth=MAX_DEPTH)

pr_agent/git_providers/__init__.py

@@ -8,9 +8,11 @@ from pr_agent.git_providers.bitbucket_server_provider import \
 from pr_agent.git_providers.codecommit_provider import CodeCommitProvider
 from pr_agent.git_providers.gerrit_provider import GerritProvider
 from pr_agent.git_providers.git_provider import GitProvider
+from pr_agent.git_providers.gitea_provider import GiteaProvider
 from pr_agent.git_providers.github_provider import GithubProvider
 from pr_agent.git_providers.gitlab_provider import GitLabProvider
 from pr_agent.git_providers.local_git_provider import LocalGitProvider
+from pr_agent.git_providers.gitea_provider import GiteaProvider
 
 _GIT_PROVIDERS = {
     'github': GithubProvider,
@@ -21,6 +23,7 @@ _GIT_PROVIDERS = {
     'codecommit': CodeCommitProvider,
     'local': LocalGitProvider,
     'gerrit': GerritProvider,
+    'gitea': GiteaProvider
 }
 
 

pr_agent/git_providers/azuredevops_provider.py

@@ -22,6 +22,7 @@ try:
     from azure.devops.connection import Connection
     # noinspection PyUnresolvedReferences
     from azure.devops.released.git import (Comment, CommentThread, GitPullRequest, GitVersionDescriptor, GitClient, CommentThreadContext, CommentPosition)
+    from azure.devops.released.work_item_tracking import WorkItemTrackingClient
     # noinspection PyUnresolvedReferences
     from azure.identity import DefaultAzureCredential
     from msrest.authentication import BasicAuthentication
@@ -39,7 +40,7 @@ class AzureDevopsProvider(GitProvider):
                 "Azure DevOps provider is not available. Please install the required dependencies."
             )
 
-        self.azure_devops_client = self._get_azure_devops_client()
+        self.azure_devops_client, self.azure_devops_board_client = self._get_azure_devops_client()
         self.diff_files = None
         self.workspace_slug = None
         self.repo_slug = None
@@ -56,6 +57,7 @@ class AzureDevopsProvider(GitProvider):
         Publishes code suggestions as comments on the PR.
         """
         post_parameters_list = []
+        status = get_settings().azure_devops.get("default_comment_status", "closed")
         for suggestion in code_suggestions:
             body = suggestion['body']
             relevant_file = suggestion['relevant_file']
@@ -78,7 +80,7 @@ class AzureDevopsProvider(GitProvider):
                 right_file_start=CommentPosition(offset=1, line=relevant_lines_start),
                 right_file_end=CommentPosition(offset=1, line=relevant_lines_end))
             comment = Comment(content=body, comment_type=1)
-            thread = CommentThread(comments=[comment], thread_context=thread_context)
+            thread = CommentThread(comments=[comment], thread_context=thread_context, status=status)
             try:
                 self.azure_devops_client.create_thread(
                     comment_thread=thread,
@@ -194,7 +196,7 @@ class AzureDevopsProvider(GitProvider):
                 return self.diff_files
 
             base_sha = self.pr.last_merge_target_commit
-            head_sha = self.pr.last_merge_source_commit
+            head_sha = self.pr.last_merge_commit
 
             # Get PR iterations
             iterations = self.azure_devops_client.get_pull_request_iterations(
@@ -350,7 +352,9 @@ class AzureDevopsProvider(GitProvider):
             get_logger().debug(f"Skipping publish_comment for temporary comment: {pr_comment}")
             return None
         comment = Comment(content=pr_comment)
-        thread = CommentThread(comments=[comment], thread_context=thread_context, status="closed")
+
+        status = get_settings().azure_devops.get("default_comment_status", "closed")
+        thread = CommentThread(comments=[comment], thread_context=thread_context, status=status)
         thread_response = self.azure_devops_client.create_thread(
             comment_thread=thread,
             project=self.workspace_slug,
@@ -379,7 +383,7 @@ class AzureDevopsProvider(GitProvider):
                 pr_body = pr_body[:ind]
 
             if len(pr_body) > MAX_PR_DESCRIPTION_AZURE_LENGTH:
-                changes_walkthrough_text = PRDescriptionHeader.CHANGES_WALKTHROUGH.value
+                changes_walkthrough_text = PRDescriptionHeader.FILE_WALKTHROUGH.value
                 ind = pr_body.find(changes_walkthrough_text)
                 if ind != -1:
                     pr_body = pr_body[:ind]
@@ -566,7 +570,7 @@ class AzureDevopsProvider(GitProvider):
         return workspace_slug, repo_slug, pr_number
 
     @staticmethod
-    def _get_azure_devops_client() -> GitClient:
+    def _get_azure_devops_client() -> Tuple[GitClient, WorkItemTrackingClient]:
         org = get_settings().azure_devops.get("org", None)
         pat = get_settings().azure_devops.get("pat", None)
 
@@ -588,13 +592,12 @@ class AzureDevopsProvider(GitProvider):
                 get_logger().error(f"No PAT found in settings, and Azure Default Authentication failed, error: {e}")
                 raise
 
-        credentials = BasicAuthentication("", auth_token)
-
         credentials = BasicAuthentication("", auth_token)
         azure_devops_connection = Connection(base_url=org, creds=credentials)
         azure_devops_client = azure_devops_connection.clients.get_git_client()
+        azure_devops_board_client = azure_devops_connection.clients.get_work_item_tracking_client()
 
-        return azure_devops_client
+        return azure_devops_client, azure_devops_board_client
 
     def _get_repo(self):
         if self.repo is None:
@@ -618,7 +621,7 @@ class AzureDevopsProvider(GitProvider):
             return pr_id
         except Exception as e:
             if get_settings().config.verbosity_level >= 2:
-                get_logger().info(f"Failed to get pr id, error: {e}")
+                get_logger().info(f"Failed to get PR id, error: {e}")
             return ""
 
     def publish_file_comments(self, file_comments: list) -> bool:
@@ -635,4 +638,50 @@ class AzureDevopsProvider(GitProvider):
         last = commits[0]
         url = self.azure_devops_client.normalized_url + "/" + self.workspace_slug + "/_git/" + self.repo_slug + "/commit/" + last.commit_id
         return url
-    
+
+    def get_linked_work_items(self) -> list:
+        """
+        Get linked work items from the PR.
+        """
+        try:
+            work_items = self.azure_devops_client.get_pull_request_work_item_refs(
+                project=self.workspace_slug,
+                repository_id=self.repo_slug,
+                pull_request_id=self.pr_num,
+            )
+            ids = [work_item.id for work_item in work_items]
+            if not work_items:
+                return []
+            items = self.get_work_items(ids)
+            return items
+        except Exception as e:
+            get_logger().exception(f"Failed to get linked work items, error: {e}")
+            return []
+
+    def get_work_items(self, work_item_ids: list) -> list:
+        """
+        Get work items by their IDs.
+        """
+        try:
+            raw_work_items = self.azure_devops_board_client.get_work_items(
+                project=self.workspace_slug,
+                ids=work_item_ids,
+            )
+            work_items = []
+            for item in raw_work_items:
+                work_items.append(
+                    {
+                        "id": item.id,
+                        "title": item.fields.get("System.Title", ""),
+                        "url": item.url,
+                        "body": item.fields.get("System.Description", ""),
+                        "acceptance_criteria": item.fields.get(
+                            "Microsoft.VSTS.Common.AcceptanceCriteria", ""
+                        ),
+                        "tags": item.fields.get("System.Tags", "").split("; ") if item.fields.get("System.Tags") else [],
+                    }
+                )
+            return work_items
+        except Exception as e:
+            get_logger().exception(f"Failed to get work items, error: {e}")
+            return []

pr_agent/git_providers/bitbucket_server_provider.py

@@ -10,6 +10,7 @@ from requests.exceptions import HTTPError
 import shlex
 import subprocess
 
+from ..algo.file_filter import filter_ignored
 from ..algo.git_patch_processing import decode_if_bytes
 from ..algo.language_handler import is_valid_file
 from ..algo.types import EDIT_TYPE, FilePatchInfo
@@ -17,7 +18,7 @@ from ..algo.utils import (find_line_number_of_relevant_line_in_file,
                           load_large_diff)
 from ..config_loader import get_settings
 from ..log import get_logger
-from .git_provider import GitProvider
+from .git_provider import GitProvider, get_git_ssl_env
 
 
 class BitbucketServerProvider(GitProvider):
@@ -37,10 +38,28 @@ class BitbucketServerProvider(GitProvider):
         self.diff_files = None
         self.bitbucket_pull_request_api_url = pr_url
         self.bearer_token = get_settings().get("BITBUCKET_SERVER.BEARER_TOKEN", None)
-        self.bitbucket_server_url = self._parse_bitbucket_server(url=pr_url)
-        self.bitbucket_client = bitbucket_client or Bitbucket(url=self.bitbucket_server_url,
-                                                              token=get_settings().get("BITBUCKET_SERVER.BEARER_TOKEN",
-                                                                                       None))
+        # Get username and password from settings
+        username = get_settings().get("BITBUCKET_SERVER.USERNAME", None)
+        password = get_settings().get("BITBUCKET_SERVER.PASSWORD", None)
+        if bitbucket_client: # if Bitbucket client is provided, use it
+            self.bitbucket_client = bitbucket_client
+            self.bitbucket_server_url = getattr(bitbucket_client, 'url', None) or self._parse_bitbucket_server(pr_url)
+        else:
+            self.bitbucket_server_url = self._parse_bitbucket_server(pr_url)
+            if not self.bitbucket_server_url:
+                raise ValueError("Invalid or missing Bitbucket Server URL parsed from PR URL.")
+            
+            if self.bearer_token:  # if bearer token is provided, use it
+                self.bitbucket_client = Bitbucket(
+                    url=self.bitbucket_server_url,
+                    token=self.bearer_token
+                )
+            else:  # otherwise use username and password
+                self.bitbucket_client = Bitbucket(
+                    url=self.bitbucket_server_url,
+                    username=username,
+                    password=password
+                )
         try:
             self.bitbucket_api_version = parse_version(self.bitbucket_client.get("rest/api/1.0/application-properties").get('version'))
         except Exception:
@@ -86,7 +105,7 @@ class BitbucketServerProvider(GitProvider):
 
     def get_repo_settings(self):
         try:
-            content = self.bitbucket_client.get_content_of_file(self.workspace_slug, self.repo_slug, ".pr_agent.toml", self.get_pr_branch())
+            content = self.bitbucket_client.get_content_of_file(self.workspace_slug, self.repo_slug, ".pr_agent.toml")
 
             return content
         except Exception as e:
@@ -244,7 +263,8 @@ class BitbucketServerProvider(GitProvider):
         original_file_content_str = ""
         new_file_content_str = ""
 
-        changes = self.bitbucket_client.get_pull_requests_changes(self.workspace_slug, self.repo_slug, self.pr_num)
+        changes_original = list(self.bitbucket_client.get_pull_requests_changes(self.workspace_slug, self.repo_slug, self.pr_num))
+        changes = filter_ignored(changes_original, 'bitbucket_server')
         for change in changes:
             file_path = change['path']['toString']
             if not is_valid_file(file_path.split("/")[-1]):
@@ -541,5 +561,7 @@ class BitbucketServerProvider(GitProvider):
         cli_args = shlex.split(f"git clone -c http.extraHeader='Authorization: Bearer {bearer_token}' "
                                f"--filter=blob:none --depth 1 {repo_url} {dest_folder}")
 
-        subprocess.run(cli_args, check=True,  # check=True will raise an exception if the command fails
+        ssl_env = get_git_ssl_env()
+
+        subprocess.run(cli_args, env=ssl_env, check=True,  # check=True will raise an exception if the command fails
             stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, timeout=operation_timeout_in_seconds)

pr_agent/git_providers/gerrit_provider.py

@@ -103,7 +103,7 @@ def prepare_repo(url: urllib3.util.Url, project, refspec):
     repo_url = (f"{url.scheme}://{url.auth}@{url.host}:{url.port}/{project}")
 
     directory = pathlib.Path(mkdtemp())
-    clone(repo_url, directory),
+    clone(repo_url, directory)
     fetch(repo_url, refspec, cwd=directory)
     checkout(cwd=directory)
     return directory

pr_agent/git_providers/git_provider.py

@@ -12,6 +12,65 @@ from pr_agent.log import get_logger
 
 MAX_FILES_ALLOWED_FULL = 50
 
+def get_git_ssl_env() -> dict[str, str]:
+    """
+    Get git SSL configuration arguments for per-command use.
+    This fixes SSL certificate issues when cloning repos with self-signed certificates.
+    Returns the current environment with the addition of SSL config changes if any such SSL certificates exist.
+    """
+    ssl_cert_file = os.environ.get('SSL_CERT_FILE')
+    requests_ca_bundle = os.environ.get('REQUESTS_CA_BUNDLE')
+    git_ssl_ca_info = os.environ.get('GIT_SSL_CAINFO')
+
+    chosen_cert_file = ""
+
+    # Try SSL_CERT_FILE first
+    if ssl_cert_file:
+        if os.path.exists(ssl_cert_file):
+            if ((requests_ca_bundle and requests_ca_bundle != ssl_cert_file)
+                    or (git_ssl_ca_info and git_ssl_ca_info != ssl_cert_file)):
+                get_logger().warning(f"Found mismatch among: SSL_CERT_FILE, REQUESTS_CA_BUNDLE, GIT_SSL_CAINFO. "
+                                     f"Using the SSL_CERT_FILE to resolve ambiguity.",
+                                  artifact={"ssl_cert_file": ssl_cert_file, "requests_ca_bundle": requests_ca_bundle,
+                                            'git_ssl_ca_info': git_ssl_ca_info})
+            else:
+                get_logger().info(f"Using SSL certificate bundle for git operations", artifact={"ssl_cert_file": ssl_cert_file})
+            chosen_cert_file = ssl_cert_file
+        else:
+            get_logger().warning("SSL certificate bundle not found for git operations", artifact={"ssl_cert_file": ssl_cert_file})
+
+    # Fallback to REQUESTS_CA_BUNDLE
+    elif requests_ca_bundle:
+        if os.path.exists(requests_ca_bundle):
+            if (git_ssl_ca_info and git_ssl_ca_info != requests_ca_bundle):
+                get_logger().warning(f"Found mismatch between: REQUESTS_CA_BUNDLE, GIT_SSL_CAINFO. "
+                                     f"Using the REQUESTS_CA_BUNDLE to resolve ambiguity.",
+                artifact = {"requests_ca_bundle": requests_ca_bundle, 'git_ssl_ca_info': git_ssl_ca_info})
+            else:
+                get_logger().info("Using SSL certificate bundle from REQUESTS_CA_BUNDLE for git operations",
+                                  artifact={"requests_ca_bundle": requests_ca_bundle})
+            chosen_cert_file = requests_ca_bundle
+        else:
+            get_logger().warning("requests CA bundle not found for git operations", artifact={"requests_ca_bundle": requests_ca_bundle})
+
+    #Fallback to GIT CA:
+    elif git_ssl_ca_info:
+        if os.path.exists(git_ssl_ca_info):
+            get_logger().info("Using git SSL CA info from GIT_SSL_CAINFO for git operations",
+                              artifact={"git_ssl_ca_info": git_ssl_ca_info})
+            chosen_cert_file = git_ssl_ca_info
+        else:
+            get_logger().warning("git SSL CA info not found for git operations", artifact={"git_ssl_ca_info": git_ssl_ca_info})
+
+    else:
+        get_logger().warning("Neither SSL_CERT_FILE nor REQUESTS_CA_BUNDLE nor GIT_SSL_CAINFO are defined, or they are defined but not found. Returning environment without SSL configuration")
+
+    returned_env = os.environ.copy()
+    if chosen_cert_file:
+        returned_env.update({"GIT_SSL_CAINFO": chosen_cert_file, "REQUESTS_CA_BUNDLE": chosen_cert_file})
+    return returned_env
+
+
 class GitProvider(ABC):
     @abstractmethod
     def is_supported(self, capability: str) -> bool:
@@ -57,12 +116,21 @@ class GitProvider(ABC):
         # #Repo.clone_from(repo_url, dest_folder)
         # , but with throwing an exception upon timeout.
         # Note: This can only be used in context that supports using pipes.
+        try:
+            ssl_env = get_git_ssl_env()
+        except Exception as e:
+            get_logger().exception(
+                "Failed to prepare SSL environment for git operations, falling back to default env",
+                artifact={"error": e}
+            )
+            ssl_env = os.environ.copy()
+
         subprocess.run([
             "git", "clone",
             "--filter=blob:none",
             "--depth", "1",
             repo_url, dest_folder
-        ], check=True,  # check=True will raise an exception if the command fails
+        ], env=ssl_env, check=True,  # check=True will raise an exception if the command fails
             stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, timeout=operation_timeout_in_seconds)
 
     CLONE_TIMEOUT_SEC = 20
@@ -376,7 +444,6 @@ def get_main_pr_language(languages, files) -> str:
                         break
         except Exception as e:
             get_logger().exception(f"Failed to get main language: {e}")
-            pass
 
         ## old approach:
         # most_common_extension = max(set(extension_list), key=extension_list.count)
@@ -401,7 +468,6 @@ def get_main_pr_language(languages, files) -> str:
 
     except Exception as e:
         get_logger().exception(e)
-        pass
 
     return main_language_str
 

pr_agent/git_providers/github_provider.py

@@ -96,7 +96,7 @@ class GithubProvider(GitProvider):
                 parsed_url = urlparse(given_url)
                 repo_path = (parsed_url.path.split('.git')[0])[1:] # /<owner>/<repo>.git -> <owner>/<repo>
             if not repo_path:
-                get_logger().error(f"url is neither an issues url nor a pr url nor a valid git url: {given_url}. Returning empty result.")
+                get_logger().error(f"url is neither an issues url nor a PR url nor a valid git url: {given_url}. Returning empty result.")
                 return ""
             return repo_path
         except Exception as e:

pr_agent/git_providers/gitlab_provider.py

@@ -1,16 +1,19 @@
 import difflib
 import hashlib
 import re
-from typing import Optional, Tuple
-from urllib.parse import urlparse
+import urllib.parse
+from typing import Any, Optional, Tuple, Union
+from urllib.parse import parse_qs, urlparse
 
 import gitlab
 import requests
-from gitlab import GitlabGetError
+from gitlab import (GitlabAuthenticationError, GitlabCreateError,
+                    GitlabGetError, GitlabUpdateError)
 
 from pr_agent.algo.types import EDIT_TYPE, FilePatchInfo
 
 from ..algo.file_filter import filter_ignored
+from ..algo.git_patch_processing import decode_if_bytes
 from ..algo.language_handler import is_valid_file
 from ..algo.utils import (clip_tokens,
                           find_line_number_of_relevant_line_in_file,
@@ -31,13 +34,34 @@ class GitLabProvider(GitProvider):
         if not gitlab_url:
             raise ValueError("GitLab URL is not set in the config file")
         self.gitlab_url = gitlab_url
+        ssl_verify = get_settings().get("GITLAB.SSL_VERIFY", True)
         gitlab_access_token = get_settings().get("GITLAB.PERSONAL_ACCESS_TOKEN", None)
         if not gitlab_access_token:
             raise ValueError("GitLab personal access token is not set in the config file")
-        self.gl = gitlab.Gitlab(
-            url=gitlab_url,
-            oauth_token=gitlab_access_token
-        )
+        # Authentication method selection via configuration
+        auth_method = get_settings().get("GITLAB.AUTH_TYPE", "oauth_token")
+
+        # Basic validation of authentication type
+        if auth_method not in ["oauth_token", "private_token"]:
+            raise ValueError(f"Unsupported GITLAB.AUTH_TYPE: '{auth_method}'. "
+                           f"Must be 'oauth_token' or 'private_token'.")
+
+        # Create GitLab instance based on authentication method
+        try:
+            if auth_method == "oauth_token":
+                self.gl = gitlab.Gitlab(
+                    url=gitlab_url,
+                    oauth_token=gitlab_access_token,
+                    ssl_verify=ssl_verify
+                )
+            else:  # private_token
+                self.gl = gitlab.Gitlab(
+                    url=gitlab_url,
+                    private_token=gitlab_access_token
+                )
+        except Exception as e:
+            get_logger().error(f"Failed to create GitLab instance: {e}")
+            raise ValueError(f"Unable to authenticate with GitLab: {e}")
         self.max_comment_chars = 65000
         self.id_project = None
         self.id_mr = None
@@ -45,12 +69,222 @@ class GitLabProvider(GitProvider):
         self.diff_files = None
         self.git_files = None
         self.temp_comments = []
+        self._submodule_cache: dict[tuple[str, str, str], list[dict]] = {}
         self.pr_url = merge_request_url
         self._set_merge_request(merge_request_url)
         self.RE_HUNK_HEADER = re.compile(
             r"^@@ -(\d+)(?:,(\d+))? \+(\d+)(?:,(\d+))? @@[ ]?(.*)")
         self.incremental = incremental
 
+    # --- submodule expansion helpers (opt-in) ---
+    def _get_gitmodules_map(self) -> dict[str, str]:
+        """
+        Return {submodule_path -> repo_url} from '.gitmodules' (best effort).
+        Tries target branch first, then source branch. Always returns text.
+        """
+        try:
+            proj = self.gl.projects.get(self.id_project)
+        except Exception:
+            return {}
+
+        import base64
+
+        def _read_text(ref: str | None) -> str | None:
+            if not ref:
+                return None
+            try:
+                f = proj.files.get(file_path=".gitmodules", ref=ref)
+            except Exception:
+                return None
+
+            # 1) python-gitlab File.decode() – usually returns BYTES
+            try:
+                raw = f.decode()
+                if isinstance(raw, (bytes, bytearray)):
+                    return raw.decode("utf-8", "ignore")
+                if isinstance(raw, str):
+                    return raw
+            except Exception:
+                pass
+
+            # 2) fallback: base64 decode f.content
+            try:
+                c = getattr(f, "content", None)
+                if c:
+                    return base64.b64decode(c).decode("utf-8", "ignore")
+            except Exception:
+                pass
+
+            return None
+
+        content = (
+            _read_text(getattr(self.mr, "target_branch", None))
+            or _read_text(getattr(self.mr, "source_branch", None))
+        )
+        if not content:
+            return {}
+
+        import configparser
+
+        parser = configparser.ConfigParser(
+            delimiters=("=",),
+            interpolation=None,
+            inline_comment_prefixes=("#", ";"),
+            strict=False,
+        )
+        try:
+            parser.read_string(content)
+        except Exception:
+            return {}
+
+        out: dict[str, str] = {}
+        for section in parser.sections():
+            if not section.lower().startswith("submodule"):
+                continue
+            path = parser.get(section, "path", fallback=None)
+            url = parser.get(section, "url", fallback=None)
+            if path and url:
+                path = path.strip().strip('"').strip("'")
+                url = url.strip().strip('"').strip("'")
+                out[path] = url
+        return out
+
+    def _url_to_project_path(self, url: str) -> str | None:
+        """
+        Convert ssh/https GitLab URL to 'group/subgroup/repo' project path.
+        """
+        try:
+            if url.startswith("git@") and ":" in url:
+                path = url.split(":", 1)[1]
+            else:
+                path = urllib.parse.urlparse(url).path.lstrip("/")
+            if path.endswith(".git"):
+                path = path[:-4]
+            return path or None
+        except Exception:
+            return None
+
+    def _project_by_path(self, proj_path: str):
+        """
+        Resolve a project by path with multiple strategies:
+        1) URL-encoded path_with_namespace
+        2) Raw path_with_namespace
+        3) Search fallback + exact match on path_with_namespace (case-insensitive)
+        Returns a project object or None.
+        """
+        if not proj_path:
+            return None
+
+        # 1) Encoded
+        try:
+            enc = urllib.parse.quote_plus(proj_path)
+            return self.gl.projects.get(enc)
+        except Exception:
+            pass
+
+        # 2) Raw
+        try:
+            return self.gl.projects.get(proj_path)
+        except Exception:
+            pass
+
+        # 3) Search fallback
+        try:
+            name = proj_path.split("/")[-1]
+            # membership=True so we don't leak other people's repos
+            matches = self.gl.projects.list(search=name, simple=True, membership=True, per_page=100)
+            # prefer exact path_with_namespace match (case-insensitive)
+            for p in matches:
+                pwn = getattr(p, "path_with_namespace", "")
+                if pwn.lower() == proj_path.lower():
+                    return self.gl.projects.get(p.id)
+            if matches:
+                get_logger().warning(f"[submodule] no exact match for {proj_path} (skip)")
+        except Exception:
+            pass
+
+        return None
+
+    def _compare_submodule(self, proj_path: str, old_sha: str, new_sha: str) -> list[dict]:
+        """
+        Call repository_compare on submodule project; return list of diffs.
+        """
+        key = (proj_path, old_sha, new_sha)
+        if key in self._submodule_cache:
+            return self._submodule_cache[key]
+        try:
+            proj = self._project_by_path(proj_path)
+            if proj is None:
+                get_logger().warning(f"[submodule] resolve failed for {proj_path}")
+                self._submodule_cache[key] = []
+                return []
+            cmp = proj.repository_compare(old_sha, new_sha)
+            if isinstance(cmp, dict):
+                diffs = cmp.get("diffs", []) or []
+            else:
+                diffs = []
+            self._submodule_cache[key] = diffs
+            return diffs
+        except Exception as e:
+            get_logger().warning(f"[submodule] compare failed for {proj_path} {old_sha}..{new_sha}: {e}")
+            self._submodule_cache[key] = []
+            return []
+
+    def _expand_submodule_changes(self, changes: list[dict]) -> list[dict]:
+        """
+        If enabled, expand 'Subproject commit' bumps into real file diffs from the submodule.
+        Soft-fail on any issue.
+        """
+        try:
+            if not bool(get_settings().get("GITLAB.EXPAND_SUBMODULE_DIFFS", False)):
+                return changes
+        except Exception:
+            return changes
+
+        gitmodules = self._get_gitmodules_map()
+        if not gitmodules:
+            return changes
+
+        out = list(changes)
+        for ch in changes:
+            patch = ch.get("diff") or ""
+            if "Subproject commit" not in patch:
+                continue
+
+            # Extract old/new SHAs from the hunk
+            old_m = re.search(r"^-Subproject commit ([0-9a-f]{7,40})", patch, re.M)
+            new_m = re.search(r"^\+Subproject commit ([0-9a-f]{7,40})", patch, re.M)
+            if not (old_m and new_m):
+                continue
+            old_sha, new_sha = old_m.group(1), new_m.group(1)
+
+            sub_path = ch.get("new_path") or ch.get("old_path") or ""
+            repo_url = gitmodules.get(sub_path)
+            if not repo_url:
+                get_logger().warning(f"[submodule] no url for '{sub_path}' in .gitmodules (skip)")
+                continue
+
+            proj_path = self._url_to_project_path(repo_url)
+            if not proj_path:
+                get_logger().warning(f"[submodule] cannot parse project path from url '{repo_url}' (skip)")
+                continue
+
+            get_logger().info(f"[submodule] {sub_path} url={repo_url} -> proj_path={proj_path}")
+            sub_diffs = self._compare_submodule(proj_path, old_sha, new_sha)
+            for sd in sub_diffs:
+                sd_diff = sd.get("diff") or ""
+                sd_old = sd.get("old_path") or sd.get("a_path") or ""
+                sd_new = sd.get("new_path") or sd.get("b_path") or sd_old
+                out.append({
+                    "old_path": f"{sub_path}/{sd_old}" if sd_old else sub_path,
+                    "new_path": f"{sub_path}/{sd_new}" if sd_new else sub_path,
+                    "diff": sd_diff,
+                    "new_file": sd.get("new_file", False),
+                    "deleted_file": sd.get("deleted_file", False),
+                    "renamed_file": sd.get("renamed_file", False),
+                })
+        return out
+
     def is_supported(self, capability: str) -> bool:
         if capability in ['get_issue_comments', 'create_inline_comment', 'publish_inline_comments',
             'publish_file_comments']: # gfm_markdown is supported in gitlab !
@@ -112,14 +346,50 @@ class GitLabProvider(GitProvider):
             get_logger().error(f"Could not get diff for merge request {self.id_mr}")
             raise DiffNotFoundError(f"Could not get diff for merge request {self.id_mr}") from e
 
-
     def get_pr_file_content(self, file_path: str, branch: str) -> str:
         try:
-            return self.gl.projects.get(self.id_project).files.get(file_path, branch).decode()
+            file_obj = self.gl.projects.get(self.id_project).files.get(file_path, branch)
+            content = file_obj.decode()
+            return decode_if_bytes(content)
         except GitlabGetError:
             # In case of file creation the method returns GitlabGetError (404 file not found).
             # In this case we return an empty string for the diff.
             return ''
+        except Exception as e:
+            get_logger().warning(f"Error retrieving file {file_path} from branch {branch}: {e}")
+            return ''
+
+    def create_or_update_pr_file(self, file_path: str, branch: str, contents="", message="") -> None:
+        """Create or update a file in the GitLab repository."""
+        try:
+            project = self.gl.projects.get(self.id_project)
+
+            if not message:
+                action = "Update" if contents else "Create"
+                message = f"{action} {file_path}"
+
+            try:
+                existing_file = project.files.get(file_path, branch)
+                existing_file.content = contents
+                existing_file.save(branch=branch, commit_message=message)
+                get_logger().debug(f"Updated file {file_path} in branch {branch}")
+            except GitlabGetError:
+                project.files.create({
+                    'file_path': file_path,
+                    'branch': branch,
+                    'content': contents,
+                    'commit_message': message
+                })
+                get_logger().debug(f"Created file {file_path} in branch {branch}")
+        except GitlabAuthenticationError as e:
+            get_logger().error(f"Authentication failed while creating/updating file {file_path} in branch {branch}: {e}")
+            raise
+        except (GitlabCreateError, GitlabUpdateError) as e:
+            get_logger().error(f"Permission denied or validation error for file {file_path} in branch {branch}: {e}")
+            raise
+        except Exception as e:
+            get_logger().exception(f"Unexpected error creating/updating file {file_path} in branch {branch}: {e}")
+            raise
 
     def get_diff_files(self) -> list[FilePatchInfo]:
         """
@@ -135,7 +405,9 @@ class GitLabProvider(GitProvider):
             return self.diff_files
 
         # filter files using [ignore] patterns
-        diffs_original = self.mr.changes()['changes']
+        raw_changes = self.mr.changes().get('changes', [])
+        raw_changes = self._expand_submodule_changes(raw_changes)
+        diffs_original = raw_changes
         diffs = filter_ignored(diffs_original, 'gitlab')
         if diffs != diffs_original:
             try:
@@ -167,14 +439,9 @@ class GitLabProvider(GitProvider):
                 original_file_content_str = ''
                 new_file_content_str = ''
 
-            try:
-                if isinstance(original_file_content_str, bytes):
-                    original_file_content_str = bytes.decode(original_file_content_str, 'utf-8')
-                if isinstance(new_file_content_str, bytes):
-                    new_file_content_str = bytes.decode(new_file_content_str, 'utf-8')
-            except UnicodeDecodeError:
-                get_logger().warning(
-                    f"Cannot decode file {diff['old_path']} or {diff['new_path']} in merge request {self.id_mr}")
+            # Ensure content is properly decoded
+            original_file_content_str = decode_if_bytes(original_file_content_str)
+            new_file_content_str = decode_if_bytes(new_file_content_str)
 
             edit_type = EDIT_TYPE.MODIFIED
             if diff['new_file']:
@@ -210,7 +477,9 @@ class GitLabProvider(GitProvider):
 
     def get_files(self) -> list:
         if not self.git_files:
-            self.git_files = [change['new_path'] for change in self.mr.changes()['changes']]
+            raw_changes = self.mr.changes().get('changes', [])
+            raw_changes = self._expand_submodule_changes(raw_changes)
+            self.git_files = [c.get('new_path') for c in raw_changes if c.get('new_path')]
         return self.git_files
 
     def publish_description(self, pr_title: str, pr_body: str):
@@ -366,7 +635,9 @@ class GitLabProvider(GitProvider):
                     get_logger().exception(f"Failed to create comment in MR {self.id_mr}")
 
     def get_relevant_diff(self, relevant_file: str, relevant_line_in_file: str) -> Optional[dict]:
-        changes = self.mr.changes()  # Retrieve the changes for the merge request once
+        _changes = self.mr.changes()  # dict
+        _changes['changes'] = self._expand_submodule_changes(_changes.get('changes', []))
+        changes = _changes
         if not changes:
             get_logger().error('No changes found for the merge request.')
             return None
@@ -529,10 +800,52 @@ class GitLabProvider(GitProvider):
         return self.id_project.split('/')[0]
 
     def add_eyes_reaction(self, issue_comment_id: int, disable_eyes: bool = False) -> Optional[int]:
-        return True
+        if disable_eyes:
+            return None
+        try:
+            if not self.id_mr:
+                get_logger().warning("Cannot add eyes reaction: merge request ID is not set.")
+                return None
 
-    def remove_reaction(self, issue_comment_id: int, reaction_id: int) -> bool:
-        return True
+            mr = self.gl.projects.get(self.id_project).mergerequests.get(self.id_mr)
+            comment = mr.notes.get(issue_comment_id)
+
+            if not comment:
+                get_logger().warning(f"Comment with ID {issue_comment_id} not found in merge request {self.id_mr}.")
+                return None
+
+            award_emoji = comment.awardemojis.create({
+                'name': 'eyes'
+            })
+            return award_emoji.id
+        except Exception as e:
+            get_logger().warning(f"Failed to add eyes reaction, error: {e}")
+            return None
+
+    def remove_reaction(self, issue_comment_id: int, reaction_id: str) -> bool:
+        try:
+            if not self.id_mr:
+                get_logger().warning("Cannot remove reaction: merge request ID is not set.")
+                return False
+
+            mr = self.gl.projects.get(self.id_project).mergerequests.get(self.id_mr)
+            comment = mr.notes.get(issue_comment_id)
+
+            if not comment:
+                get_logger().warning(f"Comment with ID {issue_comment_id} not found in merge request {self.id_mr}.")
+                return False
+
+            reactions = comment.awardemojis.list()
+            for reaction in reactions:
+                if reaction.name == reaction_id:
+                    reaction.delete()
+                    return True
+
+            get_logger().warning(f"Reaction '{reaction_id}' not found in comment {issue_comment_id}.")
+            return False
+        except Exception as e:
+            get_logger().warning(f"Failed to remove reaction, error: {e}")
+            return False
 
     def _parse_merge_request_url(self, merge_request_url: str) -> Tuple[str, int]:
         parsed_url = urlparse(merge_request_url)
@@ -645,7 +958,7 @@ class GitLabProvider(GitProvider):
             get_logger().error(f"Repo URL: {repo_url_to_clone} is not a valid gitlab URL.")
             return None
         (scheme, base_url) = repo_url_to_clone.split("gitlab.")
-        access_token = self.gl.oauth_token
+        access_token = getattr(self.gl, 'oauth_token', None) or getattr(self.gl, 'private_token', None)
         if not all([scheme, access_token, base_url]):
             get_logger().error(f"Either no access token found, or repo URL: {repo_url_to_clone} "
                                f"is missing prefix: {scheme} and/or base URL: {base_url}.")

pr_agent/git_providers/utils.py

@@ -1,6 +1,7 @@
 import copy
 import os
 import tempfile
+import traceback
 
 from dynaconf import Dynaconf
 from starlette_context import context
@@ -35,8 +36,34 @@ def apply_repo_settings(pr_url):
                 try:
                     fd, repo_settings_file = tempfile.mkstemp(suffix='.toml')
                     os.write(fd, repo_settings)
-                    new_settings = Dynaconf(settings_files=[repo_settings_file])
+
+                    try:
+                        dynconf_kwargs = {'core_loaders': [],  # DISABLE default loaders, otherwise will load toml files more than once.
+                             'loaders': ['pr_agent.custom_merge_loader'],
+                             # Use a custom loader to merge sections, but overwrite their overlapping values. Don't involve ENV variables.
+                             'merge_enabled': True  # Merge multiple files; ensures [XYZ] sections only overwrite overlapping keys, not whole sections.
+                         }
+
+                        new_settings = Dynaconf(settings_files=[repo_settings_file],
+                                                # Disable all dynamic loading features
+                                                load_dotenv=False,  # Don't load .env files
+                                                envvar_prefix=False,  # Drop DYNACONF for env. variables
+                                                **dynconf_kwargs
+                                                )
+                    except TypeError as e:
+                        # Fallback for older Dynaconf versions that don't support these parameters
+                        get_logger().warning(
+                            "Your Dynaconf version does not support disabled 'load_dotenv'/'merge_enabled' parameters. "
+                            "Loading repo settings without these security features. "
+                            "Please upgrade Dynaconf for better security.",
+                            artifact={"error": e, "traceback": traceback.format_exc()})
+                        new_settings = Dynaconf(settings_files=[repo_settings_file])
+
                     for section, contents in new_settings.as_dict().items():
+                        if not contents:
+                            # Skip excluded items, such as forbidden to load env.
+                            get_logger().debug(f"Skipping a section: {section} which is not allowed")
+                            continue
                         section_dict = copy.deepcopy(get_settings().as_dict().get(section, {}))
                         for key, value in contents.items():
                             section_dict[key] = value

pr_agent/secret_providers/__init__.py

@@ -13,5 +13,12 @@ def get_secret_provider():
             return GoogleCloudStorageSecretProvider()
         except Exception as e:
             raise ValueError(f"Failed to initialize google_cloud_storage secret provider {provider_id}") from e
+    elif provider_id == 'aws_secrets_manager':
+        try:
+            from pr_agent.secret_providers.aws_secrets_manager_provider import \
+                AWSSecretsManagerProvider
+            return AWSSecretsManagerProvider()
+        except Exception as e:
+            raise ValueError(f"Failed to initialize aws_secrets_manager secret provider {provider_id}") from e
     else:
         raise ValueError("Unknown SECRET_PROVIDER")

pr_agent/secret_providers/aws_secrets_manager_provider.py

@@ -0,0 +1,57 @@
+import json
+import boto3
+from botocore.exceptions import ClientError
+
+from pr_agent.config_loader import get_settings
+from pr_agent.log import get_logger
+from pr_agent.secret_providers.secret_provider import SecretProvider
+
+
+class AWSSecretsManagerProvider(SecretProvider):
+    def __init__(self):
+        try:
+            region_name = get_settings().get("aws_secrets_manager.region_name") or \
+                         get_settings().get("aws.AWS_REGION_NAME")
+            if region_name:
+                self.client = boto3.client('secretsmanager', region_name=region_name)
+            else:
+                self.client = boto3.client('secretsmanager')
+
+            self.secret_arn = get_settings().get("aws_secrets_manager.secret_arn")
+            if not self.secret_arn:
+                raise ValueError("AWS Secrets Manager ARN is not configured")
+        except Exception as e:
+            get_logger().error(f"Failed to initialize AWS Secrets Manager Provider: {e}")
+            raise e
+
+    def get_secret(self, secret_name: str) -> str:
+        """
+        Retrieve individual secret by name (for webhook tokens)
+        """
+        try:
+            response = self.client.get_secret_value(SecretId=secret_name)
+            return response['SecretString']
+        except Exception as e:
+            get_logger().warning(f"Failed to get secret {secret_name} from AWS Secrets Manager: {e}")
+            return ""
+
+    def get_all_secrets(self) -> dict:
+        """
+        Retrieve all secrets for configuration override
+        """
+        try:
+            response = self.client.get_secret_value(SecretId=self.secret_arn)
+            return json.loads(response['SecretString'])
+        except Exception as e:
+            get_logger().error(f"Failed to get secrets from AWS Secrets Manager {self.secret_arn}: {e}")
+            return {}
+
+    def store_secret(self, secret_name: str, secret_value: str):
+        try:
+            self.client.put_secret_value(
+                SecretId=secret_name,
+                SecretString=secret_value
+            )
+        except Exception as e:
+            get_logger().error(f"Failed to store secret {secret_name} in AWS Secrets Manager: {e}")
+            raise e 

pr_agent/servers/atlassian-connect-qodo-merge.json

@@ -0,0 +1,38 @@
+{
+  "name": "Qodo Merge",
+  "description": "Qodo Merge",
+  "key": "app_key",
+  "vendor": {
+    "name": "Qodo",
+    "url": "https://qodo.ai"
+  },
+  "authentication": {
+    "type": "jwt"
+  },
+  "baseUrl": "base_url",
+  "lifecycle": {
+    "installed": "/installed",
+    "uninstalled": "/uninstalled"
+  },
+  "scopes": [
+    "account",
+    "repository:write",
+    "pullrequest:write",
+    "wiki"
+  ],
+  "contexts": [
+    "account"
+  ],
+  "modules": {
+    "webhooks": [
+      {
+        "event": "*",
+        "url": "/webhook"
+      }
+    ]
+  },
+  "links": {
+    "privacy": "https://qodo.ai/privacy-policy",
+    "terms": "https://qodo.ai/terms"
+  }
+}

pr_agent/servers/atlassian-connect.json

@@ -30,5 +30,9 @@
         "url": "/webhook"
       }
     ]
+  },
+  "links": {
+    "privacy": "https://qodo.ai/privacy-policy",
+    "terms": "https://qodo.ai/terms"
   }
 }

pr_agent/servers/bitbucket_app.py

@@ -83,16 +83,79 @@ def _get_username(data):
     return ""
 
 
+async def _validate_time_from_last_commit_to_pr_update(data: dict) -> bool:
+    is_valid_push = False
+    try:
+        data_inner = data.get('data', {})
+        if not data_inner:
+            get_logger().error("No data found in the webhook payload")
+            return True
+        pull_request = data_inner.get('pullrequest', {})
+        commits_api = pull_request.get('links', {}).get('commits', {}).get('href')
+        if not commits_api:
+            return False
+        if not pull_request.get('updated_on'):
+            return False
+        bearer_token = context.get('bitbucket_bearer_token')
+        headers = {
+            'Authorization': f'Bearer {bearer_token}',
+            'Accept': 'application/json'
+        }
+        response = requests.get(commits_api, headers=headers)
+        if response.status_code != 200:
+            get_logger().warning(f"Bitbucket commits API returned {response.status_code} for {commits_api}")
+            return False
+
+        username =_get_username(data)
+        commits_data = response.json() or {}
+        values = commits_data.get('values') or []
+        if (not values or not isinstance(values, list) or not values[0].get('author') or not values[0]['author'].get('user')
+                or not values[0]['author']['user'].get('display_name')):
+            get_logger().warning("No commits returned for pull request or one of the required fields missing; skipping push validation",
+                                 artifact={'values': values})
+            return False
+        commit_username = commits_data['values'][0]['author']['user']['display_name']
+        if username != commit_username:
+            get_logger().warning(f"Mismatch in username {username} vs. commit_username {commit_username}")
+            return False
+
+        time_pr_updated = pull_request['updated_on']
+        time_last_commit = commits_data['values'][0]['date']
+        from datetime import datetime
+        ts1 = datetime.fromisoformat(time_pr_updated)
+        ts2 = datetime.fromisoformat(time_last_commit)
+        diff = (ts1 - ts2).total_seconds()
+        max_delta_seconds = 15
+        if diff > 0 and diff < max_delta_seconds:
+            is_valid_push = True
+        else:
+            get_logger().debug(f"Too much time passed since last commit",
+                               artifact={'updated': time_pr_updated, 'last_commit': time_last_commit})
+    except Exception as e:
+        get_logger().exception(f"Failed to validate time difference between last commit and PR update",
+                               artifact={'error': e, 'data': data})
+    return is_valid_push
+
 async def _perform_commands_bitbucket(commands_conf: str, agent: PRAgent, api_url: str, log_context: dict, data: dict):
     apply_repo_settings(api_url)
     if commands_conf == "pr_commands" and get_settings().config.disable_auto_feedback:  # auto commands for PR, and auto feedback is disabled
         get_logger().info(f"Auto feedback is disabled, skipping auto commands for PR {api_url=}")
         return
+    if commands_conf == "push_commands":
+        if not get_settings().get("bitbucket_app.handle_push_trigger"):
+            get_logger().info(
+                "Bitbucket push trigger handling disabled via config; skipping push commands")
+            return
     if data.get("event", "") == "pullrequest:created":
         if not should_process_pr_logic(data):
             return
     commands = get_settings().get(f"bitbucket_app.{commands_conf}", {})
     get_settings().set("config.is_auto_command", True)
+    if commands_conf == "push_commands":
+        is_valid_push = await _validate_time_from_last_commit_to_pr_update(data)
+        if not is_valid_push:
+            get_logger().info(f"Bitbucket skipping 'pullrequest:updated' for push commands")
+            return
     for command in commands:
         try:
             split_command = command.split(" ")
@@ -139,7 +202,7 @@ def should_process_pr_logic(data) -> bool:
         # logic to ignore PRs from specific users
         ignore_pr_users = get_settings().get("CONFIG.IGNORE_PR_AUTHORS", [])
         if ignore_pr_users and sender:
-            if sender in ignore_pr_users:
+            if any(re.search(regex, sender) for regex in ignore_pr_users):
                 get_logger().info(f"Ignoring PR from user '{sender}' due to 'config.ignore_pr_authors' setting")
                 return False
 
@@ -215,11 +278,21 @@ async def handle_github_webhooks(background_tasks: BackgroundTasks, request: Req
                 log_context["event"] = "pull_request"
                 if pr_url:
                     with get_logger().contextualize(**log_context):
-                        apply_repo_settings(pr_url)
                         if get_identity_provider().verify_eligibility("bitbucket",
                                                         sender_id, pr_url) is not Eligibility.NOT_ELIGIBLE:
                             if get_settings().get("bitbucket_app.pr_commands"):
-                                await _perform_commands_bitbucket("pr_commands", PRAgent(), pr_url, log_context, data)
+                                await _perform_commands_bitbucket("pr_commands", agent, pr_url, log_context, data)
+            elif event == "pullrequest:updated": # PR updated, might be from a push (we will validate this later)
+                pr_url = data["data"]["pullrequest"]["links"]["html"]["href"]
+                log_context["api_url"] = pr_url
+                log_context["event"] = "pull_request"
+                if pr_url:
+                    with get_logger().contextualize(**log_context):
+                        if get_identity_provider().verify_eligibility("bitbucket",
+                                                        sender_id, pr_url) is not Eligibility.NOT_ELIGIBLE:
+
+                            if get_settings().get("bitbucket_app.push_commands"):
+                                await _perform_commands_bitbucket("push_commands", agent, pr_url, log_context, data)
             elif event == "pullrequest:comment_created":
                 pr_url = data["data"]["pullrequest"]["links"]["html"]["href"]
                 log_context["api_url"] = pr_url

pr_agent/servers/bitbucket_server_webhook.py

@@ -1,6 +1,7 @@
 import ast
 import json
 import os
+import re
 from typing import List
 
 import uvicorn
@@ -40,6 +41,88 @@ def handle_request(
 
     background_tasks.add_task(inner)
 
+def should_process_pr_logic(data) -> bool:
+    try:
+        pr_data = data.get("pullRequest", {})
+        title = pr_data.get("title", "")
+        
+        from_ref = pr_data.get("fromRef", {})
+        source_branch = from_ref.get("displayId", "") if from_ref else ""
+        
+        to_ref = pr_data.get("toRef", {})
+        target_branch = to_ref.get("displayId", "") if to_ref else ""
+        
+        author = pr_data.get("author", {})
+        user = author.get("user", {}) if author else {}
+        sender = user.get("name", "") if user else ""
+        
+        repository = to_ref.get("repository", {}) if to_ref else {}
+        project = repository.get("project", {}) if repository else {}
+        project_key = project.get("key", "") if project else ""
+        repo_slug = repository.get("slug", "") if repository else ""
+        
+        repo_full_name = f"{project_key}/{repo_slug}" if project_key and repo_slug else ""
+        pr_id = pr_data.get("id", None)
+
+        # To ignore PRs from specific repositories
+        ignore_repos = get_settings().get("CONFIG.IGNORE_REPOSITORIES", [])
+        if repo_full_name and ignore_repos:
+            if any(re.search(regex, repo_full_name) for regex in ignore_repos):
+                get_logger().info(f"Ignoring PR from repository '{repo_full_name}' due to 'config.ignore_repositories' setting")
+                return False
+
+        # To ignore PRs from specific users
+        ignore_pr_users = get_settings().get("CONFIG.IGNORE_PR_AUTHORS", [])
+        if ignore_pr_users and sender:
+            if any(re.search(regex, sender) for regex in ignore_pr_users):
+                get_logger().info(f"Ignoring PR from user '{sender}' due to 'config.ignore_pr_authors' setting")
+                return False
+
+        # To ignore PRs with specific titles
+        if title:
+            ignore_pr_title_re = get_settings().get("CONFIG.IGNORE_PR_TITLE", [])
+            if not isinstance(ignore_pr_title_re, list):
+                ignore_pr_title_re = [ignore_pr_title_re]
+            if ignore_pr_title_re and any(re.search(regex, title) for regex in ignore_pr_title_re):
+                get_logger().info(f"Ignoring PR with title '{title}' due to config.ignore_pr_title setting")
+                return False
+
+        ignore_pr_source_branches = get_settings().get("CONFIG.IGNORE_PR_SOURCE_BRANCHES", [])
+        ignore_pr_target_branches = get_settings().get("CONFIG.IGNORE_PR_TARGET_BRANCHES", [])
+        if (ignore_pr_source_branches or ignore_pr_target_branches):
+            if any(re.search(regex, source_branch) for regex in ignore_pr_source_branches):
+                get_logger().info(
+                    f"Ignoring PR with source branch '{source_branch}' due to config.ignore_pr_source_branches settings")
+                return False
+            if any(re.search(regex, target_branch) for regex in ignore_pr_target_branches):
+                get_logger().info(
+                    f"Ignoring PR with target branch '{target_branch}' due to config.ignore_pr_target_branches settings")
+                return False
+
+        # Allow_only_specific_folders
+        allowed_folders = get_settings().config.get("allow_only_specific_folders", [])
+        if allowed_folders and pr_id and project_key and repo_slug:
+            from pr_agent.git_providers.bitbucket_server_provider import BitbucketServerProvider
+            bitbucket_server_url = get_settings().get("BITBUCKET_SERVER.URL", "")
+            pr_url = f"{bitbucket_server_url}/projects/{project_key}/repos/{repo_slug}/pull-requests/{pr_id}"
+            provider = BitbucketServerProvider(pr_url=pr_url)
+            changed_files = provider.get_files()
+            if changed_files:
+                # Check if ALL files are outside allowed folders
+                all_files_outside = True
+                for file_path in changed_files:
+                    if any(file_path.startswith(folder) for folder in allowed_folders):
+                        all_files_outside = False
+                        break
+                
+                if all_files_outside:
+                    get_logger().info(f"Ignoring PR because all files {changed_files} are outside allowed folders {allowed_folders}")
+                    return False
+    except Exception as e:
+        get_logger().error(f"Failed 'should_process_pr_logic': {e}")
+        return True # On exception - we continue. Otherwise, we could just end up with filtering all PRs
+    return True
+
 @router.post("/")
 async def redirect_to_webhook():
     return RedirectResponse(url="/webhook")
@@ -71,13 +154,31 @@ async def handle_webhook(background_tasks: BackgroundTasks, request: Request):
 
     commands_to_run = []
 
-    if data["eventKey"] == "pr:opened":
+    if (data["eventKey"] == "pr:opened"
+            or (data["eventKey"] == "repo:refs_changed" and data.get("pullRequest", {}).get("id", -1) != -1)):  # push event; -1 for push unassigned to a PR: #Check auto commands for creation/updating
         apply_repo_settings(pr_url)
+        if not should_process_pr_logic(data):
+            get_logger().info(f"PR ignored due to config settings", **log_context)
+            return JSONResponse(
+                status_code=status.HTTP_200_OK, content=jsonable_encoder({"message": "PR ignored by config"})
+            )
         if get_settings().config.disable_auto_feedback:  # auto commands for PR, and auto feedback is disabled
             get_logger().info(f"Auto feedback is disabled, skipping auto commands for PR {pr_url}", **log_context)
-            return
+            return JSONResponse(
+                status_code=status.HTTP_200_OK, content=jsonable_encoder({"message": "PR ignored due to auto feedback not enabled"})
+            )
         get_settings().set("config.is_auto_command", True)
-        commands_to_run.extend(_get_commands_list_from_settings('BITBUCKET_SERVER.PR_COMMANDS'))
+        if data["eventKey"] == "pr:opened":
+            commands_to_run.extend(_get_commands_list_from_settings('BITBUCKET_SERVER.PR_COMMANDS'))
+        else: #Has to be: data["eventKey"] == "pr:from_ref_updated"
+            if not get_settings().get("BITBUCKET_SERVER.HANDLE_PUSH_TRIGGER"):
+                get_logger().info(f"Push trigger is disabled, skipping push commands for PR {pr_url}", **log_context)
+                return JSONResponse(
+                    status_code=status.HTTP_200_OK, content=jsonable_encoder({"message": "PR ignored due to push trigger not enabled"})
+                )
+
+            get_settings().set("config.is_new_pr", False)
+            commands_to_run.extend(_get_commands_list_from_settings('BITBUCKET_SERVER.PUSH_COMMANDS'))
     elif data["eventKey"] == "pr:comment:added":
         commands_to_run.append(data["comment"]["text"])
     else:

pr_agent/servers/gitea_app.py

@@ -0,0 +1,221 @@
+import copy
+import os
+import re
+from typing import Any, Dict
+
+from fastapi import APIRouter, FastAPI, HTTPException, Request, Response
+from starlette.background import BackgroundTasks
+from starlette.middleware import Middleware
+from starlette_context import context
+from starlette_context.middleware import RawContextMiddleware
+
+from pr_agent.agent.pr_agent import PRAgent
+from pr_agent.algo.utils import update_settings_from_args
+from pr_agent.config_loader import get_settings, global_settings
+from pr_agent.git_providers.utils import apply_repo_settings
+from pr_agent.log import LoggingFormat, get_logger, setup_logger
+from pr_agent.servers.utils import verify_signature
+
+# Setup logging and router
+setup_logger(fmt=LoggingFormat.JSON, level=get_settings().get("CONFIG.LOG_LEVEL", "DEBUG"))
+router = APIRouter()
+
+@router.post("/api/v1/gitea_webhooks")
+async def handle_gitea_webhooks(background_tasks: BackgroundTasks, request: Request, response: Response):
+    """Handle incoming Gitea webhook requests"""
+    get_logger().debug("Received a Gitea webhook")
+
+    body = await get_body(request)
+
+    # Set context for the request
+    context["settings"] = copy.deepcopy(global_settings)
+    context["git_provider"] = {}
+
+    # Handle the webhook in background
+    background_tasks.add_task(handle_request, body, event=request.headers.get("X-Gitea-Event", None))
+    return {}
+
+async def get_body(request: Request):
+    """Parse and verify webhook request body"""
+    try:
+        body = await request.json()
+    except Exception as e:
+        get_logger().error("Error parsing request body", artifact={'error': e})
+        raise HTTPException(status_code=400, detail="Error parsing request body") from e
+
+
+    # Verify webhook signature
+    webhook_secret = getattr(get_settings().gitea, 'webhook_secret', None)
+    if webhook_secret:
+        body_bytes = await request.body()
+        signature_header = request.headers.get('x-gitea-signature', None)
+        if not signature_header:
+            get_logger().error("Missing signature header")
+            raise HTTPException(status_code=400, detail="Missing signature header")
+
+        try:
+            verify_signature(body_bytes, webhook_secret, f"sha256={signature_header}")
+        except Exception as ex:
+            get_logger().error(f"Invalid signature: {ex}")
+            raise HTTPException(status_code=401, detail="Invalid signature")
+
+    return body
+
+async def handle_request(body: Dict[str, Any], event: str):
+    """Process Gitea webhook events"""
+    action = body.get("action")
+    if not action:
+        get_logger().debug("No action found in request body")
+        return {}
+
+    agent = PRAgent()
+
+    # Handle different event types
+    if event == "pull_request":
+        if not should_process_pr_logic(body):
+            get_logger().debug(f"Request ignored: PR logic filtering")
+            return {}
+        if action in ["opened", "reopened", "synchronized"]:
+            await handle_pr_event(body, event, action, agent)
+    elif event == "issue_comment":
+        if action == "created":
+            await handle_comment_event(body, event, action, agent)
+
+    return {}
+
+async def handle_pr_event(body: Dict[str, Any], event: str, action: str, agent: PRAgent):
+    """Handle pull request events"""
+    pr = body.get("pull_request", {})
+    if not pr:
+        return
+
+    api_url = pr.get("url")
+    if not api_url:
+        return
+
+    # Handle PR based on action
+    if action in ["opened", "reopened"]:
+        # commands = get_settings().get("gitea.pr_commands", [])
+        await _perform_commands_gitea("pr_commands", agent, body, api_url)
+        # for command in commands:
+        #     await agent.handle_request(api_url, command)
+    elif action == "synchronized":
+        # Handle push to PR
+        commands_on_push = get_settings().get(f"gitea.push_commands", {})
+        handle_push_trigger = get_settings().get(f"gitea.handle_push_trigger", False)
+        if not commands_on_push or not handle_push_trigger:
+            get_logger().info("Push event, but no push commands found or push trigger is disabled")
+            return
+        get_logger().debug(f'A push event has been received: {api_url}')
+        await _perform_commands_gitea("push_commands", agent, body, api_url)
+        # for command in commands_on_push:
+        #     await agent.handle_request(api_url, command)
+
+async def handle_comment_event(body: Dict[str, Any], event: str, action: str, agent: PRAgent):
+    """Handle comment events"""
+    comment = body.get("comment", {})
+    if not comment:
+        return
+
+    comment_body = comment.get("body", "")
+    if not comment_body or not comment_body.startswith("/"):
+        return
+
+    pr_url = body.get("pull_request", {}).get("url")
+    if not pr_url:
+        return
+
+    await agent.handle_request(pr_url, comment_body)
+
+async def _perform_commands_gitea(commands_conf: str, agent: PRAgent, body: dict, api_url: str):
+    apply_repo_settings(api_url)
+    if commands_conf == "pr_commands" and get_settings().config.disable_auto_feedback:  # auto commands for PR, and auto feedback is disabled
+        get_logger().info(f"Auto feedback is disabled, skipping auto commands for PR {api_url=}")
+        return
+    if not should_process_pr_logic(body): # Here we already updated the configuration with the repo settings
+        return {}
+    commands = get_settings().get(f"gitea.{commands_conf}")
+    if not commands:
+        get_logger().info(f"New PR, but no auto commands configured")
+        return
+    get_settings().set("config.is_auto_command", True)
+    for command in commands:
+        split_command = command.split(" ")
+        command = split_command[0]
+        args = split_command[1:]
+        other_args = update_settings_from_args(args)
+        new_command = ' '.join([command] + other_args)
+        get_logger().info(f"{commands_conf}. Performing auto command '{new_command}', for {api_url=}")
+        await agent.handle_request(api_url, new_command)
+
+def should_process_pr_logic(body) -> bool:
+    try:
+        pull_request = body.get("pull_request", {})
+        title = pull_request.get("title", "")
+        pr_labels = pull_request.get("labels", [])
+        source_branch = pull_request.get("head", {}).get("ref", "")
+        target_branch = pull_request.get("base", {}).get("ref", "")
+        sender = body.get("sender", {}).get("login")
+        repo_full_name = body.get("repository", {}).get("full_name", "")
+
+        # logic to ignore PRs from specific repositories
+        ignore_repos = get_settings().get("CONFIG.IGNORE_REPOSITORIES", [])
+        if ignore_repos and repo_full_name:
+            if any(re.search(regex, repo_full_name) for regex in ignore_repos):
+                get_logger().info(f"Ignoring PR from repository '{repo_full_name}' due to 'config.ignore_repositories' setting")
+                return False
+
+        # logic to ignore PRs from specific users
+        ignore_pr_users = get_settings().get("CONFIG.IGNORE_PR_AUTHORS", [])
+        if ignore_pr_users and sender:
+            if any(re.search(regex, sender) for regex in ignore_pr_users):
+                get_logger().info(f"Ignoring PR from user '{sender}' due to 'config.ignore_pr_authors' setting")
+                return False
+
+        # logic to ignore PRs with specific titles
+        if title:
+            ignore_pr_title_re = get_settings().get("CONFIG.IGNORE_PR_TITLE", [])
+            if not isinstance(ignore_pr_title_re, list):
+                ignore_pr_title_re = [ignore_pr_title_re]
+            if ignore_pr_title_re and any(re.search(regex, title) for regex in ignore_pr_title_re):
+                get_logger().info(f"Ignoring PR with title '{title}' due to config.ignore_pr_title setting")
+                return False
+
+        # logic to ignore PRs with specific labels or source branches or target branches.
+        ignore_pr_labels = get_settings().get("CONFIG.IGNORE_PR_LABELS", [])
+        if pr_labels and ignore_pr_labels:
+            labels = [label['name'] for label in pr_labels]
+            if any(label in ignore_pr_labels for label in labels):
+                labels_str = ", ".join(labels)
+                get_logger().info(f"Ignoring PR with labels '{labels_str}' due to config.ignore_pr_labels settings")
+                return False
+
+        # logic to ignore PRs with specific source or target branches
+        ignore_pr_source_branches = get_settings().get("CONFIG.IGNORE_PR_SOURCE_BRANCHES", [])
+        ignore_pr_target_branches = get_settings().get("CONFIG.IGNORE_PR_TARGET_BRANCHES", [])
+        if pull_request and (ignore_pr_source_branches or ignore_pr_target_branches):
+            if any(re.search(regex, source_branch) for regex in ignore_pr_source_branches):
+                get_logger().info(
+                    f"Ignoring PR with source branch '{source_branch}' due to config.ignore_pr_source_branches settings")
+                return False
+            if any(re.search(regex, target_branch) for regex in ignore_pr_target_branches):
+                get_logger().info(
+                    f"Ignoring PR with target branch '{target_branch}' due to config.ignore_pr_target_branches settings")
+                return False
+    except Exception as e:
+        get_logger().error(f"Failed 'should_process_pr_logic': {e}")
+    return True
+
+# FastAPI app setup
+middleware = [Middleware(RawContextMiddleware)]
+app = FastAPI(middleware=middleware)
+app.include_router(router)
+
+def start():
+    """Start the Gitea webhook server"""
+    port = int(os.environ.get("PORT", "3000"))
+    import uvicorn
+    uvicorn.run(app, host="0.0.0.0", port=port)
+
+if __name__ == "__main__":
+    start()

pr_agent/servers/github_action_runner.py

@@ -80,6 +80,30 @@ async def run_action():
     except Exception as e:
         get_logger().info(f"github action: failed to apply repo settings: {e}")
 
+    # Append the response language in the extra instructions
+    try:
+        response_language = get_settings().config.get('response_language', 'en-us')
+        if response_language.lower() != 'en-us':
+            get_logger().info(f'User has set the response language to: {response_language}')
+
+            lang_instruction_text = f"Your response MUST be written in the language corresponding to locale code: '{response_language}'. This is crucial."
+            separator_text = "\n======\n\nIn addition, "
+
+            for key in get_settings():
+                setting = get_settings().get(key)
+                if str(type(setting)) == "<class 'dynaconf.utils.boxing.DynaBox'>":
+                    if key.lower() in ['pr_description', 'pr_code_suggestions', 'pr_reviewer']:
+                        if hasattr(setting, 'extra_instructions'):
+                            extra_instructions = setting.extra_instructions
+
+                            if lang_instruction_text not in str(extra_instructions):
+                                updated_instructions = (
+                                    str(extra_instructions) + separator_text + lang_instruction_text
+                                    if extra_instructions else lang_instruction_text
+                                )
+                                setting.extra_instructions = updated_instructions
+    except Exception as e:
+        get_logger().info(f"github action: failed to apply language-specific instructions: {e}")
     # Handle pull request opened event
     if GITHUB_EVENT_NAME == "pull_request" or GITHUB_EVENT_NAME == "pull_request_target":
         action = event_payload.get("action")
@@ -102,7 +126,7 @@ async def run_action():
                     auto_improve = get_setting_or_env("GITHUB_ACTION_CONFIG.AUTO_IMPROVE", None)
 
                 # Set the configuration for auto actions
-                get_settings().config.is_auto_command = True # Set the flag to indicate that the command is auto
+                get_settings().config.is_auto_command = True  # Set the flag to indicate that the command is auto
                 get_settings().pr_description.final_update_message = False  # No final update message when auto_describe is enabled
                 get_logger().info(f"Running auto actions: auto_describe={auto_describe}, auto_review={auto_review}, auto_improve={auto_improve}")
 

pr_agent/servers/github_app.py

@@ -270,7 +270,7 @@ def should_process_pr_logic(body) -> bool:
         # logic to ignore PRs from specific users
         ignore_pr_users = get_settings().get("CONFIG.IGNORE_PR_AUTHORS", [])
         if ignore_pr_users and sender:
-            if sender in ignore_pr_users:
+            if any(re.search(regex, sender) for regex in ignore_pr_users):
                 get_logger().info(f"Ignoring PR from user '{sender}' due to 'config.ignore_pr_authors' setting")
                 return False
 

pr_agent/servers/github_lambda_webhook.py

@@ -0,0 +1,27 @@
+from fastapi import FastAPI
+from mangum import Mangum
+from starlette.middleware import Middleware
+from starlette_context.middleware import RawContextMiddleware
+
+from pr_agent.servers.github_app import router
+
+try:
+    from pr_agent.config_loader import apply_secrets_manager_config
+    apply_secrets_manager_config()
+except Exception as e:
+    try:
+        from pr_agent.log import get_logger
+        get_logger().debug(f"AWS Secrets Manager initialization failed, falling back to environment variables: {e}")
+    except:
+        # Fail completely silently if log module is not available
+        pass
+
+middleware = [Middleware(RawContextMiddleware)]
+app = FastAPI(middleware=middleware)
+app.include_router(router)
+
+handler = Mangum(app, lifespan="off")
+
+
+def lambda_handler(event, context):
+    return handler(event, context)

pr_agent/servers/gitlab_lambda_webhook.py

@@ -0,0 +1,27 @@
+from fastapi import FastAPI
+from mangum import Mangum
+from starlette.middleware import Middleware
+from starlette_context.middleware import RawContextMiddleware
+
+from pr_agent.servers.gitlab_webhook import router
+
+try:
+    from pr_agent.config_loader import apply_secrets_manager_config
+    apply_secrets_manager_config()
+except Exception as e:
+    try:
+        from pr_agent.log import get_logger
+        get_logger().debug(f"AWS Secrets Manager initialization failed, falling back to environment variables: {e}")
+    except:
+        # Fail completely silently if log module is not available
+        pass
+
+middleware = [Middleware(RawContextMiddleware)]
+app = FastAPI(middleware=middleware)
+app.include_router(router)
+
+handler = Mangum(app, lifespan="off")
+
+
+def lambda_handler(event, context):
+    return handler(event, context)

pr_agent/servers/gitlab_webhook.py

@@ -18,6 +18,7 @@ from pr_agent.config_loader import get_settings, global_settings
 from pr_agent.git_providers.utils import apply_repo_settings
 from pr_agent.log import LoggingFormat, get_logger, setup_logger
 from pr_agent.secret_providers import get_secret_provider
+from pr_agent.git_providers import get_git_provider_with_context
 
 setup_logger(fmt=LoggingFormat.JSON, level=get_settings().get("CONFIG.LOG_LEVEL", "DEBUG"))
 router = APIRouter()
@@ -25,15 +26,14 @@ router = APIRouter()
 secret_provider = get_secret_provider() if get_settings().get("CONFIG.SECRET_PROVIDER") else None
 
 
-async def handle_request(api_url: str, body: str, log_context: dict, sender_id: str):
+async def handle_request(api_url: str, body: str, log_context: dict, sender_id: str, notify=None):
     log_context["action"] = body
     log_context["event"] = "pull_request" if body == "/review" else "comment"
     log_context["api_url"] = api_url
     log_context["app_name"] = get_settings().get("CONFIG.APP_NAME", "Unknown")
 
     with get_logger().contextualize(**log_context):
-        await PRAgent().handle_request(api_url, body)
-
+        await PRAgent().handle_request(api_url, body, notify)
 
 async def _perform_commands_gitlab(commands_conf: str, agent: PRAgent, api_url: str,
                                    log_context: dict, data: dict):
@@ -125,7 +125,7 @@ def should_process_pr_logic(data) -> bool:
         # logic to ignore PRs from specific users
         ignore_pr_users = get_settings().get("CONFIG.IGNORE_PR_AUTHORS", [])
         if ignore_pr_users and sender:
-            if sender in ignore_pr_users:
+            if any(re.search(regex, sender) for regex in ignore_pr_users):
                 get_logger().info(f"Ignoring PR from user '{sender}' due to 'config.ignore_pr_authors' settings")
                 return False
 
@@ -234,6 +234,9 @@ async def gitlab_webhook(background_tasks: BackgroundTasks, request: Request):
                     get_logger().info(f"Skipping draft MR: {url}")
                     return JSONResponse(status_code=status.HTTP_200_OK, content=jsonable_encoder({"message": "success"}))
 
+                # Apply repo settings before checking push commands or handle_push_trigger
+                apply_repo_settings(url)
+
                 commands_on_push = get_settings().get(f"gitlab.push_commands", {})
                 handle_push_trigger = get_settings().get(f"gitlab.handle_push_trigger", False)
                 if not commands_on_push or not handle_push_trigger:
@@ -256,13 +259,15 @@ async def gitlab_webhook(background_tasks: BackgroundTasks, request: Request):
             if 'merge_request' in data:
                 mr = data['merge_request']
                 url = mr.get('url')
+                comment_id = data.get('object_attributes', {}).get('id')
+                provider = get_git_provider_with_context(pr_url=url)
 
                 get_logger().info(f"A comment has been added to a merge request: {url}")
                 body = data.get('object_attributes', {}).get('note')
                 if data.get('object_attributes', {}).get('type') == 'DiffNote' and '/ask' in body: # /ask_line
                     body = handle_ask_line(body, data)
 
-                await handle_request(url, body, log_context, sender_id)
+                await handle_request(url, body, log_context, sender_id, notify=lambda: provider.add_eyes_reaction(comment_id))
 
     background_tasks.add_task(inner, request_json)
     end_time = datetime.now()
@@ -283,7 +288,7 @@ def handle_ask_line(body, data):
         path = data['object_attributes']['position']['new_path']
         side = 'RIGHT'  # if line_range_['start']['type'] == 'new' else 'LEFT'
         comment_id = data['object_attributes']["discussion_id"]
-        get_logger().info("Handling line comment")
+        get_logger().info("Handling line ")
         body = f"/ask_line --line_start={start_line} --line_end={end_line} --side={side} --file_name={path} --comment_id={comment_id} {question}"
     except Exception as e:
         get_logger().error(f"Failed to handle ask line comment: {e}")

pr_agent/servers/help.py

@@ -81,6 +81,7 @@ the tool will replace every marker of the form `pr_agent:marker_name` in the PR
   - `type`: the PR type.
   - `summary`: the PR summary.
   - `walkthrough`: the PR walkthrough.
+  - `diagram`: the PR sequence diagram (if enabled).
 
 Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.