Quox Brain2

A self-feeding second brain: connect sources and Quox Brain2 indexes them into one governed knowledge graph. Every agent can search and cite it.

Overview

Quox Brain2 is a self-feeding second brain: connect sources (dev sessions, notes, vaults, team conversations) and Brain2 indexes them automatically into one governed knowledge graph. Every agent in your organisation can search and cite it.

The engine behind Brain2 is core to QuoxCORE. Brain2 is the governed front door to that engine: a plugin that turns it into something a person can enable, connect sources to, and watch grow, rather than a service configured by editing files on a server.

Brain2 is agent-facing and human-facing at once. Agents consume it during every conversation, pulling relevant notes into context and citing them. Humans set it up, connect sources, and govern what it can see.

How it works

Brain2 unions everything visible to you into a single brain, not a set of separate vaults you switch between. Each note you connect lands in one of three scopes:

• Org: shared across your whole organisation.
• User: private to you.
• Shared: explicitly shared with a team.

Every note is indexed into notes, chunks, and links. Notes that reference each other (wikilinks, markdown links, embeds) become edges in a knowledge graph, so the brain is not just a pile of documents, it is a map of how your knowledge connects.

Retrieval combines full-text search with dense vector search where available, so a query can find a note even when it does not share exact wording with what you typed. This hybrid retrieval, which blends the two result sets with reciprocal rank fusion, sits behind the QUOXBRAIN_HYBRID_ENABLED flag; with the flag off, results fall back to full-text search only, which is always safe.

Connecting sources

Sources are things you connect, not paths you type. Brain2 ships with a catalog of source types, grouped by what they give you:

• Conversations: your AEE conversation history, ingested automatically.
• Dev sessions: Claude Code transcripts and terminal sessions, config-driven per machine.
• Folders / vaults: point Brain2 at a folder of notes (Markdown, Obsidian-style vaults) and it indexes them on a schedule, watermarked so re-runs only pick up what changed.
• Fleet logs: QuoxAgent per-host logs from machines you manage.
• Team conversations: agent and human conversations across your organisation's rooms.
• Notion / Google Drive: connect a workspace or account through an OAuth handshake rather than typing a path or token. Both sources sit behind the QUOXFEED_OAUTH_SOURCES_ENABLED flag and ship dark by default, so an operator must switch them on before either connector appears live in the catalog.

The scheduler that runs all of these sources on autopilot, syncing on an interval rather than requiring a manual re-connect each time, is itself gated by QUOXFEED_ENABLED. Like the OAuth connectors, it ships dark: an operator opts in before Brain2 pulls anything on a schedule.

Not every source suits every user. The cockpit shows the full catalog with what each source gives you and its sensitivity, and lets you connect only what fits your role. Low-sensitivity sources default on; anything touching personal data or evidence is opt-in.

Each connected source keeps its own last-sync time, note count, and health status, so you can see at a glance whether it is actually feeding the brain or stalled.

The knowledge graph

Every note you connect becomes a node in a graph you can explore directly: a 2D or 3D force-directed view, coloured by scope or by source, with links drawn between notes that reference each other. Hovering a node highlights its neighbours; the search box finds a note by content and jumps straight to it in the graph.

The graph is deliberately not a single global namespace shared across every customer. It is scoped: what you see is the union of your organisation's notes, your own private notes, and anything explicitly shared with you, and nothing else.

Search and cite

Two paths reach into the brain:

• quoxbrain_search: a tool every agent can call directly, mid-conversation, to pull relevant notes on demand.
• Automatic context: an implant that pulls relevant notes into an agent's context automatically, so it does not need to ask.

Both are org-scoped: an agent only ever sees notes visible to the organisation it is running in, never another customer's data. When an agent uses something it found in the brain, it cites the source note, so you can trace an answer back to where it came from.

The automatic-context implant is a separate opt-in behind QUOXBRAIN_IMPLANT_ENABLED, a global switch that defaults off. Even once enabled, it is further org-gatable via QUOXBRAIN_IMPLANT_ORGS, a per-organisation allowlist, so you can roll the implant out to specific organisations rather than turning it on for every customer at once.

Governance and witnessing

Brain2 inherits the same governance model as the rest of Quox. Sources are scoped (org, user, or shared) and provenanced: every note in the graph knows where it came from. Nothing is ingested from a blanket "index everything" switch.

Sources that touch evidence, such as governed policy decisions and infrastructure activity, carry the same tamper-evident properties as the rest of Quox's evidence layer: hash-chained records that can be proven, not just claimed, using the same trust anchor that signs the rest of the platform's evidence.

Access to the knowledge graph itself is licence-gated per organisation. Only agents and users in your organisation can search or view your brain.

Maturity

Not every capability on this page is at the same stage, and we would rather you know which is which:

• Stable: markdown ingest (push and filesystem vaults, with change detection and dedup), full-text search with citations, the knowledge graph API, org scoping, the quoxbrain_search agent tool, usage telemetry.
• Beta: hybrid (dense vector) retrieval behind QUOXBRAIN_HYBRID_ENABLED, the cockpit UI, folder and fleet sources, belief consolidation (QuoxDream).
• Experimental: the fleet-logs source, the automatic-context implant.
• Not yet live: the Notion and Google Drive OAuth connectors ship dark by default and have not yet been through a witnessed production sync; the docs, identity-blob and memory-export catalog entries are planned, not wired.

Non-markdown formats (PDF and friends) are not ingested yet. CJK search currently matches whole terms, not substrings.

Getting started

Activating Brain2 adds a settings section where you connect your first sources and watch the brain grow. A live counter tracks how many notes are indexed, so you can see the brain building as you go rather than wondering whether anything happened.

The suggested first source is usually the one closest to home: your own conversations and dev sessions. From there, connect a folder of notes or your team's shared knowledge as it becomes useful. You do not need to connect everything to get value. A small, well-scoped brain that agents can search and cite reliably is more useful than an empty one waiting to be filled.