SessionsAI

Find, read and pick up any Claude Code session without leaving VS Code. Your GitHub Copilot CLI and VS Code Chat sessions show up too.

Claude Code saves every conversation you have with it, but finding an old one means scrolling through claude --resume and guessing from the first line. SessionsAI adds a sidebar that shows all of your sessions across every project. You can search everything you and Claude said, read any conversation as a chat transcript, see what each session used and cost (or chart what all of them cost, by day, model and project), and resume it in one click, or carry it over into a fresh session, even in a different tool. Your GitHub Copilot CLI and VS Code Chat sessions are listed alongside, so one search covers all of them.

What you can do with it

Browse every session in one place

The sidebar shows a card for each session with its title, your latest prompt, when it happened, the git branch, how many prompts it has, and badges for subagents and pull requests. A pulsing green dot marks sessions that were active in the last few minutes.

Each card also shows what the session cost, plus a couple of usage badges when they're worth knowing about.

• Projects groups sessions by folder, and each project gets its own colored avatar. Recent groups them by date (Today, Yesterday, Previous 7 Days, and so on).
• Workspace filter: show only the sessions started in the folders you have open in this window.
• Source chips under the search box filter by tool (Claude Code, Copilot CLI, VS Code Chat). See below.
• Hover a card for quick actions: resume, continue in a new session, open in Claude Code chat, read the transcript, or copy the session ID. Right-click for more.

The sidebar refreshes on its own as sessions change, and everything follows your VS Code color theme.

Search everything you and Claude said

Press / to search. The search covers the card details and the full conversation: your prompts and Claude's replies, and the paths of files Claude's tools read or edited, but not tool output. When a session matches inside its conversation, its card shows the matching passage.

To find the sessions that worked on a file, right-click it in the Explorer or right-click its editor tab and choose Search Sessions for This File. The sidebar opens with the file name in the search box.

Read a session as a chat

Click a session to open its transcript. Your prompts are on the right and Claude's replies are on the left, with markdown, tables and syntax-highlighted code that you can copy.

• Each tool call is a compact row with a ✓ or ✗. Click it to see the input and output. File edits show as a red/green diff.
• Hide tool calls to read just the conversation, or jump straight to the latest message.
• If you opened the transcript from a search, your search words are highlighted and it starts at the first match. Step through matches with F3 / Shift+F3.
• Transcripts open in a single preview tab that the next one replaces, so tabs don't pile up. Double-click a session, or click Keep open, to give it a tab of its own.

See what a session used and cost

The top of each transcript shows the numbers Claude Code's status line shows while a session runs, so you can check them for any session, long after it ended:

When you scroll down into the conversation, a one-line version of the stats stays in the bar at the top, along with the switch for showing tool calls. Click it to go back to the top.

Cards keep it short. Each one shows the cost, plus two badges that only appear when they're worth acting on:

• Context, once the window is more than half full. It turns yellow from 80%.
• Prompt cache countdown, while the cache is still warm.

The numbers are worked out on your machine from the token counts in the session logs, using Claude API list prices. They leave out the few small background requests Claude Code doesn't log, such as naming the session.

See all your sessions at a glance

Click the dashboard button at the top of the sidebar, or run SessionsAI: Open Overview, to open a summary in an editor tab. For the last 7, 30 or 90 days, or all time, it shows:

• Totals: cost at API prices, sessions, prompts, projects and active days.
• Cost per day: each bar is split by model or by project, whichever you pick under Color by (or Total for plain bars), with a legend below. Hover a bar for that day's breakdown. A model or project keeps its color when you change the range.
• Projects and Models: each one's sessions, prompts, cost and share.
• Sessions: the most recently active, or switch to the most expensive. Click one to read its transcript.

The overview starts with the projects in your current workspace. Use the Projects menu to switch to All projects or tick the ones you want, or click a project's name in the table to show just that one. The page remembers your range, projects and color choice.

Cost is counted on the day each request was made, so a session that ran over several days is split across them.

Pick up where you left off

You'll find these on each card and at the top of each transcript. This is how they work for Claude Code sessions; Copilot CLI and VS Code Chat sessions work much the same way.

• Resume (▶) opens claude --resume <id> in a terminal tab beside your editor, in the session's project folder. If the session is already open, its terminal is focused instead.
• Continue in New Session (⮕) starts a fresh session with a handoff of where the old one stopped. The handoff includes your last request, Claude's last reply, the files it edited and read, any open to-dos, the current git status, and the path to the old transcript. If you asked the old session to write a handoff (for example "save a handoff.md for this session", or a handoff skill), the new prompt opens with where it was saved, including any copies, and tells Claude to read it first. Claude is asked to summarize and wait for your instruction before changing anything. Use this when a session has grown too long to keep working in.
• Continue in New Session with Tool or Model… does the same, but first asks where the new session runs: Claude Code, GitHub Copilot CLI or VS Code Chat. For a CLI it then asks which model and effort level to use, instead of that CLI's settings. This also lets you move work between tools, for example from a Copilot chat to Claude Code. Find it in a card's right-click menu, or click the ⌄ next to Continue in new session in a transcript.
• Open in Claude Code Chat reopens the session in the chat panel of the official Claude Code extension, if you have it installed.

GitHub Copilot CLI and VS Code Chat sessions too

The sidebar also lists your GitHub Copilot CLI sessions and your VS Code Chat (GitHub Copilot Chat) conversations, next to your Claude Code sessions. Each card has a badge naming its tool. You can search all of them and read any of them as a transcript.

• Source chips under the search box: All, then one chip per tool with its session count. Click a chip to show only that tool's sessions, then click others to add them. Click a chosen chip to remove it, and removing the last one goes back to All. The chips appear once more than one tool has sessions. They change the current window only. The claudeSessions.sources setting chooses what a new window starts with.
• Resume runs copilot --resume <id> for a Copilot CLI session. For a VS Code chat, the button reads Open in Chat. It opens the conversation in this window if the chat belongs to this window's folder. If it doesn't, you can open that folder in a new window, because VS Code shows a chat only in the window of its own folder.
• Continue in New Session works for these sessions too. A Copilot CLI session continues in a new Copilot CLI session. A VS Code chat continues in a new chat in agent mode, with the handoff in the input box so you can pick a model and press Enter.
• Open in Claude Code Chat, and the usage and cost figures, are for Claude Code sessions only. Copilot logs record no token usage, so the overview labels its cost Claude only when other tools are shown. The overview has its own source chips.

Sessions are read from ~/.copilot/session-state (or $COPILOT_HOME), and from the workspaceStorage folders of VS Code and VS Code Insiders. Chats from remote, WSL or SSH windows, and from other editors built on VS Code, are not included.

Install

You need VS Code 1.90 or newer. To use Resume and Continue in New Session, you also need the Claude Code CLI installed, so that claude runs in a terminal.

The other tools are optional. Their sessions are listed whenever their logs are on your machine, but to resume or continue them you need:

• GitHub Copilot CLI, so that copilot runs in a terminal, for Copilot CLI sessions.
• The GitHub Copilot Chat extension, for opening VS Code chats and continuing work in a new chat.

To install it:

1. In VS Code, open the Extensions view, search for SessionsAI, and click Install. Or install it from the VS Code Marketplace, or from a terminal:

   code --install-extension rellik92j.sessionsai
   

2. Click the SessionsAI icon in the Activity Bar.

VS Code keeps it up to date on its own.

If you installed an earlier version from a .vsix file, uninstall that one first. It was published as local.claude-sessions, so VS Code treats it as a different extension and won't update it.

Each release's .vsix is also on the Releases page, for installing with Install from VSIX… in the Extensions view's … menu.

Privacy

SessionsAI only reads the session logs that are already on your machine: Claude Code's in ~/.claude/projects (or $CLAUDE_CONFIG_DIR/projects if you set it), GitHub Copilot CLI's in ~/.copilot/session-state, and VS Code Chat's in VS Code's workspaceStorage folder. It sends nothing over the network, and it never changes or deletes your logs.

Keyboard shortcuts

In the sidebar:

In a transcript: F3 / Shift+F3 step through search matches, and Esc clears them.

The SessionsAI: Search Sessions… command in the Command Palette searches transcripts too, SessionsAI: Search Sessions for This File searches for the file in the active editor, and SessionsAI: Open Overview opens the overview.

Settings

Development

npm install
npm test          # compile, bundle and run unit tests (plus a smoke test against your real ~/.claude/projects)
npm run package   # build sessionsai-<version>.vsix

Press F5 with this folder open to run the extension in a development host.

How the code is laid out:

Files without VS Code imports (the three parsers, usage, query, overview, handoff, markdown, format) are unit tested directly from out/; test/activation.test.js loads the bundled extension against a fake VS Code API and drives the webviews' messages.

License

MIT