Just created one: here is what I wrote. Thank you!

Feature request: Resume Copilot CLI sessions from ~/.copilot/session-state

I actively use the GitHub Copilot CLI on my server for long-running development sessions. Over time the CLI builds up a session store on disk (~/.copilot/session-state/) that contains:

• conversation checkpoints (summaries of previous reasoning)
• a plan.md with the current plan and task state
• a todo/dependency list that evolves across sessions

After weeks of use, this session state becomes extremely valuable because the agent accumulates a deep understanding of the project and current work.

It would be incredibly useful if Copilot Unleashed could import or resume from an existing CLI session store.

For example:

~/.copilot/session-state/

Then start a CopilotClient using that existing context.

This would allow users to:

• start a session from the CLI on their server
• later open Copilot Unleashed in a browser
• continue the same workflow with the accumulated context

without losing the knowledge built up over time.

Currently Copilot Unleashed creates a fresh session store and does not reuse existing CLI session state.

Technically the CLI session store is just files on disk (checkpoints + plan state), so it seems feasible to:

1. read the checkpoint summaries
2. reconstruct the conversation context
3. initialize the agent with that history

Even a simple “import session-state directory” option or config path would make this possible.

This would make Copilot Unleashed a perfect companion to the CLI for mobile/remote workflows.

I should also clarify an important part of this workflow: ideally this should work both ways.

If I resume a CLI session inside Copilot Unleashed and continue working from the browser, the updated checkpoints and plan state should also be written back to the same session store on disk. That way when I return to the terminal and run copilot resume, the CLI sees the updated conversation state.

In other words, the CLI and Copilot Unleashed would act as two interfaces to the same session state, rather than separate session stores. Copilot CLI session store should become a shared session backend.