13.0.0 (2026-06-12)
⚠ BREAKING CHANGES
- A relative bash path token now also matches absolute allowlist rules naming the same file, resolved against the effective directory after literal cd commands. A token under a config like
path: { "*": "ask", "/workspace/project/*": "allow" }moves fromasktoallow. Tokens after a non-literal cd (e.g. cd "$DIR") stay conservative and match only their literal form. - When Pi's working directory is known, a relative path input now also matches absolute allowlist rules naming the same file. A config like
path: { "*": "ask", "/workspace/project/*": "allow" }moves a relativesrc/App.jsxfromasktoallow. To keep tighter control, narrow the allowlist patterns or add an explicitpathdeny for the sensitive paths.
Features
- add alias-aware evaluateAnyValue (#393) (2b7d240)
- add cd-aware pathRuleCandidates to BashProgram (#393) (102a491)
- add path-policy value derivation (#393) (d34e57f)
- add resolvePathPolicy resolver method (#393) (8ec81da)
- match relative path inputs against absolute allowlists (#393) (6d0c564)
- normalize path inputs to cwd-aware policy values (#393) (3c2784f)
- resolve bash path tokens with cd-aware policy values (#393) (7bcdbe7)