# Upgrade Guide — v0.24.34

<!-- bump: patch -->

## What Changed

**Session error nudge: automatic recovery from API errors.** When a session hits an API error (400 "Could not process image", rate limits, timeouts, network errors) and goes idle at the prompt, the session manager now detects the error in the terminal output and injects a nudge message to get the session working again.

Previously, API errors that caused Claude to stop and return to the idle prompt were invisible to the recovery system — it only analyzed the JSONL conversation log, which looked clean after such errors. The zombie detector would kill the session 15 minutes later with no recovery.

**How it works:**
1. SessionManager's monitor tick detects a session is newly idle at the prompt
2. Captures 30 lines of terminal output and checks for error patterns (API Error, invalid_request_error, rate_limit_error, timeouts, network errors)
3. If an error is found: injects "You hit an API error. Please continue your work — skip or work around the action that failed."
4. Resets the idle timer so the zombie detector doesn't kill immediately
5. Each session gets ONE nudge — if it goes idle again after the nudge, the normal 15-minute zombie kill proceeds

Also expanded crash-detector.ts error classification to include 400, 502, invalid_request_error, and overloaded_error as API error types.

## What to Tell Your User

- **Session error recovery**: "If your agent hits an API error mid-work (like an image it can't process), it will now automatically get nudged to continue instead of just stopping. Previously, those errors would leave the session dead at the prompt until the zombie detector cleaned it up 15 minutes later."

## Summary of New Capabilities

| Capability | How to Use |
|-----------|-----------|
| Session error nudge | Automatic — detects API errors in terminal output and nudges to continue |
| Expanded error classification | Automatic — 400, 502, overloaded errors now classified as API type |
