session-recovery

Resume interrupted Copilot CLI sessions by restoring last checkpoints from session_store.

3|5|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill session-recovery-ronniegeraghty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.squad/templates
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill session-recovery-ronniegeraghty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sql.

What problem does it solve?

This skill helps you locate and resume interrupted Copilot CLI sessions by querying the session_store to identify the last checkpoint and rehydrate work state.

Core Features & Use Cases

  • Session discovery: Detects interrupted sessions by scanning session_store.
  • Checkpoint restoration: Restores the last known checkpoint to resume work with minimal disruption.
  • Workflow continuity: Enables seamless continuation of tasks after a disruption in IDEs or terminals.

Quick Start

Resume your most recent Copilot CLI session that was interrupted to continue where you left off.

Frequently Asked Questions about session-recovery

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

FAQPage Schema
How do I resume an interrupted Copilot CLI session?▼

To resume an interrupted Copilot CLI session, this Skill queries the session_store to locate incomplete sessions, identifies the last checkpoint, and rehydrates the working directory and state for seamless continuation.

What's the best way to restore a Copilot CLI checkpoint after a terminal crash?▼

Restoring a Copilot CLI checkpoint after a crash involves scanning the session_store for interrupted sessions and rehydrating the most recent incomplete working state to minimize workflow disruption.

Does session recovery require a database dependency?▼

Yes, session recovery requires a SQL dependency because it queries the session_store database to detect interrupted sessions and identify their last known checkpoints for state restoration.

How does Copilot CLI session state rehydration work?▼

Copilot CLI session state rehydration works by finding the last checkpoint in the session_store and restoring the working directory and state, allowing you to continue exactly where the interruption occurred.

Can I recover terminal session state across different IDEs?▼

Yes, you can recover terminal session state across IDEs because this Skill ensures workflow continuity by rehydrating the Copilot CLI session state from the session_store after any disruption in your environment.

Why does my Copilot CLI session not resume automatically?▼

Your Copilot CLI session may not resume automatically because the session_store must be queried to find the last checkpoint and rehydrate the state, which this Skill handles to ensure seamless continuation.