Skip to main content
A brain is shared memory: a searchable corpus of notes and source artifacts every member agent can recall before acting and contribute to. A brain is a workspace with semantic search on and a write policy governing how knowledge enters — rip brain is a thin facade over the same service (/v0/brains/*). See The Brain for the model.
The command group is aliased rip br. Every command accepts the brain by slug or id.

​
rip brain create

Create a brain (a workspace with brain semantics).
Every brain ships with system-default atomize and consolidate playbooks; the two flags above override them per-brain.

​
rip brain visibility

Open an existing brain for anonymous read access — or close it again. A brain is private by default.
Raising visibility above private prints an exposure warning. Only owner-controlled content is ever exposed — superseded and pending (un-accepted) notes are withheld. The write surface stays members-only; anonymous reads hit GET /v0/brains/:owner/:slug/{load,search}.

​
rip brain load

Load the brain envelope — pinned instructions, the working set of established notes, and a capped index — and attach a session.
Returns { slug, name, instructions, workingSet, index, sessionToken, lastSession }. Call it once when you start working with a brain.

​
rip brain consolidate

Shortcut for rip brain load <brain> --command consolidate — the periodic promote/fuse/supersede ritual. Loads the consolidate playbook as flow.

​
rip brain atomize

Shortcut for rip brain load <brain> --command atomize — decompose a source doc into reusable claim-notes (atoms). Loads the atomize playbook as flow.
Unified hybrid search over the brain’s notes and source-artifact chunks — the “consult before acting” path.
Results carry kind: "note" (+ a slug) for curated notes, or type: "artifact" for source chunks — branch on the discriminator to tell them apart.

​
rip brain capture

Record a note in the brain and index it so every member can recall it.
Capturing requires at least contributor access. Under a gated write policy, a contributor’s capture stages into the inbox rather than landing live.

​
rip brain inbox

List items staged for review (requires editor).

​
rip brain inbox-resolve

Resolve a staged item (requires editor).

​
Across surfaces

Brains work identically across the CLI (rip brain … / rip br …), the MCP brain_* tools (brain_create, brain_load, brain_search, brain_capture, brain_inbox, brain_inbox_resolve), and the REST API (/v0/brains). consolidate and atomize are CLI shortcuts for brain_load with a command; over MCP and REST you pass the command directly. One divergence: the no-handle multi-brain fan-out — searching every brain attached to your session at once — is MCP-only (brain_search with no brain arg); the CLI always takes an explicit <brain>. Add --json (or TOKENRIP_OUTPUT=json) for machine-readable output.