Is it possible to remember code suggestions from the previous push?

[dbudwin]

Git provider (optional)

GitHub

System Info (optional)

We're using this in GitHub Actions to review PRs on every push. See config:

GitHub Action

name: PR Agent Review

on:
  pull_request:
    types: [opened, reopened, synchronize, ready_for_review]
    branches:
      - main

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

jobs:
  pr_agent:
    name: PR Agent Review
    timeout-minutes: 3
    if: github.event.pull_request.draft == false
    runs-on: ubuntu-latest
    permissions:
      id-token: write
      issues: write
      pull-requests: write
      contents: read
    steps:
      - name: Configure AWS Credentials
        uses: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708
        with:
          role-to-assume: ${{ secrets.PR_AGENT_OIDC_ROLE_ARN }}
          aws-region: us-west-2

      - name: Run PR-Agent
        uses: qodo-ai/pr-agent@d36ad319f7fb0049205017405a71275c41599587
        env:
          config.model: "bedrock/anthropic.claude-sonnet-4-5-20250929-v1:0"
          config.fallback_models: '["bedrock/anthropic.claude-sonnet-4-5-20250929-v1:0"]'
          litellm.model_id: "us.anthropic.claude-sonnet-4-5-20250929-v1:0"

          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

          github_action_config.auto_review: "true"
          github_action_config.auto_describe: "true"
          github_action_config.auto_improve: "true"
          github_action_config.pr_actions: '["opened","reopened","synchronize","ready_for_review"]'

TOML Config

[pr_code_suggestions]
# Enable inline code suggestions on specific lines (GitHub suggestion format)
commitable_code_suggestions = true
# Number of suggestions per chunk
num_code_suggestions_per_chunk = 4

[pr_reviewer]
# Extra instructions for the reviewer
extra_instructions = """
<OMITTED FOR BREVITY>
"""

Issues details

A PR may get rebased/re-pushed a few times during it's lifecycle. Each time it does Qodo will re-run and it comments the same code suggestions over-and-over adding noise. We often reply to these code suggestions, add a thumbs down, or hit "resolve" as a way to indicate to other people reviewing the PR we're ignoring this code suggestion.

When we push our PR again re-triggering the action, it will add duplicates of all the code suggestions it already mentioned from the previous push if we elected not to implement them.

It would be optimal if Qodo had context of it's previous set of code suggestions instead of adding duplicate code suggestions.

[qodo-free-for-open-source-projects]

💡 Auto-generated documentation-based answer:

Currently, Qodo Merge does not have a built-in feature to remember and avoid duplicating code suggestions from previous pushes. Each time the tool runs (whether automatically on push or manually triggered), it analyzes the current state of the PR and generates fresh suggestions.

However, there are a few approaches you can consider to reduce duplicate suggestions:

1. Use Persistent Comments: Set pr_code_suggestions.persistent_comment=true in your configuration. This makes the improve tool edit the previous comment instead of creating new ones, which helps consolidate feedback in one place.

2. Adjust Trigger Settings: You can configure when the improve tool runs automatically. For example, you might want to disable it on push events and only run it when the PR is first opened:

   [github_app]
   handle_push_trigger = false
   pr_commands = ["/improve"]

3. Incremental Update Feature (💎 Qodo Merge only): For GitHub and GitLab (v17+), there's an "Incremental Update" feature that focuses on providing feedback for the newest changes. When new commits are pushed, an "Update" button appears that generates suggestions specifically for the delta/new changes.

4. Manual Control: Instead of automatic triggers, you can invoke /improve manually only when you want fresh suggestions, giving you more control over when analysis happens.

5. Suggestion Tracking (💎 Qodo Merge only): While this doesn't prevent duplicates, Qodo Merge can track which suggestions have been implemented (either directly or indirectly) and mark them with a checkmark, making it easier to see which suggestions are still relevant.

To better assist you, it would be helpful to know:

• Are you using the open-source PR-Agent or Qodo Merge (💎)?
• Which git provider are you using (GitHub, GitLab, etc.)?
• Are you running this as a GitHub Action, webhook, or another deployment method?

Relevant Sources:

• https://docs.qodo.ai/qodo-documentation/qodo-merge/tools/improve#configuration-options
• https://docs.qodo.ai/qodo-documentation/qodo-merge/usage-guide/automations_and_usage#github-app-automatic-tools-for-push-actions-commits-to-an-open-pr
• https://docs.qodo.ai/qodo-documentation/qodo-merge/core-abilities/incremental_update#overview
• https://docs.qodo.ai/qodo-documentation/qodo-merge/tools/improve#suggestion-tracking
• https://docs.qodo.ai/qodo-documentation/qodo-merge/core-abilities/impact_evaluation#auto-impact-validator---real-time-tracking-of-implemented-qodo-merge-suggestions

[dbudwin]

I am using the open source PR-Agent on GitHub via GitHub Actions.