session-recovery

To resume an interrupted Copilot CLI session, query the local session_store SQLite database to locate the orphaned work and execute the copilot --resume SESSION_ID command to restore it from the last checkpoint exactly where you left off.

Session recovery works by querying the session_store SQLite database with read-only access to locate interrupted Copilot CLI sessions, filtering by time window, working directory, and last checkpoint to identify the exact human work to restore.

Yes, you can filter out automated heartbeat sessions when searching the session_store database, allowing you to focus specifically on locating and resuming interrupted human work rather than automated background processes.

Before resuming a Copilot CLI checkpoint, you can inspect the full session context including past conversations, saved checkpoints, touched files, and linked refs to ensure you are selecting the correct interrupted workflow to safely continue.

Yes, you need read-only access to the session_store SQLite database to find orphaned checkpoints, ensuring the recovery process safely queries interrupted Copilot CLI sessions without modifying the underlying local development environment data.

You can search interrupted Copilot CLI sessions by topic using keywords or filter by working directory to locate relevant work, applying filters directly within the session_store database to quickly narrow down the available recent checkpoints.