What problem does it solve?
Prevents accidental or unintended file modifications by restricting Edit and Write operations to a single, user-specified directory for the session, reducing the risk of touching unrelated code while debugging or making focused changes.
Core Features & Use Cases
- Session-scoped edit boundary: Ask the assistant to set a freeze directory and all Edit/Write tool calls outside that path are blocked.
- PreToolUse enforcement: A hook runs before Edit and Write tools to check the file_path and returns an explicit deny decision for out-of-bound paths.
- Persistent, reversible state: The freeze boundary is saved to a session state file and can be changed with /freeze or removed with /unfreeze; useful when debugging, performing focused refactors, or working in sensitive areas of a repository.
- Limitations: Read and non-Edit tools are unaffected and shell commands can still modify files outside the boundary, so this is a safety guard for tool-mediated edits rather than a full security sandbox.
Quick Start
Tell the assistant to freeze edits to /path/to/dir by providing the absolute path you want restricted for the session.