VS Code fork (Antigravity) shows empty session history in Past Conversations

Resolved 💬 4 comments Opened Jan 29, 2026 by clickmediapropy Closed Feb 2, 2026

Bug: VS Code fork (Antigravity) shows empty session history

Environment

  • Claude Code version: 2.1.23
  • IDE: Antigravity (Google's VS Code fork)
  • OS: macOS Darwin 25.2.0
  • Architecture: darwin-arm64

Description

The Claude Code extension's "Past Conversations" dropdown shows only 1 session (the current one), while the CLI /resume picker correctly shows all 487 sessions for the same project.

Expected Behavior

The extension's "Past Conversations" UI should show the same sessions as the CLI /resume picker, since both read from ~/.claude/projects/.

Actual Behavior

  • CLI: Shows 391+ sessions via /resume
  • Extension in Antigravity: Shows only 1 "Untitled" session

Investigation Notes

  1. Sessions are correctly stored in ~/.claude/projects/-Users-nicodelgadob-click-media-pro-convex/ (487 .jsonl files)
  2. Extension connects to CLI via WebSocket (verified via ~/.claude/ide/*.lock files)
  3. No extension-specific storage folder exists in Antigravity's globalStorage
  4. The issue appears specific to VS Code forks (Antigravity stores data in ~/Library/Application Support/Antigravity/)

Steps to Reproduce

  1. Install Claude Code extension in Antigravity (or another VS Code fork)
  2. Use Claude CLI to create multiple sessions: claude → work → exit, repeat
  3. Open Antigravity with the same project
  4. Click the "Past Conversations" dropdown in Claude Code extension
  5. Observe only 1 session instead of all CLI sessions

Workaround

Use claude --resume in the IDE's integrated terminal to access all sessions.

Screenshots

[Attach screenshot showing CLI with 391 sessions vs extension with 1 session]

Additional Context

The lock files show the extension connects correctly:

{"pid":94000,"workspaceFolders":["/Users/nicodelgadob/click-media-pro-convex"],"ideName":"Antigravity","transport":"ws",...}

But the session list is not being populated in the extension UI.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗