Recent session disappears after Ctrl+Z/restart and local/cloud IDs diverge

Copilot CLI version

1.0.81-4

Environment

Linux, interactive Copilot CLI.

Problem

After accidentally pressing Ctrl+Z, Copilot CLI exited/suspended. After reopening Copilot, the session I had just been working in was missing from the recent-session list and could not initially be recovered by name. I have also seen the same behavior after Copilot crashes and is restarted.

Recovery took more than 10 minutes of searching session history. The same conversation appeared under different local and cloud session IDs, and the cloud ID was not accepted by /resume (No session, task, or name matched ...). Only after querying the local session database separately could the locally resumable ID be identified.

Reproduction

1. Work in a long-running Copilot CLI session with many turns.
2. Press Ctrl+Z accidentally (or let the CLI crash).
3. Reopen Copilot CLI.
4. Open /resume or search recent sessions.
5. Observe that the session that was active immediately before termination is absent.
6. A synced/cloud history lookup may return the conversation under a different ID, but /resume <cloud-id> reports no match.

Expected behavior

Ctrl+Z/restart/crash should preserve the current session and make it immediately visible and resumable. Local and synced history should resolve to one stable resumable session identity, or /resume should map a synced ID to its local record.

Actual behavior

The newest working session disappears from normal session discovery. Search/recovery can instead surface a later “find my missing session” conversation, and cloud results may use a non-resumable ID different from the local record. This makes the original session look lost even though its turns still exist locally.

Additional notes

This happened more than once on the same day. The CLI help documents Ctrl+Z as “suspend,” so reopening after suspension should not orphan or hide the active session. A useful diagnostic would be to log session checkpoint persistence, local/cloud ID reconciliation, and indexing completion during shutdown/startup.

Reproduziere das Problem, indem du eine lang laufende interaktive Copilot CLI-Sitzung pausierst oder neu startest, und untersuche anschließend die Persistenz von Sitzungsprüfpunkten, die Ermittlung kürzlich verwendeter Sitzungen sowie die Zuordnung lokaler/Cloud-IDs während des Herunterfahrens und des Starts. Erledigt ist die Aufgabe, wenn die neueste Sitzung nach Ctrl+Z oder einem Absturz weiterhin sichtbar und fortsetzbar ist, mit einer stabilen Identität oder einer funktionierenden Zuordnung von der synchronisierten ID zum lokalen Datensatz.