freeze

You can restrict file edits to a specific directory during a debugging session by setting a boundary using an absolute path. The system intercepts Edit and Write tool calls, blocking any file modifications that occur outside the designated scope.

Directory scoping constrains file modifications to a user-specified boundary, preventing accidental changes outside a module. It persists this boundary in a session state file and enforces the rule by intercepting subsequent Edit and Write invocations.

To lock edits to a workspace boundary for code review, provide the target directory's absolute path. The system persists this freeze boundary for the session, ensuring that all subsequent file modifications remain contained within the designated scope.

Yes, you can use directory isolation to block Write tool calls outside a project scope. By providing an absolute path, the system intercepts both Edit and Write operations, actively blocking any attempts to modify files outside the established boundary.

Yes, the edit freeze boundary persists across multiple tool invocations in a session. The system saves the user-provided absolute path in a session state file, ensuring the restriction applies to all subsequent Edit and Write calls until the session ends.

A limitation of using a session state file for workspace boundaries is that the restriction relies on the session's persistence. The freeze intercepts Edit and Write tool calls only within that specific session, requiring a new absolute path setup for future separate debugging workflows.