fix(review): bound oversized agentic retries

[777genius]

Summary

• skip the optional missing-exploration retry when the estimated prompt exceeds 24k tokens
• preserve one retry for normal-sized prompts and preserve strict audit semantics for every prompt size
• document the bounded retry policy and cover both optional and strict oversized cases

Production evidence

Draft PR 777genius/agent-teams-ai#252 reviewed 162 non-trivial files in 7 batches. Every approximately 44k-token batch was invoked twice solely because the first pass did not execute a read-only command. The retries usually added no exploration or findings and nearly doubled provider work. This policy would keep all seven first passes while avoiding all seven optional repeat invocations.

Verification

• npm test -- --runInBand (136 suites, 1590 tests passed, 2 skipped)
• npm run typecheck
• npx prettier --check README.md src/providers/codex.ts tests/unit/providers/codex-provider.test.ts
• npx eslint src/providers/codex.ts tests/unit/providers/codex-provider.test.ts (0 errors, 29 pre-existing warnings)
• npm run build:action
• git diff --check

[coderabbitai]

Warning

Review limit reached

@777genius, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 855e72fb-53de-4691-8f83-d7f5218e785e

📥 Commits

Reviewing files that changed from the base of the PR and between dc4016d and 866a431.

⛔ Files ignored due to path filters (2)

• dist/index.js is excluded by !**/dist/**
• dist/index.js.map is excluded by !**/dist/**, !**/*.map

📒 Files selected for processing (3)

• README.md
• __tests__/unit/providers/codex-provider.test.ts
• src/providers/codex.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/bound-agentic-audit-retries

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}