{"version":"2.1.223","anchor":"slash-commands-unavailable-in-a-cloud-session-explain-how-to","canonical_anchor":"slash-commands-unavailable-in-a-cloud-session-explain-how-to","heading":"Slash commands unavailable in a cloud session explain how to continue locally","tier":"use","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/slash-commands-unavailable-in-a-cloud-session-explain-how-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Slash commands unavailable in a cloud session explain how to continue locally\n\nCommands blocked in cloud sessions now tell you the exact local command to run instead.\n\n**What**\n\nCommands that cannot run inside a cloud session now say why and give you the local command to run, instead of a generic refusal.\n\n**Details**\n\n- 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>`.\n- The tailored text requires a known remote session id from `CLAUDE_CODE_REMOTE_SESSION_ID`.\n- Without that id, the previous generic \"\/x isn't available in this environment.\" message is still used.\n\n**Evidence**\n\n`pulls a cloud session into a terminal on your own machine`\n\n- Area: Slash Commands\n- Names: `\/teleport`, `\/session`, `\/remote-control`, `claude --teleport`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}