⚠️ Scheduled upgrade in progress — brethof-brain is moving to its new architecture. Signups and new installs are paused for the moment; nothing is lost and everything returns shortly.

Up and running in 60 seconds

You already own the agent. The only reason setup has ever meant a wall of commands is that no tool has let you just ask for it. Tell your agent "install brethof-brain," and it does the whole job — fetches the client, wires it into your tools, checks its own work. No server to run, no database to stand up, no config files to edit. One plugin, a few hundred lines long, short enough to read end to end if you're the kind who verifies what leaves your machine.

Three steps, one of them optional to read

1. Sign up at brethof.ai/account, copy your API key. The one human step, and it's the same step every application on earth asks for. No credit card on the free plan.
2. Say "install brethof-brain." That's the whole sentence — the one step you don't have to read about.
3. Verify, if you want to. Ask your agent to search memory for anything, even something trivial. A well-formed answer — even "no results" — means it's connected. That's the entire test.

# Claude Code — install the plugin (hooks included) /plugin marketplace add BrethofAI/brethof-brain-client /plugin install brethof-brain@brethof # DeepSeek Harness (dsh) — native plugin from npm dsh plugin --profile main add brethof-brain-dsh # Codex — run the adapter, then trust its hooks with /hooks python3 adapters/codex/setup.py # Qwen Code — same shape python3 adapters/qwen-code/setup.py # OpenClaw, Cline, OpenCode, Kilo Code — one plugin each # Every command, per platform: brethof.ai/brain/docs/

Get your API key Full setup guide

Verify, if you want to. Ask your agent to search memory for anything, even something trivial. A well-formed answer — even “no results” — means it's connected. That's the entire test.

Your tools, one memory

The memory doesn't live in files you have to maintain. It's two stores that work as one: a curated record of the current truth, dense and up to date — and the complete raw transcript of every session, kept whole and searchable by exact words, by meaning, or through the graph of files, services, decisions and errors your work touched. All three folded into one answer. Recall never depends on what survived a summary or fit in a context window. And the memory builds itself. After each exchange, a curator reads the turn and rewrites what's known: decisions saved, changed facts folded in, claims reality has overtaken deleted. Seconds, not sessions. Nothing has to be filed by hand. When you do want something kept on the spot, you say so, and it's saved. Once a week, a healer reads the entire memory at once and does what no single exchange can: merges records that forked apart, absorbs duplicates written months apart, and reconciles the places where memory disagrees with itself.

  • Claude Code — from the Claude Code plugin marketplace — no clone, no pip plugin
  • DeepSeek Harness (dsh) — native plugin on dsh's own extension points plugin
  • Codex — clone the client repo and run it; then run /hooks once inside Codex and trust the brethof-brain entries setup script
  • Qwen Code — clone the client repo and run it; writes ~/.qwen/settings.json setup script
  • OpenClaw — gateway plugin, straight from the registry gateway plugin
  • Cline — native SDK plugin plugin
  • OpenCode — one plugin file into ~/.config/opencode/plugins/ — the same adapter serves Kilo Code plugin
  • Kilo Code — the same plugin file into ~/.config/kilo/plugin/ — CLI, VS Code and JetBrains plugin

Using the GLM coding plan? That runs inside Claude Code — full memory loop, same plugin.

And the things you killed stay dead. Reversed decisions sit in the graph flagged as dead ends, and an agent steering toward one is stopped mid-prompt. Your memory is stored, indexed and searched in the EU — the one exception is a curation pass to a provider whose terms say inputs are transient and never trained on. What leaves your machine: your messages, your agent's replies, its thinking, and one-line markers saying which tool it used. What never leaves: the contents of files it read and the output of commands it ran.

One memory, every agent you run — several at once, or a whole team on the same project. Projects are just names: say one when saving or searching, and it exists from that moment. Rules you set, for a project or for everything, shape how every agent works and load automatically into every session.

How it works →

Hear it when it ships

New releases, real benchmarks and the occasional deep-dive. No spam, unsubscribe in one click.

Everything we build

External:   YouTube · GitHub