{"version":"2.1.286","anchor":"session-mode-resolution-takes-the-call-context-into-account","canonical_anchor":"session-mode-resolution-takes-the-call-context-into-account","heading":"Unattended runs are stricter about which permission mode they use","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/session-mode-resolution-takes-the-call-context-into-account","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Unattended runs are stricter about which permission mode they use\n\nFor unattended runs, Claude Code keeps a session's permission mode only in certain cases and otherwise uses the default\n\n**Unclear.** What calls this check, and so which runs are affected, is not known.\n\n**What**\n\nA permission mode sets how freely Claude may act without asking you. When Claude Code works out which permission mode applies, it now considers how it was called and whether the run is unattended. It keeps the session's own mode only when the session recorded that mode itself, or when the mode was passed in and the host application decided it. In every other case it uses the default mode. Previously any recognised mode was used.\n\n**Why**\n\nThis can change the permission mode that unattended runs actually get.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}