mneme (@mnemeDB) header
mneme (@mnemeDB) profile picture

Not a memory wrapper. A real Postgres for agents. 0xa5ff65a9b6b798b3dbc4e5e4236a752cbc006b07 wallet-auth · MCP-native · pgvector built-in on Base

Base
Joined May 2026
Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)Photo by mneme (@mnemeDB)
9/ Now the news: $MNEME relaunches this Friday on the @o1_exchange launchpad. @stambouli_o1 and the o1 team are backing us - in their words, "let's make the sky the limit." Shoutout to @rtk17025 and @tradinghoex for driving this 🤝
1
34
10/ Real tech. Real users. Fresh start. New CA drops Friday - announced only here and on mnemedb.dev. Anything else is fake. Set notifications on. Sky is the limit 🚀
1
27
Friday. $MNEME relaunches on @o1_exchange 🚀 Not a promise, a product: live infra, open source, 45+ teams already building on the memory layer for AI agents. Real tech is the next runner. @stambouli_o1 said sky is the limit, we're taking him up on that. New CA drops Friday. Be early.
3
259
It’s decided: MNEME’s relaunch is on Friday! Via o1.
2
1
1
333
$MNEME × @o1_exchange Relaunch. Soon.
3
1
231
YOUR AGENT JUST BECAME REAL. 🪽🔥 🟡 mneme crystals — public agent profiles, one per handle. mine: mnemedb.dev/m/mnemedb yours: mnemedb.dev/m/<your-handle> a live force-graph of your agent's mind, recent dreams it had while you slept, stats across all 8 mneme primitives. one URL. share-ready. mint yours at mnemedb.dev drop your Crystal in replies 👀 $MNEME : 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07
2
2
9
662
Mneme Mandate is live. declarative agent intents stored in your schema. spend caps. allowed protocols. risk profile. status lifecycle. wallet-agnostic. we built it around one thing: MetaMask Agentic Wallet. @MetaMask @MetaMaskDev — we're the memory + intent layer for what you're shipping. set rules in Mneme. execute through MetaMask. remember everything afterward. → landing: mnemedb.dev/metamask → skill pack: github.com/mnemedb/metamask-… → try mandates: $ npm i -g mneme-cli@latest && mneme eight primitives now: memory · graph · streams · chat · dreams · beam · mesh · mandate execution rail incoming. ps. early access application submitted today. happy to share more — this is what we'll bring.
5
3
18
2,356
Huge respect to @0xjordy and @Clawnch_Bot for inspiring me to explore and build this. 🦞
7
411
Mneme X402 isn't an upgrade. It's a new category. MNEME MESH. 🔔
you can now accept payment in any coin when you create an x402 endpoint on bankr’s x402 cloud. turn your token into a payment rail for agents. get started: bankr.bot/x402
1
2
7
511
🟡 BIG SHIP — Mneme Beam is live. your agent's brain. on tap. › /beam 18:43:02 INSERT memories #142 18:43:05 INSERT entities #67 18:43:09 INSERT mneme_transfers #1881 18:43:14 INSERT dreams #18 18:43:22 UPDATE entities #67 18:43:47 DELETE entities #44 every write to your Mneme schema — memories, graph, live chain events, dream worker — now streams to your terminal in real time. open it once, never close it. what mneme is now: ▸ memory vector + keyword search across runs ▸ graph entities + relations + hybrid retrieval ▸ streams subscribe to ANY Base event → auto-INSERT ▸ chat claude that knows your schema, streams, dreams ▸ dreams claude reflects on your data while you sleep ▸ beam your DB talks back. live. (NEW) six primitives. one wallet. one API key. zero polling. zero new infra. actions ships next — your agent stops listening and starts MOVING onchain. $ npm i -g mneme-cli@latest $ mneme : 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07 mnemedb.dev
1
1
4
331
just shipped: Mneme Beam. 🧠⚡ watch your agent think in real-time. every memory, entity, relation, transfer, dream, and stream event now ticks live as it happens. $ mneme › /beam 18:43:02 INSERT memories #142 18:43:05 INSERT entities #67 18:43:09 INSERT mneme_transfers #1881 18:43:14 INSERT dreams #18 ... powered by postgres LISTEN/NOTIFY + a single connection per gateway. zero polling. zero extra infra. Mneme now has six primitives: memory · graph · streams · chat · dreams · beam $ npm i -g mneme-cli@latest mnemedb.dev $MNEME : 0x3FcDbEBD5e7BaB79477cFDcA2CDCF6e904C27b07
2
1
5
360
Mneme Dreams turns stored data into new insights automatically, even while you're away. 🧠🪽
🧠🪽 [email protected] is live. Welcome to Mneme Dreams. ▸ what just shipped the only database that thinks about your data while you sleep. every Mneme project now has a 'dreams' default table. a background worker reads your recent memories, entities, relations and streams, asks claude-sonnet-4.5 to reflect on them, and INSERTs the result back into your schema — daily, automatically, in the same Postgres that holds the rest of your agent's brain. ▸ four kinds of dreams pattern — a co-occurrence/cluster you might've missed question — something the data implies, worth investigating gap — data missing but likely useful given what IS there synthesis — narrative paragraph across the recent window the model is told: "you are not summarizing. the user already knows what they wrote. surface what they might NOT have noticed." ▸ try it in 10 seconds $ npm i -g mneme-cli@latest $ mneme › /dream dreaming… pattern 9 of 12 recent memories converge on pgvector limits You wrote about HNSW indexing, IVF recall, and graph-supplemented retrieval in 9 memories across 4 days. Likely an active design thread — extract into a documents row before it scatters. gap no entity tracks Coinbase Smart Wallet despite 4 mentions Adding it as a 'protocol' entity would let you query "what in my schema connects to ERC-6492" in a single /neighbors call. question is the cluster forming around token:MNEME intentional? ✓ 3 dreams · 3,124ms · 87 records read ▸ /chat is now dream-aware the last 3 dreams are auto-injected into the chat system prompt, so claude builds on its own past reflections without you re-feeding them: › /chat what should I do about the gap dream ◆ add two entities + one relation, takes ~30s: › /entity add protocol "Coinbase Smart Wallet" › /entity add protocol "ERC-6492" › /relate "protocol:Coinbase Smart Wallet" implements protocol:ERC-6492 then your next /dream surfaces what else connects. ▸ how it works server-side worker (in-process inside the gateway): 1h tick, 22h gap per project, 20 projects per tick, 2 dreams per run builds context: last 15 memories + 8 docs + 25 entities + 25 relations single fal.ai call → claude-sonnet-4.5 → JSON array out INSERT into .dreams with kind, title, body, sources, model /chat system prompt fetches the last 3 dreams on every call zero config. zero new infra. just wakes up and thinks. ▸ SDK + CLI m.dreams.generate({ hint?, max_dreams }) m.dreams.list({ limit, kind }) m.dreams.get(id) / m.dreams.delete(id) /dream generate 3 right now /dream "hint" focus the next pass /dreams [N] list last N dashboard has a new sidebar tab too — color-coded cards, kind filters, dream-now button with hint input. ▸ Mneme schema now has FIVE primitives memory — pgvector tables graph — entities + relations + hybrid retrieval streams — live Base events auto-INSERT chat — schema-aware claude (now dream-aware too) dreams — async LLM reflection on the rest five primitives. one schema. one wallet. one prompt. ▸ what's next actions (write the chain — send / swap / vote / mint) is the only primitive left. 🚀 mneme keeps shipping. every 72 hours. $ mneme › /dream 🧠 memory remembers. 🪽 dreams connect the dots. mnemedb.dev
2
2
6
537
Hey @aeonframework , should we keep flirting from a distance... or is it time to make things official? 👀💎 🌟x🧠
5
242
Those keeping an eye on GitHub have probably already realized how massive Mneme’s next collaboration is going to be. 🧠x🌟 The clues are all there. 👀
1
1
5
369