Feature Request: Unified session visibility across Copilot CLI, VS Code, and the GitHub Copilot app

Feature Request: Unified session visibility across Copilot CLI, VS Code, and the GitHub Copilot app

Title: Unify/surface session history across standalone CLI, VS Code Copilot Chat, and GitHub Copilot desktop app

Summary:
Sessions created in different Copilot surfaces (standalone copilot CLI in a terminal, VS Code Copilot Chat, and the GitHub Copilot desktop/app) are invisible to each other. When working in the same repository, a user has to remember which surface they used to find a past session — there is no single place to see "everything I've done in this repo."

Observed behavior:

• Running copilot directly in a terminal against a repo creates entries in a local session history store (confirmed via internal tooling: 20 recorded sessions across multiple branches/folders in one repo, dating back months).

• The GitHub Copilot desktop app's session list only shows sessions that it created/tracks (in this case, only 2 of the 20 known sessions for the same repo appeared).

• VS Code Copilot Chat maintains an entirely separate history that doesn't appear in either of the above.

Impact:

• Users lose track of prior investigation/work done in other surfaces.

• No way to resume or reference a CLI session from the desktop app, or vice versa.

• Makes it hard to audit "what has Copilot already done in this repo" across tools.

Requested behavior:

• A unified session index (at least per-repo, ideally per-machine) that all three surfaces read from and write to.

• At minimum, the GitHub Copilot desktop app should be able to list/import standalone CLI sessions recorded locally for the current repo/cwd.

• Longer term: shared visibility (read-only is fine) into VS Code Copilot Chat sessions too.

Environment: GitHub Copilot app Version 1.1.16 macOS / GitHub Copilot CLI 1.0.83.

Start by mapping the local session history store used by the standalone copilot CLI, then compare how the GitHub Copilot app and VS Code Copilot Chat store and display sessions. Done means the three surfaces can expose a shared per-repository session index, with at least CLI sessions listed or imported by the desktop app.