Summary
Auto Review can get stuck retrying a model stream after the active account hits a usage limit, instead of automatically switching to another configured account/provider as Every Code is expected to do.
Evidence
During Auto Review of snapshot 67b0fba238182646a49d829433f3d7f56969876a for PR #344, the TUI showed the review aging/stale while the underlying agent continued retrying. The visible retry message was:
Auto-retrying… ([transport] failed to start stream: You've hit your usage limit. Try again in 1 hour 13 minutes.)
The run stayed attached to Auto Review long enough that it had to be manually cancelled. After cancellation, the durable row reconciled to completed with finding_count: 0, even though the progress log showed review findings and repair attempts.
Expected behavior
When the active account hits a temporary usage limit, Every Code should use its configured account switching/fallback behavior for Auto Review instead of repeatedly retrying the limited account.
Acceptance criteria
- Auto Review detects temporary usage-limit stream failures.
- Auto Review switches to another eligible configured account/provider when available.
- The TUI/ledger clearly records the account-switch/fallback outcome.
- Cancelling a stuck Auto Review does not erase discovered findings from the visible review history.
Related evidence: PR #344, snapshot 67b0fba, Auto Review agent ae5379e3-8f3b-432b-b718-6e2037015cad.
Summary
Auto Review can get stuck retrying a model stream after the active account hits a usage limit, instead of automatically switching to another configured account/provider as Every Code is expected to do.
Evidence
During Auto Review of snapshot
67b0fba238182646a49d829433f3d7f56969876afor PR #344, the TUI showed the review aging/stale while the underlying agent continued retrying. The visible retry message was:Auto-retrying… ([transport] failed to start stream: You've hit your usage limit. Try again in 1 hour 13 minutes.)The run stayed attached to Auto Review long enough that it had to be manually cancelled. After cancellation, the durable row reconciled to
completedwithfinding_count: 0, even though the progress log showed review findings and repair attempts.Expected behavior
When the active account hits a temporary usage limit, Every Code should use its configured account switching/fallback behavior for Auto Review instead of repeatedly retrying the limited account.
Acceptance criteria
Related evidence: PR #344, snapshot
67b0fba, Auto Review agentae5379e3-8f3b-432b-b718-6e2037015cad.