Oh My OpenCode Slim
An OpenCode plugin that routes development work across specialized, configurable multi-model agents.
Per-dimension scores and reasoning
Evidence: The plugin installer modifies global config files (~/.config/opencode/opencode.json) and generates preset configs with model and MCP permissions. Skill assignment is permission-based, with default skills assigned. Installer asks about enabling Companion, default no. Data flow: docs describe Orchestrator dispatching background agents, but no explicit data flow or sensitive data handling. Dependencies include third-party packages, but no security audit evidence. External effects: modifies config, launches background processes (Companion), clones dependencies, but no explicit user confirmation. Rollback: docs mention config reset, but no automatic rollback. Source attribution: code and docs clearly attribute to author and repo, but publisher unverified. Deductions: lack of explicit least-privilege principle, user confirmation, data flow transparency, sensitive data handling; dependency security unverified; external effects not fully documented; rollback incomplete.
Evidence: README and docs are consistent, multiple docs cross-reference, good self-consistency. Dependencies listed in package.json, but no lockfile or version pinning evidence. Failure messages: docs mention troubleshooting, but no specific error handling. Deductions: dependency availability unverified, failure message handling insufficient.
Evidence: README targets developers, provides multiple use cases (codebase investigation, doc reference, architecture review, UI work, implementation tasks). Capability boundaries defined via skills and MCP permissions. Trigger precision via @agentName and skill invocation. Environment fit: supports multiple model providers and presets, but no explicit OS/version requirements. Deductions: environment fit info incomplete.
Evidence: Clear information architecture with README, docs directory, config reference. Install notes detailed, including manual and automatic. Naming stable, version numbers clear. Examples and FAQ: README includes user testimonials and quick start, but no FAQ. Known limitations: docs mention Council cost, but no systematic list. License: MIT license clear. Versioning: package.json has version, but no CHANGELOG. Maintenance responsibility: SECURITY.md and contributor guide, but no explicit maintainer. Deductions: missing FAQ, CHANGELOG, and explicit maintainer.
Evidence: Output usability: generated configs and skills directly usable. Marginal value: multi-agent orchestration provides advantage over single model. Cost-benefit: docs mention $30 preset, but no detailed cost analysis. Deductions: cost-benefit analysis insufficient.
Evidence: README claims (features, performance) lack test or benchmark data. Cross-source corroboration: user testimonials from community, but no verifiable links. Fact-inference separation: mythological descriptions mixed with functional descriptions, but not clearly separated. Deductions: lack of verifiable evidence and fact/inference separation.
- The plugin modifies global config files and may launch background processes; back up config before installation.
- Dependencies lack security audit evidence; assess supply chain risks yourself.
- Publisher identity is unverified; use with caution.
What does this agent do, and when should you use it?
Oh My OpenCode Slim is an agent-orchestration plugin for OpenCode, not a standalone application or general-purpose API service. Its Orchestrator plans work, dispatches specialist tasks in the background, and reconciles their results before proceeding. The built-in team consists of Orchestrator, Explorer, Oracle, Council, Librarian, Designer, and Fixer, with an optional Observer for visual files. Local OpenCode configuration assigns models, skills, and MCP permissions to individual roles, including supplied OpenAI and OpenCode Go presets. It fits developers who want a configurable, observable parallel-agent workflow inside OpenCode and are prepared to manage OpenCode setup and provider authentication.
The installer adds the plugin to the plugin array in ~/.config/opencode/opencode.json and generates ~/.config/opencode/oh-my-opencode-slim.json. Orchestrator creates a work graph and schedules background specialists; Explorer scouts a codebase, Librarian retrieves external information through websearch, context7, and gh_grep, Oracle handles architecture, difficult debugging, and review, and Designer and Fixer perform UI and bounded implementation work. Users can delegate explicitly with @agentName <task>, run @council to send one question to multiple models in parallel and synthesize an answer, and switch full model setups with /preset. The plugin also exposes LSP tools, AST-aware search across 25 languages, and prompt-based skills including codemap, deepwork, and verification-planning. When enabled, Observer uses the read tool to return structured observations from images, screenshots, PDFs, and other visual files.
- An engineer joining a large OpenCode project who wants Explorer to map the codebase before implementation begins.
- A staff engineer comparing two architecture options who wants
@councilto gather parallel model perspectives and synthesize them. - A developer investigating an unfamiliar dependency or current documentation who assigns Librarian to use its permitted research MCPs.
- A developer with several bounded code changes who wants Fixers to work in the background while the Orchestrator remains available in the session.
- A team whose main Orchestrator is not multimodal but needs to analyze screenshots or PDFs through an enabled Observer.
What are this agent's strengths and limitations?
- It separates orchestration, codebase reconnaissance, research, architectural judgment, UI work, and implementation into named specialist roles instead of presenting one undifferentiated assistant.
- Background specialist dispatch is the default orchestration model, allowing parallel work while the Orchestrator continues the session.
- Model, skill, and MCP access are configurable per agent, with supplied OpenAI and OpenCode Go presets plus runtime
/presetswitching. - Council provides a distinct multi-model parallel-and-synthesis path for decisions that benefit from competing perspectives.
- Concrete developer tooling includes LSP tools, AST-aware search across 25 languages, and the
websearch,context7, andgh_grepMCPs.
- Its core delivery boundary is OpenCode; the supplied evidence does not establish standalone-library, standalone-web-service, or native operation in other chat products.
- Adoption requires provider setup and
opencode auth login; available models and usage costs depend on the chosen providers and preset. - Council runs several models concurrently and is described as usually the system's highest-cost path, so automatic use is intentionally restricted.
- Observer is disabled by default; visual analysis requires enabling it and configuring a vision-capable model.
- Only part of the documentation is supplied, so the complete behavior of customization options, ACP configuration, and troubleshooting cannot be verified here.
How do you install or deploy this agent?
Prerequisites: OpenCode and authentication for the model providers you plan to use. Install with Bun: bunx oh-my-opencode-slim@latest install. If Bun is unavailable, use: npx oh-my-opencode-slim@latest install. Then run opencode auth login and opencode models --refresh. Installation generates the OpenAI and OpenCode Go presets and activates OpenAI by default; to activate OpenCode Go at install time, run bunx oh-my-opencode-slim@latest install --preset=opencode-go.
How do you use this agent?
Start opencode, then run ping all agents to verify that configured roles respond. Edit ~/.config/opencode/oh-my-opencode-slim.json and set each role's available model, optional variant, skills, and mcps under presets. Delegate manually with @agentName <task>, invoke multi-model synthesis with @council <question>, and use /preset to change presets at runtime. For a floating activity display, install with --companion=yes; the repository also documents multiplexer viewing through Tmux, Zellij, Herdr, cmux, or kitty panes.
How does this agent compare with similar options?
The repository supplies OpenAI and OpenCode Go presets. The OpenAI preset assigns Terra, Sol, and Luna to different roles; the OpenCode Go preset uses OpenCode Go models and enables Observer because its Orchestrator is not multimodal. These are configuration choices within the same OpenCode plugin, not separate competing products.
FAQ
Is it limited to one model provider?
How are networked MCP permissions controlled?
mcps setting. The supplied example gives Librarian websearch, context7, and gh_grep, while other agents may have none.What should I do if an agent does not respond?
ping all agents in OpenCode. The README directs users to check provider authentication and the configuration file when a configured agent fails to respond.