{"version":"2.1.311","anchor":"auto-mode-permission-default-settingsneverforwarded-input","canonical_anchor":"auto-mode-permission-default-settingsneverforwarded-input","heading":"Permission mode choice takes account of settings that are never forwarded","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/auto-mode-permission-default-settingsneverforwarded-input","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Permission mode choice takes account of settings that are never forwarded\n\nThe logic that picks the starting permission mode now considers whether settings are never passed along, and treats that as false unless told otherwise\n\n**Unclear.** Which sessions set this input, and so which ones get a different default permission mode, is not stated.\n\n**What**\n\nClaude Code decides which permission mode a session starts in. A permission mode is the rule for whether Claude asks before it acts. That decision now considers one more input: whether settings are never passed along to the session. Unless something says otherwise, this input is treated as false.\n\n**Why**\n\nThis may change the default permission mode some remote sessions start in. A remote session is one that runs on another machine rather than your own.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}