freeze

To block edits outside a designated directory during interactive development, you can activate a session boundary that validates file paths from tool inputs in real time. This prevents accidental modifications to files outside your intended scope.

A session boundary for blocking file modifications is a runtime constraint that persists during development and validates edit attempts against an allowed directory path. It denies any tool input attempting to write files outside the configured boundary.

To activate a directory edit lock for debugging workflows, specify the target folder path and run the activation command to enable the boundary. The lock then persists for the current session and checks subsequent edits in real time.

Yes, you can confine code changes to a single folder without affecting other files by applying a runtime boundary that intercepts edit tool inputs. It validates the file path against the allowed directory and denies any edits outside that scope.

No, the edit boundary does not persist automatically across different sessions; it is applied for the current session only. You need to reactivate the directory lock each time you start a new interactive development or debugging workflow.