freeze

To restrict file edits to a specific directory during debugging, you need directory locking mechanisms that enforce edit boundaries by validating file paths against a configured freeze directory and blocking out-of-bounds write operations.

Yes, you can prevent accidental code modifications outside your module scope by applying pre-tool use hooks that validate file paths and block all write and edit operations targeting files outside your configured project component directory.

Directory locking does not affect read, bash, glob, and grep operations. Edit boundary enforcement specifically blocks Edit and Write tool operations targeting out-of-bounds files while leaving all other read and search operations unaffected.

The best way to lock file writes to a single project component is to configure scoped development workflows that use pre-tool use hooks to validate file paths against a user-specified freeze directory, preventing unintended modifications to unrelated code.

Yes, you need python3 installed in your environment to enforce edit boundaries, as the directory lock mechanism relies on python3 to validate file paths and block out-of-bounds edit and write operations during your development session.

You should use directory lock for scope control during module-specific refactoring, debugging workflows, or component-scoped development tasks where you need to ensure all file modifications are strictly limited to a single directory to prevent breaking unrelated project parts.