freeze

To restrict edits to a single directory during a development session, you set a designated folder boundary that blocks Edit and Write actions outside that path. This prevents accidental changes to unrelated modules during focused debugging.

An edit boundary prevents accidental file modifications during debugging by enforcing a user-provided directory path via PreToolUse hooks. These hooks intercept Write and Edit actions, blocking any attempts to modify files outside the designated scoped folder.

Yes, you can lock writes to a specific folder path to maintain workflow focus. The lock persists the selected directory boundary within the session state, ensuring all subsequent edits remain confined to your chosen scope.

The best way to prevent accidental edits outside a designated project directory is to apply session-level workflow controls that enforce an editable boundary. This guides you through selecting a freeze directory and actively blocks external modifications.

No, you do not need to manually set the directory restriction every time you edit a file. Once you invoke the freeze command with a chosen directory, the boundary persists in the session state and automatically enforces restrictions for all subsequent actions.

A limitation of scoping edits to a single directory is that the boundary strictly restricts all Write and Edit tool actions to that specific path. You cannot modify files in parent or sibling directories without changing the persisted session boundary.