freeze

To restrict file edits to a specific directory during debugging, you lock edits to a chosen folder to prevent drift. This blocks Edit and Write operations outside that boundary, ensuring changes remain scoped to a single feature folder.

Directory boundary enforcement is a safeguard mechanism that restricts file edits to a user-specified directory within a session. It compares requested file paths against a stored boundary to block unauthorized modifications elsewhere in the codebase.

You lock a codebase folder by setting a user-specified directory boundary. A pretool hook then enforces this boundary for subsequent operations, persisting the configuration in your data directory to prevent unintended changes elsewhere.

Yes, you can block Write operations outside a feature folder across large codebases. The safeguard uses a pretool hook to compare requested file paths against your stored boundary, ensuring changes remain strictly confined within your scoped directory.

You need to restrict edits to a single folder during a patch when you want to ensure all changes stay within a feature folder. This session-scoped safety prevents drift when debugging or coding across large codebases.