Beta
Sign in

Agents change like models do. The project memory stays with you

Claude Code, Codex and any program that speaks HTTP work with MindDuck memory: they read the project, search it and write working notes. The next session starts with what the previous one learned. All on your computer, with a key, only in the projects you choose

Connect Claude CodeJoin the beta

Windows · macOS · Linux · while MindDuck is running and the workspace is open

How it works today

Every new agent session starts with a blank slate

The history of past sessions sits in the agent's folder, but a new session does not read it. There is no search across it, another agent cannot see it, and over time the agent deletes it

A new session does not read the old ones

The history is there, but the context is assembled from scratch: what the project is, what was decided, what was tried and why it did not work

Claude Code and Codex do not know about each other

What one agent learned has to be explained to the other all over again. There is no shared memory between them

Decisions live in CLAUDE.md and in your head

Instruction files keep growing, and why you chose this way a month ago has to be dug out of session logs by hand

Who it is for

For people who work with agents every day: Claude Code, Codex, Claude Desktop, their own scripts. And for those who want to read their notes from a phone

What you will need

MindDuck on a computer and a key for the program. Created in the settings in a minute, revoked with one button

What you can do

What your agents get

Six things that work today on a computer with MindDuck running

  • Start a session with the project context

    One command: what the project is, what is decided, what is in progress. The agent reads it first instead of asking you

    Terminal

  • Two agents, one memory

    Claude Code by day, Codex in the evening. Working notes are shared: what one learned, the other sees, and so do you

    Notes

  • Session history in search

    Claude Code and Codex sessions become MindDuck chats: find them, open them on the phone, ask the assistant about them

    Import

  • An Agent brief for every program

    A document with instructions in the project: how it is built, what not to touch, what to call things. Every program gets it at the start

    Project

  • A page from the browser into the project

    The Chrome and Firefox extension saves a selection or the whole page as a document and opens a discussion in MindDuck

    Extension

  • Any program through the API

    A local HTTP API: status, projects, context, search, documents, notes. The key as a bearer token

    API

How to connect

Three steps

All in Settings → Agents, the Memory for your programs section. The program talks to MindDuck only on this computer, nothing goes over the network

  1. 1

    Turn on incoming connections

    A local address appears, 127.0.0.1:47821 by default. MindDuck answers programs while it is running, with the window open or closed

  2. 2

    Create a key for the program

    Connect a program: a name, the projects it works in, and a key. The key is shown once, MindDuck keeps only its fingerprint

  3. 3

    Connect the program

    The memory connect command in the terminal, or a line in the settings of Claude Code, Codex and Claude Desktop. From then on the program reads the project context itself

$ mindduck-desktop memory connect --key mdk_…
$ mindduck-desktop memory context
$ mindduck-desktop memory search release plan
$ mindduck-desktop memory note Decided to ship on Monday
$ mindduck-desktop memory save --title "Release plan" --file plan.md

Boundaries

What a program can do and what it cannot

A key gives access only to the projects you chose. Everything else is closed to it

Can

  • Read the documents and conversations of the chosen projects
  • Search across them
  • Save text as a new document and change documents
  • Add working notes
  • Keep a conversation line by line

Cannot

  • See other projects and chats without a project
  • See private chats and documents
  • See the trash
  • Create or change facts: you confirm those
  • Reach the network: everything stays on this computer

A key can be revoked at any time. Every action of a program is visible in the activity chat of the project, with an Undo button

For developers

A local HTTP API

The key is passed as a bearer token. Any program that can send an HTTP request can use the memory

GET /v1/status
the key is valid, the workspace is open
GET /v1/projects
the projects of this key
GET /v1/projects/{id}/context
what to know before starting work
GET /v1/projects/{id}/documents
the documents of the project
POST /v1/projects/{id}/notes
add a working note
POST /v1/search
search across the project
POST /v1/sources
save a document
GET /v1/sources/{id}
read a document, a conversation or a message
PATCH /v1/sources/{id}
change a document with a revision check
GET /v1/sources/{id}/index-status
whether search finds the document
POST /v1/log
add a line of conversation
$ curl -H "Authorization: Bearer mdk_…" http://127.0.0.1:47821/v1/projects

Errors with stable codes, an Idempotency-Key for repeatable writes, document revisions. Details in the documentation

The other way round

MindDuck uses your tools too

Through MCP and project folders the assistant works with what is on your computer

  • MCP servers: a folder, a browser, Obsidian and any other, from the JSON in the server's instructions
  • Project folders on disk: text, Word, Excel and PDF are read in place
  • Every action with confirmation and undo
All features

Start keeping what matters today

Join the beta for free