unfreeze

Remove the active edit freeze by deleting the freeze state file.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/fray-cloud/coin --skill unfreeze-fray-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/fray-cloud/coin/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/fray-cloud/coin --skill unfreeze-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the edit freeze boundary introduced by /freeze, enabling edits across all directories within an active session.

Core Features & Use Cases

  • Lift the freeze to widen your editable scope without ending the session.
  • Restore full editing capability after a temporary restriction during a task.
  • Use in collaborative workflows where you need to adjust constraints mid-session.

Quick Start

Initiate the unfreeze operation to clear the boundary and allow edits everywhere in the current session.

Frequently Asked Questions about unfreeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove an edit freeze in a shell session without ending it?

To remove an edit freeze in a shell session, run a Bash workflow that checks the state file at STATE_DIR/freeze-dir.txt, deletes it if present, and reports the outcome, restoring full editing scope.

What is an edit freeze boundary and when do I need to clear it?

An edit freeze boundary restricts editing capabilities to a limited scope within an active session. You need to clear it when you must broaden your editing scope across all directories without terminating the current session.

Can I restore full editing capabilities mid-session after applying directory restrictions?

Yes, you can restore full editing capabilities mid-session by deleting the freeze state file. This lifts the temporary restriction and allows edits everywhere within the currently active session.

Does the unfreeze Bash workflow require any external dependencies to manage session state?

No, managing session state with this Bash workflow requires no external dependencies. It directly checks and deletes the state file at STATE_DIR/freeze-dir.txt to clear the boundary and report the outcome.

Why does my session still have restricted editing scope after the freeze file is deleted?

If editing scope remains restricted after the freeze file is deleted, the Bash workflow may have failed to locate the state file at STATE_DIR/freeze-dir.txt or reported an outcome indicating it was already absent.