[BUG] /ultrareview crashes at Dedupe step after successful Verify — findings unrecoverable

Resolved 💬 3 comments Opened May 3, 2026 by romain-rossi Closed May 3, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

/ultrareview runs to completion through Setup, Find, and Verify phases (10 candidates confirmed, 4 refuted), then crashes at the Dedupe step. The CLI surfaces an "API rate limit" error and the only output returned to the session is:

<remote-review>{"error":"Review crashed before producing findings. See session logs for details."}</remote-review>

The web session UI shows the 10 confirmed finding titles (with file paths) but the underlying analysis (reasoning, diffs, suggested fixes) is not accessible — clicking a finding does not expand it. The free credit (1 of 3) appears to have been consumed despite no actionable output being delivered.

What Should Happen?

  • Either Dedupe completes and returns the 10 confirmed findings with full details to the CLI session
  • Or, if a transient infra/rate-limit issue prevents Dedupe from finishing, the run should not consume a free credit and the partial findings (already produced by the Verify step) should remain accessible from the session web UI

Error Messages/Logs

● Remote review completed
  ⎿  API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited

<remote-review>{"error":"Review crashed before producing findings. See session logs for details."}</remote-review>

Web session pipeline state:

  • Setup: green
  • Find 14 candidates: green
  • Verify 10 confirmed · 4 refuted: green
  • Dedupe 10 issues: red (failed)

Session ID and URL: available privately on request — the affected branch contains pre-disclosure findings on a production service, so I'd rather share the identifier through a non-public channel (please indicate where to send it).

Steps to Reproduce

  1. From a local repo with a long-lived feature branch ahead of master by ~255 files / ~13.7k insertions / ~8k deletions (Spring Boot 4 + Java 25 codebase)
  2. Run /ultrareview (no arguments — uses local branch bundle)
  3. CLI confirms: Free ultrareview 1 of 3. Ultrareview launched for <feature-branch> → master (~5-10 min, runs in the cloud).
  4. Wait for completion
  5. CLI returns rate limit error and the <remote-review>{"error":...} payload; web session shows Dedupe step in red

Claude Model

Opus

Is this a regression?

I don't know

Claude Code Version

2.1.126 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

  • Free credit accounting: please confirm this run does not count toward the 3-free quota since no findings were delivered
  • Recovery: is it possible to retrieve the 10 verified findings server-side (they were produced by the Verify step before the Dedupe crash)?
  • Rate limit at Dedupe: appears to be the proximate cause — possibly the orchestrator hits a per-account API limit when fanning out the dedup pass on a large finding set

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗