freeze

Run the freeze command and provide the target directory path when prompted. The skill saves the absolute path to a state file, and a PreToolUse hook then blocks every Edit or Write operation targeting files outside that directory.

Freeze edits to the module you are investigating so the agent cannot modify unrelated code. The boundary persists for the whole session and can be changed by running freeze again or removed with the unfreeze command.

No, the freeze boundary only applies to Edit and Write tool operations. Read, Bash, Glob, and Grep are unaffected, so shell commands like sed can still modify files outside the boundary. It prevents accidental edits, not a security boundary.

The skill appends a trailing slash to the freeze directory before comparison, so the prefix check only matches true descendants of the frozen path. This prevents sibling directories with similar names from being incorrectly included.

Run the unfreeze command or simply end the conversation session. The freeze state is stored in a session-scoped state file, so it does not persist beyond the current session.