GitHub Copilot CLI Adds Session Recovery for Interrupted Work
GitHub CopilotGitHub Copilot CLI now automatically restores sessions that didn't exit cleanly — including ones interrupted mid-turn by a crash or a closed terminal — instead of losing that in-progress work. The same release moved Copilot CLI onto a native Rust runtime for its core agent engine, while keeping its terminal interface in TypeScript, which GitHub says delivers "significantly faster performance."
Key Takeaways
- GitHub Copilot CLI can now automatically restore sessions that didn't exit cleanly, including ones interrupted mid-turn.
- Recovery works by reconstructing session state from data already flushed to disk before the interruption, without requiring a manual restart.
- The feature complements existing commands like
/resumeandcopilot --continuefor picking sessions back up. - The same update moved Copilot CLI's core agent engine to a native Rust runtime, while its terminal UI stays in TypeScript.
- GitHub says the Rust runtime delivers "significantly faster performance" for the CLI.
- The changes make Copilot CLI more resilient for long-running or unattended agent sessions, such as ones left running in CI.
No More Losing Work to a Closed Terminal
Anyone who has closed a terminal window, hit a crash, or lost a network connection mid-task knows the frustration of restarting an agent session from scratch. GitHub Copilot CLI now addresses this directly with session recovery: sessions that don't exit cleanly, including ones interrupted mid-turn, can now be restored rather than lost.
How Recovery Works
When a Copilot CLI session terminates unexpectedly, the CLI can reconstruct the session from data already written to disk before the interruption, rather than requiring the developer to start over and re-establish context. Combined with existing session management commands — /resume to open a session picker, and copilot --continue to reopen the most recently closed local session — this makes Copilot CLI considerably more resilient for long-running or unattended agent work, such as sessions left running in CI or on a remote machine.
A Faster Engine Underneath
The same round of updates moved Copilot CLI's core agent engine onto a native Rust runtime, while its terminal interface remains written in TypeScript. GitHub describes the change as delivering significantly faster performance, a meaningful improvement for a tool increasingly used to drive long, multi-step agentic workflows where responsiveness compounds over many turns.
Why It Matters
As Copilot CLI leans further into autonomous, long-running agent sessions, resilience to interruption becomes as important as raw capability. Session recovery reduces the cost of experimenting with longer agent runs, since a crash or dropped connection no longer means starting from zero.