CommandCodeAI / CommandCodeAI/command-code
Conversation history is tied to case-sensitive directory paths
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The conversation history appears to be matched using the exact directory path string, including letter casing.
Expected Behavior
Since both paths refer to the same directory (on a case-insensitive filesystem), the existing conversation history should be shown.
Actual Behavior
A new conversation is created (or previous conversations are not shown) because the path comparison is case-sensitive.
Steps to reproduce the issue
Open a project from:
/path/to/project
Start a conversation.
Later, open the same physical directory using:
/path/to/Project
(only the casing differs).
Observe the conversation history.
Command Code Version
0.40.14
Operating System
Windows
Terminal/IDE
No response
Shell
No response
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing where conversation history is looked up and how project directory paths are compared on Windows, then reproduce the issue with paths differing only in letter casing. Done means the same physical directory shows its existing conversation history regardless of path casing.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100