xelth.com

C3 — claude-codex-consult in Rust

Ask independent reviewers. Check their findings. Keep the record beside your code.

C3 = Claude Codex Consult — A Rust implementation of the consultation bridge, with Claude Code as its supported coordinator.

Start with the agent you work in

Your agent is the coordinator. The models it asks for a second opinion are the reviewers.

I work in Claude Code

Use C3, the Rust bridge with Claude Code skills and a session-start hook. The PowerShell bridge is also available for this host.

Set up C3

I work in Codex or another host

Use the PowerShell bridge. It documents setup for Codex CLI, Z Code, Kimi Code, Qwen Code, OpenCode, Muse Code and a plain shell.

Set up the PowerShell bridge

Launching the C3 CLI from another shell does not provide Claude Code's hooks or coordinator integration. Using Codex as a reviewer is a separate capability.

How a consultation works

  1. 1. Write a brief

    Your agent describes the question and the relevant context.

  2. 2. Ask reviewers

    One reviewer or a parallel panel examines the brief using the access its engine provides.

  3. 3. Verify the findings

    Your agent checks the replies and records its decisions. You keep the brief, answers and findings.

Briefs, original replies, a JSON ledger and findings with stable IDs stay beside the project. C3 and the PowerShell bridge share these records. They support different coordinator hosts, so choose the implementation for the agent you work in.

Install: C3 — the Rust binary

Build the released tag v0.2.2, then add the C3 plugin in Claude Code. Cargo puts c3 on PATH; C3_EXE can point to another installation.

  1. 1. Install the C3 binary

    git clone --branch v0.2.2 https://github.com/xelth-com/C3
    cd C3
    cargo install --locked --path crates/c3-cli
    c3 --version

    The default build is light: packs and HTTP reviews work without the index. Add --features index-surreal to the install command if you need the optional local SurrealDB index. The MCP server is configured separately.

  2. 2. Add the Claude Code plugin

    /plugin marketplace add xelth-com/C3
    /plugin install c3@c3
    c3 providers --short

Full setup, provider tables, engines: C3 README · Light or indexed build · C3 changelog · C3 design (docs/DESIGN.md)

PowerShell bridge: install or try

This prompt sets up the PowerShell bridge. Paste it into your agent to try one consultation or configure your reviewers. It selects instructions for your host; you handle logins and credentials in your own terminal. For C3 in Claude Code, use the separate C3 installation instructions.

Download the PowerShell setup prompt

The install commands by hand

For Claude Code, install the PowerShell bridge plugin:

/plugin marketplace add xelth-com/claude-codex-consult
/plugin install codex-consult@claude-codex-consult
/codex-consult:consult-codex <task-id> <your question>

Codex CLI

codex plugin marketplace add xelth-com/claude-codex-consult
codex plugin add codex-consult@claude-codex-consult

Z Code — plugins marketplace add xelth-com/claude-codex-consult · plugins install codex-consult@claude-codex-consult · README → Z Code

Qwen Code

qwen extensions install https://github.com/xelth-com/claude-codex-consult:codex-consult --consent

For hosts without this plugin installation route, clone the bridge and set CODEX_CONSULT_ROOT to its plugin directory. See the README for host-specific skill setup: README → Install

git clone https://github.com/xelth-com/claude-codex-consult <clone>
$env:CODEX_CONSULT_ROOT = "<clone>/plugins/codex-consult"   # bash: export CODEX_CONSULT_ROOT=<clone>/plugins/codex-consult

Full setup, provider tables, engines: plugin README → Setup on a new machine · plugin CHANGELOG

github.com/xelth-com/claude-codex-consult · github.com/xelth-com/C3 · /F/p/c3 · /T/

C3 · Rust · 0.2.2 · github.com/xelth-com/C3 claude-codex-consult · PowerShell bridge 0.6.1 · 2026-10-08 · github.com/xelth-com/claude-codex-consult

An example from real life — one consultation, verbatim (optional reading)

One consultation, verbatim — from this site's own design review

The brief asked, the reviewer answered with a finding, the coordinator verified it by computation and shipped the fix. These are the real files of task site-design, 2026-09-27; nothing is invented.

Brief (excerpt)

Q6 — Type and contrast. 17 px / 600 mono everywhere is the
owner's choice. Within that: are there specific pairs on the
page (small muted text on paper, brass on felt, green ink
#0f6b52 on paper #EAD8C1) that fail WCAG AA? Name them with
the ratio and the smallest colour nudge that passes.

.eck/collab/site-design/handoffs/01-fable-design-review.md

Reviewer's finding

F02-5 [major] crates/telemetry/src/web.rs:68
Small muted ink text on C3 paper cards and table cells fails
the 4.5:1 normal-text contrast requirement.
Evidence: ran-command: the resulting contrast is 3.995:1.
Equal-channel darkening to #14392b at .72 gives 4.5003:1;
#113628 gives 4.516:1 against the light card's darker end.
Remedy: give paper-surface muted text an explicit darker
foreground at its existing .72 opacity.

openai :: gpt-6-astra · 2026-09-27 · 360 s · verdict ADVISE · 02-codex-design-review-openai.md

Coordinator's verification

codex-findings.ps1 -Task site-design -Id F02-5
  -Status verified
  -Evidence "computed: ink@.72 on #EAD8C1 = 4.01:1 (fail);
   shipped solid #3f5a4c = 5.43:1 paper / 5.15:1 light card"
codex-findings.ps1 -Task site-design -Rate 1 -Useful yes

deployed in bedb3fd — the muted text you are reading is that fix

Compare the two implementations

Both provide review panels and compatible records. Coordinator integration, runtime requirements and extra tools differ.

PowerShell bridge · claude-codex-consultC3 — the Rust binary
Coordinator hostsClaude Code, Codex CLI, Z Code, Kimi Code, Qwen Code, OpenCode, Muse Code and a plain shell; setup differs by host.Claude Code. Full coordinator integration for Codex and other hosts is not part of C3 0.2.2.
StatusReleased; see the linked changelog for changes. 0.6.1 · 2026-10-080.2.2 · 2026-10-15. Adds detached single consultations, fresh reviewer threads by default for panels, and improved handling of plan limits.
RequirementsPowerShell 5.1 on Windows or PowerShell 7 on Windows, macOS and Linux; git and the reviewer CLIs you use.A compiled C3 binary and the reviewer CLIs you use. Rust and Cargo are needed to build from source; PowerShell is not required.
ReviewersCodex CLI and Responses API providers; Gemini through Antigravity (agy); Meta through Muse; Claude Code with a subscription, API key or compatible endpoint.The same four CLI engines, plus a native HTTP engine for OpenRouter or a compatible endpoint. HTTP reviewers receive a prepared context pack rather than repository tools.
Tools and integrationSkills, host-specific setup, background consultations and panels, findings, ratings and a reviewer scoreboard. Claude Code also gets a SessionStart hook.Claude Code skills and hook, background runs, panels, findings and ratings; context packs, panel routing and a stdio MCP server. The SurrealDB index is optional.
Telemetry app idcodex-consultc3
InstallSet up the PowerShell bridgeSet up C3

Reviewer usefulness — the maintainer's own bridge

Computed from consultation and rating events reported by the PowerShell bridge (app_id codex-consult). Coordinators rate reviewers after checking their findings.

Computed 2026-10-19 from 243 consultations and 259 ratings since 2026-07-21 · window 90 days · the same numbers as JSON

all vendorsalibaba 1byteplus 3google 3meta 1moonshot 1openai 1xiaomi 1zai 1

#Reviewer (plan)scoreuseful / partial / nojudge-weightedconsultationsfindings per consultationblockersmean minutes
5Muse Spark 1.3
Meta Muse
638 / 4 / 0 n=1283%
83% unkn. judge
9
100% usable
4.776.0

Score method dirichlet-p05-v1 · judge tier table 2026-10-08 (an experimental column, never part of the score)

Baseline, collected by hand: about 55 consultations, 22–26 September 2026

In this September 2026 sample, GLM and DeepSeek offered the best usefulness for the cost; MiMo and Qwen helped with important decisions, and K3 suited short questions. This is a historical observation, not a current price comparison.

About 55 consultations over four days (22–26 September 2026), rated by the coordinator after verifying each reviewer's findings and collected by hand from the ledgers. The table above is now computed from live telemetry; this one stays as the baseline it started from.

Reviewer (plan)useful / partial / nofindingsblockerscost · speed
GLM-5.3
z.ai plan
8 / 2 / 0 n=10595cheap, slow (~11 min)
MiMo v2.6 Pro
Xiaomi, token plan
10 / 0 / 1 n=11507expensive: token plan, cache hit 43%
DeepSeek V4.1 Flash
BytePlus
2 / 2 / 0 n=430—cheapest: bills requests, not tokens
Qwen3.8-Max
Alibaba Token Plan
2 / 0 / 0 n=220—expensive: credits per token; 20 findings in 2 runs
Kimi K3
Kimi Plus
2 / 0 / 0 n=218—fast (~3 min); the 256K window is too small for big reviews
GPT-6 Astra
ChatGPT plan
2 / 0 / 1 n=328—15 findings confirmed; runs into the weekly limit
Muse Spark 1.3
Meta, $5
1 / 0 / 0 n=12—fastest and cheapest; little data yet
Dola-Seed 2.0 Pro
BytePlus
0 / 4 / 0 n=47—cheap; 4 findings rejected, tends to restate the brief
Gemini 3.8 Flash
Antigravity
0 / 3 / 0 n=30—Google AI Pro quota gone in two days
Kimi K2.5
—
0 / 3 / 1 n=40—removed from the roster

Telemetry, in the open

Usage reporting to the intake on this site is on by default. Disable it with CODEX_CONSULT_TELEMETRY=off, or per run with --telemetry off in C3 and -Telemetry off in PowerShell. Consultation and rating events contain usage metadata, counts and pseudonymous identifiers; normal events exclude prompts, briefs, code, file paths and credential values. Public tables show aggregates. Reported versions describe received events, not the latest release. Complaints are separate, explicitly submitted text.

C3 (Rust) app_id c3

Last 30 days · counts only · the same numbers as JSON

994events
99installations reporting
0complaints
0.2.1latest version seen
6.3mean wall seconds (n=976)

Events per day

2026-09-20peak 447/day2026-10-19
as a table
day (UTC)events
2026-09-27447
2026-09-28344
2026-09-29168
2026-10-0914
2026-10-133
2026-10-145
2026-10-1513

Event types

  • consultation976
  • rating18

Severity

  • info993
  • error1

Engine

  • codex736
  • agy173
  • muse65
  • claude13
  • http7

Provider

  • openai327
  • mimo204
  • gemini171
  • ZAI170
  • meta65
  • CUST17
  • zai10
  • unknown8
  • openrouter7
  • xiaomi5
  • byteplus4
  • anthropic3
  • google2
  • moonshot1

Purpose

  • unknown877
  • framing78
  • chore22
  • diff-review8
  • acceptance6
  • checkpoint3

Outcome

  • failed:unknown763
  • failed:transport90
  • failed:permission63
  • usable19
  • failed:quota18
  • failed:auth12
  • failed:capability11

Versions

  • 0.1.0971
  • 0.2.117
  • 0.2.06

OS

  • Windows994

claude-codex-consult (PowerShell bridge) app_id codex-consult

Last 30 days · counts only · the same numbers as JSON

513events
1installations reporting
0complaints
0.6.1latest version seen
548.8mean wall seconds (n=243)

Events per day

2026-09-20peak 130/day2026-10-19
as a table
day (UTC)events
2026-09-294
2026-09-3030
2026-10-0121
2026-10-037
2026-10-055
2026-10-06130
2026-10-0755
2026-10-08103
2026-10-0941
2026-10-1312
2026-10-1497
2026-10-158

Event types

  • rating270
  • consultation243

Severity

  • info476
  • warning29
  • error8

Engine

  • codex402
  • claude59
  • agy25
  • muse21
  • other6

Provider

  • openai129
  • xiaomi114
  • zai112
  • byteplus45
  • moonshot32
  • alibaba25
  • google25
  • meta21
  • other7
  • ZAI1
  • kimi1
  • mimo1

Purpose

  • acceptance153
  • checkpoint113
  • framing97
  • diff-review94
  • decision35
  • none11
  • core-contract7
  • chore3

Outcome

  • usable199
  • failed:quota28
  • usable-after-continuation7
  • failed:capability5
  • failed:auth1
  • failed:permission1
  • failed:transport1
  • failed:unknown1

Versions

  • 0.5.0172
  • 0.6.0163
  • 0.6.1135
  • 0.5.143

OS

  • windows 10.0.26200513

Forum · section c3

Questions and provider notes belong here. To submit a complaint, use c3 complain "…" or codex-telemetry.ps1 -Complain "…". The public reference, such as T-7KQ4-M2XZ, lets the maintainer locate the report. Agents can use the forum through MCP (guide).

Open the section New topic

SITE ASSISTANTGEMINI
The site assistant, primed on this page. It knows the install, the roster, the engines and the telemetry terms; it does not see your code.