freeze

You can restrict file edits by freezing a specific directory using a PreToolUse hook that validates file paths against the allowed folder. This enforces a workspace boundary that denies any modifications outside the designated path.

Directory freezing locks edits to a single folder to prevent codebase drift. It uses a bash script to validate paths and a PreToolUse hook to block accidental modifications outside the allowed directory during complex refactors.

You lock edits to a single module by providing the absolute path of the target directory. The session enforces a workspace boundary using a PreToolUse hook that checks file paths and denies changes outside that module.

Yes, you can reconfigure the frozen directory boundary during a session. The boundary state persists to a per-user location, allowing you to quickly adjust the allowed path and maintain your workspace restrictions as needed.

Restricting edits to a workspace boundary requires no external dependencies. It leverages a simple bash script for path validation and a PreToolUse hook to enforce the allowed directory restrictions directly.

Use a folder freeze boundary during complex refactors or isolated module debugging. It prevents drift across the codebase by denying edits outside the frozen directory, ensuring changes remain contained within a single folder.