[BUG] Auto-Memory folder not opening on Windows in /memory command
Status Open
Reported on v2.1.74
Maintainer reply None cached
Activity 8 comments · opened Mar 12, 2026
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?
Auto-Memory folder not opening on WIndows when selecting "open auto-memory folder" in /memory command
What Should Happen?
The Auto-Memory folder should open in explorer
Error Messages/Logs
Steps to Reproduce
- Type /command
- Select "Open auto-memory folder"
- Nothing happens
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.74
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
6 Comments
Bump, currently experiencing this issue on 2.1.81
Bump, also experiencing this issue on 2.1.104. Very annoying as accessing memory from files is clunky since they're saved to random ass values. All I get is a green checkmark when I select "Open auto-memory". :(
This is still happening more than a month and a half later (v2.1.157)
Not stale.
Still facing with it
I'm hitting this same issue. Selecting "Open auto-memory folder" from /memory does nothing — no file explorer window opens, no error shown.
To confirm it's not a path/permissions problem on my end, I ran explorer.exe "<the same folder path>" directly from a shell and it opened the folder without any issue. So the folder exists and is accessible — the failure seems isolated to how the /memory menu action itself invokes the "open folder" behavior.
Environment: