Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Code CLI 10 Nov 2026
One change · claude-code

Continue local sessions from any device with Remote Control changedremote-control

Nearest release: v2.1.322, published 17 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 10 Nov 2026 19:12 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 10 Nov 2026 19:37 UTC.

Upstream edited
Recorded here
Lines+11added
Lines−0removed
From line 181 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits77to this page, all time

### Fork a session from your browser

The whole hunk

from line 181, old and new numbered
/
lines
from line 181
181181* **Effort level**: when you set the [effort level](https://code.claude.com/docs/en/model-config.md#adjust-effort-level) from a connected device, with `/effort` or the device's effort control, Claude Code applies it to the session on your machine. If you pinned a level with `CLAUDE_CODE_EFFORT_LEVEL`, the session keeps that level, and Claude Code refuses a different pick from the effort control. Picking a level from the effort control requires Claude Code v2.1.234 or later on your machine.
182182* **Reconnecting after a connection failure**: run `/remote-control` to reconnect. If compaction rewrote the conversation or you switched conversations with `/resume` in the meantime, Claude Code archives the server session it was using instead of leaving it in the session list. You can still find that session among your [archived sessions](https://code.claude.com/docs/en/claude-code-on-the-web.md#find-an-archived-session) at claude.ai/code. Switching conversations while a device is still connected doesn't archive the session.
183183 
184### Fork a session from your browser
185 
186To try a different direction without interrupting a session, open it at [claude.ai/code](https://claude.ai/code) and select **Fork** in the session's menu, or fork from an earlier message in the transcript. The fork opens as a new session in your session list and continues the conversation from that point while the original keeps running. Forking requires Claude Code v2.1.277 or later on your machine.
187 
188A `claude remote-control` server started with `--spawn session` has room only for its one session, so it can't run a fork.
189 
190Claude Code declines the fork in cases such as these:
191 
192* The session is busy. Fork when it's idle.
193* The session is hosted by the VS Code extension or another app built on the [Agent SDK](https://code.claude.com/docs/en/agent-sdk/overview.md).
194 
184195### Enable Remote Control for all sessions
185196 
186197Remote Control only activates when you explicitly run `claude remote-control`, `claude --remote-control`, or `/remote-control`, unless auto-connect is turned on. To turn auto-connect on for every interactive session, run `/config` inside Claude Code and set **Enable Remote Control for all sessions**. The toggle takes three values:
Feedback