TWITTER_ARTICLE

Supermemory launched a Claude Code plugin on 2026-01-30 that aims to persist…

Brief

Supermemory's new plugin for Claude Code is designed to give the coding agent persistent memory across sessions, addressing a common complaint that users must repeatedly restate coding conventions, architecture constraints, and personal preferences every time they reopen a session. The company says the system builds both episodic and static user profiles, allowing Claude Code to remember ongoing work, prior bug fixes, and evolving style preferences. Technically, Supermemory argues this goes beyond conventional RAG by using a hybrid memory architecture that extracts structured facts, tracks changes over time, and retrieves context based on relevance rather than simple similarity. On its internal benchmark reference, LongMemEval, the company reports an 81.6% score versus the 40-60% range it attributes to typical RAG systems. The plugin also differs from Supermemory's MCP integration by automatically injecting a user profile at session start and automatically capturing conversation turns, giving the system more reliable data to store and recall later.

Why it matters

Supermemory launched a Claude Code plugin on 2026-01-30 that aims to persist developer-specific context across sessions, including coding preferences, codebase details, team decisions, and recent goals such as reducing costs or migrating Postgres providers.

Key details

  • The plugin is built on Supermemory's "hybrid memory" approach, which the company says extracts facts, tracks how they change over time, maintains a current user profile, and retrieves relevant context rather than relying only on standard RAG-style similarity search.
  • Supermemory cites an 81.6% score on LongMemEval for its memory system, compared with the 40-60% range it says is typical for RAG systems on memory-specific tasks.
  • Compared with Supermemory's earlier MCP approach, the new Claude Code plugin adds two capabilities the company says MCP could not guarantee: automatic user-profile context injection at session start and automatic capture/storage of conversation turns for future recall.
  • The post positions the plugin as a solution to repetitive setup work in Claude Code, such as repeatedly restating constraints like "the user service connects to Postgres, not MySQL" or preserving preferences like avoiding certain refactors or using fewer React useEffect hooks.
Cleaned source text

title: @DhravyaShah: Today, we are launching the Supermemory plugin for Claude Code!...

author: DhravyaShah

content_type: twitter_article

published: 2026-01-30T00:56:54+00:00

source_url: https://x.com/DhravyaShah/status/2017039283367137690

word_count: 701

Today, we are launching the Supermemory plugin for Claude Code!

> TLDR: You can use supermemory in claude code now.

> https://github.com/supermemoryai/claude-supermemory

Claude code has genuinely changed how I work. But there's this one thing that drives me crazy... Every day, I have to explain the same exact things to claude code. I have to keep repeating my coding style, preferences, etc.

"The user service connects to Postgres, not MySQL."

"Don't refactor that function—I know it looks ugly but there's a reason it's like that."

Claude writes great code. Then I close the session, and it forgets everything.

Next day? Groundhog Day. Again. We have built all of these workarounds - Massive CLAUDE.md files, copy pasting the context at the start of every prompt, maintaining "memory" documents that feel like the agent is never looking at them..

After our success with the clawd bot plugin and the opencode plugins , we knew that we're in the right spot to do something about it.

So we built something.

At Supermemory, we've been working on memory infrastructure for AI agents for a while now. We power memory for tens of thousands of AI applications. And we kept hearing the same thing from developers: "I wish my coding agent actually remembered stuff."

Today we're launching a Supermemory plugin for Claude Code.

The idea is simple: Claude Code should know you. Not just for this session—forever. It should know your codebase, your preferences, your team's decisions, and the context from every tool you use.

Here's what that actually looks like in practice:

it remembers where you left off

We utilize user profiles in supermemory to create a profile of you, which contains both episodic content about you, as well as the "static" information. Claude knows that this week, your entire goal is to drive the costs down and migrate to another postgres provider.

it learns your style

Instead of writing slop code just like everyone else, it will learn as you use it - like "Use less useEffects!!!". https://x.com/DhravyaShah/status/2016027476787679598?s=20

Claude code will now remember exactly how you fixed an error last time , and this knowledge compounds into an agent that feels truly insanely customized for your use case... slowly.

it knows YOU

It knows that you're a founder, or college student, or a system engineer, and will suggest tools and practices accordingly. Claude code learns your requirements, your style, your taste. Because taste is the #1 thing that differentiates good engineering vs bad.

The technical piece that makes this work is what we call hybrid memory.

Most "memory" solutions for AI are just RAG—retrieve some similar documents and stuff them in the context. That works for knowledge bases. It doesn't work for memory.

We built a system that actually extracts facts, tracks how they change over time, builds a profile of you that's always current, and retrieves the right context at the right moment. Not just similar context—relevant context.

The benchmark we use for this (LongMemEval) puts us at 81.6%. For comparison, most RAG systems score in the 40-60% range on memory-specific tasks.

How is this different from the MCP?

The supermemory MCP is great for things like this, but comes with one big limitation: We cannot control when claude code chooses to run the tools. This means that we have no control / data point to learn things from, and a memory system is only good if there's things to recall later.

This plugin adds:

Context Injection:

On session start, a User Profile is automatically injected into Claude's context

Automatic Capture

: Conversation turns are captured and stored for future context

Both of these things were not possible with the MCP before.

So, go ahead and install it! Instructions here https://github.com/supermemoryai/claude-supermemory

Feel free to let us know if you like it, you can also join our community https://supermemory.link/discord for any feedback!

Posted: 2026-01-30T00:56:54.000Z

Engagement: 2532 likes, 242 retweets, 91 replies