booboo

Booboo is a "unified operations brain" tool that fuses the wiring, knowledge, memory, agents, and scheduled tasks (crons) of an AI system into a rooted, queryable 3D graph. In contrast, most tools show only one slice: a knowledge graph, an agent flow diagram, a memory store, or a trace view; Booboo fuses them all into a single graph rooted at one point, letting you see and query how the entire system is connected together.

Main capabilities

• Single 3D graph: Structure, knowledge, memory, agents, and automation fused into one rooted, queryable 3D graph.
• Million-node rendering: The viewer supports rendering millions of nodes at 60fps in a browser tab (the repository demonstrates a live view of 50,000 nodes, 4 layers, with no console errors).
• REST + MCP query layer: Query via REST or MCP; MCP runs over stdio, ready to use instantly without a hosted server.
• Command-line tool: A unified booboo command, providing subcommands such as view, mcp, panel, and vault.
• Organizational panel (Organigram): Presents the agent fleet as a real organizational chart, with drag-and-drop hierarchy adjustment; organizational file changes are versioned via git and validated before every write (circular dependencies cannot land).
• Markdown knowledge base (Vault): Exports the same snapshot as a wiki-linked Markdown library, one page per node, with frontmatter and links; index pages are generated by layer and cluster, and agent profiles include the chain of command, inheritance rules, memory buckets, machines, and contracts.
• Real-time memory system: booboo_remember / booboo_report are enabled by default; agents can write back persistent memories and reports that survive rebuilds; read-only mode can be enabled via --no-write or BOOBOO_READONLY=1.
• Quality gate: Each build prints an ingestion quality line (authored · orphans · dump-suspects), making content governance a number rather than a feeling.
• Contracts provided with the scaffold: npx create-booboo generates AGENTS.md (imported by CLAUDE.md) into the project, serving as operating guidelines that AI agents automatically read.

UsageApproaches

1. Try it first: visit booboo.fractionalhq.uk in a browser to view the live brain, no registration or cloning required.
2. Run a synthetic brain locally: start it with a single command, no database, configuration, or registration required (for example, booboo view --demo --nodes 50000). One million nodes at 60fps is the main selling point; on an ordinary laptop it can be lowered to --nodes 50000.
3. Point it at your own stack: edit booboo.config.yaml to point it at your own Postgres/Supabase (the scaffold includes a commented example). For detailed configuration, see docs/CONFIG.md; for troubleshooting, see docs/TROUBLESHOOTING.md.
4. MCP access to Claude / Cursor: booboo mcp speaks over stdio; point any MCP client at it. Agents can query the entire system (search, neighbors, path, stats); booboo_boot('<agent-id>') returns the agent's rules, memory reachability, and reports, thereby booting it from the organization; booboo_remember / booboo_report write back to persistent memory and reports. If the client's working directory differs, you can point --snapshot / --org at absolute paths.
5. Organization chart panel: booboo panel opens the org chart of the agent fleet. Five tabs share one organization file and one snapshot: organigram (drag-and-drop hierarchy), buckets (who remembers what), reports (the fleet's latest completed items), rules (who declares, who inherits), graph (the embedded 3D brain). Rules are inherited top-down; declare once on a branch, and all members beneath it are bound. Reports and memory buckets can be populated in two ways: live (agents call booboo_remember / booboo_report to write persistent logs, without needing a rebuild) or bulk import from your own tables according to the configuration.
6. Markdown knowledge base: booboo vault outputs the same snapshot as a wiki-linked Markdown library. Use [[node-id]] or [[exact label]] in the note text and set wikilinks: true; the builderIt will be converted into a first-class author edge, taking precedence over collection relationships in the graph, API, 3D view, and knowledge base. A nightly insurance copy can be generated.

Architecture and Packages

Booboo is centered on a single JSON specification; adapters feed data into it, and consumers render/serve/query it: emit JSON, and you get a viewer, API, and MCP server for free. Unusual data requires only about 50 lines of adapter code, with no need to fork (see SPEC.md).

Eight published packages (alpha status, each with independent semver, MIT):

• @booboo-brain/spec (contract)
• @booboo-brain/build (configuration-driven postgres/json adapters)
• @booboo-brain/serve (REST + MCP query layer)
• @booboo-brain/viewer (million-node 3D rendering)
• @booboo-brain/panel (org chart)
• @booboo-brain/vault (wiki-linked Markdown export)
• @booboo-brain/cli (unified booboo command)
• create-booboo (project scaffolding)

Use Cases

• Developers or teams who want to visually unify the structure, knowledge, memory, agents, and automation of an AI system.
• Those who need to let agents such as Claude and Cursor query the entire system via MCP, and start from the organization and write back memory.
• Those who want to manage an agent fleet like a company, using an org chart to control rule inheritance and memory access.
• Those who need to export the brain as an Obsidian-compatible Markdown knowledge base for portability and an insurance copy.

Limitations and Notes

• The current status is alpha.
• Rendering performance depends on the machine; in low-spec environments, it is recommended to reduce the number of nodes.
• Connecting your own Postgres/Supabase requires editing configuration files and consulting the documentation.
• Regarding facts such as pricing, hosted service prices, and specific platform support, the materials do not currently provide clear details; apart from the optional Fractional HQ custom service (custom adapters, hosted snapshots, refresh pipelines), all features are MIT and free forever. This optional service does not change the repository or the configuration schema, nor is it a fork or a gate.