{"version":"2.1.246","anchor":"edit-auto-mode-rules-as-a-document-in-your-editor","canonical_anchor":"edit-auto-mode-rules-as-a-document-in-your-editor","heading":"Edit auto mode rules as a document in your editor","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/edit-auto-mode-rules-as-a-document-in-your-editor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Edit auto mode rules as a document in your editor\n\nIn \/permissions Auto mode you can open the environment rules as a document and edit them in your editor.\n\n**What**\n\nThe Auto mode tab of `\/permissions` gains an \"Edit environment\" action that opens the environment rules as a document in your editor. When you save, the whole draft is re-checked against what the screen loaded and refused with \"The environment changed since this screen loaded\" if it moved underneath you. Lines starting with `### ` are treated as section headers, not rules, and cannot be added, edited or deleted through this flow.\n\n**Details**\n\n- The tab renders whenever auto mode is available to the session; it is hidden only when the session reports auto mode unavailable. No remote flag controls it.\n- All add, update, delete and toggle paths are now wrapped in a telemetry span named `auto_mode_rule_edit`, whose failure code comes from the underlying write error.\n- One branch is dead by construction: the toggle path computes its escape hatch as a function that always returns false, so switching off an empty section always refuses with \"An empty section cannot hold the off state\".\n\n**Evidence**\n\n`'### ' lines are environment section headers (structure, not entries) and cannot be written here.`\n\n- Area: Permissions\n- Names: `\/permissions`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}