Bridge worker processes are launched with a resume argument

Remote bridge worker processes now start with a resume argument derived from the session URL.

Under the hood Internal Changes

JSON All of v2.1.232

Under the hoodTier: how much it should matter to you

2Useful: my rating, 1 to 5

3Signal: worth watching, 1 to 5

SessionsArea: what it touches

Internal ChangesKind: in v2.1.232, 13 Aug 26

Internal ChangesSection of the release

What

The child process started for a remote-control bridge session is now passed a --resume= argument derived from the session's SDK URL, in addition to the existing --sdk-url, --session-id and --replay-user-messages flags.

Evidence

"--replay-user-messages"

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

The build it came inv2.1.232

13 Aug 2026 · 405 entries, this one is #378.

Either side of it

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--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
cli--sdk-url
Startup stats now note the input format, whether --sdk-url was passed, and an experiment flag.
cli--session-id
Use a specific session ID for the conversation (must be a valid UUID)
cli--replay-user-messages
Re-emit user messages from stdin back on stdout for acknowledgment. Requires --input-format stream-json and --output-format stream-json

Is this right?