{"version":"1.0.122","anchor":"sandbox-violation-filtering","canonical_anchor":"sandbox-violation-filtering","heading":"Sandbox Violation Filtering","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/1.0.122\/e\/sandbox-violation-filtering","release_url":"https:\/\/changelogs.core-directive.com\/v\/1.0.122","markdown":"### Sandbox Violation Filtering\n\n**What:** Configure which sandbox violations to ignore for specific commands or globally\n\n**How to use:**\n\n`\/\/ In settings file { \"sandbox\": { \"ignoreViolations\": { \"*\": [\"\/tmp\", \"\/dev\/null\"], \/\/ Ignore these paths for all commands \"npm install\": [\"\/private\/var\/folders\"], \/\/ Ignore for specific command \"python\": [\"\/Library\/Python\"] } } }` **Details:**\n\n- Reduces noise from expected\/harmless sandbox violations\n- Violations are now correlated with the specific command that triggered them\n- Commands are base64-encoded in sandbox logs for precise tracking\n- Each violation now includes the command, not just the filesystem path\n- **Evidence**: `Ec4 schema at line 370115`, `eR2() at line 370611`, `jc4() at line 370372`"}