freeze

Restrict AI agent file edits to a specific directory by applying a PreToolUse hook that denies Edit and Write operations targeting paths outside your allowed scope, enforcing a safe boundary for debugging sessions.

Yes, you can block write operations while leaving read-only operations unaffected, as the edit blocking mechanism only intercepts and denies tool requests targeting paths outside the user-specified directory boundary.

Directory restriction enforces session guardrails by resolving requested paths and checking prefix inclusion with a normalized trailing-slash-safe rule, returning a deny decision if an edit targets files outside the frozen module.

Yes, edit blocking persists across multiple tool calls during a debugging session by saving the freeze boundary to a state file, ensuring every subsequent Edit or Write request is consistently checked against the allowed path.

The best way to lock down edits to a single module folder is to specify that exact directory path, which triggers a PreToolUse hook to block any file modifications attempting to target paths outside that boundary.

The edit guardrail denies tool requests targeting paths outside the allowed scope to prevent accidental modifications to unrelated files, resolving the requested path and returning a permissionDecision deny on boundary violations.