Running teleport inside a cloud session now tells you the exact local command to run instead of just failing.
What's wrong with this entry?
Running a teleport or remote-control command from inside a cloud session now returns a targeted explanation instead of failing opaquely.
- Applies to
/teleport, the session command and remote control. - The message includes the exact
claude --teleport <id>command to run locally. - Triggered when running as a remote session, detected via
CLAUDE_CODE_REMOTE_SESSION_ID.
/teleport pulls a cloud session into a terminal on your own machine, so it can't run from inside this 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.
-
v2.1.219
Teleport branch-mismatch error explains what the checkout actually is
Both mention teleport
-
v2.1.224
--teleportand--cloudshow up inclaude --helpBoth mention teleport
-
v2.1.229
/teleporthint mentions both directionsBoth mention teleport