CyberSecurityUPandClaude Opus 5 d2ec0a112d fix(models): treat subscription session/usage-limit stdout as exhaustion ...

Subscription CLIs (claude) report a hit session limit as ordinary stdout with a
ZERO exit code — 'You've hit your session limit · resets …'. Left as Ok it
became a 'response' each agent then failed to parse, and the run burned every
remaining agent against a dead session instead of pausing. Now the sentinel is
caught (length-guarded so a real finding mentioning 'rate limit' is not misread)
and surfaced as exhaustion, so the pool parks the run for /continue — the
pause-on-quota path that already existed but this case never reached.

Found during a live benchmark when run B collapsed to 0 findings mid-run.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-19 23:16:56 -03:00

..

harness

fix(models): treat subscription session/usage-limit stdout as exhaustion

2026-09-19 23:16:56 -03:00