freeze

To restrict AI file edits to a specific directory, you apply a pre-tool hook that resolves file paths and denies Edit or Write operations outside a configured freeze boundary. This prevents unintended changes across your repository during debugging.

A tool hook for scoped refactoring is a pre-operation check that intercepts file modification commands. It enforces boundary checks by resolving target paths and blocking any edit operations outside an explicitly allowed directory scope.

Yes, you can read files outside the freeze directory. The safety guardrail specifically restricts Edit and Write operations, while read operations remain completely unrestricted across the entire repository.

You set up a session-persistent boundary for file edits by specifying an allowed directory path, which the system saves to a state file. The pre-tool hook reads this state file on each tool invocation to enforce the freeze.

The freeze scope persists throughout your session via a state file read on each tool invocation. You must explicitly manage the session boundary to remove the edit restrictions once your scoped refactoring or debugging workflow is complete.