gstack-freeze

To restrict file edits to a specific directory, you can freeze the session boundary to that path. This prevents accidental writes or modifications to any files located outside the defined directory scope.

Yes, you can prevent accidental code changes by freezing edits to the target module's directory. This enforces a strict boundary that blocks all write and edit operations on unrelated files for the current session.

Directory freezing works by recording the target path in the session state and applying a check to all Edit and Write tool inputs. Any file modification attempted outside this recorded directory is automatically blocked.

Yes, the directory freeze boundary persists for the session but can be adjusted or cleared as needed. You can update the allowed path or remove the restriction entirely once your focused module work is complete.

The best way to scope edits is to set a freeze boundary pointing to your chosen project folder. This locks all write operations to that specific directory, ensuring no unintended changes occur elsewhere in your workspace.