freeze

You can prevent accidental file edits by locking write operations to a specific directory. This enforces a strict boundary that blocks modifications to unrelated files while leaving read and search tools fully functional.

Yes, you can still read and search files outside the directory restriction. The edit lock specifically blocks edit and write operations, leaving read, search, and command tools fully functional for navigating the broader codebase.

You set an edit lock by asking the AI to restrict file modifications to your chosen directory for the current session. A pre-tool use hook then validates file paths against this boundary to deny operations outside the allowed scope.

Directory restriction works for both absolute and relative file paths. The pre-tool use hook resolves all path types and validates them against the configured boundary to ensure no file modifications occur outside the allowed scope.

The best way to isolate code changes is by applying a directory restriction that locks edits to a specific scope. This prevents accidental modifications to unrelated modules during scoped feature updates or focused debugging tasks.

Yes, you can update or remove the directory restriction at any time during your development session. Simple boundary management commands allow you to set, change, or clear the edit lock without requiring any complex configuration.