Back to BlogAI & Development Tools![[EP3] oh-my-opencode vs MoAI-ADK - Enhancement Layer In-Depth Analysis](/_next/image?url=%2Fimages%2Fposts%2F2026%2F01%2Fmoai-adk-oh-my-opencode-vs-moai-ep3%2Fcard.png&w=3840&q=75)
[EP3] oh-my-opencode vs MoAI-ADK - Enhancement Layer In-Depth Analysis
9.695min
oh-my-opencodeMoAI-ADKAgent SystemToS RiskClaude Code ExtensionOpenCode ExtensionSPEC-First TDD
In-depth comparative analysis of the OpenCode extension framework oh-my-opencode and Claude Code-based MoAI-ADK from the perspectives of agent ecosystem, ToS risk, execution capability, and user control.
![[EP3] oh-my-opencode vs MoAI-ADK - Enhancement Layer In-Depth Analysis](/_next/image?url=%2Fimages%2Fposts%2F2026%2F01%2Fmoai-adk-oh-my-opencode-vs-moai-ep3%2Fcard.png&w=3840&q=75)
SeriesEP 3 / 5
Analysis Overview
This episode provides a comparative analysis of the Enhancement Layer built on top of Base Layer tools. oh-my-opencode extends OpenCode, while MoAI-ADK extends Claude Code.
The focus is particularly on the stability and long-term viability of each tool after Anthropic's technical restrictions in January 2026.
1. Basic Architecture Comparison
| Item | oh-my-opencode | MoAI-ADK |
|---|---|---|
| Foundation | OpenCode plugin | Claude Code official CLI extension |
| GitHub | https://github.com/code-yeongyu/oh-my-opencode | https://github.com/modu-ai/moai-adk |
| Main Agent | Sisyphus (Claude Opus 4.5, 32K tokens) | Alfred orchestrator |
| Model Support | Multi-model (Claude, GPT, Gemini) | 3 LLM modes (opus/hybrid/glm) |
| GitHub Stars | stars: 13k / as of January 10 | stars: 450 / as of January 10 |
| License | SUL-1.0 (Sustainable Use License) | Copyleft (open-source) |
| Development Investment | $24,000 token cost | 1.3B token development |
| Skill System | ā None | ā 90+ domain skills |
| Supported Languages | Model-dependent | 16 programming languages |
| UI Languages | English-centric | 4 languages (EN, KO, JA, ZH) |
2. ToS and Stability Comparison
2.1 January 2026 Anthropic Technical Restriction
Plain Text
šØ CRITICAL UPDATEError message: "This credential is only authorized for use with Claude Code."Impact:āāā Cannot use Claude Code OAuth tokens in third-party tools (including OpenCode)āāā Multiple account suspension cases reported when using OpenCode with OAuth subscriptionāāā Recommended workaround: Use Anthropic API key directly (incurs additional costs)
This change neutralizes oh-my-opencode's core value proposition. oh-my-opencode originally advocated the following approach:
"START WITH YOUR ChatGPT, Claude, Gemini SUBSCRIPTIONS. WE ALL COVER THEM."
The core was the ability to use advanced features without additional costs by utilizing existing subscriptions. However, since January 2026, with Claude subscription usage no longer possible, direct API key purchase has become necessary.
3. Agent Ecosystem Comparison
3.1 oh-my-opencode Team Composition (6 Specialized Agents)
Plain Text
Sisyphus (Claude Opus 4.5, 32K tokens) - Orchestratorāāā Oracle (GPT-5.2): Strategic reasoning and debuggingāāā Librarian (Claude Sonnet 4.5 / Gemini 3 Flash): Documentation and analysisāāā Frontend UI/UX (Gemini 3 Pro): UI/UX developmentāāā Document-Writer: Documentation specialistāāā Multimodal-Looker: Image/screenshot analysisāāā Explore: Fast codebase pattern matching
Performance cases reported by community (December 2025 ~ January 2026):
Ed Huang (PingCAP CTO, January 4, 2026)
"Recently rewrote an old PostgreSQL-compatible SQL layer with oh-my-opencode."
Jacob Ferrari (December 22, 2025)
"Processed 8,000 ESLint warnings in one day."
James Hargis (January 2, 2026)
"Converted a 45,000-line Tauri app to SaaS overnight."
However, criticism of oh-my-opencode's cost efficiency exists. Token costs of $50-100 per session may occur, earning it the nickname "Token Furnace."
3.2 MoAI-ADK Agent Ecosystem (20 agents)
Plain Text
Alfred Orchestratorāāā Manager Agents (8)ā āāā manager-git: Commit, branch, PR managementā āāā manager-spec: EARS format requirements, acceptance criteriaā āāā manager-tdd: RED-GREEN-REFACTOR cycleā āāā manager-docs: README, API docs, technical documentationā āāā manager-quality: TRUST 5 validation, code reviewā āāā manager-project: Project setup, configurationā āāā manager-strategy: Architecture decisions, technology evaluationā āāā manager-claude-code: Claude Code configuration, MCP integrationāāā Expert Agents (8)ā āāā expert-backend: API design, authentication, databaseā āāā expert-frontend: React, Vue, Next.js, componentsā āāā expert-security: OWASP, vulnerability assessment, secure codingā āāā expert-devops: CI/CD, Docker, Kubernetesā āāā expert-performance: Profiling, optimization, benchmarkingā āāā expert-debug: Error diagnosis, troubleshooting, root cause analysisā āāā expert-testing: E2E, integration testing, QA automationā āāā expert-refactoring: AST-based transformation, large-scale changesāāā Builder Agents (4)āāā builder-agent: Custom agent creationāāā builder-command: Slash command developmentāāā builder-skill: Knowledge skill authoringāāā builder-plugin: Marketplace plugin development
4. Core Feature Comparison
| Feature | oh-my-opencode | MoAI-ADK |
|---|---|---|
| Activation Keywords | ultrawork, ulw | /moai:alfred, skill commands |
| Parallel Execution | ā Background tasks | ā 3-tier parallel (Tool/Agent/Worktree) |
| LSP Support | ā IDE-level tools | ā AST-grep integration |
| Refactoring | ā Full LSP + AST-Grep | ā expert-refactoring + AST-grep |
| Git Integration | ā Git Master Skill | ā manager-git + worktree isolation |
| Session Management | ā 85% context compression | ā Multi-terminal /clear recommendation system |
| TDD Support | ā No explicit (unconfirmed) | ā SPEC-First TDD (RED-GREEN-REFACTOR) |
| Quality Gates | ā No explicit (unconfirmed) | ā TRUST 5 validation |
5. Execution Capability Comparison
The biggest philosophical difference between the two frameworks lies in execution capability.
5.1 oh-my-opencode: "Relentless Execution"
oh-my-opencode uses the "Todo Continuation Enforcer" pattern:
- Forces agents not to give up midway
- Unlimited execution until goal completion
- Completion detected by
<promise>DONE</promise>marker
This approach provides strong execution capability but requires giving up significant user control.
5.2 MoAI-ADK: "Checkpoint-Based Execution"
MoAI-ADK provides 8 control mechanisms:
- AskUserQuestion Checkpoints: User confirmation at major decision points
- Type A Command Constraints: Workflow commands allow Task only
- TRUST 5 Quality Gates: Progress blocked when quality criteria not met
- Git Checkpoints: Rollback possible with automatic backups
- Subagent Isolation: Limited permission scope for each agent
- Configuration-Based Control: Customize behavior via .moai/config/
- Resumable Patterns: Resume interrupted work via agentId
- Output Style Enforcement: Consistent response styles like R2-D2, Yoda
oh-my-opencode Execution Model
Loading diagram...
MoAI-ADK Execution Model
Loading diagram...
5.3 User Control
| Aspect | oh-my-opencode | MoAI-ADK |
|---|---|---|
| Execution Philosophy | Unlimited autonomous execution | Checkpoint-based execution |
| Intermediate Confirmation | Minimized (execute to completion) | Mandatory approval per phase |
| Runaway Risk | ā ļø Present | ā Prevented with 8 controls |
| Intent Deviation | Possible | Minimized with AskUserQuestion |
6. Context Efficiency Comparison
6.1 oh-my-opencode
- Preemptive Compaction: Automatic summarization at 85% context usage
- Extract only necessary information through multimodal analysis
- Directory-Specific Context Injection (automatic AGENTS.md collection)
6.2 MoAI-ADK
- 200K Token Budget Management: 7.5% system + 75% conversation + 10% reference + 7.5% reserve
- /clear recommendation system (token prediction + automatic guidance)
- Progressive Disclosure (5-Tier loading)
- Preemptive Compaction: Automatic summarization at 85% context usage
- Configuration modularization (sections/*.yaml)
- Reduction Rate: 60-70%
7. Workflow Philosophy Comparison
7.1 oh-my-opencode Automatic Task Decomposition and Team Allocation
Loading diagram...
7.2 MoAI-ADK Workflow: /moai:alfred One-Click Automation
The core of MoAI-ADK is the 759-line /moai:alfred command. A single command automates the entire development lifecycle from requirements definition to PR creation.
Intelligent Routing
alfred analyzes requests to determine optimal execution paths:
Loading diagram...
3-Phase Workflow
Loading diagram...
Quality Gate Checkpoints
Quality validation is mandatory at each Phase transition:
| Gate | Condition | Options on Failure |
|---|---|---|
| Phase 1 ā 2 | User SPEC approval | Modify, save draft, cancel |
| Phase 2 ā 3 | 85%+ coverage, TRUST 5 passed | Retry, override, manual fix |
| Phase 3 Complete | Documentation synced, Git commit | Resolve conflicts, force sync |
Multi-LLM Mode
alfred supports 3 LLM modes:
| Mode | Plan (Phase 1) | Run/Sync (Phase 2-3) | Usage Scenario |
|---|---|---|---|
| Claude-only | Claude Opus | Claude sonnet + haiku | High quality required, single terminal |
| MashUp | Claude Opus or Sonnet | GLM 4.7 (worktree) | Cost optimization, parallel work |
| glm-only | GLM 4.7 | GLM 4.7 (worktree) | Cost minimization |
Interrupt/Resume Support
Workflow state is preserved even when interrupted:
Bash
# Resume interrupted workflow/moai:alfred SPEC-AUTH-001 continue please!!# State storage location: .moai/cache/alfred-{spec-id}.json
Usage Examples
Bash
# Basic usage/moai:alfred "User authentication with JWT tokens"# Automatic branch creation/moai:alfred "Shopping cart feature" --branch# Automatic PR creation/moai:alfred "Payment integration" --branch --pr
7.3 Quality Assurance
| Aspect | oh-my-opencode | MoAI-ADK |
|---|---|---|
| Quality Framework | Implicit | TRUST 5 explicit |
| TDD Enforcement | ā | ā RED-GREEN-REFACTOR |
| Code Review | Optional | manager-quality mandatory |
| Test Coverage | Not measured | Target setting (default 85%) |
8. Selection Guide
When oh-my-opencode is Suitable
- When preferring autonomous execution: When wanting work to proceed without intervention after starting
- When wanting to utilize various models: When wanting to switch and use GPT, Claude, Gemini according to situation
- When rapid prototyping is needed: Early development stage where speed is more important than quality
Caution: Cannot use Claude subscription since January 2026. Direct API key purchase required. OpenAI subscription model usable.
When MoAI-ADK is Suitable
- When ToS compliance is important: When wanting stable use without account suspension risk
- When quality-focused development is needed: Enterprise environment where TDD, code review, quality gates are essential
- When wanting controlled automation: When balance between AI's strong execution capability and user control is needed
- When conducting long-term projects: When stable tool support and consistent quality are important
Next Episode Preview
The next episode EP.4: MoAI-ADK Core Technology Deep Dive provides an in-depth analysis of MoAI-ADK's core technologies:
- /moai:alfred: 759-line one-click development automation command
- Ralph Engine: LSP + AST-grep + Loop Controller integrated quality engine
- Anti-Hallucination Strategy: 90+ domain skills system