freeze

You can restrict file edits by setting a per-session directory boundary that blocks Edit and Write operations outside the allowed path. This prevents accidental modifications to other modules during focused work.

Directory boundary enforcement confines file edits to a target folder by persisting the allowed absolute path to a state file and using a pre-tool hook to block write operations outside that boundary.

To lock changes to a single module, specify the target directory to restrict edits to for the session. The boundary is resolved to an absolute path and persisted, keeping debugging work scoped.

Yes, you can prevent accidental modifications by enabling a boundary that blocks edit and write operations outside a specified directory. This keeps session work confined to the allowed path.

The edit restriction boundary persists across the entire session by saving the allowed directory path to a state file. The pre-tool hook references this file to block outside edits continuously.

Use a directory boundary when debugging or doing focused development to lock changes to a single module. This prevents unintended modifications to other parts of the filesystem during the session.