Repeater22746 · HN

ContextVault – Shared memory layer for your AI and your team

snakaya · HN

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

@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

@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

kitforai · GitHub

kitforai Kit for AI developer hub — official SDK, Claude Code plugin, MCP setup, and llms.txt.

ximihoque · HN

Collaborative context-sharing memory platform for agents and teams

dariusmonsef · HN

OzBrain, a shared brain for knowledge between agents and your team

@AudaxicTech · X

Memory for AI agents, most affordable in the industry

@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

u/clausyn · Reddit

I built Pastepile because I was tired of re-explaining the same context to Claude and Cursor I originally built Pastepile as a fast way to share code, logs, configs, and text without creating an account. While using AI coding tools, I kept running into another problem: every new session meant explaining the same architecture, decisions, debugging history, and project context all over again. So I added an MCP server that lets Claude, Cursor, Windsurf, VS Code, and other MCP clients save us