[BUG] Recent activity showing conversations from different projects/sessions
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Description:
I'm experiencing an issue where the "Recent activity" panel in Claude Code
is displaying work from sessions I didn't perform.
What I'm seeing:
In my Recent activity for the Ambassador-Scoring project, I see:
- 12h ago: check bot error (correct - this is mine)
- 12h ago: CMC URL Column Fix (correct - this is mine)
- 14h ago: Debugging Python Web Scraper with Selenium and BeautifulSoup (NOT mine)
<img width="884" height="198" alt="Image" src="https://github.com/user-attachments/assets/c308b488-4563-4c84-a795-1834fa26a460" />
Expected behavior:
The recent activity should only show activities from my own sessions in
this project.
Environment:
- Platform: macOS (Darwin 24.6.0)
- Project: Ambassador-Scoring
- Working directory: /Users/user/Desktop/dev/Ambassador-Scoring
Additional context:
The incorrect activity appears to be from a completely different project
(Python web scraping), while my actual project is related to bot commands,
CMC, and leaderboards. When I asked Claude about it, it confirmed having
no record of working on any web scraper in this repository.
This suggests either:
- Activities are being mixed between different users/sessions
- There's a caching issue mixing activities from different projects
- The activity tracking is incorrectly associating external activities
with my current workspace
What Should Happen?
- 14h ago: Debugging Python Web Scraper with Selenium and BeautifulSoup (NOT mine)
Error Messages/Logs
Steps to Reproduce
open claude cli
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.1 (Claude Code)
Platform
Other
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗