freeze

To restrict file edits to a specific directory during a debugging session, you can set a temporary boundary that denies any edits outside the defined path. This prevents accidental changes to unrelated code while you work.

A freeze boundary is a persistent session constraint that blocks edits outside a user-specified directory. It reads the defined path and denies modification requests to files outside that boundary to prevent accidental code changes.

To set up a directory boundary, specify the target directory path and activate the freeze command. This establishes a persistent lock for the session that confines all subsequent code edits to that specific directory.

Yes, you can reset the directory edit lock once your debugging session is finished by running a specific command. This removes the persistent freeze boundary and restores unconstrained editing capabilities across all directories.

Restricting edits to a single directory works as a standalone boundary check without requiring additional dependencies. It directly reads the freeze boundary and denies edits outside that path during code editing and debugging workflows.