freeze

You can restrict file edits by freezing a specific directory path to create a boundary. This enforces a directory-only edit restriction for the active session, blocking any Edit or Write operations targeting files outside the allowed folder.

A PreToolUse hook intercepts Edit and Write operations before execution, checking the target file path against a persisted frozen directory boundary. If the target falls outside the allowed absolute path, the hook blocks the operation to ensure safe scoping.

Yes, you can lock edits to a folder to safely scope changes during debugging. By freezing the target directory, the session enforces a strict boundary that prevents accidental modifications to files outside that specific project path.

The best way to sandbox file modifications is to freeze the module's directory path, which establishes a persistent edit boundary for the session. This restricts all file changes to the target folder, reducing the risk of introducing unrelated edits.

Yes, the process requires user input to specify the directory to freeze, which is then resolved to an absolute path. This resolved path is persisted as the boundary state to reliably block outside edits across session operations.