Skip to content
VS Code extension

Lifecycle

Auto-name Claude Code sessions with the terminal tab name you started them in.

Terminalopensin VS CodeTab nameregisteredPOST 127.0.0.1Claude writesJSONL~/.claude/projects/Daemoncorrelateslsof + shell PIDAuto-aliasappliedsession named

What it watches

  • +onDidOpenTerminal, rename, and close events
  • +POSTs shell_pid, tab_name, and cwd to 127.0.0.1
  • +Daemon correlates via lsof when JSONL appears

What it never does

  • −Read terminal buffer or output
  • −Touch the clipboard
  • −Read editor buffers or files
  • −Make any outbound network call (loopback only)

Status bar in VS Code, Cursor, Windsurf

Recall·3

Number of currently registered terminals.

VS Code extension

Lifecycle and what-it-watches above. Install paths:

Search Claude Recall in Extensions. Direct: clauderecallhq.clauderecall-vscode.

#CLI sideload

bash
recall install-extension                  # auto-detects every editor on PATH
recall install-extension --editor cursor  # one editor only

#Local build

bash
cd extensions/vscode
npm install && npm run build && npm run package
code --install-extension clauderecall-vscode-*.vsix

#Enable

VS Code settings: claude-recall.autoAlias: true. Status bar shows ⟳ Recall · N (N = registered terminals).

#Troubleshooting

  • Status bar shows ⊘ Recall: autoAlias is off. Turn it on.
  • No status bar at all: daemon isn't running. recall start.
  • Tab named X but session aliased differently: stale correlation. Run "Re-register all open terminals" from the palette.
  • Session titles show the first sentence instead of your tab name: extension can't reach the daemon. Run recall doctor and read the Pipeline health section. Most common cause is a daemon update that the Marketplace extension hasn't caught up to yet. Reinstall the extension, then run "Developer: Restart Extension Host" from the palette.

Last updated