skills.rest
Golnaz89
Golnaz89COMMUNITY
Explore all skills by this author →
Website𝕏@Golnaz89GitHub

session-recovery

Query the session_store database to identify interrupted Copilot CLI sessions.

Updated Jan 5, 2026
Search Tags:#workflow#cli#sqlite#resume#recovery#session#copilot
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill session-recovery-golnaz89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill session-recovery-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by crashes, network drops, or accidental window closures, leaving work in progress and checkpoints that need resuming.

Core Features & Use Cases

  • Query the session_store database to identify recently active sessions and capture the last checkpoint to understand where work stopped.
  • Filter out automated heartbeat/monitor sessions to keep the focus on human-driven work.
  • Inspect full session context (turns, checkpoints, touched files, and references) to safely resume tasks or complete pending work.
  • Use copilot --resume SESSION_ID to continue the interrupted session with preserved context.

Quick Start

List recent sessions and resume the interrupted work with copilot --resume 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?▼

To resume an interrupted Copilot CLI session, query the session_store database to locate recent human-initiated work, then use the command copilot --resume SESSION_ID to continue with preserved context.

How does session recovery handle automated heartbeat sessions?▼

Session recovery filters out automated heartbeat and monitor sessions by applying workflow logic within a defined time window, ensuring the focus remains strictly on human-initiated tasks.

Can I inspect full session context before resuming a Copilot CLI task?▼

Yes, you can retrieve full session context including turns, checkpoints, touched files, and references. This allows you to safely verify where work stopped before resuming the task.

Do I need a specific database connection to recover Copilot CLI sessions?▼

You need a read-only connection to the session_store database. This allows the tool to execute SQL queries and identify the most recent in-progress work without modifying the database.

What is the best way to find the last checkpoint after a Copilot CLI crash?▼

The best way to find the last checkpoint is to query the session_store database for recently active sessions. This captures the exact state where the work stopped due to the crash or network drop.

Related Skills

Explore More Software Engineering Skills→
usepowershellusepowershell
9

session-recovery

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

Community
Intermediate
lbouriezlbouriez

session-recovery

Query the session_store to identify interrupted Copilot CLI sessions and resume them.

Community
Intermediate
tamirdreshertamirdresher
41

session-recovery

Query SQLite session_store to recover and resume Copilot CLI sessions.

Community
Intermediate
zpointzpoint
40

debug-store

Debug vibe-seller store runtime via SQLite inspection, CDP proxy control, and unauthenticated API access.

Community
Advanced