unfreeze

To resume edits in Claude Code after freezing the workspace, you need to clear the freeze boundary by removing the state marker. This restores full workspace write access across all directories so you can continue editing files.

If you clear the freeze boundary when no freeze is active, the system checks for the state file in the default directory. Since no boundary was set, it simply reports that no freeze boundary exists rather than throwing an error or modifying files.

Removing the freeze boundary to re-enable directory edits involves deleting the state file located in the default state directory. Once this freeze marker file is removed, full write access is restored across the entire workspace.

The freeze boundary state file is stored at a path defined by the state directory environment variable, defaulting to the user's home directory within a hidden configuration folder. The specific file is named freeze-dir.txt in this location.

You should clear the freeze boundary during development when you need to transition from a restricted, read-only state back to unrestricted editing. This is typically done when you are ready to apply changes across all project directories after a temporary freeze.

Yes, you can use this unfreeze command without any external dependencies or complex setup. It operates by directly checking and removing a local state file, making it a lightweight solution for managing workspace edit permissions during sessions.