{"version":"2.1.299","anchor":"sandbox-path-check-no-longer-special-cases-privatetmp-and","canonical_anchor":"sandbox-path-check-no-longer-special-cases-privatetmp-and","heading":"Sandbox path check drops two redundant \/private rules","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-path-check-no-longer-special-cases-privatetmp-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sandbox path check drops two redundant \/private rules\n\nClaude Code's sandbox path check no longer has separate rules for \/private\/tmp and \/private\/var paths, with the same result\n\n**What**\n\nThe sandbox checks whether a path was redirected somewhere else by a symlink, a file that points to another location. That check no longer has two separate rules for paths that already start with `\/private\/tmp\/` or `\/private\/var\/`. An earlier step in the same check already gives the same answer for these paths, so they are treated as before. The rules that link `\/tmp` and `\/var` to their `\/private` versions remain.\n\n**Why**\n\nThis check decides which paths count as redirected, which matters for security. Removing the duplicate rules leaves the result for these paths the same.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}