Opt-in
No shadow is projected until you request it. The feature is local and off by default.
Limits
What Codex Council does not provide.
Council is an advisory workflow. Its verdict helps structure a decision; it does not replace tests, browser checks, security review, or your responsibility for the result.
Known constraints
Read the evidence, not just the verdict.
- One Codex model. The council uses isolated role prompts, not independent providers or model families.
- Advisory output. A
buildverdict is not a production approval or proof of correctness. - Browser evidence is required. UI behavior is verified only when the relevant path is executed in a real browser.
- Estimates are heuristic. Local token reports are planning aids, not billing telemetry, quota data, or measured savings.
- Expanded is explicit. The larger allowance does not start without your confirmation.
- Decision Runtime is experimental. Its shadow view is non-authoritative; original session artifacts and verdicts remain the source of truth.
Privacy and state
Local state still needs care.
Session scaffolds, estimates, prompts, outputs, stats, history, and alter overrides may
contain project context. Before publishing a repository, confirm that
.codex-council/ is ignored and uncommitted.
# Check for local runtime artifacts before publishing.
git status --short
find . -name '.codex-council' -o -name '.DS_Store' -o -name '__pycache__'Decision Runtime
An optional view, never the authority.
Non-authoritative
Missing or unhealthy shadow state is ignored. The saved session and verdict remain authoritative.
Still sensitive
Shadow data is local state, not encrypted evidence. Protect it like the source session.
Where it comes from
Inspired by LLM Council, adapted for one Codex environment.
The pattern comes from karpathy/llm-council and llm-council.dev. Codex Council keeps the multi-perspective review shape, but uses isolated prompts inside Codex rather than claiming independent-model diversity.