Skip to content

feat: DISMISS F# protocol (v1.2.0)#4

Merged
royosherove merged 1 commit into
mainfrom
feat/dismiss-protocol
May 10, 2026
Merged

feat: DISMISS F# protocol (v1.2.0)#4
royosherove merged 1 commit into
mainfrom
feat/dismiss-protocol

Conversation

@royosherove
Copy link
Copy Markdown
Member

Fixes the max-repeat review loop. Agent can now dismiss false positives.

How it works:

  1. Findings numbered: - **F1 Medium:** file:line — problem
  2. Agent replies: DISMISS F1: intentional design
  3. After 2 dismissals → auto-suppressed in future cycles
  4. All suppressed → passes as LGTM, push unblocked

14 new tests, all 413 green.

When the reviewer flags findings the agent disagrees with, the agent
can reply 'DISMISS F1: reason'. After 2 dismissals of the same finding,
it's suppressed in future review cycles within that session.

- Findings are numbered (F1, F2, ...) in review messages
- Agent told to use DISMISS F#: reason format
- DismissTracker in orchestrator stores dismissed findings
- filterSuppressed removes them before display
- If all findings suppressed, review auto-passes as LGTM
- 14 new unit tests for dismiss module
- All 413 tests green
@royosherove royosherove merged commit fb99b41 into main May 10, 2026
0 of 2 checks passed
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3c81c77ec5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread index.ts
Comment on lines +619 to +623
const filteredResult = orchestrator.applyDismissFiltering(outcome.senior.result);

// If dismiss filtering converted issues to LGTM, clear the issues state
if (filteredResult.isLgtm && !outcome.senior.result.isLgtm) {
orchestrator.clearIssuesAfterDismiss();
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Run architect review after dismiss-driven LGTM

When applyDismissFiltering flips a senior result from ISSUES_FOUND to LGTM, this path sends an LGTM message but outcome.architect is still absent because architect execution already happened (or was skipped) inside handleAgentEnd based on the unfiltered result. For multi-file git-based changes, that bypasses the intended architect cross-file check and can tell the agent it's safe to push without ever running it. This occurs whenever all remaining findings are suppressed via DISMISS F#.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant