freeze

Directory boundary enforcement blocks Edit and Write operations outside a selected folder using pre-tool validation hooks. It prevents accidental or unwanted edits to unrelated parts of a codebase during debugging, refactoring, or experimentation.

Yes, locking file changes to one folder is achieved by normalizing paths and persisting a freeze state. This ensures only files within the chosen module path are writable, while all other directories remain protected from modifications.

Preventing accidental edits outside a module requires scoped edit enforcement. By setting a freeze boundary on your target folder, any Edit or Write operations targeting files outside that directory are automatically blocked before execution.

Edit restriction works across an entire debugging session through session persistence. The freeze boundary is stored and maintained, so the directory restriction continues throughout the conversation rather than applying to a single command.

The best way to protect a production folder is to set a freeze boundary that blocks Edit and Write operations outside that directory. This safety-oriented workflow lets you troubleshoot and experiment while preventing collateral edits to critical areas.

Directory-scoped edit restrictions should not be used when your workflow requires modifying files across multiple folders or modules simultaneously. The freeze boundary blocks all Edit and Write operations outside the allowed path, which limits cross-directory refactoring.