freeze

To restrict file edits to a specific directory, you set a boundary path that persists in a state file, blocking Edit and Write operations outside that scope to prevent accidental changes.

Yes, you can continue reading files and running bash commands locally while write restrictions are enforced, allowing safe debugging without unintended cross-module edits.

Directory freezing implements a boundary check that resolves paths and denies outside edits by persisting the allowed region in a state file, logging usage locally for auditing.

The best way to lock edits to a single module folder is to freeze that directory path, applying a guardrail that blocks Edit and Write operations across the project outside that scope.

Directory freezing works across the entire project by blocking any Edit or Write operations outside the user-specified directory, preventing drift throughout the active session.

A limitation of the freeze guardrail is that it only restricts Edit and Write operations; it does not block reading files or running commands outside the specified directory boundary.