freeze

Sandboxing file edits prevents accidental or unauthorized changes to files outside a designated project path. It enforces a boundary using a PreToolUse hook that denies out-of-bound Write and Edit operations for the current session.

You set up a sandbox by providing a target directory path to freeze. The session stores this boundary and applies it to tool inputs, actively preventing out-of-bound modifications while you debug or collaborate.

Yes, you can lock a directory boundary by specifying the allowed path. The enforced PreToolUse hook intercepts edit-control operations and denies any Write or Edit actions targeting files outside that defined boundary.

Restricting edits to a single directory works effectively for collaborative debugging by keeping changes focused on a specific module. It ensures that modifications remain confined to the designated boundary throughout the interactive session.

If you attempt to write to a file outside the frozen directory boundary, the PreToolUse hook denies the operation. This edit-control mechanism ensures no modifications occur beyond the user-specified path during the session.