Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.302 ·

New guidance messages for terminals attached to remote or cloud sessions

/resume refuses in a terminal attached to a remote session, and cloud sessions get new hints to /exit and reopen with claude --resume or claude --cloud

Group of 2 You'll notice Improvements
JSON All of v2.1.302
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.302,
ImprovementsSection of the release

What

A terminal can be attached to a session that runs somewhere else, such as a remote or cloud session. Several messages for this situation are new or changed.

  • /resume now refuses when the terminal is attached to a remote session. It says it can't open this computer's conversations from there, and tells you to run /exit, then claude --resume in a shell. Before, it went straight to the session picker.
  • A failed resume that throws a particular kind of error now shows that error's message in the conversation instead of being logged as a failure.
  • A new hint tells you to run /exit, then claude --cloud <session-id> to open another cloud session, and says session IDs are listed at claude.ai/code.
  • A message now says a command was not run because the folder the server was started in is gone, and that retrying will not help.
  • A desktop_rc_refusal entry was added to the information sent with requests.

Why

In a terminal attached to a remote or cloud session, you now get a clear explanation and the exact next step instead of a picker that cannot help or an error that invites pointless retries.

Read from
Names in the bundle/resume/exitclaude --resume
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up /exit, on Error reference. * If a former teammate you resumed yourself with `claude --resume` got this refusal, nothing was sent. To end that session, run `/exit` at its prompt. errors see the edit
Confirmed since Anthropic's documentation has since written up /resume, on What's new. **Resume terminal sessions in the Desktop app**: type `/resume` in the Claude Code Desktop prompt box to pick up any session you started from the CLI, with the full conversation and context intact. whats-new/index see the edit
Confirmed since Anthropic's documentation has since written up claude --resume, on Desktop application. > While a conversation's Claude Code process is still running, don't run [`claude --resume`](/docs/en/cli-reference#cli-flags) for it on the remote machine. Claude Code doesn't stop you, and both processes then write to the same conversati… desktop see the edit
Added since A small documentation edit on Manage sessions touched a line naming claude --resume after this was published. * Default display name: interactive sessions you never name still get a default display name when they start. The default combines the working directory's name with a two-character suffix, for example `my-app-3f`, and identifies the sessio… sessions see the edit
Added since A small documentation edit on Manage sessions touched a line naming /resume after this was published. * Default display name: interactive sessions you never name still get a default display name when they start. The default combines the working directory's name with a two-character suffix, for example `my-app-3f`, and identifies the sessio… sessions see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesA small documentation edit on Manage sessions touched a line naming /resume after this was published.

See this entry in the whole of v2.1.302 →

Feedback