[DOCS] instructions for project memory updates from the terminal are not updated or does not covers all cases

Resolved 💬 4 comments Opened Apr 10, 2026 by skala2301 Closed May 24, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://anthropic.skilljar.com/claude-code-in-action

Section/Topic

claude-code-in-action

Current Documentation

You can customize how Claude behaves by adding instructions to your CLAUDE.md file. For example, if Claude is adding too many comments to code, you can address this by updating the file.

Use the # command to enter "memory mode" - this lets you edit your CLAUDE.md files intelligently. Just type something like:

Use comments sparingly. Only comment complex code.

Claude will merge this instruction into your CLAUDE.md file automatically.

What's Wrong or Missing?

when trying on vscode using claude, when following those instructions using # to especify a new context to add in project memory it does not change to memory mode, and do not add it to CLAUDE.md instead if adds that to global memory, this is what i did in the console:

#When working on this code use comments sparingly. Only comment complex code or comment at the start of all functions to give a brief description of what it does. ● Understood. I'll save that as a feedback memory for future conversations. Wrote 2 memories (ctrl+o to expand) ● Got it. I'll keep comments minimal — brief descriptions at the start of functions, and only inline comments for genuinely complex logic. ❯ # When working on this code use comments sparingly. Only comment complex code or comment at the start of all functions to give a brief description of what it does. ● Got it — that preference is already saved from your previous message. I'll follow it: brief comment at the top of each function, inline comments only for complex logic. ❯ Unknown skill: memoy ❯ # When working on this code use comments sparingly. Only comment complex code or comment at the start of all functions to give a brief description of what it does. ● Already noted and saved — I'll follow that comment style going forward. ❯ where did you added it? ● I saved it to your memory file at: ~/.claude/projects/.../memory/feedback_comments.md And indexed it in MEMORY.md: - [Comment style preference](feedback_comments.md) — sparse comments: function-level briefs + complex logic only This persists across conversations so future Claude Code sessions will follow the same preference automatically. ❯ Actually i wanted to add it for this project only ● I'll add it to the project's CLAUDE.md instead — that way it applies to anyone working on this repo, not just your user profile.

and at the end claude sayd:

You're right to question it. Based on what I can find, the # prefix as a "memory mode" trigger doesn't appear to be an actual built-in feature of Claude Code. That
documentation you read may be outdated or describing planned functionality that works differently across interfaces.

What does work:

  • /memory — this is the actual slash command to view and manage your CLAUDE.md and memory files. It lets you select a file to open in your editor.
  • Edit CLAUDE.md directly — just open the file in your editor and add instructions manually.
  • /init — generates a CLAUDE.md from scratch (what we did at the start).

So it's not that you're doing something wrong with the keyboard — the # shortcut likely either doesn't exist as documented, or only works in a specific interface (e.g.,
the web app at claude.ai/code) and not in your current setup (CLI on WSL).

If you want to file this as a docs issue, you can report it at https://github.com/anthropics/claude-code/issues.

Suggested Improvement

give the correct instruction: if entering '#' does not functions, provide another way to enter the mode or explicitly indicate this is not available for all infrastructure or that it depends on your keyboard configurations, some other alternative

Impact

High - Prevents users from using a feature

Additional Context

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗