[BUG] # memory shortcut no longer saves to CLAUDE.md
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?
The # shortcut for quickly adding memories to CLAUDE.md files has stopped working.
What Should Happen?
Typing # <memory text> at the start of a message should save that text to the user or project CLAUDE.md file (with a prompt to choose the destination).
Error Messages/Logs
Steps to Reproduce
Description
The # shortcut for quickly adding memories to CLAUDE.md files has stopped working.
## Expected Behavior
Typing # <memory text> at the start of a message should save that text to the user or project CLAUDE.md file (with a prompt to choose the destination).
## Actual Behavior
The # prefix is treated as regular text and no memory saving action is triggered.
## Environment
- Claude Code version: 2.0.74
- OS: Windows
## Steps to Reproduce
- Open Claude Code CLI
- Type
# This is a test memory - Press Enter
- Expected: Prompt to save to user/project memory
- Actual: Message is processed as regular input, no memory save occurs
## Additional Context
This feature was working in a previous version. The /memory command still works as an alternative for manually editing CLAUDE.md files.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.0.74 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Windows Terminal
Additional Information
_No response_
13 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Removed as of 2.0.70 Changelog
<img width="935" height="413" alt="Image" src="https://github.com/user-attachments/assets/843a15ff-38c4-48d3-97ed-ac207bb228ad" />
Can confirm this issue on Linux (CachyOS) with Claude Code 2.0.74.
Environment:
Reproduction:
Typing
# test ruleat the prompt passes through as regular text to the assistant instead of triggering the memory file selector.This worked correctly prior to 2.0.72.
IT was so convenient, please readd it back
It was a hasty decision to remove it. It was a very useful shortcut.
Not only is the feature gone, "just tell her to memorize" doesn't work either:
after 2 minutes no memory added :(
I've been taking this course https://anthropic.skilljar.com/claude-code-in-action, and it must be updated to remove the content regarding memory shortcut which has been used a lot there.
All documentation and online material refers to # being working, also the model thinks it does. This is messy and should be brought back or at least, there should be a clear answer to
> Why is # not workingI also tryed to use
#following the course mentioned by @deerawan and lost some good time until I found this. Does the issue being closed means the#shortcut is gone for good? For now I guess we have to use/memoryI guess…agreed - folks are sharing around that skilljar course and going "whoa I had no idea" and then getting frustrated it's not working. Google says it works. Claude says it works. If you're not going to put it back, you've got to correct all the courses and documentation.
Having said that... having this would've saved me a bunch of time. It feels like such a convenient feature. Any rationale for removing it? Any chance we could have it back?
My favorite part about that command was the ability to choose which CLAUDE.md file the instruction saved to, such as project, local project, or user global.
By default, most
claudeinstances are unaware of and unable to edit files in my user directory, and they shouldn't have that capability. Therefore, this new method makes it much more complicated to add something to the global CLAUDE.md than necessary.Why have you removed this ? It was used several times a day... please add it back
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.