freeze

To lock edits to a directory, you apply an edit boundary that blocks Edit and Write operations outside the allowed path, preventing accidental modifications to unrelated code during interactive debugging.

Directory-boundary edit restriction is a mechanism that confines file modifications to a single user-specified path, ensuring changes remain scoped to one module and reducing the risk of unintended changes.

You can prevent Write and Edit operations outside a target path by using a pretool hook to transparently enforce a boundary file, checking every edit request against the allowed directory.

Yes, the edit restriction works transparently with pre-tool hooks to enforce the directory boundary, blocking any attempts to modify files outside the defined safe zone during the session.

The limitation of scoping edits to a single directory is that the boundary relies on a stored file at ~/.gstack/freeze-dir.txt, meaning the restriction is confined to the active session and a single allowed path.