explaingit

henrijss/opencode-simple-orchestrator

12Audience · developerComplexity · 3/5Setup · moderate

TLDR

A personal configuration for the Opencode AI coding tool that pairs one capable coordinator model with cheaper specialized subagents for researching docs, exploring code, and running edits across a codebase in a five-phase workflow.

Mindmap

mindmap
  root((orchestrator))
    Agents
      Main coordinator
      Scout research
      Explore read-only
      General workhorse
    Models used
      GPT 5.5 main
      DeepSeek subagents
    Five phases
      Map codebase
      Gather context
      Plan task
      Execute per domain
      Verify results
    Use Cases
      Cost-efficient coding
      Multi-agent workflows
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Use the Scout subagent to look up documentation on Deepwiki or Context7 before any code changes are made

USE CASE 2

Run the five-phase flow to map, plan, and independently execute changes across separate domains of a codebase

USE CASE 3

Adapt the subagent tool restrictions to your own model choices to keep AI coding costs low while keeping the coordinator capable

Tech stack

OpencodeGPT-4.5DeepSeek

Getting it running

Difficulty · moderate Time to first run · 1h+

Requires an Opencode installation with orchestrator support and your own API keys for the coordinator and subagent models.

No license information was mentioned in the explanation.

In plain English

This repository is a personal configuration for the Opencode AI coding tool's orchestrator feature, shared publicly so others can use it as a starting point. The author's README warns clearly that the setup is specific to their own workflow and models, and anyone borrowing it should adapt it rather than copy it directly. The core idea is to run one capable, expensive AI model as a central coordinator that breaks a task into pieces and hands each piece to a cheaper, more focused subagent. The author pairs GPT 5.5 as the main agent with DeepSeek v4 Flash for the subagents. The main agent is permitted to use all tools as a fallback if the subagents fail, but otherwise stays out of direct execution. Three subagents are configured. Scout handles documentation research using Deepwiki, Context7, and web crawlers to look up references. Explore is a read-only agent that verifies files and maps the structure of a codebase. General is the workhorse agent that runs commands and edits files, with access to the full tool set. When a task comes in, the main agent works through five phases: map the relevant parts of the codebase, gather context from those areas, produce a plan, spawn one General subagent per domain to carry out the plan independently, and then spawn verification agents to review the results. The configuration files are intentionally verbose because restricting each agent to only the tools it needs is central to keeping costs low and behavior predictable. The project contains no application code, only prompt and tool configuration intended to be reworked for a different person's setup.

Copy-paste prompts

Prompt 1
How do I adapt the opencode-simple-orchestrator config to use my own models instead of GPT 5.5 and DeepSeek?
Prompt 2
Walk me through how the five orchestration phases work when I give it a task like adding authentication to an API.
Prompt 3
What tools does each subagent have access to in this config, and why is the Explore agent restricted to read-only operations?
Prompt 4
How do I configure the Scout agent to search Deepwiki and Context7 for documentation before General starts editing files?
Open on GitHub → Explain another repo

← henrijss on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.