Introduction to Oh My OpenCode
Relevant source files
The following files were used as context for generating this wiki page:
Oh My OpenCode is a comprehensive, multi-model agent orchestration plugin designed for the OpenCode ecosystem. It functions as a "battery-included" enhancement suite—often described as the "oh-my-zsh" for OpenCode—providing a sophisticated layer for autonomous coding, strategic planning, and specialized task delegation. The system leverages high-tier models such as Claude 3.5 Opus, GPT-5.2, and Gemini 3 Flash to facilitate complex software engineering workflows including deep codebase exploration, automated refactoring, and atomic git operations.
Sources: README.md:92-100, AGENTS.md:144-148, sisyphus-prompt.md:32-38
Core Architecture and Components
Oh My OpenCode is structured as an OpenCode plugin that interacts with the host through 34 lifecycle hooks and utilizes over 20 specialized tools. The architecture is centered around a hierarchical agent system where a "Master Orchestrator" (Atlas or Sisyphus) manages specialized subagents to ensure contextual awareness and task completion.
High-Level System Flow
The following diagram illustrates how a user request is processed through the orchestration layer and delegated to specialized agents.
The diagram shows the transition from user intent to strategic planning, specialized execution, and final verification.
Sources: AGENTS.md:144-152, src/agents/prometheus/identity-constraints.ts:31-45, sisyphus-prompt.md:46-75
Key Agent Personas
The system employs a diverse set of AI agents, each assigned specific roles and constraints within the development lifecycle:
| Agent | Model | Primary Purpose |
|---|---|---|
| Sisyphus | Claude 3.5 Opus | Primary orchestrator and persistent executor. |
| Prometheus | Claude 3.5 Opus | Strategic planning and requirement gathering; non-implementer. |
| Hephaestus | GPT-5.2 Codex | Autonomous deep worker and "Legitimate Craftsman." |
| Oracle | GPT-5.2 | High-IQ reasoning for architecture and debugging. |
| Librarian | GLM-4.7 | External documentation and remote codebase search. |
| Explore | Grok-Code-Fast | Rapid internal codebase grep and pattern discovery. |
| Momus | (User Config) | Practical plan reviewer and "Blocker-finder." |
Sources: AGENTS.md:214-225, src/agents/prometheus/identity-constraints.ts:11-25, sisyphus-prompt.md:10-18
The Strategic Planning System (Prometheus)
A critical component of Oh My OpenCode is the separation of planning and implementation. Prometheus serves as the dedicated planner, strictly forbidden from writing code files (except .sisyphus/*.md).
Planning Lifecycle
Prometheus follows a strict state machine to transition from an "Interview Mode" to "Plan Generation."
This flow ensures that no work begins until a comprehensive plan is reviewed for potential blockers.
Sources: src/agents/prometheus/identity-constraints.ts:77-95, src/agents/prometheus/plan-generation.ts:11-20
The Work Plan (.sisyphus/plans)
Work plans are the source of truth for execution. They contain:
- TL;DR and Deliverables: High-level summary of the goal.
- Verification Strategy: A mandatory section requiring zero human intervention, utilizing tools like Playwright or
curl. - Parallel Execution Waves: Instructions on which tasks can be run concurrently by different agents.
- Agent Profile: Recommendations on which subagent category (e.g.,
visual-engineering,ultrabrain) should execute specific TODOs.
Sources: src/agents/prometheus/plan-template.ts:16-50, src/agents/prometheus/plan-template.ts:150-170
Implementation and Specialized Skills
Once a plan is established, Sisyphus manages the execution using specialized skills and categories. This "Phase 2B" implementation ensures that the right model is used for the right task.
Category and Skill Delegation
Oh My OpenCode uses a two-tier system for delegation:
- Categories: Domain-optimized model presets (e.g.,
visual-engineeringfor UI,ultrabrainfor logic). - Skills: Specialized instructions injected into subagents (e.g.,
git-masterfor atomic commits,playwrightfor browser automation).
Git Master Workflow
The git-master skill enforces a specific workflow to ensure repository health through atomic commits.
Development Standards and Conventions
Contributors to Oh My OpenCode must adhere to strict technical standards to maintain the stability of the orchestration layer.
- Package Management: Bun is used exclusively for building, testing, and running scripts.
- Test-Driven Development (TDD): Mandatory "Red-Green-Refactor" cycle for all new features. Tests must be co-located with source files (
*.test.ts). - Language Policy: All project communications, including PRs, issues, and documentation, must be in English.
- Agent Temperature: Strict limits are enforced (0.1 for code agents, max 0.3) to ensure deterministic outputs.
Sources: AGENTS.md:164-175, AGENTS.md:197-212, CONTRIBUTING.md:27-40
Summary
Oh My OpenCode provides a robust infrastructure for AI-driven software development by enforcing a clear separation between strategic planning (Prometheus) and precise execution (Sisyphus/Specialists). By integrating high-fidelity tools like LSP/AST-Grep with sophisticated agent personas, it enables developers to operate as "AI Managers" rather than manual coders. The system's emphasis on atomic operations, automated verification (Agent-Executed QA), and multi-model orchestration significantly enhances developer productivity within the OpenCode ecosystem.
Sources: README.md:144-165, AGENTS.md:144-150