Get Mochi
Download the app from the latest release, open it, and you have a workspace. Nothing to sign up for and nothing to configure.
Running it from a checkout instead needs Node 24 or newer.
Docs
Download it, point an agent at it, name a workspace. That is the whole setup.
Download the app from the latest release, open it, and you have a workspace. Nothing to sign up for and nothing to configure.
Running it from a checkout instead needs Node 24 or newer.
In the app. Open Settings — the gear beside your account, at the foot of the sidebar — and stay on the Agents tab it opens on.
It lists the clients it can find on this machine: Claude Code, Claude Desktop, Codex, OpenCode, Hermes Agent and OpenClaw. Anything it cannot find is marked Not installed rather than hidden, so a client you expected to see and do not tells you something. Press Connect on the one you use, then restart that client so it notices.
Connecting writes Mochi into that client’s own MCP configuration, alongside whatever is already in it. Nothing else in the file is touched, and the panel names the other servers it found there so you can see that for yourself. Disconnect removes just that entry.
For a client that is not in the list, the same panel shows the command to add by hand, with a button to copy it.
The agent talks to Mochi over a pipe on your own machine, so there is no port to open, no token to paste and nothing in between.
Nothing is created until you name it. Press New workspace, give it a short name — a name, not a path — and pick what to start from: an empty workspace, or one of the samples (CRM, HR, Inventory, Projects) which arrives with tables and a few rows in it, so there is something to look at straight away.
Each workspace is a separate database file on your machine. Or ask the agent, once it is connected, and it does the same thing:
Create a workspace named sales-demo, seed the CRM template, and open it.
Ask the agent to open a table and it opens the one for the workspace you are in. It cannot be handed a path or a link, so a prompt can never point it somewhere you did not mean.
Your rows are in a file under ~/.mochi, on your machine. Nothing about a row is sent anywhere, and the app works with the network off.
Database files are ignored by Git by default, so nothing lands in a commit by accident.
Every change is attributed to whoever made it, whether that was a person or an agent. Undo puts things back without erasing the record of what happened.
You can take the whole history with you. Open More actions → History and press Export as a Git bundle. What you get is one ordinary file that Git understands on its own — no Mochi needed to read it back:
git bundle verify history.bundle git clone history.bundle history
Download Mochi and start in about a minute. Nothing to set up, nothing to sign up for.