{"version":"2.1.299","anchor":"bridge-auto-mode-withheld-when-unavailable","canonical_anchor":"bridge-auto-mode-withheld-when-unavailable","heading":"Remote Control no longer gives auto mode to sessions that cannot use it","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/bridge-auto-mode-withheld-when-unavailable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Remote Control no longer gives auto mode to sessions that cannot use it\n\nWhen auto mode is unavailable, sessions started through Remote Control are no longer granted it\n\n**What**\n\nAuto mode lets Claude Code act without asking for permission on each step. When Remote Control starts a child session (a session launched from another one), it decides which mode that session gets. It now checks whether auto mode is available first. If it is not, the child session is not granted auto mode, and Claude Code records the reason as auto mode being unavailable.\n\nBefore, the only case where auto mode was held back was when another mode had already been chosen.\n\n**Why**\n\nThis stops a child session from being put into auto mode when auto mode cannot be used.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}