freeze

You can restrict file edits to a specific directory by setting a freeze boundary that blocks Edit and Write operations targeting paths outside the chosen folder. This keeps interactive debugging and scoped development safely contained.

Yes, you can lock code changes to one folder by applying a persistent freeze boundary. The PreToolUse hook checks file paths against this boundary, ensuring modifications stay contained within the designated directory scope.

To set a boundary, ask for the target directory and use the freeze command. This stores the directory path in a state file, establishing a persistent lock that remains active across the current session until explicitly removed.

The freeze boundary persists across the entire session by storing the scope in a state file. You must explicitly use the unfreeze command to change or remove the boundary when you need to modify files outside the originally designated directory.

A limitation of restricting edits to a single directory is that Write and Edit operations are blocked for any valid paths outside the frozen scope. You must explicitly remove the boundary via the unfreeze command before making changes elsewhere.