querying-council-with-agents
Agent-Enhanced Council Execution
Use parallel Claude subagents for deeper analysis. Each subagent queries its provider, evaluates response quality, can ask follow-up questions, and returns structured insights.
Step 1: Determine Provider Details
For each selected provider, gather:
- Provider name and script path:
${CLAUDE_PLUGIN_ROOT}/scripts/providers/{name}.sh - Model name: run
bash ${CLAUDE_PLUGIN_ROOT}/scripts/query-council.sh --list-availableor read the provider script defaults
Step 2: Spawn Provider Agents in Parallel
Launch ALL provider agents in a single message (multiple Agent tool calls) for parallel execution.
Use run_in_background: true and subagent_type: "general-purpose" for each.
Agent prompt template: See agent-prompt-template.md for the full template.
Read it and fill in {PROVIDER}, {SCRIPT_PATH}, and {QUESTION} for each agent.
More from hex/claude-council
querying-council
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.
9integrating-providers
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".
9