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:
/plugin marketplace add https://github.com/nyldn/claude-octopus.git
This registers the Claude Octopus repository as a plugin source.
2

Install the plugin

/plugin install claude-octopus@nyldn-plugins
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:
/plugin enable claude-octopus
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:
# Add marketplace
claude -p "/plugin marketplace add https://github.com/nyldn/claude-octopus.git"

# Install plugin
claude -p "/plugin install claude-octopus@nyldn-plugins"

# Fully restart Claude Code

Method 3: Manual installation (advanced)

For development or custom modifications:
# Clone the repository
git clone https://github.com/nyldn/claude-octopus.git
cd claude-octopus

# Run install script
./install.sh
The install script uses the Claude Code plugin manager internally and is equivalent to Method 1.

Verification

1

Verify plugin is installed

claude plugin list | grep claude-octopus
Expected output:
claude-octopus@nyldn-plugins (enabled)
2

Test a command

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

Run diagnostics

Run the comprehensive diagnostic tool:
/octo:doctor
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:
/octo:setup
Expected output with all providers:
Claude Octopus Setup Status

Providers:
  Claude: ✓ Built-in
  Codex CLI: ✓ Authenticated via OAuth
  Gemini CLI: ✓ Authenticated via API key

You're all set! Multi-AI features are enabled.

Try: /octo:embrace build a user authentication system

Configuration

Project-specific settings

Claude Octopus stores project state in .octo/ directory:
project-root/
├── .octo/
│   ├── STATE.md           # Current phase and progress
│   ├── LESSONS.md         # Captured insights
│   └── checkpoints/       # Rollback points
This directory is automatically created on first use.

Global settings

User-level configuration lives in ~/.claude-octopus/:
~/.claude-octopus/
├── results/               # Workflow outputs
├── logs/                  # Execution logs
└── config/                # User preferences

Autonomy modes

Configure how much human oversight workflows require:
ModeBehaviorWhen to use
Supervised (default)Pause after each phase for approvalLearning the tool, high-stakes projects
Semi-autonomousOnly prompt if quality gates failTrusted workflows, moderate oversight
AutonomousRun all phases without interventionRepeated patterns, full automation
Set during workflow execution:
/octo:embrace build feature  # Will prompt for autonomy preference
Or configure via orchestrate.sh:
${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh embrace --autonomy autonomous "your prompt"

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:
    /plugin uninstall claude-octopus@nyldn-plugins
    /plugin install claude-octopus@nyldn-plugins
    
Symptoms: “Plugin not found” when trying to uninstallSolution: Match the scope used during installation:
# If installed user-scoped (default)
/plugin uninstall claude-octopus@nyldn-plugins --scope user

# If installed project-scoped
/plugin uninstall claude-octopus@nyldn-plugins --scope project

Provider issues

Symptoms: Setup shows Codex as unavailableSolutions:
  1. Check CLI is installed: which codex
  2. Verify authentication:
    codex --version
    codex whoami  # Check logged-in user
    
  3. Re-authenticate:
    codex logout
    codex login
    
  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:
    echo $GEMINI_API_KEY
    
  3. Test authentication:
    gemini --version
    
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:
    /octo:discover <query>  # Uses only Claude by default
    

Workflow issues

Symptoms: Workflow completes but files aren’t foundCheck these locations:
# Global results
ls -la ~/.claude-octopus/results/

# Project state
ls -la .octo/

# Recent results
ls -lt ~/.claude-octopus/results/ | head -10
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:
    /octo:discover <topic>  # Research first
    /octo:define <scope>    # Then clarify
    

Environment diagnostics

Use the built-in doctor command for comprehensive checks:
# Run all diagnostics
/octo:doctor

# Check specific category
/octo:doctor providers
/octo:doctor auth --verbose

# Machine-readable output
/octo:doctor --json
Doctor checks 9 categories:
CategoryWhat it checks
providersClaude Code version, Codex CLI, Gemini CLI installation
authAuthentication status for each provider
configPlugin version, install scope, feature flags
stateProject state.json, stale results, workspace writability
smokeSmoke test cache, model configuration
hookshooks.json validity, hook scripts
schedulerScheduler daemon, jobs, budget gates
skillsSkill files loaded and valid
conflictsDetection of conflicting plugins

Update and maintenance

Updating Claude Octopus

# Update from marketplace
/plugin update claude-octopus

# Or via terminal
claude -p "/plugin update claude-octopus"

Checking version

View current version:
/plugin list | grep claude-octopus
Or check the plugin.json:
cat ~/.claude/plugins/claude-octopus@nyldn-plugins/.claude-plugin/plugin.json | grep version

Clean uninstall

Remove plugin and all data:
# Uninstall plugin
/plugin uninstall claude-octopus@nyldn-plugins

# Remove global data (optional)
rm -rf ~/.claude-octopus/

# Remove project state (optional, per-project)
rm -rf .octo/
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

Build docs developers (and LLMs) love