version: "1.0.5" name: provider-integration description: 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".

Adding AI Providers to Claude Council

Provider Script Interface

Each provider is a shell script in scripts/providers/ that:

1. Accepts a prompt as the first argument
2. Outputs the AI response to stdout
3. Exits 0 on success, non-zero on failure

Quick Start

1. Create scripts/providers/{name}.sh (see api-patterns.md for templates)
2. chmod +x scripts/providers/{name}.sh
3. Set {NAME}_API_KEY environment variable
4. Test: ./scripts/providers/{name}.sh "Hello"

Current Providers

CLI providers (codex, antigravity, grok-cli, kimi-cli, cursor-cli) need no key: they are discovered when their binary is on PATH and use that CLI's own login. See scripts/providers/kimi-cli.sh and cursor-cli.sh for the headless-run pattern: a read-only mode, a JSON output format the answer is parsed from, --model only on an explicit *_CLI_MODEL override, and run_with_deadline in place of the API providers' retry.

Troubleshooting

• Not discovered: Check API key is set and script is executable
• API errors: Verify key, check rate limits, confirm model name
• Parse fails: Add echo "$RESPONSE" to debug, check response format

Reference

For API patterns and code templates, see api-patterns.md in this directory.