Live preview options in claude remote-control still unavailable

The claude remote-control options behave as before, and --enable-live-preview and --preview-port still report they are not available

Under the hood Internal Changes

JSON All of v2.1.309

Under the hoodTier: how much it should matter to you

1Useful: my rating, 1 to 5

0Signal: worth watching, 1 to 5

Remote ControlArea: what it touches

Internal ChangesKind: in v2.1.309, 22 Oct 26

Internal ChangesSection of the release

What

The part of Claude Code that reads the options given to claude remote-control was rebuilt, but it behaves the same as before. The options it accepts and its error messages have not changed, including --session-id and --continue.

--sandbox and --no-sandbox are still rejected.
--enable-live-preview and --preview-port still give the error "--enable-live-preview and --preview-port are not available in this build."

Why

Live preview is still switched off in this version of claude remote-control, so those two options cannot be used yet.

Read from

Names in the bundle--session-id--continue

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed the claude remote-control status line showing HEAD as the branch for a folder that is not in a git repository

See this entry in the whole of v2.1.309 →

The build it came inv2.1.309

22 Oct 2026 · 281 entries, this one is #246.

Use it now14
You'll notice167
Nothing to try yet16
Under the hood84

Either side of it

v2.1.308Older

Open the release →

Names in this entry

cliremote-control
Remote sessions now rebuild a stuck connection when heartbeats keep failing but data still flows.
cli--session-id
Use a specific session ID for the conversation (must be a valid UUID)
cli--continue
Load the most recent conversation in the current directory, including a background session that has finished; opening finished background sessions requires Claude Code v2.1.257 or later. Skips sessions created with claude -p or the Agent SDK, and sessions whose first prompt was /loop. claude -p --continue includes -p, SDK, and /loop sessions. Includes sessions that added this directory with /add-dir

Anthropic's note

Upstream's own release notes for v2.1.309 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed the claude remote-control status line showing HEAD as the branch for a folder that is not in a git repository

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

v2.1.229 remote-control --continue is documented as reattaching, not resuming
Both mention continue
v2.1.257 print --continue now reports when a background session blocks resume
Both mention continue
v2.1.288 Errors for conflicting cloud session options can name a different option
Both mention continue