status
The status slash command checks connectivity and configuration for all AI providers in the Claude Council system, displaying connection states, response times, model names, and provider-specific fix commands. Use this command to diagnose configuration issues, verify which providers are available, and monitor background council job status before executing multi-provider operations.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/hex/claude-council/HEAD/commands/status.md -o ~/.claude/commands/status.mdstatus.md
Check the status of all configured AI providers.
## Execution
Run the status check script:
```bash
bash ${CLAUDE_PLUGIN_ROOT}/scripts/check-status.sh
```
## Output
Present the script output directly - it includes formatted status for each provider:
- Connection status (connected, timeout, auth error, not configured)
- Response time in milliseconds
- Configured model name
- Per-provider fix command for anything not available
- Summary of available providers
No additional formatting needed - the script handles all presentation.
## Background Jobs
Also list any background council jobs:
```bash
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --jobs
```
If the output is non-empty, present it as a table (job id, status, created)
and mention `/claude-council:result <job-id>`. If empty, omit the section.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.
Fetch, list, or cancel background council jobs started with --async
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".