freeze

To restrict edits to a single directory during an interactive coding session, use a boundary enforcement tool that checks Write and Edit operations against a configured path and blocks writes outside the allowed directory.

The best way to prevent accidental file changes outside a project subfolder while debugging is to apply a session-scoped edit boundary that persists throughout the session and blocks write operations outside the allowed directory.

Yes, you can change or remove the directory edit boundary after it has been set by running boundary management commands like /freeze to change the target directory or /unfreeze to remove the restriction entirely.

No, the directory edit boundary does not persist across different debugging sessions because it is implemented as a session-scoped restriction that only persists for the current interactive coding session.

To set up an edit boundary for a project subfolder, initiate a prompt-based setup that asks which directory should be frozen, then run the /freeze command to apply the boundary for the session with minimal friction.

You should use directory edit boundaries during software development when running interactive coding sessions, debugging, or incremental experiments where changes must stay strictly within a specific project subfolder to prevent drift.