Back to Blog
AI & Development Tools

[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

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

Itemoh-my-opencodeMoAI-ADK
FoundationOpenCode pluginClaude Code official CLI extension
GitHubhttps://github.com/code-yeongyu/oh-my-opencodehttps://github.com/modu-ai/moai-adk
Main AgentSisyphus (Claude Opus 4.5, 32K tokens)Alfred orchestrator
Model SupportMulti-model (Claude, GPT, Gemini)3 LLM modes (opus/hybrid/glm)
GitHub Starsstars: 13k / as of January 10stars: 450 / as of January 10
LicenseSUL-1.0 (Sustainable Use License)Copyleft (open-source)
Development Investment$24,000 token cost1.3B token development
Skill SystemāŒ Noneāœ… 90+ domain skills
Supported LanguagesModel-dependent16 programming languages
UI LanguagesEnglish-centric4 languages (EN, KO, JA, ZH)

2. ToS and Stability Comparison

2.1 January 2026 Anthropic Technical Restriction

Plain Text
🚨 CRITICAL UPDATE
Error 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

Featureoh-my-opencodeMoAI-ADK
Activation Keywordsultrawork, 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:
  1. AskUserQuestion Checkpoints: User confirmation at major decision points
  2. Type A Command Constraints: Workflow commands allow Task only
  3. TRUST 5 Quality Gates: Progress blocked when quality criteria not met
  4. Git Checkpoints: Rollback possible with automatic backups
  5. Subagent Isolation: Limited permission scope for each agent
  6. Configuration-Based Control: Customize behavior via .moai/config/
  7. Resumable Patterns: Resume interrupted work via agentId
  8. 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

Aspectoh-my-opencodeMoAI-ADK
Execution PhilosophyUnlimited autonomous executionCheckpoint-based execution
Intermediate ConfirmationMinimized (execute to completion)Mandatory approval per phase
Runaway Riskāš ļø Presentāœ… Prevented with 8 controls
Intent DeviationPossibleMinimized 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:
GateConditionOptions on Failure
Phase 1 → 2User SPEC approvalModify, save draft, cancel
Phase 2 → 385%+ coverage, TRUST 5 passedRetry, override, manual fix
Phase 3 CompleteDocumentation synced, Git commitResolve conflicts, force sync

Multi-LLM Mode

alfred supports 3 LLM modes:
ModePlan (Phase 1)Run/Sync (Phase 2-3)Usage Scenario
Claude-onlyClaude OpusClaude sonnet + haikuHigh quality required, single terminal
MashUpClaude Opus or SonnetGLM 4.7 (worktree)Cost optimization, parallel work
glm-onlyGLM 4.7GLM 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

Aspectoh-my-opencodeMoAI-ADK
Quality FrameworkImplicitTRUST 5 explicit
TDD EnforcementāŒāœ… RED-GREEN-REFACTOR
Code ReviewOptionalmanager-quality mandatory
Test CoverageNot measuredTarget setting (default 85%)

8. Selection Guide

When oh-my-opencode is Suitable

  1. When preferring autonomous execution: When wanting work to proceed without intervention after starting
  2. When wanting to utilize various models: When wanting to switch and use GPT, Claude, Gemini according to situation
  3. 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

  1. When ToS compliance is important: When wanting stable use without account suspension risk
  2. When quality-focused development is needed: Enterprise environment where TDD, code review, quality gates are essential
  3. When wanting controlled automation: When balance between AI's strong execution capability and user control is needed
  4. 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:
  1. /moai:alfred: 759-line one-click development automation command
  2. Ralph Engine: LSP + AST-grep + Loop Controller integrated quality engine
  3. Anti-Hallucination Strategy: 90+ domain skills system

References