OpenCode Orchestrator

🚀 The mothership that deploys AI crews to unknown planet

The STARSHIP hovers above an uncharted planet. No docs. No tests. Just a mission. The Commander speaks: "We don't assume. We explore. We adapt. We conquer." — OpenCode Orchestrator is that STARSHIP, deploying AI crews to complete missions in any planet.

⚡ Quick Start

npm install -g opencode-orchestrator

Then in OpenCode:

/task "Build a REST API with authentication"

The STARSHIP deploys. The crew lands. The mission begins.

🛸 The STARSHIP Protocol

┌───────────────────────────────────────────────────┐
│  🔍 EXPLORE → 📝 LEARN → 🔄 ADAPT → ⚡ ACT          │
│  Scan        Document    Adjust      Execute      │
└───────────────────────────────────────────────────┘

👨‍🚀 The Crew

When the STARSHIP arrives, four specialists deploy:

Agent	Role	Mission
🎯 Commander	The Captain	"I lead the mission. I delegate. I don't leave until it's done."
📋 Planner	The Scientist	"I map the terrain. I document everything. I create paths to follow."
🔨 Worker	The Engineer	"I build with local materials. I adapt to what I find."
✅ Reviewer	The Inspector	"Nothing launches until I verify it. Zero defects."

📖 The Codex

These are the rules every crew member lives by:

Principle	In Practice
🔍 Never Assume Gravity	Read `context.md`, detect stack, find actual commands
📝 Document for Future Missions	Record patterns, conventions, and findings for reuse
📚 Evidence Over Memory	Cite docs, run commands, complete only with proof
🔄 Adapt to the Terrain	Behavior evolves based on what we've documented
🤝 Each Crew Member Has a Role	Specialists don't overlap — they collaborate

🏛️ Mission Control

Inside the STARSHIP, Mission Control coordinates everything:

        🌍 UNKNOWN CODEBASE
                │
        /task "Build REST API"
                │
    ╔═══════════════════════════════════╗
    ║   🛸 STARSHIP MISSION CONTROL     ║
    ╠═══════════════════════════════════╣
    ║  🎯 COMMANDER — "Deploy the crew" ║
    ╚═══════════════╤═══════════════════╝
                    │
    ┌───────────────┼───────────────┐
    ▼               ▼               ▼
┌───────┐      ┌───────┐      ┌───────┐
│PLANNER│      │WORKER │      │WORKER │   ← 🔥 50 PARALLEL
│plan.md│      │auth.ts│      │api.ts │      DEPLOYMENTS
└───────┘      └───────┘      └───────┘
    │               │               │
    └───────────────┼───────────────┘
                    ▼
    ╔═══════════════════════════════════╗
    ║  ✅ REVIEWER — "Final inspection" ║
    ╚═══════════════╤═══════════════════╝
                    │
           ┌────────┴────────┐
           │ TODO 100%?      │
           │ Issues = 0?     │
           └────────┬────────┘
             No ↙       ↘ Yes
          ♻️ LOOP      🎖️ MISSION SEALED

🚀 STARSHIP Capabilities

The STARSHIP isn't just any vessel. It's built for the impossible:

Capability	What It Means
⚡ 50 Parallel Deployments	Deploy up to 50 crew members simultaneously
🔥 Multi-Zone Operations	Workers build different sectors at the same time
🧩 Smart Crew Assignment	One file = one specialist. Zero conflicts
🔗 Real-Time Comms	Shared `.opencode/` state syncs all agents
🛡️ Pre-Launch Verification	E2E tests, import checks, integration validation
🩹 Self-Repair Systems	Auto-recovery with 3 retries per session
🧬 Adaptive AI Cores	Agents evolve based on what they discover

🚨 Emergency Protocols

When things go wrong in space, the STARSHIP knows what to do:

Emergency	Recovery Action
💥 Tool crash	Inject recovery prompt
🚦 Rate limit hit	Exponential backoff + retry
📦 Context overflow	Smart compaction
⏱️ Session timeout	Resume from checkpoint
🔨 Build failure	Loop back, fix, retry

📸 Screenshots

TUI

Window

📚 Documentation

System Architecture — Full technical deep-dive

🎹 Developer's Words

Read the full note →

📄 License

MIT License. LICENSE