freeze

You can restrict file edits by setting a per-session freeze boundary that validates tool inputs and denies Write or Edit operations outside the specified folder. This confines work to a single directory and protects surrounding code from accidental modifications.

A freeze boundary is a per-session restriction that confines Write and Edit operations to a user-specified directory. It prevents scope creep by validating tool inputs at runtime and denying any modification attempts outside the defined folder boundary.

Yes, you can lock edits to a specific folder during pair programming by applying a per-session freeze boundary. This confines all Write and Edit operations to the chosen directory and prevents accidental modifications to other parts of the codebase.

To apply a freeze boundary, provide the target directory path and run the freeze command. This persists the boundary for the session and denies any Edit or Write operations attempted outside that directory during debugging.

The freeze boundary is enforced on a per-session basis. You provide the directory path to restrict edits to and run the freeze command to apply the boundary, which then validates tool inputs and denies unauthorized edits for that session.

Edit and Write operations are blocked when attempted outside the freeze boundary. The boundary validates tool inputs against the stored target directory at runtime and denies any modifications to files outside the specified folder.