freeze

Restrict file edits by setting a designated directory as a freeze boundary, which blocks all Edit and Write operations outside that path to prevent accidental changes. This confinement helps focus debugging and protects project integrity.

Preventing accidental writes outside a specific folder is achieved by configuring a directory boundary that intercepts edit operations via a pretool hook. The hook reads the freeze directory from state and blocks unauthorized modifications while logging analytics.

You can reconfigure the allowed edit path during an active session by running the /freeze command to set a new directory boundary. Running the /unfreeze command clears the restriction entirely, allowing edits across the project again.

The freeze boundary safeguard blocks both modifications to existing files and the creation of new ones. It specifically intercepts and prevents any Edit and Write operations attempted outside the designated directory path.

You should not use a directory boundary to confine edits when your workflow requires modifying files across multiple project folders simultaneously. The restriction blocks all Write and Edit operations outside the single designated path, which will disrupt cross-directory tasks.