[georgenijo]

Closes #85.

Built by the dogfood mesh (Sonnet worker); the in-mesh Opus reviewer returned request_changes with a sharp, correct catch (retry budget inferred from ReviewFeedback=="" loops unboundedly when notes are empty). Director applied the reviewer's suggested fix + a regression test, then merged. (#85's own auto-redispatch isn't on main yet to self-heal this — bootstrap.)

What

• MESH_REVIEW_RETRIES (default 2): on request_changes, the scheduler re-dispatches the same task with the reviewer's notes as feedback, on the existing branch, up to N times; only fails after exhausting retries (or on reject).
• Worker: branch-aware worktree re-allocation + review feedback injected into the prompt.
• Reviewer-caught fix: dedicated Record.Redispatched flag for first-dispatch detection (not feedback-emptiness) → budget always decrements. Regression test TestReviewRetriesExhaustedWithEmptyNotes.

Verification

gofmt clean · go build ./... · go vet ./... · go test ./internal/... green.

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes review-gate terminal behavior and task state machine (running→pending via Redispatch); bounded by tests but affects job success/failure and extra worker/review LLM spend.

Overview
Adds MESH_REVIEW_RETRIES (default 2, 0 = fail immediately) so a request_changes review no longer always fails the task. The scheduler can re-dispatch the same task up to N times with reviewer notes as ReviewFeedback, on the existing worker branch so prior commits accumulate.

Scheduler splits request_changes from reject: handleRequestChanges uses persisted RetriesLeft and Redispatched (not empty feedback) to bound retries, then task.Store.Redispatch moves running → pending. Worker checks out an existing branch via addWorktreeFromBranch and injects feedback into the prompt.

Includes config/coordinator wiring, TestLoadReviewRetriesKnob, and review-gate tests including a regression for empty reviewer notes (unbounded retry trap).

^{Reviewed by Cursor Bugbot for commit c5ed216. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_7b58c3bb-5fa0-4b26-ab80-a5195bee3794)

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 15 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: b9d1332e-0454-4dd2-86f0-b2e21c23e9be

📥 Commits

Reviewing files that changed from the base of the PR and between 9e63809 and c5ed216.

📒 Files selected for processing (8)

• internal/config/config.go
• internal/config/config_test.go
• internal/coordinator/coordinator.go
• internal/scheduler/review_gate_test.go
• internal/scheduler/scheduler.go
• internal/task/task.go
• internal/task/transition.go
• internal/worker/worker.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/85-redispatch

---

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.}