{"version":"2.1.269","anchor":"edit-tool-always-allow-rules-get-provenance-tracking-for-h","canonical_anchor":"edit-tool-always-allow-rules-get-provenance-tracking-for-h","heading":"Edit-tool 'always allow' rules get provenance tracking for host-dialog-originated approvals","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/edit-tool-always-allow-rules-get-provenance-tracking-for-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Edit-tool 'always allow' rules get provenance tracking for host-dialog-originated approvals\n\nEdit tool's 'always allow' rules now track when they came from a host permission dialog\n\n**What**\n\nClaude Code now keeps a per-session record of rule text added for the Edit tool's session-scoped \"always allow\" behavior, via a tracked set called `editRuleContents`. A new helper checks whether a given permission rule matches one of these tracked entries, and if so, reports that the rule's origin ('provenance') was a `host_dialog`, meaning it came from a host application's permission dialog rather than another source.\n\n**Why**\n\nThis lets Claude Code distinguish permission rules granted through a host application's own dialog from rules created other ways, which is useful for understanding where an editing permission actually came from.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}