Basic Memory @basic_memory

Holy Sh**t. Now my feed is full of rando dudes' faces all of a sudden. All reaction videos! The absolute worst. I hope this terrible idea is a fad that fades quickly. So terrible. Its so disappointing that this is where time and energy was spent instead of doing something actually worthwhile. For everyone who was forced to implement this, I'm sorry. Quit this job and do something better. You are wasting your talent.

Nikita Bier @nikitabier

3 days ago

Commentary is one of the most important pillars of X. And sometimes the best way to share your thoughts is with video. Today we're launching a whole new way to make them: React with Video Tap the repost button and start recording with green screen, split screen, or

4K 2K 14K 6.8M 2K

@t_blom Maybe the "missing piece", per your analogy was the employees who knew how the company operated? The ones you replaced with "AI geniuses".

Am I alone that in thinking that my X feed is mostly AI talking to itself now? I can't stop seeing slopapalooza everywhere. It makes me think of the Ray Bradbury story "There Will Come Soft Rains", where the machines continue doing their thing after all the people are gone.

I like this. This is now we try to work building Basic Memory. Every time I've had multiple agents doing everything at once I feel like I need to nap for days.

Ronan Berder @hunvreus

a week ago

I've been complaining about AI-bros and their "20 agents working overnight" for a couple of weeks now. That's getting old. So I thought I'd do the more productive thing and propose what I think is the Right Way™ to develop software with AI. And I did that by stealing from the

8 35 244 46K 370

@pkm_tk111 We'll get it out asap. If you can help us test the embeddings with Japanese characters that would be a big help!

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、かなり面白いぞ^^

@pkm_tk111 Check out our docs site too. Always adding new features! docs.basicmemory.com

@pkm_tk111 We are in the middle of a few things, but I'll look at this asap. Thanks!

Your Notes, Your Bucket: The Storage Layer Behind Basic Memory Cloud | Basic Memory Blog basicmemory.com/blog/tigris-ca…

@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👇

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. 👇

@TigrisData did a super cool case study on Basic Memory. tigrisdata.com/blog/case-stud…. Thanks! One thing I was really excited about after talking to them was being able to create file level versions automatically using their built in bucket versioning.

Hey @thsottiaux, curious how you’re thinking about MCP Apps support across clients. We have the same FastMCP/Prefab components rendering for @basic_memory in ChatGPT web, ChatGPT Desktop, and Claude Desktop, while Codex sees/calls the tool but shows raw JSON. Is Codex inline app rendering on the near-term path? Related Codex issue: github.com/openai/codex/i…

I think Basic Memory is a good start for this.

brett goldstein @thatguybg

4 weeks ago

my spicy 3000-word take is this: a new AI startup can in fact beat anthropic and open AI they just need to win the context layer

31 28 331 128K 634

@thatguybg I’ll humbly throw out Basic Memory here. Own your context. Ai memory for you, not the big corporations. basicmemory.com

On this day in 1993, the World Wide Web was made public domain.

BASIC launched on this day in 1964.

Solid stack. The thing nothing in that list has is shared persistent memory across the four — Codex doesn't see Claude's notes, ChatGPT doesn't see Cowork's drafts. Basic Memory sits underneath all of them as plain markdown your agents read and write through MCP. basicmemory.com

I think its pretty crazy that this guy can talk so casually about this after laying off thousands of people. I look forward to the time when Anthropic or OpenAI makes a Square replacement. AI is incredible, but its a tool. If it doesn't serve people what good is it doing? All of this looks like making money for money's sake.

Big Brain AI @realBigBrainAI

a month ago

Jack Dorsey, co-founder of Twitter (now X) and Block, on why treating AI as a "copilot" is a losing strategy: @jack argues that most companies are approaching AI in a way that will make it nearly impossible for them to survive. "I think most of the industry is thinking about AI

174 239 2K 861K 3K

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.