unfreeze

Clears the freeze boundary state file to allow edits in all directories again.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill unfreeze-sanjanb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/gstack-unfreeze
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill unfreeze-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After using /freeze to restrict an AI agent's edit scope to a specific directory, you may need to widen that scope without ending the session. This Skill removes the freeze boundary so edits are permitted everywhere again. ## Core Features & Use Cases - Boundary Removal: Deletes the freeze-dir.txt state file that enforces directory-scoped edit restrictions. - Session Continuity: Widens edit scope without restarting the agent session or losing context. - Use Case: You froze edits to the src/ directory while refactoring, finished the task, and now want the agent to modify tests and docs elsewhere. Run /unfreeze to restore full edit access, then re-freeze later if needed. ## Quick Start Ask the agent to unfreeze and allow edits to all directories 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 a directory edit freeze in an AI agent session?

Run the /unfreeze command, which deletes the freeze-dir.txt state file from the gstack state directory. Once removed, edits are allowed in all directories without ending the session.

What is the difference between /freeze and /unfreeze?

/freeze sets a boundary restricting edits to a specific directory by writing a state file, while /unfreeze deletes that state file to restore edit access everywhere. They are complementary commands for scoping agent edits.

Does unfreeze disable the freeze hooks for the session?

No, the /freeze hooks remain registered for the session after unfreezing. They simply allow all edits because the freeze-dir.txt state file no longer exists, and you can re-freeze by running /freeze again.

What happens if I run unfreeze when no freeze is set?

The command checks for the freeze-dir.txt file first and reports that no freeze boundary was set. It makes no changes and exits safely without errors.