Use Cases for Oh My OpenCode
When and why to use the orchestration layer: monorepos, hybrid stacks, build pipelines, and team workflows
Oh My OpenCode is built for developers who need more than basic code completion—project-level AI workflows that understand your repo structure and build pipeline. Here are the use cases where it shines.
🏗️ Monorepos & Multi-Repo Setups
When you have multiple packages, apps, or services in one repo (or across repos), plain agents often get lost. Oh My OpenCode's agents and hooks understand multi-folder layouts and can plan across packages—touching Vite configs, shared libs, and app code in a single guided flow.
Orchestration →⚡ Hybrid Stacks (Hugo, React, Vite)
Hybrid static/SPA sites with custom build scripts are a common pain point. Oh My OpenCode has been used to build features in Hugo/React hybrids with custom build steps—navigating templates, React components, and build config in one session.
Real stories →🔄 Build Pipeline & CI Awareness
Need the agent to change not just source code but Vite configs, Hugo config, or CI scripts? The orchestration layer is build-pipeline aware so agents can safely touch configs and scripts that other tools avoid.
Configuration →👥 Team & Shared Configuration
Check oh-my-opencode.json into the repo so the whole team gets the same agents, hooks, and defaults. No more "works on my machine"—everyone gets consistent AI behavior and guardrails.
🤖 Limited Time to Babysit Agents
You want guard-railed workflows that recover from errors and enforce task completion. Hooks handle context window management, session recovery, and task continuation so you don't have to restart sessions manually.
Hooks →🔍 Exploring Large or Legacy Codebases
Agents, MCPs (e.g. grep.app, Context7), and LSP support help you safely explore unfamiliar or legacy projects. Get docs, search code, and refactor with type-aware tooling.
Agents → · MCPs →🌐 Multi-Model Setups (Claude, GPT, Gemini)
You already use multiple models through OpenCode. Oh My OpenCode adds sane orchestration on top—same CLI, same models, but with curated defaults for agents, hooks, and MCPs so switching models doesn't mean redoing config.
Features →📚 Documentation & Cross-File Refactors
Updating docs across many files or doing multi-file refactors is where project-level workflows beat inline completion. Specialized agents and hooks keep context and task scope under control.
Documentation →Who It's Not For
Oh My OpenCode is aimed at project-level and pipeline-aware work. If you only need single-file completions or a simple chat with the model, plain OpenCode (or an IDE plugin) may be enough. If you're managing complex repos, build pipelines, or team configs, the orchestration layer pays off.
See Oh My OpenCode vs plain OpenCode and the homepage for a quick comparison.
Next Steps & Related Pages
These pages help you get more traffic and context:
- Install Oh My OpenCode and try it in your repo
- OpenCode Tutorial — Step-by-step from zero to first session
- Configure agents and hooks for your workflow
- Oh My OpenCode vs OpenCode — What the plugin adds
- FAQ for common questions
- Features — Full feature overview