{"version":"2.1.257","anchor":"agentsettings-permission-mode-widening-now-blocked-with-n","canonical_anchor":"agentsettings-permission-mode-widening-now-blocked-with-n","heading":"Agent\/settings permission-mode 'widening' now blocked with new telemetry","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/agentsettings-permission-mode-widening-now-blocked-with-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Agent\/settings permission-mode 'widening' now blocked with new telemetry\n\nAn agent definition's permissionMode can no longer widen the mode inherited from its parent context.\n\nPermission-mode resolution now detects when an agent's frontmatter `permissionMode` would widen the effective mode inherited from a parent or agent view, and ignores that widening instead of applying it. This closes a path where a repo-controlled agent definition could loosen permissions beyond what the parent context allowed. The event `tengu_agent_frontmatter_mode_widening_carry_ignored` is logged whenever this happens.\n\n- Area: Permissions\n- Names: `permissionMode`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}