What problem does it solve?
Prevents accidental or out-of-scope file edits by restricting Edit and Write operations to a single directory for the session, reducing risk during debugging, focused development, or code review.
Core Features & Use Cases
- Session-scoped edit boundary: Persistently records a freeze directory so all subsequent Edit/Write tool calls are checked against it.
- PreToolUse enforcement: A hook script validates file paths and returns a permissionDecision deny for operations outside the allowed path, blocking edits (not just warning).
- Practical uses: Limit changes to a single module while debugging, enforce a temporary code freeze during reviews, or allow contractors to modify only a subdirectory.
- Behavior notes: Read and Bash tools are unaffected by the freeze guard, and the hook uses path normalization and symlink resolution to avoid bypasses; this is a safety guard, not an absolute security boundary.
Quick Start
Set the freeze boundary to /project/src so that edits are only allowed inside that folder.