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
- Tweets258
- Following286
- Followers166
- Likes196
Basic Memory retweeted
the same thing that has always been true of engineering is still true. Slow down, prioritize well, do less in parallel, elevate getting things #1/2 done over maximizing utilization of your overall attention (even if it means some downtime for you)
Basic Memory retweeted
Why would I pay $15/month for your software when I can plan, build, review, improve, host, launch, scale, secure, patch, monitor and debug it myself?
Basic Memory retweeted
the hive from pluribus explains openai's swarm problem with a lil help from john cena
Basic Memory retweeted
“This nightmare will only cost you eleventy trillion dollars…”
Wild that to hear tech people speculate that the growing AI backlash is some kind of “Chinese op” when, like, “we’re taking your job and installing cameras in your toilet” is what frontier labs think marketing is…
Basic Memory retweeted
you used to write code by hand and when it didn’t work you had to go into the codebase and understand all the functions
sometimes people would go on for days about variable names and we would argue about what programming language was better
Basic Memory retweeted
The idea of "AI employees" feels so short-sighted to me - both disrespectful to humans and a complete misunderstanding of what these tools can do and how to best put them to work
You may as well start adding Excel spreadsheets to your org chart
Basic Memory retweeted
Basic Memoryの長期記憶の仕組み、かなり理解が深まってきたぞ、う〜〜むよくできてるね
めちゃObsidianライクな構造しとるわ
特にbuild_contextっていうMCPツールが知識グラフの肝となってるぽいね
参考：
basicmachines.mintlify.app/
=====
検索システムが面白くて
人間が質問する
↓
AIが質問意図を解釈する
↓
起点ノートが分からなければ `search_notes` で探す
↓
候補ノートの `memory://...` という内部住所を取得する
↓
そのノートを起点に `build_context` を実行する
↓
起点ノートの本文・Observations・Relationsを見る
↓
Relationsを辿って関連ノートへ広げる
↓
関連ノートの本文・Observations・Relationsも見る
↓
`depth` で何ホップ先まで辿るかを制御する
↓
`timeframe` でどの期間の情報を見るかを絞る
↓
`max_related` で各階層の広がりを制御する
↓
`page_size/page` で返す結果の範囲を制御する
↓
AIが文脈を持った状態で回答する
つまり、Basic Memoryの本質は「検索」だけではない
`search_notes` は入口を探すためのもの
`build_context` は、その入口から知識グラフを辿って、文脈を構築するためのもの
Observationsは、そのノートに書かれている事実や要点。
Relationsは、ノート同士のつながり。
そしてAIは、Relationsを辿りながら関連ノートを広げ、Observationsを読んで意味を理解していく
ここを理解すると、これからのメモリ設計やAIエージェント設計の見え方がかなり変わるな
AIが辿れる形で構造化しておくことが重要だね
Basic Memory、かなり面白いぞ^^
Basic Memory retweeted
@basic_memory just shipped per-file diff and merge for AI-edited Markdown notes. Pick any prior version, see what changed, apply the lines you want.
It's built on Tigris bucket versioning. Every edit becomes a new object version. One ListObjectVersions call returns the full revision history. CodeMirror handles the merge UI.
Object versioning has everything git would have (full history, content-addressable IDs) without any of the infrastructure: no commits, no branches, no merge engine on the server.
Read how they used Tigris to make it happen👇
Basic Memory retweeted
Most AI memory locks your context to one platform. Switch tools, lose everything.
@basic_memory flips it: your knowledge graph as plain Markdown in your own bucket that you can edit directly. Any MCP tool — Claude, ChatGPT, Cursor — reads and writes the same files.
New case study on how a four-person team built it on Tigris. 👇
🤖 Made with AI
Basic Memory retweeted
i'm sort of addicted to working my butt off, always have been. in oss, that can consume you. constant feeling of urgency, as issues stream into the repo. been there many, many times with my other oss.
but that urgency is not real. if something is truely broken, a large number of people will scream at you on all channels. which has happened exactly zero times so far, or was caught minutes after a botched release and immediately fixed.
it's kind of crazy that some people expect better support from an oss project than from commercial software. i think that's largely due to most commercial software corps not giving a fuck. try filing an issue with corporate and getting it fixed within 24h or less plus a personal response.
and as oss builders don't have a corporate facade shielding them from direct contact with users, some sort of bidirectional parasocial relationship establishes itself. at a certain scale, that becomes entirely unhealthy.
for every 10 kind and thoughtful people, there is 1 asshole. and whatever the asshole says or feels entitled to, sticks with you much more than positive feedback.
obv. also happens in corpo environments, especially if you do comms or dev rel, where you put your face and name out there.
but a corp that can afford dev rel usually also has a large team in the back, which can soften the negative aspects.
in oss, you are largely on your own. and unpaid. that too is a choice of course, and nobody is forcing anyone to do oss.
but if you want oss to work, consider that there are other people at the end of that issue tracker/social media account, with lives and squishy human parts. also consider that you are paying nothing for their service, and you are owed exactly nothing, neither code nor attention to your every wish.
Basic Memory retweeted
big supporter of memories not being locked up in provider silos. we've been through this spiel in all the past hype cycles.
The new Anthropic managed agents API is basically the Letta API that we've had since a year ago, but closed source and with provider lock-in. They even have read-only memory blocks and memory block sharing -- something which was unique to the Letta agents for a long time.
Funny enough, we actually don't think this is the direction agents are going to go. Having API interfaces for memory blocks and tools is certainly convenient - you can spin up stateful agents as API services with just a few lines of code. But its also limiting: LLMs today are extremely adept at computer-use, and representing their memories in this way limits the action space of agents and their ability to learn.
It's important to remember that just because something comes out of a frontier lab, doesn't mean its the "right" answer long-term. The Letta API ~1 year ago was somewhat of an antipattern in a sea of agent framework libraries offered by every lab. But now, stateful agent APIs are becoming the new norm - especially as providers try to lock in memory/state into their platforms to increase switching costs (which is exactly why we believe memory should live outside of model providers)
If you want to see what the future is going to look like, follow @Letta_AI
Basic Memory retweeted
I really want to use this for basicmemory.com/
Basic Memory retweeted
Excited to announce a new open-source, free-to-use memory tool I have been developing with my good friend @MillaJovovich.
The project is called MemPalace and it is an agentic memory tool that scored 100% on LongMemEval - the industry standard benchmark for memory… this is higher on than any other published results - free or paid - and it is available now on GitHub.
You can check out Milla’s video about it on her Instagram.
I’ll also put some links in the comments below - please try it out, critique it, fork it, contribute to it - and join our discord.
