[BUG] Session history shows empty — extension writes session files but never updates history.jsonl

Resolved 💬 1 comment Opened Apr 22, 2026 by eemq Closed May 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Description

The VSCode extension's "Session history" UI consistently shows no past conversations. After every window reload, all session context is lost. This has been ongoing for approximately 3 weeks.

The extension does write session conversation data (.jsonl files under ~/.claude/projects/), but does not write corresponding entries to ~/.claude/history.jsonl, which appears to be the index the session history UI reads from.

Environment

  • Claude Code Extension: 2.1.117-darwin-arm64
  • VSCode: macOS (Darwin 25.2.0, Apple Silicon)
  • Auth method: AWS Bedrock (CLAUDE_CODE_USE_BEDROCK=1), not Anthropic API directly
  • Model: global.anthropic.claude-opus-4-6-v1
  • Workspace type: Multi-root workspace (3 folders)
  • Preferred location: Sidebar (claudeCode.preferredLocation: "sidebar")

What Should Happen?

Expected behavior

  • history.jsonl should be updated each time a user sends a message in a session
  • list_sessions_request should return all local sessions for the current project
  • Session history UI should show past conversations that can be resumed

Error Messages/Logs

## Diagnostic findings

### Session data IS being written to disk


~/.claude/projects/bbd-automation/4f584612-a4fa-4068-926e-bbc02d8b0ee1.jsonl  (89KB)
~/.claude/projects/-bbd-automation/c09db1db-49c5-4428-9cb6-56357aadd4a1.jsonl  (112KB)
~/.claude/projects/bbd-automation/d49dfd02-af32-47e4-a05c-ba7e72493e2a.jsonl  (114KB)
... (14 session files total across projects)


### Session index is stale and incomplete


~/.claude/history.jsonl:
  - Total entries: 26 (all valid JSON, no corruption)
  - Last modified: 2026-04-01 (3 weeks ago, stopped updating)
  - Entries for analytics-tests-status-report project: 0
  - Sessions in index: 7 out of 14 on disk (50% missing)
  - Current active session (54b5bcb1): NOT in index
  - File is writable, no lock held by any process
  - Has com.apple.provenance xattr (macOS provenance flag)


### Extension logs show no response to session list requests

From `Claude VSCode.log`:

13:59:51.943 [info] Received message from webview: {"type":"request","requestId":"hyjnmwdl6m","request":{"type":"list_sessions_request"}}
  (no response logged — session list presumably returns empty)

13:59:53.479 [info] Received message from webview: {"type":"request","requestId":"rgi6asz6s5s","request":{"type":"list_remote_sessions"}}
13:59:53.567 [info] Keychain read failed, trying file fallback
13:59:53.567 [warning] No OAuth token available for teleport
13:59:53.568 [error] Error processing client request: Error: Failed to connect to remote server


The `list_remote_sessions` failure is expected (Bedrock auth, no Anthropic OAuth token). The `list_sessions_request` (local) fires but produces no visible response in the log.

### No extension globalStorage directory


~/Library/Application Support/Code/User/globalStorage/anthropic.claude-code/
  → Does not exist

Steps to Reproduce

Reproduction

  1. Open a multi-root workspace in VSCode with Claude Code extension
  2. Start a conversation in the sidebar
  3. Have a full conversation (session .jsonl file grows on disk)
  4. Reload the VSCode window
  5. Click "Session history" — list is empty
  6. Previous conversation context is completely lost

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.91

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

Additional context

  • The CLI (claude --resume) also relies on history.jsonl and shows the same stale data
  • The extension's PreToolUse hook (AWS credential check) works correctly and is not interfering
  • No other AI extensions installed that could conflict
  • Workspace trust is not restricted

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗