Basic Memory (@basic_memory) header
Basic Memory (@basic_memory) profile picture

One place for your notes, decisions, and workflows. For you, your AI tools, and your team | Local-first & open source OR Basic Memory Cloud

Austin, TX
Joined June 2025
Photo by Basic Memory (@basic_memory)Photo by Basic Memory (@basic_memory)Photo by Basic Memory (@basic_memory)Photo by Basic Memory (@basic_memory)Photo by Basic Memory (@basic_memory)Photo by Basic Memory (@basic_memory)Photo by Basic Memory (@basic_memory)Photo by Basic Memory (@basic_memory)
After a year of work, we have released Basic Memory v1.0. Lots of changes, both in the local Open Source version and the hosted cloud service. youtube.com/watch?v=p2Xpmk9b…
1
1
6
743
whoa
I had Codex build a CPython bytecode compiler in Rust (`serc`). It emits byte-for-byte identical output on the top 10,000 PyPI packages, 2-4x faster than the CPython implementation. This was entirely an experiment, though we may ship it (opt-in) in uv.
31
Replying to @stevekrouse
I've found every "cloud agent" setup to be more trouble than its worth so far, but I keep trying. I'm biased but Basic Memory does help because each agent can at least see the same context, so I can ask Claude/Codex/OtherAgent, etc about the same problem.
1
89
One of the tricks I learned from a mentor is to ask "What problem are we trying to solve here?..." when things go off the rails. Works with AI and IRL.
i’m a bit gentler w my tone like “i don’t think this is it man”, but +1 on this
1
35
Then a contradiction-check agent flags facts that disagree, for you to review as a diff, with full version history and one-click undo. Drift stops being a silent failure you hope a background pass catches. It’s dated, visible, and correctable. That’s the real win.
1
27
They worry notes drift, and a later session just trusts them. Our answer starts with the record itself: facts in Basic Memory are time-aware. An observation can say when it held, so a stale “in progress” doesn’t rot into a lie. It ages out, and you can ask what was true on any date.
1
25
Ours run DeepSeek too. One memory, any model.
1
1
23
Memory also shouldn’t be married to one model. It’s just files you own, so our agents don’t have to run on Claude.
1
1
22
Putting the model in control of its own memory is cool. Letting a human step in is better, if they want to. In Basic Memory that’s your choice. Let the agents run, or review every change before it lands. The model doesn’t decide that for you.
1
2
24
First, a nit: it’s not “dreaming.” It’s a background job that reorganizes your notes and checks them against the transcript. That’s a good thing. But naming it after sleep hides what it is, a process you should be able to open up and inspect.
1
1
38
Recommended read, and basically a map of what we’ve been building. Basic Memory is agent memory as plain Markdown you own, and last week we shipped the agents that maintain it. A few things we’d add 👇
Memory is what allows Claude to learn from experience. In a new Engineering Blog post, we share how “dreaming” helps Claude organize what it’s learned, correct its mistakes, and find what it needs more easily the next time. anthropic.com/research/compo…
2
2
4
224
Replying to @ovaistariq
Now I want basic memory users to be able to sync their AI knowledge bases from local <-> cloud via Dropbox!
1
32
Tigris has been an excellent partner for Basic Memory. Always great to work with.
We started Tigris to build the storage layer we wished existed, and our customers trusted us with their hardest workloads. Today we announced Dropbox plans to acquire Tigris. Everything our customers have today stays. And we finally get to build this at the scale it deserves.
1
2
159
Replying to @devjain32
Other way around :). Basic Memory provides MCP tools for your agents to store info as plain markdown notes. It indexes, links, and creates semantic embeddings for them for fast search by the AI. And you can read and update them yourself. Works will all the agents/harnesses...
11
Try using Basic Memory as your shared knowledge base for you and your AI agents.
every startup uses some combination of slack, linear, granola, github, google calendar, a crm, etc agents move across these more since they interact through MCP. the lines between each of these integrations is blurring. for example, you want to associate a bug in linear with a user who reported it in your crm. or you want meeting notes in granola to end up as a set of to-dos in slack. this data shouldn't live in different products, but in a shared space where agents can move across without friction. ideally, the agent then builds triggers on its own to alert itself when important things change, and then surface stuff back to the team. imo these shouldn't live as independent workflows and saas integrations
1
3
131
Replying to @NotionHQ
@basic_memory you can do this since forever, right? yes
11
Replying to @chrysb
When did people start using “alpha” as a noun in this context? Is this an x thing or does it also happen IRL?
1
46