session-recovery

Query the SQLite session_store to restore interrupted Copilot CLI sessions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill session-recovery-carlossardo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill session-recovery-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find and resume interrupted Copilot CLI sessions using session_store queries.

Core Features & Use Cases

  • Find recent sessions and determine last checkpoint to resume work.
  • Filter out automated sessions to avoid noise.
  • Search by directory or topic to locate relevant sessions.
  • Get full session context before resuming and then resume with Copilot CLI.

Quick Start

Identify a recent interrupted session and run copilot --resume SESSION_ID to continue.

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?

You can resume an interrupted Copilot CLI session by querying the SQLite session_store database to find the session ID and its last checkpoint, then executing copilot --resume SESSION_ID in your terminal.

What is a session_store database and how does it track Copilot checkpoints?

The session_store is a SQLite database that tracks Copilot CLI sessions, checkpoints, and metadata. It records session states so you can search by directory or topic and retrieve the full context before resuming.

Can I filter out automated Copilot sessions when searching for my last checkpoint?

Yes, when querying the session_store database you can filter out automated sessions to avoid noise, allowing you to isolate interactive Copilot CLI sessions and accurately determine the last checkpoint to resume.

Do I need SQLite to recover a crashed Copilot terminal session?

Yes, recovering a crashed Copilot terminal session requires access to the SQLite session_store database and a sql tool to fetch session IDs, checkpoints, and metadata needed to restore and continue your work.

What's the best way to find a specific Copilot session by directory or topic?

The best way to find a specific Copilot session is to query the SQLite session_store database filtering by directory or topic, retrieving the full session context and last checkpoint before executing the resume command.