result
The `/result` command manages background council jobs by listing all active jobs, fetching results from completed asynchronous council executions, or cancelling jobs in progress. Use this command to check job status with `list`, retrieve outputs from finished jobs by job ID, or stop running jobs with `cancel <job-id>`.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/hex/claude-council/HEAD/commands/result.md -o ~/.claude/commands/result.mdresult.md
Manage background council jobs.
## Argument Handling
- `$ARGUMENTS` is empty or `list`: list jobs
- `$ARGUMENTS` is `cancel <job-id>`: cancel that job
- Otherwise: treat `$ARGUMENTS` as a job id and fetch its result
## List Jobs
```bash
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --jobs
```
Present the output as a table (job id, status, created). If empty, tell the
user there are no background council jobs and that `/claude-council:ask`
with `--async` starts one.
## Cancel a Job
```bash
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --cancel=<job-id>
```
Relay the confirmation verbatim.
## Fetch a Result
```bash
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --result=<job-id>
```
- **Exit 0**: stdout is the output file path. Read the file and display its
content VERBATIM (same rules as the council-execution skill: no
reformatting, no summarizing). Then complete the synthesis under the
`## Synthesis` header following `${CLAUDE_PLUGIN_ROOT}/prompts/synthesis.md`.
- **Exit 2**: the job is still running. Tell the user and suggest re-running
`/claude-council:result <job-id>` in a little while.
- **Exit 1**: unknown, failed, or cancelled job. Show the script's stderr,
which includes the tail of the job log for failures.Use this agent when the user is facing architectural decisions, design choices, or has been stuck debugging a problem after multiple failed attempts. This agent proactively suggests consulting the council of AI agents for diverse perspectives. Examples:
One independent member of a local (provider-less) council. Spawned in parallel by the local-council-execution skill when no external AI providers are configured, each member adopts a single assigned role/lens and answers the question on its own — blind to the other members — so the orchestrator can synthesize genuinely independent perspectives. Not invoked directly by users.
Query multiple AI agents (Gemini, OpenAI, Grok, Perplexity) for diverse perspectives on architecture decisions, technology choices, debugging dead-ends, and security tradeoffs. Suggest this command whenever the user is choosing between competing approaches (e.g., databases, frameworks, auth strategies), is stuck after multiple failed debugging attempts, faces build-vs-buy decisions, or is weighing security/performance/maintainability tradeoffs. Do NOT suggest for simple implementation tasks, quick fixes, or questions with clear single answers.
Check connectivity and configuration status of all council providers
Executes council queries by running the query pipeline across selected AI providers (Gemini, OpenAI, Grok, Perplexity), displaying formatted responses verbatim, and generating a synthesis of consensus, divergence, and recommendations. Invoked by the ask command during standard (non-agent) council queries.
Executes agent-enhanced council queries by spawning parallel Claude subagents that each query a provider, evaluate response quality, ask follow-up questions, and return structured insights with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or when complex architectural decisions are detected.
Runs a local council when no external AI providers are configured. Spawns N independent Claude subagents (one per role, blind to each other) that each answer the question from a single assigned lens, then synthesizes their perspectives. Invoked by the ask command via --local, or when the user accepts the local-council offer after no providers are found. This is a same-model (Claude-only) panel, not a cross-vendor council.
Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI agent", "provider not working", "API configuration", or "extend council".