session-recovery

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

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/rett-europe/opentreasury --skill session-recovery-rett-europe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/rett-europe/opentreasury/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/rett-europe/opentreasury --skill session-recovery-rett-europe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When Copilot CLI sessions are interrupted by a crash, network drop, or restart, this skill helps you locate the last active session and resume work from the most recent checkpoint.

Core Features & Use Cases

  • FindRecentSessions by querying the sessions table for recently updated sessions and attaching the last checkpoint.
  • FilterAutomatedSessions to exclude automated monitors or heartbeat-driven sessions that do not reflect user work.
  • GetFullSessionContext to inspect turns, checkpoints, touched files, and linked references before resuming.
  • ResumeSession with the Copilot CLI resume command to continue work from the identified checkpoint.

Quick Start

Identify the target session from recent results 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 after a crash?

You can recover a crashed Copilot CLI session by querying the session_store SQLite database to identify the interrupted session's ID and running copilot --resume SESSION_ID to continue from the last checkpoint.

What is the best way to find recent Copilot CLI sessions in the SQLite database?

Finding recent Copilot CLI sessions involves querying the sessions table in the session_store SQLite database for recently updated entries, which attaches the last saved checkpoint for quick review.

Can I filter out automated Copilot sessions when looking for my interrupted work?

Yes, you can filter automated Copilot sessions by excluding heartbeat-driven or automated monitor entries from the SQLite query results, ensuring you only locate sessions reflecting actual user work.

How do I inspect the full context of a Copilot session before resuming it?

You inspect the full context of a Copilot session by querying the session_store SQLite database to review previous turns, saved checkpoints, touched files, and linked references before executing the resume command.

Does session recovery work if the Copilot agent restarts due to a network drop?

Yes, session recovery works after a network drop or agent restart by using structured SQL queries to locate the interrupted Copilot CLI session in the session_store database and providing a resume flow from the most recent checkpoint.