unfreeze

Clears the /freeze edit boundary to enable edits across all directories.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/kunalrawat425/conductor-playground --skill unfreeze-kunalrawat425
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/kunalrawat425/conductor-playground/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/kunalrawat425/conductor-playground --skill unfreeze-kunalrawat425

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a session restricts edits with a persistent freeze boundary, this Skill clears that boundary so you can modify any directory again without restarting the session.

Core Features & Use Cases

  • Clear the freeze boundary set by /freeze to restore full edit permissions.
  • Preserve session hooks while removing the restriction, enabling seamless continuation of work.
  • Use during collaborative sessions or iterative experimentation when you need to widen the scope of edits without restarting the session.

Quick Start

Run the unfreeze command to remove the edit restrictions and enable edits across all directories.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I remove edit restrictions in a frozen shell session?

You can unfreeze a workspace by clearing the edit boundary set by the freeze command. This action removes the restriction state file in the designated directory while preserving session hooks for seamless continuation.

What is a workspace edit boundary and when do I need to clear it?

A workspace edit boundary is a persistent restriction that limits modifications to specific directories during session-based workflows. You need to clear it when collaborating across multiple project folders or during iterative sandbox experiments.

Can I restore edit permissions in a session without restarting?

Yes, you can restore edit permissions without restarting by clearing the freeze state file in the designated state directory. This updates runtime behavior directly while preserving your active session hooks.

Does clearing the freeze boundary preserve my configured session hooks?

Yes, clearing the freeze boundary preserves your configured session hooks. The operation specifically targets and removes the freeze state file to update runtime behavior without disrupting the underlying session workflow.

Why does my session still restrict edits after modifying the freeze state file?

If your session still restricts edits, the freeze state file in the designated directory may not have been fully cleared. Unfreezing relies on successfully checking and removing this file to update runtime behavior.