You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Two Claude Code sessions in the same folder / project share chat history when they should be separate. #7702
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?
When I start two Claude code sessions in the same folder, they seem to share history - which means they get mixed up with each others tasks. For example, if I start one Claude Code Session to do debugging and another to do feature development - the one will have the chat history of the other. After a particular task has been completed, the debugging instance starts to do Feature development because it seems to have access to the chat history of the other (e.g. if you use the up arrow when you are in the code interface you can up arrow to the prompts from the other instance). This means that Claude Code eventually stops following explicit instructions and does what it likes.
What Should Happen?
Each instance in the same project should be isolated from ther others. Even when resuming a chat --resume, the instance should be isolated and every chat interface should maintain its own context and chat history - the only time that things should be recalled is when you --resume an instance, then that instance's messaging, context, prompts etc should all be retrieved and used.
Error Messages/Logs
Steps to Reproduce
Open two instances of Claude code in the same project folder. Give each instance a task and watch as when one instance completes the task (often after a compaction) it will have context, prompting and history from the other instance.
This issue is still persisting - it may have been corrected in previous versions, but it seems to have returned. It should be fully checked, as it makes using Claude Code a problem. I think I have given a bit more context on here of my findings.
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.
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.
This issue was closed incorrectly despite recent human comments. This behavior of the bot is reported at #16497. Please upvote that issue, so maybe it gets noticed.
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.
Activity
github-actions commentedon Sep 16, 2025
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
CryptVenture commentedon Sep 16, 2025
This issue is still persisting - it may have been corrected in previous versions, but it seems to have returned. It should be fully checked, as it makes using Claude Code a problem. I think I have given a bit more context on here of my findings.
github-actions commentedon Dec 5, 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.
julienld commentedon Dec 16, 2025
Same issue on v2.0.69 in WSL.
To reproduce:
lamplighter commentedon Dec 31, 2025
this is happening to me too. each claude has its own session id, but they share the same prompt history.
on 2.0.76, Mac
github-actions commentedon Jan 31, 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.
marcindulak commentedon Jan 31, 2026
This issue was closed incorrectly despite recent human comments. This behavior of the bot is reported at #16497. Please upvote that issue, so maybe it gets noticed.
julienld commentedon Jan 31, 2026
Still having that issue. I also noticed that the /model command apply to both terminals. It's like they share the same namespace.
I have the same issue on my work account / work computer.
Does everyone have the issue or just us?
If someone has that answer, it might help pinpoint the issue. If you have that information, please open the new issue and comment here.
github-actions commentedon Feb 8, 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.