Skip to content
| Marketplace
Sign in
Visual Studio Code>AI>Claude RecallNew to Visual Studio Code? Get it now.
Claude Recall

Claude Recall

clauderecallhq

|
10 installs
| (1) | Free
Syncs your VS Code terminal tab names to Claude Recall session aliases, automatically. Renames propagate live.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Claude Recall for VS Code

Never lose a Claude Code session again. Label every session with the name of the terminal it ran in. Automatically.

Marketplace CLI on npm Website License


Claude Recall

Claude Recall is a local-first memory tool that indexes every Claude Code session you have ever run and makes them searchable from the recall CLI, a browser UI, and an MCP server. This extension is the VS Code companion that gives every session a meaningful name with zero manual steps. Renames in your editor propagate to your session library automatically.


Claude Recall web UI — every Claude Code session you have ever run, searchable, threaded, re-injectable

The library this extension keeps labeled for you.



MCP server connected to Claude — search and get_session tool calls executing live

Claude calls Recall as native MCP tools. Searches your history. Pulls context. Decides.



Cost analytics dashboard with daily spend bars and top sessions ranked by cost

Cost analytics. Hover any day. Exact cost. Exact tokens.



Collections panel — drag-to-organize sessions across projects

Collections. Drag-to-organize sessions across projects.



Full-screen terminal UI — sessions list with live preview pane, slash-to-filter

Or stay in the terminal. recall tui ships the same library as a full-screen terminal app.



Side-by-side: Obsidian vault on the left, Claude Recall TUI on the right

Built specifically for Claude Code, not adapted from notes apps.


What it does

  1. Name your terminal tabs the way you already do (auth-refactor, billing-bug, dashboard-v2).
  2. Run claude in any of those tabs as you normally would.
  3. The session shows up in Claude Recall labeled with the tab name within a couple seconds. Rename the tab mid-session and the alias updates live.

Works in VS Code, VS Code Insiders, Cursor, and Windsurf.


What's new in 0.18

Tab names flow through every time, no matter what

The 0.18 series fixes a regression where the extension was silently rejected by newer daemons that require an auth token. Symptom: sessions stopped picking up your tab name and fell back to the heuristic first-message snippet. Fix: the extension now reads ~/.recall/daemon.token on every request and attaches it as X-Recall-Token. Older daemons without the token still work; the header is simply omitted.

Pipeline-health visibility in recall doctor

A new diagnostics section in recall doctor reports the live state of the tab-name → session-alias chain: how many extension requests the daemon rejected, when the last successful sync was, and what fraction of recent sessions fell back to the heuristic title. If something silently breaks the chain, you see it in five seconds, not eighteen hours.

Real version in daemon logs

The User-Agent string clauderecall-vscode/X.Y.Z is now sourced from the extension's actual package.json at activation time, so daemon access logs always show the real client version instead of a stale literal.


Recent releases

Version Date Headline
0.18 2026-05-05 Collapsible side panes, threads UX polish, doctor + optimize commands. Auth-token migration, pipeline-health diagnostic, accurate User-Agent (0.18.1-0.18.3, 2026-05-06).
0.17 2026-05-03 Editor-source PID ownership ends two-editor alias war
0.16 2026-05-03 Extension neighborhood command: bundle parents/children/citations into context
0.15 2026-05-03 Interim release. See CHANGELOG.md for details.
0.14 2026-05-02 Orphan-session re-bind after editor or laptop restart. Daily stale-link reaper.
0.13 2026-05-02 Activation-race fix. First claude after VS Code launch always gets the right tab name.
0.12 2026-05-02 Auto-recover historical sessions via terminal scrollback. Secret redaction filter.
0.11 2026-05-01 Brand reveal hero
0.10 2026-04-28 Pro license activation
0.9 2026-04-28 Cross-platform support contract
0.8 2026-04-24 Live rename detection. Idempotent sync.
0.7 2026-04-19 First public release

Full history: CHANGELOG.md.


Install

Open the Extensions panel (Cmd+Shift+X / Ctrl+Shift+X), search Claude Recall, install the entry by publisher clauderecallhq.

You also need the Recall daemon running. Install the CLI:

npm install -g @clauderecallhq/cli
recall start

Requires Node 22 LTS or newer on macOS (Apple Silicon / Intel), Linux x64 / arm64 (glibc), or Windows 10+ x64.


Enable

In VS Code settings (Cmd+, / Ctrl+,) flip claude-recall.autoAlias to true. A ⟳ Recall · N indicator appears in the status bar showing how many terminals are connected to your session library.


Settings

Setting Default What it does
claude-recall.autoAlias false Master switch. When on, your terminal tab names are pushed to your session library.
claude-recall.captureScrollback true Forwards a rolling 4 KB tail of each terminal's output to the daemon so historical sessions can be reconnected to the terminal that ran them. Disable to opt out entirely.
claude-recall.daemonPortFile ~/.recall/daemon.port Where the local daemon publishes its port. Change only if you have customised the daemon's home directory.

Commands

Command Use
Claude Recall: Show daemon status Quick health check
Claude Recall: Re-register all open terminals Resend every open tab to the daemon after a daemon restart
Claude Recall: Upgrade to Pro Open the pricing page

How it works

  1. The extension watches every VS Code terminal you have open. It reports the tab name to the local Claude Recall daemon and updates that name whenever you rename the tab.
  2. When you run claude in a terminal, the extension tells the daemon which terminal you started it from.
  3. The daemon uses that to label the new session with the terminal's tab name.
  4. For sessions that ran before the daemon knew about them, the v0.12 scrollback matcher reconnects them by spotting verbatim text from the conversation in your open terminal buffers.

Everything happens on your machine. Nothing about your code, prompts, or terminal output ever leaves 127.0.0.1.


Troubleshooting

Status bar shows ⊘ Recall Auto-alias is off. Flip claude-recall.autoAlias to true in settings.

Status bar shows nothing The Recall daemon is not running. Run recall status to check, recall start to fix.

Status bar shows ⟳ Recall · 0 but terminals are open Run Claude Recall: Re-register all open terminals from the command palette.

Renames in VS Code not appearing in Claude Recall Open the Claude Recall Output channel from the View menu. Every rename the extension detects is logged there with the before and after tab name. If you do not see your rename in the log, try renaming the tab one more time. Some terminal title overrides from other extensions can race with our detection on the first edit.

An old session is still showing as unlinked Open it in the web UI. With 0.12+ installed, the system tries to relink it the moment you open it by matching scrollback content from your live terminals. If the original terminal was closed long ago, click the chain icon next to the title and pick the right terminal from the list.


Privacy

Local-first design — daemon binds to 127.0.0.1, no telemetry, no outbound network calls

We promise three things:

  1. Nothing leaves your machine. Every byte the extension produces is bound for 127.0.0.1 and the local daemon. There are no outbound network calls. No telemetry. No analytics.
  2. Secrets get redacted before they leave the extension. The redaction filter runs inside the extension on every byte of terminal output. Anthropic, OpenAI, GitHub, AWS, Slack-style keys, Bearer tokens, JWTs, and PASSWORD= / API_KEY= style assignments are replaced with placeholders before the daemon ever sees them.
  3. The extension never reads your code. No editor buffer access. No clipboard. No files outside the daemon's port file.

What the extension actually sends to the daemon, in plain English:

When What
You open / rename / close a terminal The tab name and its process ID
You run claude in a terminal Which terminal you ran it in
You type or get output in a terminal (opt out via settings) A rolling buffer of recent text, with secrets redacted

Buffers live in daemon memory only. They never reach disk.


Built for security teams

  • Zero runtime dependencies. The published .vsix ships only our own bundled JavaScript, an icon, and metadata. There is no transitive supply chain to audit.
  • Localhost-only by construction. The HTTP client refuses any host other than 127.0.0.1. The connection target is enforced in code, not configuration.
  • No webview, no HTML rendering. The extension's only UI surface is a status bar text indicator.
  • Hard timeouts on every daemon request so a hung daemon never blocks the editor.

Links

  • Product site: clauderecall.com
  • CLI on npm: @clauderecallhq/cli
  • Pricing & Pro: clauderecall.com/pricing
  • Public profile: gitlab.com/clauderecallhq/clauderecallhq
  • Send feedback from inside the CLI: recall feedback
  • Changelog: CHANGELOG.md

Get Claude Recall

Stop losing your Claude Code sessions in the noise.

Install the extension · Get the CLI · Upgrade to Pro


A Claude Recall product, built by ToolboxLogic.
Local-first. No telemetry. Your sessions never leave your machine.
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft