Skip to content

AidenGeunGeun/OpencodeOrchestra

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

197 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OpenCodeOrchestra

OpenCodeOrchestra

Your AI agent doesn't need 15 tools. It needs a team.

PM plans. Orchestrator executes. Specialists investigate, review, research, and document.
Each role has its own depth, permissions, and model. Like a real engineering team.

GitHub Release GitHub Stars License

A fork of OpenCode v1.2.5 · AI SDK 6.x · GPT-5.4 default agent stack


Install in 30 seconds

Release downloads by platform

Platform Recommended download
macOS Desktop .dmg
Ubuntu / Debian Desktop .deb
Fedora / RHEL Desktop .rpm
Windows CLI .zip
Linux terminal-only CLI .tar.gz

Tip

For Agents — paste this into your LLM agent (Claude Code, OpenCode, Cursor, etc.):

Install and configure OpenCodeOrchestra by following the instructions here:
https://raw.githubusercontent.com/AidenGeunGeun/OpencodeOrchestra/main/docs/installation.md

For Humans — copy, paste, run:

# Download the latest binary from GitHub Releases, put it on your PATH
# macOS: codesign -f -s - ~/.local/bin/oco

mkdir -p \
  ~/.config/oco/prompts \
  ~/.config/oco/skills/agents-md/references \
  ~/.config/oco/skills/skill-creator/references

curl -fsSL https://raw.githubusercontent.com/AidenGeunGeun/OpencodeOrchestra/main/config/oco.jsonc -o ~/.config/oco/oco.jsonc
for f in pm orchestrator investigator auditor web-search docs compaction; do
  curl -fsSL "https://raw.githubusercontent.com/AidenGeunGeun/OpencodeOrchestra/main/config/prompts/${f}.txt" -o ~/.config/oco/prompts/${f}.txt
done

curl -fsSL https://raw.githubusercontent.com/AidenGeunGeun/OpencodeOrchestra/main/config/skills/agents-md/SKILL.md -o ~/.config/oco/skills/agents-md/SKILL.md
curl -fsSL https://raw.githubusercontent.com/AidenGeunGeun/OpencodeOrchestra/main/config/skills/agents-md/references/examples.md -o ~/.config/oco/skills/agents-md/references/examples.md
curl -fsSL https://raw.githubusercontent.com/AidenGeunGeun/OpencodeOrchestra/main/config/skills/agents-md/references/detection-patterns.md -o ~/.config/oco/skills/agents-md/references/detection-patterns.md
curl -fsSL https://raw.githubusercontent.com/AidenGeunGeun/OpencodeOrchestra/main/config/skills/skill-creator/SKILL.md -o ~/.config/oco/skills/skill-creator/SKILL.md
curl -fsSL https://raw.githubusercontent.com/AidenGeunGeun/OpencodeOrchestra/main/config/skills/skill-creator/references/schemas.md -o ~/.config/oco/skills/skill-creator/references/schemas.md

oco auth login
oco

That's it. You have a PM, an Orchestrator, and four specialist agents. Full setup guide →

If you already have an older ~/.config/opencode/ install, the new binary reads it as a fallback until you migrate. Run scripts/migrate-config.sh to copy missing config, prompts, state, and cache files into the new oco namespace and duplicate opencode.jsonc / opencode.json as oco.jsonc / oco.json.

Updating

OCO does not auto-update. To update, check GitHub Releases, download the newest release for your platform, and reinstall it using the same steps as your initial install.


The Problem

Vanilla OpenCode has two agents: build and plan. They share everything — context, permissions, tools. You prompt, it codes, you hope for the best.

That works for small tasks. It falls apart when you need multi-file changes, architecture decisions, or anything where "the AI went off the rails" means hours of rework.

The Fix

OCO splits the work the way a real team would:

You
 │
 ▼
PM (Depth 0) ─── talks to you, investigates, drafts specs
 │
 ├──▶ Orchestrator (Depth 1) ─── executes the approved spec
 │         │
 │         ├──▶ Investigator ─── reads code, traces calls, reports facts
 │         ├──▶ Auditor ─── reviews changes, returns PASS or FAIL
 │         ├──▶ Web-Search ─── fetches info from the web
 │         └──▶ Docs ─── updates documentation
 │
 ▼
You review, approve, or redirect

The PM doesn't write code. The Orchestrator doesn't talk to you. The Investigator can't edit files. Each agent does one thing, scoped to its depth level.


How It Works

Step What happens
1 You describe what you want to the PM
2 PM investigates the codebase and drafts a spec
3 You approve (or adjust) the spec
4 PM hands off to the Orchestrator
5 Orchestrator implements through focused subagents
6 Auditor reviews the full changeset — PASS or FAIL
7 Orchestrator calls handoff_to_pm to return control to PM
8 PM reports results and follow-ups back to you

No free-form "just go implement this." Spec first, approval gate, audit loop, clean handoff.


Agents


PM

Orchestrator

Investigator

Auditor

Web-Search

Docs
Agent Depth Default Model Recommended What it does Constraint
PM (build / plan) 0 GPT-5.4 Heavy model (GPT-5.4, Claude Opus) Talks to you. Investigates, plans, writes specs, delegates. Must get your approval before execution
Orchestrator 1 GPT-5.4 Heavy model (GPT-5.4, Claude Opus) Executes the approved spec. Spawns subagents. Runs the audit loop. Must call handoff_to_pm to return control
Investigator 2+ GPT-5.4 mini Fast model (GPT-5.4 mini, Claude Sonnet) Reads code, traces call chains, cross-references files. Read-only. No editing, no shell.
Auditor 2+ GPT-5.4 Heavy model (GPT-5.4, Claude Sonnet) Reviews changes against the spec. PASS/FAIL verdict. Read-only. No editing, no shell.
Web-Search 2+ GPT-5.4 mini Fast model (GPT-5.4 mini, Claude Sonnet) Searches the web and returns evidence with source citations. Read-only. No editing.
Docs 2+ GPT-5.4 mini Fast model (GPT-5.4 mini, Claude Sonnet) Updates README, docs, API references. Docs scope only.

Note

The shipped config defaults every agent to OpenAI.
PM, Orchestrator, and Auditor use GPT-5.4; Investigator, Web-Search, Docs, and Compaction use GPT-5.4 mini. Claude remains a supported swap if you prefer it. See customization →


What Makes This Different

Vanilla OpenCode OCO
Agent structure Flat — two agents share everything Hierarchical — PM → Orchestrator → Subagents
Before execution Nothing Spec approval gate
Code review Hope the model checks itself Dedicated Auditor with PASS/FAIL
Depth enforcement None Runtime enforced — agents can't escape their level
Execution handoff Single-shot stdin/stdout Durable handoff_to_pm steering message with summary
AI SDK 5.x 6.x with Claude 4.6 adaptive thinking

Documentation

Doc What's in it
Installation Zero-to-working setup — agent-followable and human-readable
Architecture Why the hierarchy exists, depth model, spec workflow, audit loop
Agents Each agent's role, model, permissions, and prompt design
Customization Model swaps, plugins, MCPs, and recipes for different setups
Upstream Diff Code-level divergence from OpenCode 1.2.5

Build From Source

git clone https://github.com/AidenGeunGeun/OpencodeOrchestra.git
cd OpencodeOrchestra && bun install
cd packages/opencode && bun run build --single --skip-install
# Binary: dist/@skybluejacket/oco-<platform>-<arch>/bin/oco

Requires Bun. macOS binaries must be ad-hoc signed: codesign -f -s - ./oco

See CONTRIBUTING.md for development workflow.


Config and prompts ship in config/ — no more "works on my machine" agent setups.

Get started →

About

Multi-layer agent orchestration. PM plans, specialists execute.

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors