session-recovery

Resumes interrupted Copilot CLI sessions by querying the session store.

619|188|Updated Jul 4, 2024

Search Tags:#session recovery #Copilot CLI #work resumption #CLI session #interrupted session

Ready to run

npx skills add https://github.com/CommunityToolkit/Aspire --skill session-recovery-communitytoolkit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/CommunityToolkit/Aspire/tree/main/examples/squad/CommunityToolkit.Aspire.Hosting.Squad.AppHost/dev-squad/.copilot/skills/session-recovery
Command: npx skills add https://github.com/CommunityToolkit/Aspire --skill session-recovery-communitytoolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you recover and resume interrupted Copilot CLI sessions, ensuring that your work is not lost and can be picked up right where you left off.

Core Features & Use Cases

Session Detection: Identifies and lists interrupted sessions from the session store.
Session Filtering: Filters out automated sessions to focus on human-generated work.
Session Resume: Provides commands to resume sessions directly.
Use Case: If your session was interrupted due to a crash or network issue, this Skill can help you find the last checkpoint and continue your work seamlessly.

Quick Start

To resume a session, use the command: 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 after a terminal crash?▼

To resume an interrupted Copilot CLI session, the Skill queries the session store to find your last checkpoint and provides the `copilot --resume SESSION_ID` command to seamlessly continue your work.

Can I filter out automated Copilot CLI sessions to only see my human-generated work?▼

Yes, you can filter out automated Copilot CLI sessions because the Skill specifically includes session filtering to identify and focus on recovering human-generated work from the session store.

What is the best way to recover lost work from a Copilot CLI session interrupted by network issues?▼

The best way to recover lost work from an interrupted Copilot CLI session is to use this Skill to detect the interrupted session, retrieve the checkpoint, and execute the provided resume command.

Do I need access to the session store to resume a Copilot CLI session?▼

Yes, you need access to the session store and the `copilot` CLI installed, as the Skill queries this store to detect interrupted sessions and generate the commands needed to resume your work.

How does Copilot CLI session recovery handle automated background sessions?▼

Copilot CLI session recovery handles automated background sessions by applying a session filtering mechanism that excludes them, ensuring you only resume human-generated work checkpoints.