unfreeze

To remove the edit freeze boundary in a Claude code session, run the unfreeze command. This deletes the state file at $STATE_DIR/freeze-dir.txt, restoring unrestricted editing across all project directories without ending the session.

Yes, you can resume full directory edits after freezing files by running the unfreeze command. It clears the active freeze boundary and allows edits across all directories, which is useful for reorganizing files or resuming development.

No, running the unfreeze command does not permanently delete the freeze hooks. It only removes the current edit restriction by deleting the state file, while preserving the existing /freeze hooks so you can re-freeze directories when needed.

The freeze-dir.txt state file is used to enforce an edit restriction within a Claude code session. It is created by the /freeze command and limits edits to a subset of directories until it is deleted by the unfreeze command to allow full-project edits again.

You should unfreeze a project directory during a development session when you need to widen the scope of edits mid-session, such as reorganizing files or resuming development across all directories without ending the Claude code session.

To re-freeze directories after expanding the edit scope, use the existing /freeze command. The unfreeze command preserves the freeze hooks, allowing you to re-establish the edit boundary and limit edits to a subset of directories whenever necessary.