You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Bug FixesKind: in v2.1.257,
Bug FixesSection of the release
When claude -p --continue finds no eligible session to resume but a matching session is currently running in the background, the CLI now emits a specific abort message instead of silently falling through. This case also logs a tengu_continue failure event.
Read from
Names in the bundleclaude -p --continue
Since it was published
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up claude -p --continue, on CLI reference.| `--continue`, `-c` | Load the most recent conversation in the current directory, including a [background session that has finished](/docs/en/sessions#resume-a-session); opening finished background sessions requires Claude Code v2.1.257 o…cli-referencesee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up claude -p --continue, on CLI reference.
Anthropic's release notes agreeFixed --resume listing a backgrounded conversation twice and --continue reopening its stalled pre-background copy; --continue now also opens…
