freeze

To prevent accidental file edits outside a project directory, you can set a directory boundary that blocks Write and Edit actions. The boundary resolves your chosen path to an absolute directory and persists throughout the session.

A directory freeze boundary is a safeguard that restricts file modifications to a single allowed directory. It intercepts Edit and Write tool invocations to block changes to files outside the resolved absolute path.

You restrict edits to a sandbox directory by prompting the assistant to set a freeze boundary with your chosen path. The system resolves the path to an absolute directory, appends a trailing slash, and saves it to a state file for ongoing enforcement.

No, you do not need to manually reapply edit restrictions for every file write. Once you set the directory boundary, it persists across the entire session by saving the resolved absolute path to a state file for continuous enforcement.

Yes, you will be notified when a file change attempts to cross the directory boundary. The system provides a clear message whenever an Edit or Write operation targets a file outside the allowed directory during your session.

Yes, you can use directory boundaries to safeguard against unwanted changes in large codebases. By restricting edits to a specific absolute path, the system blocks accidental modifications to files outside that chosen folder during development workflows.