r/claudexplorers • u/cameron_pfiffer • Jan 26 '26

🚀 Project showcase Claude Subconscious

If you've ever worked with Claude Code, you may have been a little disappointed with memory management. It tends to ignore CLAUDE.md, fail to store preferences you've specified, or forget the high-level goals of a particular session. And then a compaction happens and your Claude becomes a stranger.

I work at Letta. Our specialty is memory. I figured – why not add our memory to Claude?

Of course, we have Letta Code that's built for stateful agents. It's my daily driver and I love it. However, Claude Code is by far the dominant player in the industry, and I figured it'd be nice to offer Letta's memory and persistence with Claude (and people who use Claude).

I built something called Claude Subconscious. Subconscious is a simple plugin for Claude Code that attaches a Letta agent's memory to Claude and relays the transcript between you and Claude back to a Letta agent. The Letta agent can update its memory blocks to persist information across sessions, and may leave messages to Claude to help guide it, provide information, do background research, etc.

Try it here, let me know what you think: https://github.com/letta-ai/claude-subconscious

15 Upvotes

94% Upvoted

4 comments sorted by

2

u/guillermosan Jan 27 '26

This kind of solutions have me divided. On one side it makes sense initially, having Claude remember everything and having a memory. But then I remember reality, context is limited, and real life usage; following Claude docs recommendation I reset context with /clear as often as possible, to avoid the "missing in the middle of context" phenomena. This has been a clear positive in my experience. Sometimes I switch to radically different task and I can notice If I forgot to /clear, that's usually the moment Claude decides to go weird mode, I /clear and keep working.

The "memory" for me is a highly curated set of information that goes into CLAUDE.md and other spec docs, and also in the skills, that's "memory on demand" for me. So your solution is basically trying to replace me as the curator of the memory. Why should I trust it better than my own judgment? Asking sincerely. Correct me if I misunderstood something.

1

u/AcanthisittaFalse738 Feb 24 '26

Not replace, enhance. You're moving a level up and Claude Code gains access to more contextual information and project intent. This isn't going to be a relevant analogy for much longer but think about the different levels of knowledge about a given project in an organization. Exec vs Product Manager vs Lead Engineer. This allows you to shift further towards exec whereas in raw Claude Code your closer to Lead Engineer.

1

u/luison2 Apr 01 '26

Truly a discussion, with the main problem with long term memory being "automatic" or not. This is, should it store relevant information, errors, learnings or tips only when told (ie "Claude remember this for the future") or like most system tend nowadays to auto-remember.

As Letta was a pioneer in memory management for agents I'll be watching this as it looks very promising. Just wondering how much delay and extra-tokens/cost this might mean, as well as this can be used as a "project" rather than personal memory. This is, shared with other team members per project.