freeze

To restrict edits during debugging, set a freeze boundary that validates file paths and blocks modifications outside the allowed folder. This prevents accidental changes in other modules and maintains code integrity.

Directory containment restricts file modifications to a single folder, needed when isolating work to a module during debugging, experimentation, or code review to prevent unintended changes elsewhere in the codebase.

Yes, you can lock edits to one folder with a boundary that persists across multiple tool invocations within the same session. The boundary is set per session and continuously validates file paths to allow or deny edits.

The best way to prevent accidental code changes is to apply directory containment by setting a freeze boundary. This ensures edits are restricted to a specific directory for the duration of your working session.

A session boundary for file editing persists across tool invocations within that session. You set the freeze boundary to a specific directory, and it remains active to validate file paths and deny edits outside that path.

You should use directory containment instead of manual checks because it automatically validates file paths against a stored freeze boundary to allow or deny edits. This removes human error and reliably prevents accidental changes during debugging.