Mnemosyne OS
New The documentation is live: every engine, step by step. docs.mnemosyne-os.io →

Guide · vibe coding

Build like you always do.
Memory is already wired in.

A cartridge is a regular React app. The only difference: the SDK gives you a memory that's already connected, you ingest and query the vault , under FGAC , with no backend to stand up. Here's the process, from prompt to cartridge.

1

Arm your IDE

Tell your assistant (Cursor, Claude, …) to use the boilerplate, @mnemosyne_os/sdk, the MCP server and the llms.txt from the repo. Have it clone a reference MIT cartridge and read its src/, it codes against the real thing, not against its memory.

VS Code Cursor Claude Code Antigravity

The starting prompt:

Prompt Build a Mnemosyne OS cartridge: [describe your app]. Read the llms.txt at the root of github.com/Mnemosyne-OS/Mnemosyne-Neural-OS, clone the MIT cartridge MnemoReader and read its src/. Connect to the vault with @mnemosyne_os/sdk (and the MCP if needed), under FGAC. Follow the reference patterns, don't guess the API.

2

Find the idea, and spot what goes into memory

Before a single line of code, just one question: what does your app need to remember? Notes, decisions, history, entities… That's what you ingest. Everything else is ordinary UI.

3

Ask, and build

Describe the feature; the assistant codes against the SDK. ingest() to write into the vault, query() / ask() to read by meaning, all under FGAC and at limited scope. You iterate exactly like on any other app.

4

Memory is the back-end

No database to provision, no API to host, no auth to wire. The local vault is your persistence, already there, already governed by the human. You get the whole back-end for free, and you never manage anyone's data for them. 

flowchart TB
  A["Your idea"] --> B{"What needs to be in memory?"}
  B -->|worth keeping| C["SDK · ingest()"]
  B -->|everything else| D["Regular React UI"]
  C --> V[("Local vault · FGAC")]
  D --> E["SDK · query() / ask()"]
  E --> V
  V --> F["Answer by meaning"]
  F --> D
From prompt to cartridge: you decide what goes into memory, the SDK does the rest, writing and retrieving by meaning.

Ready?

Download, request your free license, and get started.

The OS is free for personal use; the founder license is free for devs who build, with $5 of cloud credits to test without an API key. The full reference for the SDK, the sandbox covenant and the open-core is on the developers page.

Download, free The developers page

Not up for coding? We build it for you →