Bring Verity One home.
Seven calm steps to a running local node: install from source, start the node, open the dashboard, start a project, wire your agents, and feed it what you know. No accounts to create, nothing to sign up for. Everything below runs on your own machine.
A node on your machine at localhost:3100. Yours, offline-capable, no cloud required.
Built from source — one line clones the repo and bootstraps the stack. Stable channel is 0.1.2.
Local agents speak to it over MCP. The graph remembers across sessions and tools.
-
Install Verity One
One line clones the repository and runs the local bootstrap — Postgres, migrations, your tenant, config files. It is a source install: you are building from the published commit, not unpacking a binary. When it finishes, it prints the command to start the node.
$ curl -fsSL https://verityone.app/install.sh | bashmacOS: the installer verifies the manifest signature with OpenSSL 3 (macOS ships LibreSSL), so run brew install openssl@3 first if you don't have it — the installer fails closed with that hint otherwise. It also links a vo-mcp launcher at ~/.local/bin/vo-mcp (used in step 4 below, after you build mcp/); if vo-mcp isn't found afterward, add that dir to your PATH.
-
Start the API server
The installer does not start the node for you — run it once now. Foreground (recommended for first run so you can see the logs):
$ cd ~/verity-one && bun run api/src/index.tsOr in the background: nohup bun run api/src/index.ts > /tmp/vo-api.log 2>&1 &
-
Open the local dashboard
With the node running, visit the dashboard in your browser. This is your window into the graph — it lives on your machine, served by the node you just started.
→ http://127.0.0.1:3100/dashboard -
Create or choose a project
From the dashboard, name a project — a workspace, a codebase, a body of research. It is the frame your memories and sources hang on, and the scope your agents read from. Start with one; add more whenever you like.
-
Connect your local agents
Wire an on-machine agent to the local node over MCP. Supported clients today are codex, claude-desktop, and generic. For claude-desktop,
vo-mcp installwrites the config directly. For codex, it prints a pasteable [mcp_servers.verity-one] TOML block — copy it into ~/.codex/config.toml yourself. For generic, it prints a JSON snippet to paste. Local MCP is the authority — what an agent writes here lands in the graph in real time.One-time prerequisite: the source installer does not build the mcp/ package for you, so build it once before vo-mcp install. The installer links a vo-mcp launcher into ~/.local/bin, so once the build finishes the bare vo-mcp command resolves.
$ bun install --cwd ~/verity-one/mcp && bun run --cwd ~/verity-one/mcp build$ vo-mcp install --client codex -
Add what you know
Feed the graph the things worth keeping — notes, files, the decisions behind them. Save a memory from the dashboard, or let an agent record one as it works. Over time these become the truth your agents return to instead of guessing.
-
Enable VO+ OPTIONAL
VO+ is an optional web bridge — a way to carry your memory beyond the desk on demand, for agents that run off your machine. It does not replace the local node and it is not a second source of truth; the web connector simply mirrors what local already holds. Turn it on only when you want it.
When you want the wiring
This page is the calm path. The protocol detail — MCP transport, schema, the hosted connector, advanced flags — lives in the docs. Reach for them when you are ready to go past the on-ramp.
Your local node is the source of truth. Everything else answers to it.