Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Cloud sessions started with a title rename themselves instead of auto-titling

Use it now
Useful3 Signal0
Cloud Sessions

Cloud sessions you start with --name keep that name instead of being overwritten by a generated title.

--name
What

A cloud session created with an explicit name keeps that name rather than having a generated title overwrite it.

Details
  • Session bootstrap emits a rename_session control request when a title is supplied, with a request id assembled as rename-session-<uuid>.
  • The remote attach path now passes both title and hasExplicitTitle in the teleport/cloud session options.
  • The automatic title-generation callback bails out when hasExplicitTitle is set, alongside the existing checks for initialPromptUuid, viewer-only sessions and attach-to-existing sessions.
  • The CLI --name value is now trimmed and sanitized before use rather than only .trim()ed.
Evidence

hasExplicitTitle, rename_session

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

Related

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

See this entry in the whole of v2.1.223 →