Skip to main content

🚀 Boomerang for OpenCode

License: MIT OpenCode Plugin Multi-Agent Orchestration

Intelligent multi-agent coordination for OpenCode — because great software is a team sport.


🚀 Vanilla OpenCode Install (One-Click Prompt)

Copy and paste the following prompt into a fresh OpenCode Builder session. It will do everything automatically.

I want you to install the Boomerang multi-agent plugin for OpenCode. Do this step by step:

1. Install the Boomerang package from PyPI. Run: pip install opencode-boomerang (or uv tool install opencode-boomerang if uv is available).

2. Install super-memory from PyPI. Run: pip install super-memory (or uv tool install super-memory if uv is available).

3. Edit the project's .opencode/opencode.json file to include:
   - The Boomerang plugin: "plugin": ["opencode-boomerang"]
   - An MCP server entry for super-memory with command ["super-memory"] or ["uv", "run", "super-memory"] depending on how it was installed
   - An MCP server entry for sequential-thinking with command ["npx", "-y", "@modelcontextprotocol/server-sequential-thinking"]

4. Confirm completion and tell me to:
   a) Restart OpenCode completely
   b) After restart, open the Skills panel (type /skills) and select "boomerang-init" to run the initialization skill

🎯 What is Boomerang?

Boomerang is an intelligent multi-agent orchestration plugin for OpenCode that coordinates a team of specialized AI agents working together on your codebase. Instead of relying on a single AI, Boomerang implements the Boomerang Protocol — a structured 6-step workflow that ensures thorough, consistent, and high-quality code delivery.

Think of it as your AI development team lead — the Orchestrator plans the work, delegates to specialists, enforces quality gates, and ensures nothing falls through the cracks.


🏗️ Architecture

┌─────────────────────────────────────────────────────────────────┐
│                          USER                                    │
└────────────────────────────┬────────────────────────────────────┘
                             │
                             ▼
┌─────────────────────────────────────────────────────────────────┐
│              🎯 ORCHESTRATOR (Kimi K2.5)                         │
│   • Plans task execution & dependency graph                       │
│   • Delegates to specialized sub-agents                          │
│   • Enforces quality gates                                       │
└────────────────────────────┬────────────────────────────────────┘
                             │
         ┌───────────────────┼───────────────────┐
         │                   │                   │
         ▼                   ▼                   ▼
┌─────────────┐      ┌─────────────┐      ┌─────────────┐
│   💻        │      │   🏗️        │      │   🔍        │
│  CODER      │      │ ARCHITECT  │      │ EXPLORER   │
│ MiniMax M2.7│      │ Kimi K2.5  │      │ MiniMax M2.7│
└─────────────┘      └─────────────┘      └─────────────┘
         │                   │                   │
         └───────────────────┼───────────────────┘
                             │
                             ▼
┌─────────────────────────────────────────────────────────────────┐
│                  🔄 THE BOOMERANG PROTOCOL                       │
│                                                                 │
│   1️⃣ Memory   →   2️⃣ Think   →   3️⃣ Delegate                  │
│   4️⃣ Git Check →   5️⃣ Quality Gates →   6️⃣ Save Memory        │
└─────────────────────────────────────────────────────────────────┘

The 6-Step Boomerang Protocol

Step Name Description
1️⃣ Memory Query super-memory for context, past decisions, and learnings
2️⃣ Think Analyze task, build dependency graph, plan execution
3️⃣ Delegate Assign work to appropriate sub-agents by specialty
4️⃣ Git Check Verify changes, stage, and commit with proper discipline
5️⃣ Quality Gates Run lint, typecheck, and tests before completion
6️⃣ Save Memory Persist decisions and context back to super-memory

🤖 Agent Roster

Agent Model Role
boomerang Kimi K2.5 🎯 Orchestrator — Plans, coordinates, enforces protocol
boomerang-coder MiniMax M2.7 💻 Fast code generation — Write and modify code efficiently
boomerang-architect Kimi K2.5 🏗️ Design decisions — Trade-off analysis and architecture
boomerang-explorer MiniMax M2.7 🔍 Codebase exploration — Find files, search patterns, understand structure
boomerang-tester MiniMax M2.7 🧪 Testing specialist — Unit/integration tests, verification
boomerang-linter MiniMax M2.7 ✅ Quality enforcement — Lint, format, style consistency
boomerang-git MiniMax M2.7 📦 Version control — Commits, branches, history discipline
researcher MiniMax M2.7 🌐 Web research — Search, fetch, and synthesize online information

🧠 Super-Memory Integration

⚠️ SUPER-MEMORY IS REQUIRED — Boomerang will not function without it.

Why is super-memory required?

Unlike simple context windows, super-memory provides persistent long-term memory across sessions. When you start a new OpenCode session, Boomerang agents automatically:

  • Query memory at start — Retrieve relevant context, past decisions, and learnings from previous sessions
  • Save memory at end — Persist key decisions, code patterns, and project-specific knowledge

This means Boomerang learns your codebase over time and doesn't repeat mistakes.

Installation

# Using uv (recommended)
uv tool install super-memory

# Or using pip
pip install super-memory

Configuration

Add super-memory to your global ~/.opencode/opencode.json:

{
  "mcp": {
    "super-memory": {
      "type": "local",
      "command": ["super-memory"],
      "enabled": true
    }
  }
}

Note: If you installed with uv run, use "command": ["uv", "run", "super-memory"]

Verify Installation

super-memory --version

📋 Prerequisites

Dependency Status Installation
super-memory ⚠️ Required uv tool install super-memory or pip install super-memory
searxng 🔧 Optional Docker: docker run -d -p 8080:8080 --name searxng searxng/searxng
sequential-thinking ✅ Usually pre-installed MCP server: npx -y @modelcontextprotocol/server-sequential-thinking

🚚 Installation

⭐ For the easiest install experience, use the "Vanilla OpenCode Install" prompt above — just copy, paste, and let OpenCode do everything!

Option 2: Manual Install

  1. Install Boomerang from PyPI:
    pip install opencode-boomerang
    # Or if using uv
    uv tool install opencode-boomerang
    
  2. Install super-memory from PyPI:
    pip install super-memory
    # Or if using uv
    uv tool install super-memory
    
  3. Update your .opencode/opencode.json to include the plugin:
    {
      "plugin": ["opencode-boomerang"]
    }
    
  4. Add super-memory and sequential-thinking MCP configurations (see Configuration section below)
  5. Start OpenCode and run /boomerang-init skill
  6. Restart OpenCode for agents to load

⚙️ Configuration

Example opencode.json

{
  "plugin": ["opencode-boomerang"],
  "mcp": {
    "super-memory": {
      "type": "local",
      "command": ["super-memory"],
      "enabled": true
    },
    "searxng": {
      "type": "local",
      "command": ["npx", "-y", "mcp-searxng"],
      "environment": { "SEARXNG_URL": "http://localhost:8080" },
      "enabled": false
    },
    "sequential-thinking": {
      "type": "local",
      "command": ["npx", "-y", "@modelcontextprotocol/server-sequential-thinking"],
      "enabled": true
    }
  }
}

Key Configuration Points

Setting Description
plugin Path to Boomerang plugin dist directory
mcp.super-memory Required — Long-term memory for agents
mcp.searxng Optional — Web search capabilities
mcp.sequential-thinking Usually pre-installed — Chain of thought reasoning

🔄 The Boomerang Protocol (Detailed)

Every Boomerang session follows this strict protocol:

Step 1: Memory Query

At session start, agents query super-memory for:
• Previous decisions and rationale
• Project-specific patterns and conventions
• Known issues and workarounds
• User preferences and habits

Step 2: Think & Plan

The Orchestrator:
• Breaks down the task into subtasks
• Identifies dependencies between subtasks
• Builds an execution DAG (Directed Acyclic Graph)
• Determines which agents to delegate to

Step 3: Delegate

Sub-agents are invoked based on specialty:
• Code generation → boomerang-coder
• Design review → boomerang-architect
• Exploration → boomerang-explorer
• Testing → boomerang-tester
• Quality → boomerang-linter
• Version control → boomerang-git

Step 4: Git Check

Before any work is considered complete:
• git status shows clean working tree (or changes staged)
• Commits are made with descriptive messages
• Branches are properly managed

Step 5: Quality Gates

Mandatory checks before completion:
✓ Lint passes (boomerang-linter)
✓ Typecheck passes (where applicable)
✓ Tests pass (boomerang-tester)
✓ No regression in existing functionality

Step 6: Save Memory

At session end, critical information is saved:
• Key architectural decisions
• Code patterns established
• Lessons learned
• User preferences

🔥 Release Pipeline & Updating

When a new version of Boomerang is released:

1. Check for Updates

gh release view Veedubin/opencode-boomerang --json tagName,createdAt

2. Update Your Installation

# Update Boomerang from PyPI
pip install --upgrade opencode-boomerang
# Or if using uv
uv tool upgrade opencode-boomerang

# Re-run initialization
opencode /boomerang-init

3. Verify Installation

# Check the version in your installed plugin
cat .opencode/plugins/boomerang/package.json | grep version

📁 Release Package Contents

The boomerang.tar.gz release contains:

.opencode/
├── agents/                    # Agent definitions
│   ├── boomerang.md          # Orchestrator
│   ├── boomerang-coder.md    # Code generation
│   ├── boomerang-architect.md # Architecture
│   ├── boomerang-explorer.md  # Exploration
│   ├── boomerang-tester.md    # Testing
│   ├── boomerang-linter.md    # Linting
│   ├── boomerang-git.md       # Git operations
│   └── researcher.md          # Web research
├── skills/                    # Boomerang skills
│   ├── boomerang-architect/
│   ├── boomerang-coder/
│   ├── boomerang-init/
│   ├── boomerang-orchestrator/
│   └── boomerang-tester/
└── plugins/boomerang/        # Plugin implementation
    ├── dist/                  # Compiled JavaScript
    └── package.json

📄 License

MIT License — see LICENSE for details.


Built with 🚀 by Veedubin

Your AI development team, on demand.

Metadata

Release files for opencode-boomerang 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for opencode-boomerang 0.1.2
File Size Uploaded
opencode_boomerang-0.1.2.tar.gz 36.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for opencode-boomerang 0.1.2
File Interpreter ABI Platform
opencode_boomerang-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 97.4 kB

Release files / opencode_boomerang-0.1.2.tar.gz

Download URL opencode_boomerang-0.1.2.tar.gz
Size 36.3 kB
Tags Source
SHA-256 checksum
How to use checksums
80d341612e7e0cd72054847bdb538f085cffa3c2555b49c98a16e009909ebb12
BLAKE2b-256 checksum
How to use checksums
bac837b1ed862089458153f340f3b4410e954f84f05d1c2bc33f783ff1438ccd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.

Transparency log

Release files / opencode_boomerang-0.1.2-py3-none-any.whl

Download URL opencode_boomerang-0.1.2-py3-none-any.whl
Size 61.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a0ee2001da2c5a2c489143fa44f4ace34b8094a2c84bc1cf0fd934244f85f0a7
BLAKE2b-256 checksum
How to use checksums
b9f29c68bfe2898494a2ee3ced341877b30ee20e050dcede9fc36eeba9697b3e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page