[Feature Request] memorize in background / queue

Status Closed — not planned
Maintainer reply None cached
Activity 7 comments · opened Aug 2, 2025 · closed Jan 8, 2026

Right now when we want to add things to the memory with the # hashtag, we cannot press enter until the system is done talking/thinking/acting. Please make it so that we can add information to the memory file in the background or at least submit them to a Queue.

By the way I love how if you manually change the memory file claude picks up the changes while it is working and acts on it accordingly!

View original on GitHub ↗

7 Comments

github-actions[bot] · 1 year ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/535
  2. https://github.com/anthropics/claude-code/issues/3099
  3. https://github.com/anthropics/claude-code/issues/1813

If your issue is a duplicate, please close it and 👍 the existing issue instead.

🤖 Generated with Claude Code

pannous · 1 year ago
  1. The first link is a near duplicate but we are a special case and it's not sure if that was included or intended.
  2. The second link is rather unrelated
  3. the third link is a much broader concept (and slightly orthogonal)
paulirwin · 1 year ago

+1, this really interrupts the queue-based flow. It also would be nice if it could adapt to what it memorizes in this way in real time, for subsequent changes it's working on.

github-actions[bot] · 10 months ago

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.

pannous · 10 months ago

dear bot, don't close yet

github-actions[bot] · 9 months ago

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.

github-actions[bot] · 9 months ago

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.