skills.rest
webmaxru
webmaxruCOMMUNITY
Explore all skills by this author →
Website𝕏@webmaxruGitHub

session-recovery

Resume interrupted Copilot CLI sessions from the session_store SQLite database.

49|6|Updated Aug 24, 2021
Search Tags:#cli#sqlite#resume#recovery#session#copilot#session_store
One-click install
npx skills add https://github.com/webmaxru/bpm-counter --skill session-recovery-webmaxru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/webmaxru/bpm-counter/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/webmaxru/bpm-counter --skill session-recovery-webmaxru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by crashes, disconnections, or terminal closures, leaving work incomplete. This skill identifies and resumes those sessions using the session_store history to restore context and progress.

Core Features & Use Cases

  • Detect interrupted Copilot CLI sessions from the session_store database.
  • Retrieve the last checkpoint and session metadata to resume work without duplication or loss.
  • Apply across crashes, network drops, or closed terminals to maintain session continuity.

Quick Start

Resume the most recent interrupted Copilot CLI session using the session_store data.

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?▼

To resume an interrupted Copilot CLI session, this Skill queries the session_store SQLite database to locate the last checkpoint and restore your previous context and progress in one step.

Can I recover Copilot CLI session history after my terminal closed unexpectedly?▼

Yes, you can recover Copilot CLI session history after a terminal closure by retrieving stored session metadata and checkpoints from the session_store database to restore ongoing tasks.

Do I need access to the SQLite database to restore a Copilot session?▼

Yes, restoring a Copilot session requires access to the session_store SQLite database to execute SQL queries that identify and retrieve the last checkpoint and session context.

What's the best way to recover unfinished work from a disconnected Copilot CLI session?▼

The best way to recover unfinished work from a disconnected Copilot CLI session is querying the session_store history to detect the interruption and automatically resume the task without duplication or loss.

What types of session interruptions can be recovered using the session_store history?▼

Session_store history supports recovery across various interruptions including application crashes, network disconnections, and unexpected terminal closures to maintain session continuity and restore progress.

How does Copilot session recovery locate the last checkpoint for resuming work?▼

Copilot session recovery locates the last checkpoint by running SQL queries against the session_store SQLite database to extract session metadata and identify the exact state before the interruption.

Related Skills

Explore More Software Engineering Skills→
jonnymuirjonnymuir
1

session-recovery

Query the local SQLite session_store database to recover interrupted Copilot CLI sessions.

Community
Intermediate
CommunityToolkitCommunityToolkit
619

session-recovery

Resumes interrupted Copilot CLI sessions by querying the session store.

Official
Intermediate
WayneWalterBerryWayneWalterBerry

session-recovery

Query the session_store to locate interrupted Copilot CLI sessions and retrieve latest checkpoints.

Community
Intermediate
snow-jallensnow-jallen

session-recovery

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

Community
Advanced