Commands blocked in cloud sessions now tell you the exact local command to run instead.
What's wrong with this entry?
Commands that cannot run inside a cloud session now say why and give you the local command to run, instead of a generic refusal.
- 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.
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.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command