markdown vs @supermemory
in markdown only memory systems, the agent may have to look through and traverse files to answer things. This is wasteful and slow! The files also get stale really fast, and there's no forgetfulness, updates, etc. The agent has to just look through things.
supermemory is kinda like a dense interconnected markdown system, except that we automatically construct almost an 'instant' file that will directly one shot what the agent needs. That context has the whole history of the thing, removes forgotten info, and even related things that the model should probably know.
This information is dense, fast, and dynamically constructed, so you have a living breathing improving system.
So yes, you should use supermemory instead of markdown
every day I'm even more bullish on how beautifully simple and composable supermemory's architecture is. And this is with incremental improvements throughout years of being with customers and really really caring about THEIR products.
@supermemory will be the default way to do memory in the agents era. There's nothing else that makes sense to me.
a bad memory is a pile of chat turns ranked by similarity. the fact from march sits next to the one from today and both look equally true.
so what is a good memory?
- scoped to a user, project, tenant, or any entity, with reference material kept as documents in that same scope
- written when it's worth remembering, so casual chatter is less likely to stick
- kept as a fact that holds until updated, a preference that strengthens with repetition, or an episode that fades unless it mattered
- related with updates, extends, or derives, so the latest fact wins, history stays, and a guess ranks lower until confirmed
- atomic, time-aware, and willing to forget when the window closes
- attributed to source documents and traceable
That is supermemory.
Big shout out to @supermemory for supporting memories so that the conversational interactions can feel much more personal for returning users.
Without their indexing this wouldn’t be possible.
Releasing Muse Code in beta today. It's a terminal coding agent that takes on complete software engineering tasks across large repos: planning changes, writing code, validating the results. Powered by Muse Spark 1.2, a coding-focused model update.
In personal assistant and chat based agents, 𝚑𝚢𝚋𝚛𝚒𝚍 mode in supermemory can greatly improve your agents performance. Here's why:
Typically in memory systems, the main model, or another model has to figure out what's important to learn - we do this too! But, it's impossible to be able to accurately predict everything important for learning.
In supermemory, learnings are formed for things that are important for future context and needs to stay fresh, or forgotten. But, raw context is also indexed.
If the memories don't include all the information that the model needs, supermemory will automatically add parts of the previous conversations to enrich the context!
In the background, learnings are made with this info, now that supermemory knows that it has importance.
Fun fact: In supermemory we not only learn memories, but automatically index the conversations as well.
Below is an example of how @supermemory works in the Vercel @eve harness.
everything works together in a harmony. Memories are formed in a coherent manner (even for things
Your agents are interchangeable but your context shouldn't be.
@supermemory is the persistent context layer across all your agents
Swap the model and keep the memory!
playin with this beauty today..
@supermemory console just got so much better: playground, scoped memory spaces, the graph, connectors, agent install flows, the whole control surface for a memory layer is here
walkthrough soon!
We are discontinuing our company brain and personal brain products. Everyone affected will be refunded
Now, all the focus is to continue to build our frontier memory API for agents. x.com/i/article/2097…
Super bullish on WebMCP. Much like Tesla FSD meets the world where it is (streets, stoplights, potholes and all), agents *need* to ride the existing WWW infrastructure… WebMCP makes it more efficient.
Some pretty unique wins too. e.g: Next.js dev pages could expose debugging
373 Followers 4K FollowingFounder @nile_squad | Built a 10k+ dev community | Divergent & Creator of things, Delta Agents, Nile Js, Writter, Nextpress, etc | All in for OSS, & AI safety.
1K Followers 990 FollowingDad. Founder/CTO @hellogumbox. We help businesses build production AI systems. Building and launching software products for 20 years. OSS enthusiast.
15K Followers 138 FollowingBuilding the first full-stack AI financial infrastructure | Find our 24/7 Cafes, Events, Bus Routes: https://t.co/y3PCKlqgp8
4K Followers 4K FollowingFounder/CEO of Graphlit (@graphlit): Operational Context Layer for AI Agents 🚀 @zine_ai @dossium 👋 ex-MSFT, PA born, Seattle bred. Dad to dogs/humans