freeze

To restrict file edits to a specific directory, you need a per-session boundary that blocks Write and Edit operations outside the allowed path, preventing accidental changes during debugging or scoped module work.

Yes, you can lock edits to a single directory boundary by configuring a freeze-dir state and a pre-tool hook that checks each file_path against the boundary before allowing any modifications.

The best way to prevent accidental edits to unrelated files is enforcing a directory boundary that intercepts Edit and Write operations, isolating modifications to a chosen path for safe experimentation.

Restricting edits to a directory boundary requires no special dependencies, relying solely on a configured freeze-dir state and a pre-tool hook to verify file paths before applying changes.

You should use a directory boundary to block edits during interactive coding, debugging sessions, isolated refactors, or any scoped work on a single module where modifying unrelated files is a risk.

Edits are blocked outside the freeze directory because the pre-tool hook actively checks the file_path against the per-session boundary, preventing any Write or Edit operations beyond the specified path.