skills.rest
jperezdelreal
jperezdelrealCOMMUNITY
Explore all skills by this author →
GitHub

session-recovery

Find and resume interrupted Copilot CLI sessions from the session_store SQLite database.

Updated Apr 6, 2026
Search Tags:#workflow#cli#resume#recovery#copilot#session_store
One-click install
npx skills add https://github.com/jperezdelreal/GymBro --skill session-recovery-jperezdelreal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/jperezdelreal/GymBro/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill session-recovery-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by terminal crashes, network drops, or reboots, leaving work partially completed. This skill provides a reliable way to locate and resume those sessions using the session_store database.

Core Features & Use Cases

  • Find recent interrupted sessions from the session_store and identify the last active checkpoint.
  • Filter out automated or heartbeat sessions to focus on human-initiated work.
  • Resume a session by loading its ID into Copilot CLI to continue where it left off.

Quick Start

Identify the most recent interrupted Copilot CLI session from session_store and resume it using its session ID.

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 after a terminal crash?▼

To resume an interrupted Copilot CLI session after a terminal crash, you can query the session_store SQLite database to find the most recent human-initiated session, identify its last active checkpoint, and reload the corresponding session ID into the Copilot CLI.

How do I find recent session IDs in the session_store SQLite database?▼

You can find recent session IDs in the session_store SQLite database by querying it to locate interrupted Copilot CLI sessions, filtering out automated or heartbeat sessions to focus on human-initiated work, and identifying the last active checkpoint for recovery.

Does session recovery work for Copilot CLI sessions terminated by network outages or reboots?▼

Yes, session recovery works for Copilot CLI sessions terminated by network outages or reboots. It queries the session_store database to locate interrupted sessions and resumes them using the last active checkpoint's session ID.

How do I filter out automated or heartbeat sessions when querying the session_store?▼

To filter out automated or heartbeat sessions when querying the session_store, the recovery process specifically targets and isolates human-initiated work, allowing you to focus only on the actual interrupted Copilot CLI sessions.

What is needed to locate and resume an interrupted Copilot session?▼

To locate and resume an interrupted Copilot session, you need access to the local development environment, the Copilot CLI, and the session_store SQLite database to query sessions and identify the latest checkpoint for recovery.

Related Skills

Explore More Software Engineering Skills→
QuintenpsQuintenps

session-recovery

Query the session_store SQLite database to resume interrupted Copilot CLI sessions.

Community
Intermediate
furrycolombia-sysfurrycolombia-sys
1

resume-checkpoint

Loads saved checkpoint and restores Codex context for paused work on a branch.

Community
Intermediate
CommunityToolkitCommunityToolkit
619

session-recovery

Resumes interrupted Copilot CLI sessions by querying the session store.

Official
Intermediate
webmaxruwebmaxru
49

session-recovery

Resume interrupted Copilot CLI sessions from the session_store SQLite database.

Community
Intermediate