Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] [ultrareview] Free runs consumed on large-scope branch reviews with empty findings (2 sessions) [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56396•Fetched 2026-05-06 06:29:12
View on GitHub
Comments
3
Participants
3
Timeline
8
Reactions
0
Author
diek617diek617
Participants
diek617diek617github-actions[bot]github-actions[bot]yurukusayurukusa
Timeline (top)
labeled ×5commented ×3

Error Message

Same as #50029: silent skip on large-scope bundle (>100k LOC), free run consumed despite no review delivered. No error message, no findings, no agent activity logs visible from CLI. Refund both free runs. Plus: clearer error surfacing when bundle exceeds analyzable size limit. Same as #50029: silent skip on large-scope bundle (>100k LOC), free run consumed despite no review delivered. No error message, no findings, no agent activity logs visible from CLI. Refund both free runs. Plus: clearer error surfacing when bundle exceeds analyzable size limit.

Error Messages/Logs

Same as #50029: silent skip on large-scope bundle (>100k LOC), free run consumed despite no review delivered. No error message, no findings, no agent activity logs visible from CLI. Refund both free runs. Plus: clearer error surfacing when bundle exceeds analyzable size limit.

Root Cause

Root cause hypothesis

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Bug

Same failure mode as #50029 — /ultrareview consumed free runs on large-scope branch reviews, returned empty findings in ~25 seconds (vs expected 5-10 min).

Two sessions affected (Pro/Max plan, today 06.05.2026)

Session 1 — Atlas/CraftBot Dashboard repo

  • Branch: review-full-atlas (created at initial commit 350f0cd, no cherry-pick — branch HEAD is initial-commit, default branch main is HEAD)
  • Comparison: main against review-full-atlas
  • Scope: 601 files changed, +124344 / -618 LOC
  • Findings: []
  • Duration: ~25 seconds
  • Free run consumed: 1/3 → 2/3
  • Session ID: 019eDUpc3TgSyYQbeUXYKtJq

Session 2 — VerwaltBot repo

  • Branch: review-full-verwaltbot (cherry-picked 201 commits from initial commit 597544c onto branch)
  • Comparison: review-full-verwaltbot → main
  • Scope: 731 files changed, +131107 / -37 LOC
  • Findings: []
  • Duration: ~20 seconds
  • Free run consumed: 2/3 → 3/3
  • Session ID: session_013EXdL7Du2PQgMVEpDWvzQD

Root cause hypothesis

Same as #50029: silent skip on large-scope bundle (>100k LOC), free run consumed despite no review delivered. No error message, no findings, no agent activity logs visible from CLI.

Request

Refund both free runs. Plus: clearer error surfacing when bundle exceeds analyzable size limit.

Environment

  • Plan: Claude Pro/Max
  • Date: 2026-05-06
  • Two separate repositories, same failure mode

What Should Happen?

Bug

Same failure mode as #50029 — /ultrareview consumed free runs on large-scope branch reviews, returned empty findings in ~25 seconds (vs expected 5-10 min).

Two sessions affected (Pro/Max plan, today 06.05.2026)

Session 1 — Atlas/CraftBot Dashboard repo

  • Branch: review-full-atlas (created at initial commit 350f0cd, no cherry-pick — branch HEAD is initial-commit, default branch main is HEAD)
  • Comparison: main against review-full-atlas
  • Scope: 601 files changed, +124344 / -618 LOC
  • Findings: []
  • Duration: ~25 seconds
  • Free run consumed: 1/3 → 2/3
  • Session ID: 019eDUpc3TgSyYQbeUXYKtJq

Session 2 — VerwaltBot repo

  • Branch: review-full-verwaltbot (cherry-picked 201 commits from initial commit 597544c onto branch)
  • Comparison: review-full-verwaltbot → main
  • Scope: 731 files changed, +131107 / -37 LOC
  • Findings: []
  • Duration: ~20 seconds
  • Free run consumed: 2/3 → 3/3
  • Session ID: session_013EXdL7Du2PQgMVEpDWvzQD

Root cause hypothesis

Same as #50029: silent skip on large-scope bundle (>100k LOC), free run consumed despite no review delivered. No error message, no findings, no agent activity logs visible from CLI.

Request

Refund both free runs. Plus: clearer error surfacing when bundle exceeds analyzable size limit.

Environment

  • Plan: Claude Pro/Max
  • Date: 2026-05-06
  • Two separate repositories, same failure mode

Error Messages/Logs

Steps to Reproduce

Bug

Same failure mode as #50029 — /ultrareview consumed free runs on large-scope branch reviews, returned empty findings in ~25 seconds (vs expected 5-10 min).

Two sessions affected (Pro/Max plan, today 06.05.2026)

Session 1 — Atlas/CraftBot Dashboard repo

  • Branch: review-full-atlas (created at initial commit 350f0cd, no cherry-pick — branch HEAD is initial-commit, default branch main is HEAD)
  • Comparison: main against review-full-atlas
  • Scope: 601 files changed, +124344 / -618 LOC
  • Findings: []
  • Duration: ~25 seconds
  • Free run consumed: 1/3 → 2/3
  • Session ID: 019eDUpc3TgSyYQbeUXYKtJq

Session 2 — VerwaltBot repo

  • Branch: review-full-verwaltbot (cherry-picked 201 commits from initial commit 597544c onto branch)
  • Comparison: review-full-verwaltbot → main
  • Scope: 731 files changed, +131107 / -37 LOC
  • Findings: []
  • Duration: ~20 seconds
  • Free run consumed: 2/3 → 3/3
  • Session ID: session_013EXdL7Du2PQgMVEpDWvzQD

Root cause hypothesis

Same as #50029: silent skip on large-scope bundle (>100k LOC), free run consumed despite no review delivered. No error message, no findings, no agent activity logs visible from CLI.

Request

Refund both free runs. Plus: clearer error surfacing when bundle exceeds analyzable size limit.

Environment

  • Plan: Claude Pro/Max
  • Date: 2026-05-06
  • Two separate repositories, same failure mode

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.128

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Cursor

Additional Information

No response

extent analysis

TL;DR

The issue can be addressed by implementing a check for the analyzable size limit of the bundle before consuming a free run, and providing a clear error message when this limit is exceeded.

Guidance

  • Review the code for /ultrareview to identify where the silent skip on large-scope bundles is occurring and modify it to provide a clear error message when the bundle size limit is exceeded.
  • Consider adding a check at the beginning of the review process to determine if the bundle size is within the analyzable limit, and if not, return an error message without consuming a free run.
  • Investigate the root cause of the issue, which is suspected to be related to the bundle size exceeding 100k LOC, and adjust the size limit or the review process accordingly.
  • Refund the consumed free runs for the affected sessions as a temporary workaround.

Example

No code example can be provided without more information about the implementation of /ultrareview. However, a possible solution could involve adding a size check at the beginning of the review process:

if bundle_size > 100000:
    return "Error: Bundle size exceeds analyzable limit"

Notes

The provided information suggests that this issue is related to a known problem (#50029), and the root cause is suspected to be the same. However, without more information about the implementation of /ultrareview and the review process, it is difficult to provide a more specific solution.

Recommendation

Apply a workaround by adding a check for the bundle size limit and providing a clear error message when this limit is exceeded, as this will help prevent unnecessary consumption of free runs and provide a better user experience.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#chain error#conversation history#tool integration#LLM response

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] [ultrareview] Free runs consumed on large-scope branch reviews with empty findings (2 sessions) [3 comments, 3 participants]