freeze

You can restrict file edits to a specific directory by setting a session boundary that logs and denies any Edit or Write operations outside the allowed path. This prevents accidental changes during development workflows.

A PreToolUse hook enforces edit boundaries by intercepting file modification tools before they execute, denying any Edit or Write operations that fall outside the user-specified allowed path during the current session.

Yes, you can adjust the per-session boundary with a command after initially restricting edits. This enables safer debugging and module isolation by allowing you to modify the target directory scope on the fly.

Yes, you need python3 and git installed as dependencies to enforce the edit boundary. The runtime state file and PreToolUse hook rely on these environments to deny edits outside the allowed directory.

Locking edits to a target folder during debugging prevents drift and accidental changes outside your scoped area. By enforcing a per-session boundary, you isolate modules and ensure only the intended directory is modified.

When an Edit or Write operation falls outside the allowed directory path, the PreToolUse hook denies the action and logs the attempt. This enforces the edit boundary and prevents unintended modifications to files outside the target folder.