Where GitHub Copilot CLI stores your session history

GitHub Copilot CLI, the copilot command, stores each session in its own folder. It differs from most agents in one way that matters: by default it syncs sessions to your GitHub account.

#Where the files are

~/.copilot/
├── session-state/
│   └── <session-id>/
│       ├── events.jsonl       # the session, as a stream of events
│       ├── workspace.yaml
│       ├── plan.md
│       ├── checkpoints/
│       └── files/
├── session-store.db           # SQLite index used for search
├── command-history-state/
└── settings.json

Versions before 0.0.342 used history-session-state/. COPILOT_HOME moves the whole folder. The events.jsonl schema is not documented.

#Turn off the cloud sync

In ~/.copilot/settings.json:

{
  "remoteExport": false
}

Or for a single run: copilot --sync-session=off. On Copilot Business and Enterprise, the organization policy "Store local sessions in the Cloud" controls this.

#Resume and export

copilot --resume             # pick a session
copilot --resume=<id|name>
copilot --continue           # the latest

Inside a session, /resume switches sessions and /share (also /export) writes the session to a file, HTML or a gist. --share=PATH does it at the end of a non-interactive run.

#Delete history

/session delete [ID] removes one session and /session delete-all removes them all. Turn off sync first if you do not want a copy kept on GitHub.

#Privacy notes

• Synced sessions sit in your GitHub account, alongside your code.
• Local files include command output and file contents. Redact before sharing.

The groundedby evaluator does not read Copilot CLI sessions yet.