freeze

To restrict file edits to a specific directory, you can lock a workspace boundary using a per-session state file. This intercepts Edit and Write operations, ensuring all changes remain strictly within the frozen folder for that session.

Locking edits to a folder during debugging prevents accidental file modifications elsewhere in the project. By enforcing a runtime boundary on Write and Edit tools, you guarantee focused work stays entirely within the target module's directory.

Yes, you can enforce edit boundaries using a PreToolUse hook. The hook intercepts tool invocations at runtime, checking the requested file paths against a stored directory boundary to block any unauthorized Write or Edit operations.

The best way to prevent accidental writes outside a project folder is to establish a runtime boundary via a per-session state file. This approach automatically blocks any Edit or Write tool attempts targeting files outside the designated directory.

Yes, session-based edit locking applies to both file writing and editing operations. The enforcement mechanism specifically intercepts and validates both Write and Edit tool invocations against the frozen directory path stored in the session state.

You should not use a frozen directory boundary if your current work requires modifying files across multiple project folders simultaneously. The boundary strictly confines all Write and Edit operations to a single specified directory for the entire session duration.