freeze

You can restrict file edits to a single directory by setting a boundary that blocks Edit and Write operations outside it. This prevents accidental changes while debugging or scoping work to one module.

Directory freezing locks edits to a chosen path for your session. Use it during debugging or when you need to scope changes to a single module, ensuring no unintended modifications occur outside the boundary.

To lock a directory boundary, you apply a freeze that reads the specified path from a state file. A hook then denies any Edit or Write operations attempted outside that directory during the session.

Yes, freezing directory edits blocks both Edit and Write operations. Once the boundary is set, a PreToolUse hook reads the freeze state and denies any file modification attempts outside the specified directory.

You can scope changes to a specific module by applying a directory freeze. This restricts the session so that all edits are confined to the chosen boundary, preventing modifications to files elsewhere.

The directory freeze relies on a state file to enforce the boundary. If the state file is missing or unreadable, the PreToolUse hook cannot validate the boundary, potentially allowing edits outside the intended scope.