{"version":"2.1.302","anchor":"resumecontinue-startup-errors-surface-cleanly","canonical_anchor":"resumecontinue-startup-errors-surface-cleanly","heading":"Errors when continuing or resuming a session now show their own message","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/resumecontinue-startup-errors-surface-cleanly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Errors when continuing or resuming a session now show their own message\n\nA specific error during `--continue` or `--resume` now prints its message and exits, including in `claude -p` print mode with exit code 1\n\n**What**\n\n`--continue` and `--resume` reopen an earlier conversation. When starting one of these fails with a particular kind of error, Claude Code now stops with that error's own message instead of a generic failure.\n\n- In the normal interactive mode, that error exits with its own message. Before, every failure was recorded as the same generic launch failure.\n\n- In print mode (`claude -p`), the error is printed and Claude Code exits with code 1. A failed resume of this kind is marked as aborted. Before, the error was logged and an empty conversation was returned.\n\n- A new check runs before the stored session is looked up.\n\n**Why**\n\nYou see why a resume failed. Scripts using `claude -p --continue` or `--resume` now get a non-zero exit code they can detect, instead of silently carrying on with an empty conversation.\n\n- Area: Sessions\n- Names: `--continue`, `--resume`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}