What happened
Issue #187 identified that model: sonnet in .fullsend/harness/review.yaml resolved to unavailable claude-sonnet-4-6. The code agent created PR #188, pinning the model to claude-sonnet-4-5@20250929. This PR was merged after a human fixed the title. However, claude-sonnet-4-5@20250929 is also not provisioned on the repo's Vertex AI endpoint. PR #191 attempted to correct this to claude-sonnet-4@20250514 (the model the error message suggests), but the review agent failed immediately with zero tokens because it reads config from the base branch (which has the broken model). PR #191 was closed without merge. The review harness model on main remains claude-sonnet-4-5@20250929.
What could go better
The code agent's fix in PR #188 replaced one unavailable model with another unavailable model. The Vertex AI error message explicitly says to use claude-sonnet-4@20250514, but the retro agent that filed issue #187 recommended claude-sonnet-4-5@20250929 instead, and the code agent followed that recommendation without verification. Since PR #188 was merged, every review agent run on this repo has failed. PR #191's closure without merge means no fix has landed. High confidence — the error is reproducible and the current config is confirmed broken by the PR #191 review run.
Proposed change
Update .fullsend/harness/review.yaml to use model: claude-sonnet-4@20250514 (the model the Vertex AI error explicitly recommends). This is the same change PR #191 attempted. Since the review agent cannot review this change (chicken-and-egg — it reads model config from the base branch where the model is broken), the PR may need to bypass review or a maintainer can merge directly.
Validation criteria
After the model is updated, the next review agent run on any PR should complete successfully (non-zero tokens, review output produced) instead of failing with 'model not available'. Verify within the next PR opened on this repo.
Generated by retro agent from #191
What happened
Issue #187 identified that
model: sonnetin.fullsend/harness/review.yamlresolved to unavailableclaude-sonnet-4-6. The code agent created PR #188, pinning the model toclaude-sonnet-4-5@20250929. This PR was merged after a human fixed the title. However,claude-sonnet-4-5@20250929is also not provisioned on the repo's Vertex AI endpoint. PR #191 attempted to correct this toclaude-sonnet-4@20250514(the model the error message suggests), but the review agent failed immediately with zero tokens because it reads config from the base branch (which has the broken model). PR #191 was closed without merge. The review harness model onmainremainsclaude-sonnet-4-5@20250929.What could go better
The code agent's fix in PR #188 replaced one unavailable model with another unavailable model. The Vertex AI error message explicitly says to use
claude-sonnet-4@20250514, but the retro agent that filed issue #187 recommendedclaude-sonnet-4-5@20250929instead, and the code agent followed that recommendation without verification. Since PR #188 was merged, every review agent run on this repo has failed. PR #191's closure without merge means no fix has landed. High confidence — the error is reproducible and the current config is confirmed broken by the PR #191 review run.Proposed change
Update
.fullsend/harness/review.yamlto usemodel: claude-sonnet-4@20250514(the model the Vertex AI error explicitly recommends). This is the same change PR #191 attempted. Since the review agent cannot review this change (chicken-and-egg — it reads model config from the base branch where the model is broken), the PR may need to bypass review or a maintainer can merge directly.Validation criteria
After the model is updated, the next review agent run on any PR should complete successfully (non-zero tokens, review output produced) instead of failing with 'model not available'. Verify within the next PR opened on this repo.
Generated by retro agent from #191