Repository navigation
[BUG] Claude Code's past conversation indexing is not working and may suffer from poor design #9898
Closed as not planned
Description
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?
Claude Code has three interfaces:
- Terminal Application
- IDE Terminal
- VS Code Extension v2.0
The /resume command fails to reliably index and display conversation history, causing several issues:
Cross-Interface Inconsistency:
- Conversations created in one interface often don't appear in
/resumewhen accessed from another interface
Same-Interface Indexing Failures:
- Within a single interface, switching between many conversations may cause some to disappear from
/resume
Incomplete v2.0 Migration:
- When VS Code Extension v2.0 launched, it only indexed a some of pre-v2.0 conversations
- Terminal
/resumeshows different number of conversations than Extension/resume or 'Past conversations'
Path-Dependent Design Flaw:
- All conversations are stored in
~/.claude/projects/organized by absolute directory path - Moving a project directory breaks access to ALL previous conversations via
/resume - The conversation files still exist in
~/.claude/projects/but become inaccessible
Root Cause:
Conversations are indexed by absolute directory paths rather than a centralized index or project identifier.
What Should Happen?
Claude Code should implement a centralized conversation index similar to claude.ai/recents where:
- Unified History: All conversations accessible from a single, persistent index across all three interfaces
- Portable Projects: Conversations tied to project identifiers (not absolute paths), so moving/renaming directories doesn't break history
- Reliable Indexing: All conversations in
~/.claude/projects/are consistently indexed and accessible - Cross-Interface Sync: Conversations created in any interface appear in
/resumeacross all interfaces
Steps to Reproduce
Issue 1: Cross-interface visibility
- Create a conversation using the Terminal Application
- Open the same project in VS Code Extension v2.0
- Run
/resume - Observe: Conversation may not appear in the list
Issue 2: Lost after project move
- Create a conversation in a project at
/path/to/project - Verify it appears in
/resume - Move the project to
/new/path/to/project - Run
/resumein the new location - Observe: All previous conversations for that project are gone from
/resume - Check
~/.claude/projects/- files still exist but are inaccessible
Issue 3: Same-interface disappearance
- Create multiple conversations in the same interface
- Switch between them multiple times using
/resume - Observe: Some conversations disappear from the
/resumelist despite files existing in~/.claude/projects/
Claude Model
None
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
2.0.22
Platform
Other
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
No response
Reacted by kerim
Activity
github-actions commentedon Oct 19, 2025
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
kerim-ca commentedon Oct 19, 2025
Related GitHub Issues
#9258 - History Sessions lost in VS Code plugin
#1516 - Directory moves break --continue
#2717 - Conversation History Retrieval Failure in /resume
#4050 - Project-specific session storage configuration
Other Resume/History Issues:
#8937 - Resume conversation doesn't display previous messages in terminal
#3188 - v1.0.45 --resume bug
#2302 - Resuming Previous Sessions Fails with "No Conversation Found"
#3138 - Resume flag fails after hitting usage/context limits
#371 - Resume old sessions (original feature request)
#1340 - Feature Request: Session Resumption for CLI
#6912 - Allow Claude Code to access /resume command
Official Documentation
Claude Code Common Workflows - Official docs on --continue and --resume
Claude Code VS Code Integration - Documentation on the VS Code extension
Claude Code Best Practices - Anthropic's official best practices
Anthropic News: Claude Code Autonomous Features - Announcement of v2.0 features
Community Resources & Workarounds
GitHub Gist: Directory Migration Guide - Detailed explanation of how Claude Code stores conversations and how to migrate after directory moves
Claude Code Session Management Guide - Steve Kinney's comprehensive guide
Claude Code Tutorials Part 2: Resume Conversations - Practical tutorial on resuming conversations
Third-Party Extensions (mentioned in research)
Claude Code Chat Extension - Alternative VS Code interface
Claude Code Assist - Chat History Viewer - Extension specifically for browsing history
Additional Context
Claude Code Cheat Sheet - Comprehensive command reference
Complete Review & Guide to Claude Code 2.0 - Third-party review of v2.0 changes
scampcat commentedon Oct 20, 2025
Confirmed bug on Mac OS 26, same version, same problem in Claude Code CLI.
alsage13 commentedon Oct 23, 2025
This is a really annoying issue. Having recently migrated from Claude desktop/browser, not being able to find past chats is a massive pain! I like that they're housed in a project, but there should be a unified view, too.
schpet commentedon Oct 28, 2025
yeah, would be great to e.g. be able to set a project name in a project's
.claude/settings.local.jsoni'm using symlinks to work around this, e.g. given i have a project at /Users/schpet/code/foobar and run
git worktree add ../bazbarto add a copy of it at /Users/schpet/code/bazbarthen i run this:
this lets me share history between git worktrees, and in my case more commonly, jj workspaces
github-actions commentedon Dec 9, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
github-actions commentedon Jan 12, 2026
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
github-actions commentedon Jan 19, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.