Oh My OpenCode vs Plain OpenCode
What's the difference, and when should you use the Oh My OpenCode plugin?
OpenCode is the open source AI coding agent (60K+ stars, 650K+ monthly users). Oh My OpenCode is a plugin that runs on top of it—an orchestration layer with opinionated agents, hooks, MCPs, and configuration. Here's how they compare.
At a Glance
| Capability | Plain OpenCode | Oh My OpenCode (plugin) |
|---|---|---|
| Core AI agent | ✓ | ✓ (same) |
| 75+ model providers | ✓ | ✓ (same) |
| Planner / multi-agent orchestration | Manual or minimal | ✓ Sisyphus + specialized agents |
| Built-in hooks (context, recovery, etc.) | Limited | ✓ 20+ hooks |
| MCPs pre-wired (Context7, grep.app) | You configure | ✓ Sensible defaults |
| LSP defaults & priority | You configure | ✓ Preconfigured |
| Build-pipeline / multi-repo awareness | Generic | ✓ Designed for it |
| Team-shared config (repo-checked) | Possible | ✓ oh-my-opencode.json |
Plain OpenCode: What You Get
OpenCode gives you a powerful, model-agnostic coding agent. You get the same CLI, the same models (Claude, GPT, Gemini, etc.), and you can configure everything yourself. It's like "Debian/Arch"—flexible and minimal by default.
- Single, capable AI agent
- Full control over config and extensions
- No extra plugin layer—simpler stack
Oh My OpenCode: What You Add
Oh My OpenCode layers on opinionated defaults: which hooks to enable, how to configure LSP servers, how to wire MCPs, and how to structure agents for large codebases. Think "Ubuntu/Omarchy"—same core, preconfigured for serious day-to-day work.
- Planner-Sisyphus (and other agents) for task completion and planning
- 20+ hooks for context management, session recovery, task continuation
- MCPs like Context7 and grep.app wired in correctly from day one
- Build-pipeline awareness for monorepos and hybrid stacks
When to Use Plain OpenCode
Stick with plain OpenCode if you prefer minimal setup, want to hand-pick every extension, or only need single-file or simple multi-file edits without heavy orchestration.
When to Use Oh My OpenCode
Use the plugin when you:
- Work with complex repos or monorepos and want agents that understand structure
- Want guard-railed workflows that recover from errors and complete tasks
- Use multiple models and want consistent orchestration on top
- Want team-shared config (agents, hooks, MCPs) checked into the repo
- Need build-pipeline and multi-repo awareness (Vite, Hugo, custom scripts)
See use cases for more examples.
OpenCode vs Other Tools (Cursor, etc.)
OpenCode itself is open source and model-agnostic—you can use Claude, GPT, Gemini, or 75+ providers. Tools like Cursor are commercial IDEs with their own models and licensing. Oh My OpenCode doesn't replace Cursor or other IDEs; it enhances OpenCode for project-level workflows. If you already use OpenCode and want better orchestration, the plugin fits. If you're comparing "OpenCode vs Cursor," that's a separate choice (open vs closed, CLI vs IDE, etc.).
Related Pages
These pages help you get more traffic and context:
- Install Oh My OpenCode — Get the plugin in minutes
- OpenCode Tutorial — Step-by-step from zero to first session
- OpenCode vs Cursor — Compare with IDE tools
- Use Cases — When the plugin shines
- FAQ — Common questions
Try It
You can install Oh My OpenCode in minutes. It extends your existing OpenCode config—you can disable or remove the plugin anytime. For questions, see the FAQ.