Brief
Claude Code adds forking of remote-control sessions as background jobs
Claude Code v2.1.273 adds the ability to fork a session started with claude --remote-control or /remote-control from the Claude app, running the fork as a background session on your computer.
The release notes for Claude Code v2.1.273 list several changes. The most useful new capability for everyday work is the ability to fork a session started with claude --remote-control or /remote-control from the Claude app. The fork runs as a background session on your computer. This means you can branch off a remote-controlled session and continue working locally without interrupting the original session. The release also adds opt-in request headers for LLM gateways and a notification when an MCP server disconnects and reconnection gives up.
Our reading
Our reading is that this gives users a way to branch off a remote-controlled session and continue work locally without interrupting the original session.
What to do or watch
If you run sessions via claude --remote-control or /remote-control, update to v2.1.273 and try forking one to see whether the background fork behaves as you need. The release notes don't specify whether a fork stays tied to the original session or diverges from it, so watch how changes in the fork and the original interact.
Source details and supporting facts
Each line is stated by the page named above it.
Stated by github.com
- Added forking a session started with claude --remote-control or /remote-control from the Claude app; the fork runs as a background session on your computer.
- Added x-claude-code-request-class, x-claude-code-agent-type, x-claude-code-prev-tool-durations, x-claude-code-compaction and x-claude-code-context-compacted request headers for LLM gateways; opt in with CLAUDE_CODE_GATEWAY_HINT_HEADERS=1
- Added a notification when an MCP server disconnects mid-session and automatic reconnection gives up, pointing at /mcp
Sources
- Anthropic Claude Code release notes (GitHub)Text stored 15 September 2026
How this story was checked. Written from the 1 page listed above, stored 15 September 2026; claims checked against that stored text on 15 September 2026.
What that means
- 3 of 3 reported statements were confirmed against the page that carries them; the rest were removed rather than published.
- Figures in the text were required to appear in the stored source text: yes. Identifiers: yes.
- The check reads stored text only: no claim rests on a fresh look that did not happen.
- Where the reporting was silent, the text says so instead of filling the gap.