freeze

To restrict file edits to a specific directory during a coding session, you can apply a session-boundary using a PreToolUse hook with a Bash script. This blocks Edit and Write operations outside your defined folder while keeping Read tools unaffected.

Yes, you can lock edits to a single folder to prevent accidental changes by enforcing a directory boundary. This stateful boundary persists your target directory path to a local state file, ensuring the restriction remains active across all actions in your current session.

PreToolUse hooks block edits outside a project directory by running a Bash script before file modification tools execute. The script checks the target file path against your user-defined boundary and cancels any Edit or Write operation attempting to modify files outside that specified folder.

Restricting edits to a directory does not affect reading files outside the boundary. The enforcement mechanism specifically targets and blocks only Edit and Write operations, leaving Read and other non-modifying tools completely unaffected for safe debugging and code exploration.

You should use a session-boundary to confine edits to one folder during interactive debugging or coding sessions where you want to prevent accidental changes. It is ideal when exploring or modifying unfamiliar codebases where you need strict containment of file modifications.

You do not need any dependencies to set up a directory edit lock with a Bash hook. The boundary enforcement operates independently using a standard Bash script and a session-local state file, requiring no external packages or additional components to function.