Skip to main content

Three providers, one workflow

Claude Octopus orchestrates Codex (OpenAI), Gemini (Google), and Claude (Anthropic) across every workflow. Each provider has a distinct role designed to leverage its unique strengths.
You don’t need all three providers. One external provider plus Claude gives you multi-AI features. No external providers still gives you 33 personas, workflows, and skills.

Provider roles

Each provider is assigned a specific role based on its strengths:

Codex

Implementation depth
  • Code generation
  • Technical analysis
  • Architecture patterns
  • API design
  • Algorithm optimization

Gemini

Ecosystem breadth
  • Research synthesis
  • Alternative approaches
  • Security review
  • Best practices
  • Community patterns

Claude

Orchestration & synthesis
  • Quality gates
  • Consensus building
  • Strategic synthesis
  • Moderation
  • Final recommendations

Why these roles?

Role assignment is based on empirical testing and provider characteristics:

Role assignment by workflow

Different workflows emphasize different provider strengths:

Discover phase role assignment

Execution: Parallel (fastest)Example:

Consensus gates

Consensus gates enforce agreement thresholds before work advances.

How consensus is measured

Scoring methodology

Consensus score is based on:
  1. Subtask success rate - What percentage of subtasks succeeded?
  2. Agreement score - How similar are the provider outputs?
  3. Conflict detection - Are there direct contradictions?
Formula:

Threshold configuration

Default threshold: 75% Override via environment variable:
Lowering below 75% reduces confidence in multi-AI consensus. Use cautiously.

What happens at gate failure?

1

Identify disagreements

Parse which subtasks failed and where providers disagree
2

Analyze root cause

Determine if disagreement is fundamental or resolvable
3

Revision attempt

Retry with refined prompt or additional context (max 3 attempts)
4

Human escalation

Present findings and ask user to break tie or adjust approach

Cost transparency

Claude Octopus shows exactly which providers are running and what it costs.

Visual indicators

Before every multi-AI workflow, you see:

Provider cost breakdown

Model costs (as of Feb 2026):

Cost controls

Workflows check estimated cost before execution and abort if over limit.
Provider router automatically selects cheapest capable provider:
  • Analyzes task requirements
  • Matches to provider capabilities
  • Selects cheapest option that can handle it
  • Falls back if first choice unavailable
Install only one external provider:
  • Codex only: Dual perspective (Codex + Claude)
  • Gemini only: Dual perspective (Gemini + Claude)
  • Neither: Claude-only mode (personas and workflows still work)

Provider authentication

Claude Octopus supports two authentication methods:

Provider detection

Claude Octopus auto-detects available providers:

Graceful degradation

Workflows automatically adapt based on what’s available.

Security considerations

Environment isolation (v8.7.0+)

External providers run with minimal environment:
Prevents:
  • API key leakage to external providers
  • Access to sensitive environment variables
  • Unintended environment pollution

Trust markers

Provider outputs are wrapped with trust indicators:
Claude outputs pass through unchanged (trusted by default).

Data flow

Best practices

Don’t second-guess role assignment. Codex for implementation, Gemini for ecosystem, Claude for synthesis—each provider does what it does best.
If providers disagree significantly (less than 75% consensus), investigate why. Forcing through disagreements undermines multi-AI value.
Set OCTOPUS_MAX_COST_USD on shared accounts or CI/CD to prevent runaway costs.
Use OAuth authentication instead of API keys—it’s included in subscriptions and requires no key management.

Next steps

Double Diamond

Learn about the four-phase workflow structure

Workflows

Explore workflow patterns and autonomy modes

Provider setup

Configure Codex and Gemini authentication

Cost optimization

Learn to minimize multi-AI costs