session-recovery

To find recent Copilot sessions, the recovery process queries the sessions table in the session_store to surface the most recently active entries, filters out automated monitors, and identifies the last checkpoint where your work stopped.

To filter out automated heartbeat sessions when searching for past Copilot work, the recovery process excludes automated monitors from the session_store query results, ensuring only human-driven sessions are surfaced for potential resumption.

Yes, you can recover your working directory and checkpoint context by querying the session_store for past session details and applying the ready-to-use resume action, which preserves your working directory and checkpoint for immediate continuation.

The best way to rehydrate Copilot session context after a disconnection is to query the session_store for the interrupted session, retrieve the session ID, and execute the resume command to restore your previous working state and checkpoint.

No, session recovery requires no external dependencies to query the session_store; it implements the necessary SQL queries natively to find interrupted work, filter automated monitors, and return the resume command for immediate continuation.