Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Feature request: store conversation history by project identity, not file path [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#53201•Fetched 2026-04-26 05:21:45
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
zalim-khanzalim-khan
Participants
github-actions[bot]github-actions[bot]zalim-khanzalim-khan
Timeline (top)
labeled ×2closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Feature request: store conversation history by project identity, not file path

Currently, conversation history is tied to the absolute path of the working directory. If a user moves or renames a project folder, all history is lost — even though the project itself hasn't changed.

It would be great if Claude Code could identify projects by something more stable, like a unique ID stored in .claude/ when the project is first created. That way, moving or renaming a folder wouldn't break the conversation history.

Proposed Solution

It would be great if Claude Code could identify projects by something more stable, like a unique ID stored in .claude/ when the project is first created. That way, moving or renaming a folder wouldn't break the conversation history.

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

File operations

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Store a unique project ID in a .claude directory to decouple conversation history from the project's file path.

Guidance

  • Consider introducing a project initialization step that generates and stores a unique ID in a .claude directory.
  • Update the conversation history storage to use this project ID instead of the absolute file path.
  • Ensure the project ID is persisted across project moves or renames.
  • Investigate potential ID generation methods, such as UUIDs, to ensure uniqueness.

Notes

The proposed solution relies on the ability to store and retrieve a unique project ID, which may require modifications to the existing project initialization and conversation history storage mechanisms.

Recommendation

Apply workaround: Store a unique project ID in a .claude directory to decouple conversation history from the project's file path, as this approach addresses the core issue of conversation history loss due to project moves or renames.

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…
#conversation history#docker error#permission error#memory optimization#batch processing

Still need to ship something?

×6

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

Back to top recommendations

TRENDING