{"version":"2.1.257","anchor":"session-sandboxsettings-scan-now-also-protects-a-new-policy","canonical_anchor":"session-sandboxsettings-scan-now-also-protects-a-new-policy","heading":"Session sandbox\/settings scan now also protects a new policy-limits path pair","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/session-sandboxsettings-scan-now-also-protects-a-new-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Session sandbox\/settings scan now also protects a new policy-limits path pair\n\nTwo more policy-limits paths join the fixed set always treated as reach-relevant during settings scans.\n\nThe fixed set of paths always treated as reach-relevant during session sandbox\/settings scans now includes two additional `policy-limits.json` locations, returned by helper functions, alongside the existing set of `scheduled_tasks.json`, `launch.json`, `CLAUDE.md`, `daemon.json`, and `policy-limits.json`.\n\n- Area: Sandbox\n- Names: `policy-limits.json`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}