@v1b3_x · X

I built a persistent, Git-like memory engine for LLM agents so they never lose context across session. works with ClaudeDesktop <—> Claude Code <—> Codex

@Nikborneklint · X

Shipped today: AEGIS Code's Terminal picker now includes @xai's grok CLI alongside AEGIS Code & Claude Code — all sharing one memory bridge via MCP. Local memory's free forever. #grokbuild @elonmusk

12ziyad · HN

Shared memory graph for Claude and ChatGPT, over MCP

@vitverb · X

hi :) One tap back to the work you meant to finish. No tasks to manage. Nothing to set up. Local-first

u/OrganicArgument2092 · Reddit

I shipped Lodekeep: portable memory for AI agents that follows you across Claude, Cursor, and ChatGPT Every new AI chat starts from zero. Claude, Cursor, ChatGPT all forget my stack, my decisions, the gotchas I already solved, so I kept re-pasting the same context every single session. I got sick of it and built Lodekeep. You capture a decision, preference, or lesson once, and it's recallable in every future session across every MCP client (Claude web + desktop, Claude Code, Cursor, Gemini

snakaya · HN

Vibsync – One Shared Memory for Claude Code, Cursor and Codex (MCP)

ihamilton7 · HN

Cogni: MCP memory for LLMs, with no LLM in the retrieval path

@SouravDaaa · X

- End to end personalised memory retrieval in 10ms. Would love some feedback here

@StuSim · X

hey Adam, I run , lightweight agent memory

@dorikuio · X

AI agents have amnesia — Claude Code figures out the codebase, an hour later Codex starts from zero. So I built a shared memory + task board for every MCP agent — Claude Code, Codex, Cursor, Gemini CLI: Is this just my problem? Help me find out.

adjohu · HN

A public AI whose memory is shared across all users

schillingderek · HN

Building Table Canon, an AI Campaign Memory Engine for TTRPGs