freeze

To restrict file edits to a single directory during a session, you can use a boundary enforcement tool that validates Edit and Write operations against a specified path and denies any modifications outside it.

A PreToolUse hook prevents accidental file changes by intercepting edit operations, reading a persistent state file for the allowed directory boundary, and actively denying any write actions targeting files outside that designated path.

Yes, you can lock down edits to a specific directory path to stay focused on debugging by setting a session boundary that persists across operations until explicitly deactivated or the session ends.

The best way to prevent accidental code drift outside a target directory is applying a session-wide edit boundary that restricts all write operations exclusively to the specified module path.

You can unfreeze or change the directory boundary by running a simple command like /unfreeze, which deactivates the current restriction and allows you to set a new path or resume unrestricted editing.

Yes, restricting edits to a directory boundary logs violations for analytics during the session, recording attempts to modify files outside the designated path while persisting the boundary state for the active session.