{"version":"2.1.300","anchor":"teleport-and-remote-env-become-available-to-console-profil","canonical_anchor":"autofix-pr-slash-command-now-available-to-console-profile-au","heading":"\/teleport, \/remote-env and autofix-pr open to Console-profile sign-ins","tier":"use","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/teleport-and-remote-env-become-available-to-console-profil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### \/teleport, \/remote-env and autofix-pr open to Console-profile sign-ins\n\nCommands that were limited to claude.ai sign-ins, including `\/teleport`, `\/remote-env` and `autofix-pr`, now also allow Console-profile sign-ins\n\n**Unclear.** Which accounts count as a Console profile login is not shown.\n\n**What**\n\nClaude Code can be signed in through claude.ai or through a Console profile. Some commands were limited to claude.ai sign-ins and are now listed for both:\n\n- `\/teleport` and `\/remote-env` changed `availability` from `[\"claude-ai\"]` to `[\"claude-ai\", \"console-profile\"]`. Their `isEnabled` check now passes for either kind of sign-in instead of claude.ai alone.\n\n- The `allow_remote_sessions` check uses the same wider test.\n\n- The `autofix-pr` command also changed `availability` to `[\"claude-ai\", \"console-profile\"]`. It still has its own `isEnabled` check, and what that check allows was not traced.\n\n**Why**\n\nIf you sign in with a Console profile, you may now see these commands. `\/teleport` and `\/remote-env` let you move sessions to and from the cloud (Claude Code running on a remote machine) and choose a cloud environment.\n\n- Area: Cloud Sessions\n- Names: `\/teleport`, `\/remote-env`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}