Guides.

Each one gets a specific thing working. Configuration was verified against each vendor’s own current documentation on 2026-08-20, not written from memory — and the connection mechanics live in one place so three copies cannot drift apart.

8 guides

Start here

Quickstart

First call in five minutes: get a key, price a question for free, convene a panel, read the receipt.

Read

/docs/guides/quickstart Quickstart First call in five minutes: get a key, price a question for free, convene a panel, read the receipt.
/docs/guides/mcp Connect your editor The canonical MCP setup. One verified config per client, and the wrapper-key difference that breaks a copy-paste. Companion paper: Your editor
/docs/guides/escalation-router The escalation router Classify a question for free, then decide whether it earns a panel. The threshold is yours, not ours. Companion paper: The router
/docs/guides/quorum-with-claude-code Quorum with Claude Code A second opinion inside the agent loop, and an honest read on when the wait is worth it. Companion paper: Claude Code
/docs/guides/quorum-with-vscode Quorum with VS Code Setup for the one client that nests servers under a different key from everyone else. Companion paper: VS Code
/docs/guides/quorum-with-cursor Quorum with Cursor Setup for Cursor, including a known header behaviour worth knowing before you debug it yourself. Companion paper: Cursor
/docs/guides/quorum-and-excel Quorum and Excel Reaching a panel from a spreadsheet cell, what comes back, and what it cannot see. Companion paper: Excel
/docs/guides/moding-and-vibe-coding Moding and vibe coding Shipping a Mode inside the thing you built. No streaming on the hosted path, and why that shapes the UI. Companion paper: Vibe coding

Where to start

If you are connecting an editor, read Connect your editor first — it holds the config every per-editor guide points back to. If you are deciding what deserves a panel at all, start with the escalation router.

Not written yet

Stated rather than omitted, because a library that hides its holes is harder to trust than one that names them. This list is checked against the plan of record, not written from memory.

/docs/guides/reading-a-receipt Reading a receipt How to interpret judge scores, convergence and dissent once you have them. The endpoint is documented; what to do with the answer is not.
/docs/guides/{researching,building,testing}-a-mode The Mode Maker guides Researching a Mode, building one, and testing it — three distinct jobs, none written up.
/docs/guides/byok · /docs/guides/migrating-from-openai Bring your own keys, and migrating from a single-model API Per-provider keys including the Bedrock path; and precisely where our OpenAI-compatible surface differs from OpenAI’s.

Anything the pages above do not cover, the assistant at the top of each page will say it does not cover rather than guess.