freeze

To restrict file edits to a specific directory during a debugging session, you define a boundary path and apply a session-scoped lock. This prevents accidental modifications to code outside that designated directory while you work.

Yes, you can lock writes to a directory without affecting read operations. The edit restriction enforces the boundary by denying Edit and Write operations outside the path, while Read commands remain unaffected.

The best way to prevent accidental code changes when performing scoped work is applying a directory-boundary lock. This restricts edits and writes to a user-specified directory, keeping the rest of the project untouched during the session.

You toggle directory edit restrictions on and off using the /freeze and /unfreeze commands. Running /freeze applies the boundary for the current session, while /unfreeze removes the restriction to restore full edit access.

The session-scoped edit boundary persists for the current session to support manual debugging or scoped work. It remains active until you explicitly toggle it off, ensuring your directory boundary is enforced throughout your tasks.

A limitation of restricting edits to a directory boundary is that the lock is session-scoped and applies only to Edit and Write operations. You must manually specify the boundary path and toggle it off when the debugging session ends.