freeze

You can scope edits to a single module by setting a designated folder boundary that blocks Edit and Write operations outside the allowed path. This persists through the session and prevents accidental modifications to unrelated code while debugging.

Yes, locking writes to a designated folder only blocks Edit and Write operations outside the boundary. Read access remains fully available across the entire project, allowing you to reference other modules while keeping your modifications scoped safely to one directory.

Directory boundary enforcement works by storing a boundary file in the plugin state and using a PreToolUse hook to inspect file_path arguments. If a write operation targets a path outside the designated directory, the hook automatically denies the edit before it executes.

The best way to scope code changes is to establish a session-scoped directory boundary before you begin editing. This constrains all writes to your chosen module folder, preventing accidental modifications elsewhere in the project until you clear or update the boundary.

No manual hook configuration is needed because the boundary mechanism automatically uses a PreToolUse hook stored in the plugin state. You simply designate the target directory, and the system enforces the edit restriction by inspecting file paths during your session.

You should avoid directory-based edit restrictions when your task requires modifying files across multiple project folders simultaneously. Because the boundary blocks all Edit and Write operations outside a single designated path, cross-directory refactoring or multi-module updates will be denied.