What probably matters to youSection of the release
The --bg/--background CLI flag's help text now documents that combining it with --resume <session-id> continues that session in the background under the same ID, or starts a copy and reports it when the session is already running, rather than only starting a fresh background session.
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.
Added sinceA small documentation edit on Common workflows touched a line naming --resume after this was published.| [`/loop`](/docs/en/scheduled-tasks) | The current CLI session | Quick polling while a session is open. `--resume` and `--continue` restore unexpired fixed-interval loops. |common-workflowssee the edit
Confirmed sinceAnthropic's documentation has since written up --resume, on Claude Code changelog.* Improved `--continue` / `--resume`: the conversation appears immediately instead of waiting for SessionStart hooks, and the first message no longer re-reads the whole transcriptchangelogsee 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 --resume, on Claude Code changelog.
Anthropic's release notes agreeFixed --resume listing a backgrounded conversation twice and --continue reopening its stalled pre-background copy; --continue now also opens…
