Open source · npm
The dev layer is on npm.
Everything you need to build on Mnemosyne OS is published under the @mnemosyne_os scope, MIT-licensed. The packages talk to the memory on the user’s machine. Nothing here calls a cloud.
Start here
One command scaffolds a working cartridge:
npm create @mnemosyne_os/appThe packages
All of them under one npm organization — npmjs.com/org/mnemosyne_os ↗
@mnemosyne_os/sdk
Build cartridges against the local memory runtime. Ingest, query and ask, under FGAC, over WebSocket or IPC.
npm i @mnemosyne_os/sdk View on npm ↗ @mnemosyne_os/create-app
One command gives you a running cartridge, from the official scaffold.
npm i @mnemosyne_os/create-app View on npm ↗ @mnemosyne_os/cartridge-sdk
The bridge for embedded cartridges. It sandboxes postMessage for iframe widgets.
npm i @mnemosyne_os/cartridge-sdk View on npm ↗ @mnemosyne_os/mcp
The MCP server. Your AI agents get the vault memory, the resonances and the git context. They also see what the other coding agents on this machine are doing.
@mnemosyne_os/forge
The MnemoForge CLI. It scaffolds sovereign modules for the ecosystem in one command.
npm i @mnemosyne_os/forge View on npm ↗ @mnemosyne_os/design-sdk
Write UI skins for Mnemosyne OS in pure JSON. No TypeScript required.
npm i @mnemosyne_os/design-sdk View on npm ↗ @mnemosyne_os/public-contracts
Public types, Zod schemas and interfaces make up the official integration surface. It carries no business logic.
npm i @mnemosyne_os/public-contracts View on npm ↗ @mnemosyne_os/agent-transcripts
Read what coding agents already write on your disk. The connector format is declarative, and the interpreter never evaluates it.
npm i @mnemosyne_os/agent-transcripts View on npm ↗ @mnemosyne_os/affine-reader
Read a local AFFiNE workspace, SQLite and Yjs, and render its documents to Markdown. It reads only, and needs no native module.
npm i @mnemosyne_os/affine-reader View on npm ↗ What is not there
The core is sealed inside the app.
The dev layer is public and MIT. The memory core is sealed inside the app, on purpose. You build on the SDK, and the memory stays on the user’s machine, governed by them.
@mnemosyne_os/sync reserves the name of the P2P layer to come. Today the package holds a placeholder, not the library.