claude-code - 💡(How to fix) Fix [BUG] UI history conversation display issue [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#51972Fetched 2026-04-23 07:39:59
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×5commented ×1unlabeled ×1

Error Message

Error Messages/Logs

Root Cause

Root Cause: Drive letter case mismatch — CLI writes K:\... but extension writes k:\..., causing extension to fail to find CLI-created sessions

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

Symptom: Session history panel in VSCode extension shows no history

What Should Happen?

Session history panel in VSCode extension should shows history

Error Messages/Logs

Steps to Reproduce

Verification Method: claude --resume in terminal lists all sessions correctly

Root Cause: Drive letter case mismatch — CLI writes K:\... but extension writes k:\..., causing extension to fail to find CLI-created sessions

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.117 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

The issue can likely be fixed by ensuring consistent drive letter casing between the CLI and the VSCode extension.

Guidance

  • Verify that the drive letter case mismatch is the root cause by checking the session history files written by the CLI and the extension to confirm the case difference.
  • Consider modifying the extension to handle drive letter case insensitivity, allowing it to correctly find sessions regardless of the case used by the CLI.
  • Check if there are any configuration options in the extension or the CLI to normalize the drive letter case.
  • Test the claude --resume command with different drive letter cases to see if it affects the output.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The fix may require changes to the VSCode extension or the CLI, and the exact implementation details are not provided. Additionally, the issue is specific to the Windows operating system.

Recommendation

Apply a workaround to ensure consistent drive letter casing between the CLI and the extension, as the root cause is identified and a code change may be required to fix the issue permanently.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING