freeze

To restrict file edits to a specific directory, you can apply a freeze boundary that blocks Write and Edit operations outside the allowed path. This ensures changes are isolated to the configured directory for the duration of the session.

A PreToolUse hook for blocking repository changes is a mechanism that reads and enforces a persistent freeze boundary stored in the session state. It exposes a deny response to automatically block any out-of-bound edits.

Yes, you can lock down a folder to isolate module changes while debugging by setting a defined directory as the freeze boundary. This prevents accidental modifications to other parts of the repository during the session.

To start restricting edits, provide a directory path to set the freeze boundary. This immediately starts limiting Write and Edit operations to that specific directory throughout your current working session.

Yes, the freeze boundary maintains session persistence, meaning the restrictions remain active for the duration of the session. It continuously reads the hook and reports when a change is denied.