freeze

To restrict file edits to a specific directory during debugging, you provide the allowed folder path to lock the session. A PreToolUse hook then evaluates file paths and blocks any writes outside the declared boundary.

A PreToolUse hook prevents unintended changes by evaluating the file_path of every edit or write operation against a user-defined directory boundary. If the path falls outside the frozen directory, the hook blocks the action and logs an analytics violation.

Yes, you can lock edit boundaries for scoped workflows without dependencies. The feature operates independently by capturing your allowed path interactively and persisting the boundary directly within the session state.

The best way to prevent accidental writes outside a target directory is to freeze the session scope. This locks all edit and write operations exclusively to your declared path, ensuring debugging changes remain strictly bounded.

Your file edits are blocked because a session boundary restricts writes to a specific directory. When you attempt to modify files outside the frozen folder, the enforcement hook intercepts the action and prevents the change.

Yes, the freeze boundary persists across the entire debugging session. Once you provide the allowed directory path, the restriction is saved in the session state and continuously enforced by the hook until the session ends.