freeze

You can restrict file edits during a debugging session by setting a persistent freeze boundary that blocks Edit and Write operations outside a designated directory. This confines changes and prevents accidental drift to other project files.

A session-boundary edit control is a safeguard that confines file modifications to a specific project directory. It implements a runtime boundary using a PreToolUse hook to deny write operations outside the allowed path.

Set up directory restriction by providing a directory path to freeze, which establishes a persistent boundary for the session. The system then actively blocks any Edit or Write operations attempted outside that frozen directory.

Yes, you can remove the directory freeze boundary after a debugging session by using the /unfreeze command. The freeze is persistent across the session but can be easily removed when isolation is no longer needed.

No, the directory restriction safeguard does not block direct Bash commands. It functions as a safety guard against accidental drift via Edit and Write operations, not as a strict security boundary for shell commands.