Source Intelligence

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

Slash commands unavailable in a cloud session explain how to continue locally

Use it now
Useful4 Signal0
Slash Commands

Commands blocked in cloud sessions now tell you the exact local command to run instead.

/teleport/session/remote-controlclaude --teleport
What

Commands that cannot run inside a cloud session now say why and give you the local command to run, instead of a generic refusal.

Details
  • Applies to /teleport, /session and /remote-control among others; for example /teleport returns text explaining that it pulls a cloud session into a terminal on your own machine, so it cannot run from inside this session, and gives claude --teleport <id>.
  • The tailored text requires a known remote session id from CLAUDE_CODE_REMOTE_SESSION_ID.
  • Without that id, the previous generic "/x isn't available in this environment." message is still used.
Evidence

pulls a cloud session into a terminal on your own machine

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 →