freeze

To restrict edits to a specific directory during a debugging session, you can apply a freeze boundary that persists per session and blocks noncompliant Edit and Write operations outside the allowed path.

A session boundary for directory edit restrictions is a persistent freeze mechanism that confines file modifications to a single folder, preventing accidental changes outside the allowed path until the boundary is deactivated.

You can prevent accidental file changes outside a specific folder by applying a freeze boundary that blocks noncompliant Edit and Write operations, ensuring changes remain scoped to the allowed directory.

Yes, you can unfreeze a directory and restore full editing access later by deactivating the freeze boundary that was applied to restrict edits during the session.

You need to lock edits to a single directory when isolating work to a module during debugging or code reviews, ensuring changes remain contained to a specific folder and avoiding broader unintended edits.

Yes, the freeze boundary blocks all noncompliant Write and Edit operations outside the allowed path, enforcing the directory restriction and preventing accidental modifications until the session boundary is unfrozen.