Skip to main content

Installation

Complete guide to installing and configuring Claude Octopus for Claude Code.

Prerequisites

Required

  • Claude Code v2.1.50 or later — Check your version in the about menu
  • Git — Used by the plugin marketplace to fetch plugins
  • Bash shell — For orchestration scripts (default on macOS/Linux, WSL on Windows)
Claude Code version requirement: Claude Octopus requires v2.1.50 or newer. Earlier versions lack critical plugin APIs for multi-AI orchestration.

Optional (for multi-AI features)

  • Codex CLI — For OpenAI integration
  • Gemini CLI — For Google integration
  • Node.js 18+ — Required only if using the OpenClaw MCP server
You can start using Claude Octopus immediately with just Claude built-in. External providers are optional and only needed for multi-AI orchestration features (parallel research, adversarial debate, consensus validation).

Installation methods

The plugin marketplace method is the recommended approach:
1

Add the marketplace repository

In Claude Code, run:
This registers the Claude Octopus repository as a plugin source.
2

Install the plugin

Installation scope:
  • Default: User-scoped (--scope user) — available across all projects
  • Alternative: Project-scoped (--scope project) — only available in current project
3

Enable the plugin

The plugin should enable automatically, but you can verify:
4

Restart Claude Code

Fully quit and reopen Claude Code:
  • macOS: Cmd+Q, then reopen
  • Windows/Linux: Complete exit, then relaunch
A simple window close may not be sufficient. Ensure Claude Code fully terminates.

Method 2: Terminal installation

Alternatively, install from your terminal:

Method 3: Manual installation (advanced)

For development or custom modifications:
The install script uses the Claude Code plugin manager internally and is equivalent to Method 1.

Verification

1

Verify plugin is installed

Expected output:
2

Test a command

Try running setup:
You should see provider detection output.
3

Run diagnostics

Run the comprehensive diagnostic tool:
This checks 9 categories: providers, auth, config, state, smoke tests, hooks, scheduler, skills, and conflicts.

Provider setup

Claude Octopus works with three AI providers. Claude is built-in. Codex and Gemini are optional.

Claude (built-in)

✅ No setup required — Claude is included with Claude Code and works immediately. Cost: Included in your Claude Code subscription (Sonnet 4.6). Opus 4.6 uses per-token billing at 5/5/25 per MTok.

Codex (OpenAI)

Codex provides implementation depth — code patterns, technical analysis, and architecture.

Gemini (Google)

Gemini provides ecosystem breadth — alternatives, security review, and research synthesis.

Verify provider configuration

After configuring providers, run setup to verify:
Expected output with all providers:

Configuration

Project-specific settings

Claude Octopus stores project state in .octo/ directory:
This directory is automatically created on first use.

Global settings

User-level configuration lives in ~/.claude-octopus/:

Autonomy modes

Configure how much human oversight workflows require: Set during workflow execution:
Or configure via orchestrate.sh:

Troubleshooting

Commands not recognized

Symptoms: /octo:* commands show “unknown command” errorSolutions:
  1. Verify installation: claude plugin list | grep claude-octopus
  2. Check plugin is enabled: /plugin enable claude-octopus
  3. Fully restart Claude Code (Cmd+Q on macOS, not just close window)
  4. Check debug logs: ~/.claude/debug/*.txt
  5. Try reinstalling:
Symptoms: “Plugin not found” when trying to uninstallSolution: Match the scope used during installation:

Provider issues

Symptoms: Setup shows Codex as unavailableSolutions:
  1. Check CLI is installed: which codex
  2. Verify authentication:
  3. Re-authenticate:
  4. Check PATH includes npm global bin directory
Symptoms: Setup shows Gemini as unavailableSolutions:
  1. Check CLI is installed: which gemini
  2. Verify API key is set:
  3. Test authentication:
Symptoms: Workflows fail with timeout errorsSolutions:
  1. Check network connectivity
  2. Verify API keys are valid (not expired)
  3. Check rate limits on provider accounts
  4. Try running with single provider first:

Workflow issues

Symptoms: Workflow completes but files aren’t foundCheck these locations:
Symptoms: Workflows blocked at 75% consensus gateUnderstanding quality gates:
  • 75% threshold means 2 out of 3 providers must agree
  • Failures indicate genuine disagreement worth investigating
  • Review synthesis files to see divergent perspectives
Solutions:
  1. Review the synthesis: ~/.claude-octopus/results/*-synthesis-*.md
  2. Provide more context in your prompt
  3. Run phases individually to isolate issues:

Environment diagnostics

Use the built-in doctor command for comprehensive checks:
Doctor checks 9 categories:

Update and maintenance

Updating Claude Octopus

Checking version

View current version:
Or check the plugin.json:

Clean uninstall

Remove plugin and all data:
Removing ~/.claude-octopus/ deletes all workflow results and logs. Consider backing up first.

What’s next?

Quickstart

Run your first workflow in under 5 minutes

Command Reference

Explore all 46 commands

Double Diamond

Learn the four-phase workflow methodology

Personas

Discover the 33 specialized AI agents