Claude Code v2.1.315 · 30 Oct 2026
Hidden option marks a session that began as a copy of another
A hidden --session-began-as-copy option, sent by the server, stops --resume from continuing the copied session's last turn
Use it now Tier: how much it should matter to you
4 Useful: my rating, 1 to 5
4 Signal: worth watching, 1 to 5
Sessions Area: what it touches
New Features Kind: in v2.1.315, 30 Oct 26
What probably matters to you Section of the release
What
Claude Code has a new hidden command-line option, --session-began-as-copy, which the server sends. A value of 1 means the session began as a copy of another session. In print mode (running non-interactively and printing the result), --resume then:
does not continue the last turn of the session it was copied from
does not run a tool call that a hook (a user-defined script that runs at set points) put off in that session
It means the same as setting CLAUDE_CODE_SESSION_BEGAN_AS_COPY =1. The option is also on the list of options passed through alongside --attach-serve and --runner-declares.
Why
This is server-driven plumbing for copied or forked remote sessions. It is not a switch meant for people to set themselves.
What the documentation says
How sure we are
One source agrees One thing we can check says the same as this entry.
Anthropic's documentation agrees --resume on Claude Code changelog
See this entry in the whole of v2.1.315 →
30 Oct 2026 · 237 entries, this one is #15.
Use it now19 You'll notice112 Nothing to try yet19 Under the hood87
Open the release →
Names in this entry
cli --resume Resume a specific session by ID or name, or show an interactive picker to choose a session. In place of an ID, you can pass the absolute path to a session's .jsonl transcript file . The picker and name search include sessions that added this directory with /add-dir. When you pass a session ID, Claude Code searches the current project directory and its git worktrees, then every other project on this machine. Before v2.1.223, the ID search covered only the current project directory and its git worktrees. Background sessions appear in the picker marked with bg. Resuming one that is still running opens that session in this terminal through claude attach, and a prompt you pass on the command line goes to it as its next turn. Before v2.1.285, Claude Code refused and printed the claude attach command to run instead
env CLAUDE_CODE_SESSION_BEGAN_AS_COPY A hidden --session-began-as-copy option, sent by the server, stops --resume from continuing the copied session's last turn
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 14 of 237
Claude Code drops suspect CA certificates from NODE_EXTRA_CA_CERTS, with two opt-out…
Use it now Network Security
In v2.1.315 What probably matters to you release-page order
Next → · 16 of 237
Post-turn memory's smaller_pass gains a form setting
Use it now Memory