{"version":"2.1.296","anchor":"remote-session-create-can-carry-a-builtin-tool-restriction","canonical_anchor":"remote-session-create-can-carry-a-builtin-tool-restriction","heading":"Cloud session creation is prepared to limit built-in tools, but nothing is limited yet","tier":"soon","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/remote-session-create-can-carry-a-builtin-tool-restriction","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Cloud session creation is prepared to limit built-in tools, but nothing is limited yet\n\nCreating a session with --remote can now pass a built-in tool restriction, though in this version no restriction is ever sent\n\n**What**\n\nWhen you start a cloud session with `--remote` (a deprecated alias for `--cloud`), Claude Code can now pass a list of built-in tools to the new session, and it has a way to refuse when that restriction is rejected. Built-in tools are the actions Claude Code ships with, such as editing files or running commands. Before, only the list of disallowed tools was passed on.\n\nIn this version the value that would carry the restriction is always empty, so no built-in tools are actually limited.\n\nFailure reports for session creation also now note whether the session was archived.\n\n**Why**\n\nThis lays the ground for limiting built-in tools in cloud sessions. For now, cloud sessions behave as before.\n\n- Area: Cloud Sessions\n- Names: `--remote`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}