freeze

You can restrict file edits to a specific directory by applying a directory lock that blocks Write and Edit operations outside the configured path. This enforcement persists for the session via a PreToolUse hook and boundary-check script.

Yes, the directory lock only constrains Edit and Write operations. Read, Bash, Glob, and Grep commands remain completely unaffected, allowing you to inspect files and run non-editing commands outside the boundary.

To prevent accidental changes when debugging a single module, set a freeze boundary around that target directory. This ensures all your edits stay strictly within the module's path, reducing accidental modifications to other code areas.

A PreToolUse hook enforces scoped changes by intercepting tool calls before they execute and running a boundary-check script. If an Edit or Write operation targets a path outside the allowed directory, the hook blocks the action for the session.

The best way to sandbox edits is to establish an edits-boundary that isolates Write and Edit actions to a target directory. This approach secures your modifications while maintaining full read access to the broader file system.

The primary limitation of a session-based directory lock is that the boundary enforcement is temporary and does not persist after the session ends. It also only restricts editing tools, meaning non-editing commands can still execute outside the target directory.