Blog·Engineering

We added supermemory to Claude Code. It's INSANELY powerful now...

By Dhravya Shah·3 min read

Orange banner pairing the Claude Code and Supermemory logos with the caption "stateful coding agents"
Supermemory claude code

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

TL;DR
You can use supermemory in claude code now. - github.com/supermemoryai/claude-superme…

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.

Cover graphic pairing the Claude Code and Supermemory logos: "Supercharge your Claude Code with Supermemory."

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!!!". x.com/DhravyaShah/status/20160274767876…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.

Developer: "I need to add rate limiting to this endpoint"
Agent: "Based on the rate limiting you implemented in the payments-api 
last month (using sliding window with Redis), and your preference for 
the express-rate-limit middleware, here's an approach that matches 
your existing patterns..."

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

LongMemEval-S bar chart: Supermemory beats other systems across all categories with 85.4% overall accuracy

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.Memory isn't just "find similar stuff." It's understanding that when you say "the auth bug," you mean the specific issue you've been debugging for three days. It's knowing that your preferences have evolved—you used to like classes, now you prefer functions. It's tracking that a decision was made, then revisited, then changed.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 github.com/supermemoryai/claude-superme…

Claude Code plugins marketplace showing the installed supermemory-plugin for persistent cross-session memory

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

  1. An update to supermemoryWe've discontinued the supermemory company brain and Nova. Everyone who was charged has been refunded, our MCP and plugins continue to run, and we're going all in on the memory engine.
  2. SMFS: making agentic retrieval 55% cheaper AND more accurateWe launched SMFS.ai (Supermemory Filesystem) a few weeks ago, with a simple bet: We can redesign the filesystem specifically for agents, with special files, structures, and commands that it can use for it's tasks. Today, SMFS is used by hundreds of companies to power their agents.
  3. Introducing Dynamic Dreaming: supermemory now connects the dots, for you.Dreaming is magical. TLDR: We're launching Dynamic Dreaming in supermemory today, which automatically works if you're using supermemory in any way - API, OpenClaw, Hermes agent, etc.
  4. Dear reader, we just made supermemory insanely cheap... the Context CloudWhen I first started building supermemory, I had one goal: To build the best memory system for AI. I would talk to customers, and find out that memory was not the only thing they needed - They were all setting up 7-8 different vendors at the same time.
  5. Introducing @supermemory/tools v2.0.0Today we're releasing v2.0.0. This release unifies the API across all agents sdk integrations from AI SDK to Mastra, makes conversation identity a first-class concept, and ships with memory saving on by default.
  6. supermemory will make your Hermes-agent crazy powerfulToday, we are launching supermemory support to your Hermes agent TLDR: you can use supermemory now in your Hermes agent, it totally free to get started - https://supermemory.ai/docs/integrations/hermes In case you missed it: Hermes Agent is a self-improving AI agent from Nous Research.
  7. Solving the Precision-Recall Tradeoff: Search Result AggregationWhen you're building memory for AI, search is your foundational layer. The way search generally works is straightforward: the user defines a query, and then sets a limit (top-K) on how many search results they want returned. Usually, this is set to 10 or 20.
  8. Infinitely running stateful coding agentsWe built a plugin for Claude Code and OpenCode that gives your coding agent persistent memory. It remembers your preferences, learns your codebase, and never loses context mid-conversation. The result is an agent you can run for months without starting over.
  9. Why everyone is complaining about OpenClaw's memory (it sucks) - and why supermemory fixes it.TLDR: Today, we are releasing a new version of our openclaw plugin - https://github.com/supermemoryai/openclaw-supermemory. This post is going to be a bit technical, so bear with me (or bookmark for later!) In this post, I will talk about what we do about OpenClaw memory, and how we fix it.
  10. Clawd / Molt bot's memory SUCKS. We gave it supermemory.I'm the founder of supermemory. Clawd/Molt bot is blowing up right now, with many, many use cases. I set it up, too, and have been using it through telegram. TLDR: just go to https://supermemory.ai/docs/integrations/clawdbot to set up supermemory for your clawd bot.
  11. Catch up with our UNFORGETTABLE Launch WeekOver the last year, one belief has guided almost everything we’ve built at Supermemory AI becomes meaningfully useful only when it remembers. Memory shouldn’t be something developers rebuild from scratch. It shouldn’t be fragile, expensive, or trapped inside a single tool.
  12. Empowering the Next Generation of Founders: Supermemory Startup ProgramIf there’s one thing we’ve learned while building Supermemory, it’s that most startups don’t fail because they didn't build features; they fail when infrastructure slows them down, or they built too slow.
  13. Building code-chunk: AST Aware Code ChunkingAt Supermemory, we're building context engineering infrastructure for AI. A huge part of that is dealing with code: ingesting repos, understanding structure, and making it searchable. The problem is that most code chunking solutions are terrible. We built code-chunk to fix this.
  14. Supermemory raises $3 million with the best memory engine for LLMsToday, I am excited to announce our first funding round to accelerate our mission of building an interoperable, scalable and reliable memory for LLMs and agents. Memory is one of the hardest challenges in AI right now.
  15. Unified Memory That Works Where You Work: Your Second Brain With SupermemoryHi everyone, I’m Dhravya, the founder of Supermemory. I want to start with a little story behind why this product means so much to me. You can also skip straight to what it is and how it works below.
  16. Supermemory just got faster on PlanetScaleWhat is Supermemory? Supermemory completes the missing part of the LLM puzzle: memory. Just as memory is crucial for human intelligence, it's essential for truly intelligent AI systems.
  17. Faster, smarter, reliable infinite chat: Supermemory IS context engineering.People are obsessed with prompts and prompt engineering. Sure, what you say is important, but what the model knows when you say it is the difference between a stateless text generator and an intelligent AI system. In short, context is the most crucial component.
  18. We solved AI API interoperabilityOne API to rule them all, One spec to find them, One library to bring them all and in the TypeScript, bind them. When we were building the the Infinite Chat API, initially, we only supported the OpenAI format. This was fine, until a lot of our customers started asking, asking for more.
  19. The UX and technicalities of awesome MCPsLast month, we launched the Supermemory MCP, mostly to test our own infrastructure and get some initial traction. It blew up. To my absolute surprise, the initial launch itself got half a million impressions (!!!). Then, we launched and got #2 on ProductHunt too.
  20. Architecting a memory engine inspired by the human brainLanguage is at the heart of intelligence, but what truly powers meaningful interaction is memory — the ability to accumulate, recall, and contextualize information over time. Large Language Models (LLMs) have mastered language, but memory remains their Achilles’ heel.