Cross-Agent Memory

Documentation Index

Fetch the complete documentation index at: https://docs.linksee.app/llms.txt

Use this file to discover all available pages before exploring further.

​

The problem with vendor-locked memory

Claude has built-in memory. So does GPT. But they don’t talk to each other. If you use Claude Code for backend work and Cursor for frontend, your backend decisions are invisible to your frontend agent. Switch to Codex for a deploy script? Start from zero.

​

One SQLite, every agent

Linksee Memory stores everything in a single SQLite file on your machine. Any MCP-compatible client can read and write to it. When Claude Code stores a caveat about a Supabase issue, Cursor sees it immediately. When Cursor discovers an API quirk, Codex can recall it.

​

No cloud. No account. No sync conflicts.

• The database is a local file — no cloud dependency
• No account registration required
• No API keys to manage
• Multiple agents can read simultaneously (SQLite WAL mode)
• File-level locking prevents concurrent write corruption

​

What cross-agent looks like

Session 1 (Claude Code):

“Remember: the freee API returns dates in JST, not UTC. Our conversion layer is in src/utils/date.ts.”

Session 2 (Cursor, different project window):

“I’m building a freee integration. What do I need to know?”

Cursor calls recall("freee") and gets:

• The JST date caveat
• The date.ts file location
• Any other freee-related memories from any agent

​

Supported clients

Any client implementing the MCP specification works: