What problem does it solve?
Restrict file edits to a specific directory for the session. Blocks Edit and
Write outside the allowed path. Use when debugging to prevent accidentally
"fixing" unrelated code, or when you want to scope changes to one module.
Use when asked to "freeze", "restrict edits", "only edit this folder",
or "lock down edits". (gstack)
Core Features & Use Cases
- Freeze edits to a directory to lock editing scope and prevent accidental changes across modules.
- Enforce a boundary during debugging sessions to isolate changes to a target folder.
- PreToolUse integration via check-freeze.sh to validate edits against the boundary.
Quick Start
Ask the user which directory should be restricted for edits, then save that path and start enforcing the boundary.