{"version":"2.1.282","anchor":"desktop-code-tab-session-edit-allow-rules-on-claude-narrow","canonical_anchor":"desktop-code-tab-session-edit-allow-rules-on-claude-narrow","heading":"Desktop Code tab drops broad session permissions to edit the .claude folder","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/desktop-code-tab-session-edit-allow-rules-on-claude-narrow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Desktop Code tab drops broad session permissions to edit the .claude folder\n\nIn Desktop Code tab sessions, session-only permissions to edit the .claude folder are now dropped unless they cover a single skill\n\n**Unclear.** The exact condition Claude Code checks to decide that a session is a Desktop Code tab session is not known.\n\n**What**\n\nAn allow rule is a permission that lets Claude Code do something, such as edit files, without asking you each time. A session-scoped rule lasts only for the current session, meaning the current conversation.\n\nIn Claude Code sessions run from the Code tab of the Desktop app, Claude Code now discards session-scoped rules that allow editing inside the `.claude` folder unless the rule is narrowed to one single skill (a skill is a packaged set of instructions Claude can use). It writes a debug log message when it drops such a rule.\n\n**Why**\n\nA broad approval to edit anything in `.claude` is no longer accepted in these Desktop sessions. Only approvals limited to one skill's files are kept.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}