Deliberationv4.6.1

Setup & Configuration

How to configure Deliberation: the two expert modes, the config.json schema and its sections, OpenRouter model records, and opt-in session persistence. For provider internals, environment variables, and manual MCP setup, see TECHNICAL.md.

Modes

Every expert supports two modes, chosen automatically from your request:

Mode Sandbox Use when
Advisory read-only Analysis, recommendations, reviews
Implementation workspace-write Making changes, fixing issues

Quick setup: init

bash
npx -y @antonbabenko/deliberation-mcp init

init is the fastest way to a working config on any host. /deliberation:setup runs it first. In order, it:

  1. Finds the credentials you already have: a logged-in codex CLI, agy on PATH, XAI_API_KEY and OPENROUTER_API_KEY. GEMINI_API_KEY / GOOGLE_API_KEY are reported but not used yet. Key values are never printed.
  2. Writes the config at the normal path (DELIBERATION_CONFIG wins). A new file enables each provider it found and has no model records, so OPENROUTER_API_KEY alone gives the built-in panel. An existing file only gains the missing providers.<name>.enabled: true flags; init shows them as a diff, asks on a terminal, and applies them without asking only with --yes. An enabled: false you set is kept.
  3. Pings each enabled provider with one tiny prompt and prints OK or FAIL <errorKind>.
  4. Runs one short demo consensus (one round, low effort) and prints the verdict and the voices that answered. --no-demo skips it.
  5. Prints the install line for your host, or a short table when it cannot tell the host.

Run it again any time: a second run changes nothing and says so. When Deliberation was used here before (a config file or saved sessions exist), the output is shorter and the demo is skipped unless you pass --demo.

Rendered from SETUP.md in the repository.

Type to search the site.