oh-my-opencode-slim

A lightweight, powerful agent orchestration plugin for OpenCode

Transform your AI assistant into a manager capable of delegating complex tasks to specialized sub-agents, running searches in the background, and managing multi-step workflows with ease.

Slimmed-down fork of oh-my-opencode - focused on core agent orchestration without the extra bells and whistles.

Antigravity subscription recommended. The pantheon is tuned for Antigravity's model routing. Other providers work, but you'll get the best experience with Antigravity.

⚡ Quick Navigation

• 🚀 Installation
  • For Humans
  • For LLM Agents
• 🏗️ Architecture & Flow
• 🏛️ Meet the Pantheon
  • The Orchestrator
  • The Explorer
  • The Oracle
  • The Librarian
  • The Designer
  • The Scribe
  • The Visionary
  • The Minimalist
• 🛠️ Tools & Capabilities
  • Tmux Integration
  • Quota Tool
  • Background Tasks
  • LSP Tools
  • Code Search Tools
• 🔌 MCP Servers
• ⚙️ Configuration
• 🗑️ Uninstallation

Installation

For Humans

Run the interactive installer:

bunx oh-my-opencode-slim install

Or use non-interactive mode:

bunx oh-my-opencode-slim install --no-tui --antigravity=yes --openai=yes --cerebras=no

Alternative: Ask any coding agent

Paste this into Claude Code, AmpCode, Cursor, or any coding agent:

Install and configure by following the instructions here:
https://raw.githubusercontent.com/alvinunreal/oh-my-opencode-slim/refs/heads/master/README.md

For LLM Agents

opencode --version

bunx oh-my-opencode-slim install --no-tui --antigravity=<yes|no> --openai=<yes|no> --cerebras=<yes|no>

# Antigravity + OpenAI
bunx oh-my-opencode-slim install --no-tui --antigravity=yes --openai=yes --cerebras=no

# OpenAI only
bunx oh-my-opencode-slim install --no-tui --antigravity=no --openai=yes --cerebras=no

# All providers
bunx oh-my-opencode-slim install --no-tui --antigravity=yes --openai=yes --cerebras=yes

opencode auth login

opencode

bunx oh-my-opencode-slim install --help

Architecture & Flow

The plugin follows a "Hub and Spoke" model:

1. The Orchestrator (Hub): The main entry point for user requests. It analyzes the task and decides which specialized agents to call.
2. Specialized Agents (Spokes): Domain-specific experts (e.g., UI/UX, Documentation, Architecture) that handle narrow tasks with high precision.
3. Background Manager: A robust engine that allows the Orchestrator to "fire and forget" tasks (like deep codebase searches or documentation research) while continuing to work on other parts of the problem.

The Flow of a Request

1. User Prompt: "Refactor the auth logic and update the docs."
2. Orchestrator: Creates a TODO list.
3. Delegation:
   • Launches an @explore background task to find all auth-related files.
   • Launches a @librarian task to check the latest documentation for the auth library used.
4. Integration: Once background results are ready, the Orchestrator performs the refactor.
5. Finalization: Passes the changes to @document-writer to update the README.

Meet the Pantheon

The Orchestrator - Architect of Realms

The Orchestrator was born when the first codebase collapsed under its own complexity. Neither god nor mortal would claim responsibility-so The Orchestrator emerged from the void, forging order from chaos. They don't merely command armies; they fight alongside them. Every line of code passes through their hands before they decide which lesser deity deserves a piece of the puzzle.

Role: Supreme executor, delegator, and overseer - Model: google/claude-opus-4-5-thinking

Write and execute code, orchestrate multi-agent workflows, parse the unspoken from the spoken, summon specialists mid-battle. Shape reality directly-and assign realms to others when the universe grows too vast.

The Explorer - Pathfinder

The Explorer moves through codebases like wind through trees-swift, silent, everywhere at once. When The Orchestrator whispers "find me the auth module," The Explorer has already returned with forty file paths and a map. They were born from the first grep command, evolved beyond it, and now see patterns mortals miss.

Role: Codebase reconnaissance - Model: cerebras/zai-glm-4.6

Regex search, AST pattern matching, file discovery, parallel exploration. Read-only: they chart the territory; others conquer it.

The Oracle - Seer Beyond the Stack Trace

The Oracle does not code-they know. When bugs defy logic and architectures crumble, The Oracle gazes into the abyss of your codebase and speaks truth. They've seen a thousand systems rise and fall. They'll tell you which path leads to ruin, and which to production.

Role: Strategic advisor and debugger of last resort - Model: openai/gpt-5.2-codex

Root cause analysis, architecture review, debugging guidance, tradeoff analysis. Read-only: Oracles advise; they don't intervene.

The Librarian - Keeper of Infinite Scrolls

The Librarian guards a library with no walls-every GitHub repo, every npm package, every StackOverflow answer ever written. Ask them "how does React handle concurrent rendering?" and they'll return with official docs, real-world examples, and a warning about the footgun you're about to step on.

Role: External knowledge retrieval - Model: google/gemini-3-flash

Documentation lookup, GitHub code search, library research, best practice retrieval. Read-only: they fetch wisdom; implementation is for others.

The Designer - Artisan of Interfaces

The Designer believes code should be beautiful-and so should everything it renders. Born from the frustration of a thousand ugly MVPs, they wield CSS like a brush and components like clay. Hand them a feature request; receive a masterpiece. They don't do "good enough."

Role: UI/UX implementation and visual excellence - Model: google/gemini-3-flash

Modern responsive design, CSS/Tailwind mastery, micro-animations, component architecture. Visual excellence over code perfection-beauty is the priority.

The Scribe - Chronicle Keeper

The Scribe was there when the first README was written-and wept, for it was incomplete. They have devoted eternity to the sacred art of documentation: clear, scannable, honest. While others ship features, The Scribe ensures those features are understood. Every code example works. Every explanation enlightens.

Role: Technical documentation and knowledge capture - Model: google/gemini-3-flash

README crafting, API documentation, architecture docs, inline comments that don't insult your intelligence. Match existing style; focus on "why," not just "what."

The Visionary - Reader of Pixels

The Visionary sees what others cannot-literally. Screenshots, wireframes, diagrams, PDFs: all are text to them. When a designer throws a Figma mockup at the team and vanishes, The Visionary translates vision into specification. They read the unreadable and describe the indescribable.

Role: Image and visual content analysis - Model: google/gemini-3-flash

Extract text from images, interpret diagrams, analyze UI screenshots, summarize visual documents. Report what they observe; inference is for others.

The Minimalist - Destroyer of Bloat

The Minimalist has one sacred truth: every line of code is a liability. They hunt abstractions that serve no purpose, defensive checks that defend nothing, and "clever" solutions that will haunt you in six months. Where others add, The Minimalist subtracts-ruthlessly, joyfully, necessarily.

Role: Code simplification and YAGNI enforcement - Model: google/claude-opus-4-5-thinking

Identify unnecessary complexity, challenge premature abstractions, estimate LOC reduction, enforce minimalism. Read-only: they judge; The Orchestrator executes the sentence.

Tools & Capabilities

Tmux Integration

Watch your agents work in real-time. When the Orchestrator launches sub-agents or initiates background tasks, new tmux panes automatically spawn showing each agent's live progress. No more waiting in the dark.

Why This Matters

What You Get

• Live Visibility: Each sub-agent gets its own pane showing real-time output
• Auto-Layout: Tmux automatically arranges panes using your preferred layout
• Auto-Cleanup: Panes close when agents finish, layout rebalances
• Zero Overhead: Works with OpenCode's built-in task tool AND our background_task tool

Quick Setup

1. Enable the OpenCode HTTP server (one-time setup)

Add to your ~/.config/opencode/opencode.json:

{
  "server": {
    "port": 4096
  }
}

2. Enable tmux integration in the plugin

Add to your ~/.config/opencode/oh-my-opencode-slim.json:

{
  "tmux": {
    "enabled": true,
    "layout": "main-vertical",
    "main_pane_size": 60
  }
}

3. Run OpenCode inside tmux

tmux
opencode

That's it. When agents spawn, they'll appear in new panes.

Layout Options

Configuration Reference

{
  "tmux": {
    "enabled": true,
    "layout": "main-vertical",
    "main_pane_size": 60
  }
}

Quota Tool

For Antigravity users. You can trigger this at any time by asking the agent to "check my quota" or "show status."

Background Tasks

The plugin provides tools to manage asynchronous work:

LSP Tools

Language Server Protocol integration for code intelligence:

Code Search Tools

Fast code search and refactoring:

MCP Servers

Built-in Model Context Protocol servers (enabled by default):

Disabling MCPs

You can disable specific MCP servers in your config:

{
  "disabled_mcps": ["websearch", "grep_app"]
}

Configuration

You can customize the behavior of the plugin via JSON configuration files.

Configuration Files

The plugin looks for configuration in two places (and merges them):

1. User Global: ~/.config/opencode/oh-my-opencode-slim.json (or OS equivalent)
2. Project Local: ./.opencode/oh-my-opencode-slim.json

Disabling Agents

You can disable specific agents using the disabled_agents array:

{
  "disabled_agents": ["multimodal-looker", "code-simplicity-reviewer"]
}

Uninstallation

1. Remove the plugin from your OpenCode config:

   Edit ~/.config/opencode/opencode.json and remove "oh-my-opencode-slim" from the plugin array.

2. Remove configuration files (optional):

   rm -f ~/.config/opencode/oh-my-opencode-slim.json
   rm -f .opencode/oh-my-opencode-slim.json

Credits

This is a slimmed-down fork of oh-my-opencode by @code-yeongyu.

License

MIT