# Persistent memory for Claude Code with Weaviate Engram

Date: 8 Oct 2026
Released by: Weaviate

## MediaRelease.co Summary

Weaviate has released an Engram plugin for Claude Code that gives the coding agent long-term memory across repositories and sessions. The plugin captures work history, such as features added, approaches chosen and libraries rejected, that does not belong in a project rules file. Weaviate says Claude can then recall earlier decisions when similar work arises in another project, helping keep codebases consistent without developers tracking every past choice.

## Original release

There's a category of knowledge that never makes it into a CLAUDE.md: what you actually did. The feature you added last week, and the small decisions you made about its shape along the way. The approach you settled on for a tricky change after trying two others first. The library you evaluated and rejected, and what tipped the decision. None of this belongs in a rules file. It's history, not policy. But all of it changes what a good answer looks like the next time you touch that code, or write code somewhere else that has to match it. Claude Code keeps its own notes, but they stay with the project they were written in, and most real work spans more than one. Switch repos, and Claude starts from zero. That's why we built the Engram plugin for Claude Code. It gives Claude a long-term memory that isn't tied to any one repo or session. What you do in one place is remembered, and recalled wherever it becomes relevant again. You install it once, and it catches exactly this layer. How it feels You install the plugin and keep working. Nothing visibly changes on day one. A few sessions later, it starts to. Across sessions You've solved this before. Maybe it was a while ago. Maybe it was in this repo, maybe a different one. You added rate limiting to one service and picked a particular approach after some back and forth. Now you're adding rate limiting to another service, and you've half forgotten what you settled on and why. Claude hasn't. It recalls the earlier change and suggests the same approach, or points out that this case is similar and proposes a variation. Your codebases drift toward consistency without you having to hold every past decision in your head. Source: https://weaviate.io/blog/engram-for-claude-code

## Key details

- Issued by: Weaviate
- Published: 8 Oct 2026
- Publisher country: United States
- Subject country/region: United States
- Topics: AI
- Original source: https://weaviate.io/blog/engram-for-claude-code
- MediaRelease.co URL: https://mediarelease.co/us/mr01541-persistent-memory-for-claude-code-with-weaviate-engram-08102026.html

Original source: https://weaviate.io/blog/engram-for-claude-code
MediaRelease.co canonical URL: https://mediarelease.co/us/mr01541-persistent-memory-for-claude-code-with-weaviate-engram-08102026.html