{"version":"2.1.321","anchor":"remote-control-slash-commands-unavailable-here-get-specific","canonical_anchor":"remote-control-slash-commands-unavailable-here-get-specific","heading":"Commands that cannot run in a remote session now say what to use instead","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-control-slash-commands-unavailable-here-get-specific","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Commands that cannot run in a remote session now say what to use instead\n\nIn some remote sessions, `\/model`, `\/effort`, `\/mcp`, `\/rename` and `\/reload-plugins` explain that they are unavailable and point to an alternative\n\n**What**\n\nSome slash commands cannot run when you control Claude Code from a remote place such as claude.ai or the mobile app. Each of these now has its own message saying so:\n\n- `\/model`\n\n- `\/effort`\n\n- `\/mcp`\n\n- `\/rename`\n\n- `\/reload-plugins`\n\nThe messages point to another way to do the same thing, such as the model picker or connectors on claude.ai. For example, `\/model` says: \"Changing the model by command isn't available here. Use the model picker instead. Not every session shows one.\"\n\n**Why**\n\nIn a claude.ai or mobile session you get a clear answer and a next step, instead of a command that seems to do nothing.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}