OpenCode moved past the stage of “interesting alternative” a long time ago. With over 170,000 stars on GitHub, it became one of the most important open source projects in the development agent ecosystem.
But there’s a detail many users still haven’t discovered.
Installing OpenCode is just the beginning.
Around the project, a complete ecosystem is emerging with:
-
plugins
-
agents
-
workflows
-
themes
-
integration tools
-
shared configurations
And just like what happened with VS Code, the difference between a basic installation and a truly productive one will probably come down to the extensions you add on top.
First: install OpenCode
If you don’t have it installed yet:
npm install -g opencode-ai
or via Homebrew:
brew install opencode-ai/tap/opencode
Then start a session:
opencode
And you already have access to Claude, OpenAI, Gemini, OpenRouter and other compatible providers.
Where to find plugins and agents?
The best reference today is the Awesome OpenCode repository, a community-maintained collection that groups:
-
plugins
-
agents
-
themes
-
MCP servers
-
workflows
-
compatible tools
It’s basically the unofficial directory of the OpenCode ecosystem.
And it’s already starting to look a lot like the early years of the VS Code marketplace.
1. Architecture Reviewer
One of the most useful agents for medium and large projects.
Before modifying code:
-
analyzes existing architecture,
-
identifies dependencies,
-
reviews patterns used,
-
detects potential impacts.
Ideal for onboarding or for repositories you’re not familiar with.
When to use it
-
refactors
-
audits
-
onboarding new developers
2. Security Auditor
Probably one of the agents that delivers the most value.
Scans for:
-
insecure configurations
-
exposed secrets
-
vulnerable patterns
-
excessive permissions
It doesn’t replace dedicated tools, but it serves as a first line of review.
When to use it
Before opening a Pull Request or making important deployments.
3. Documentation Writer
We all know the story.
Code changes.
Documentation doesn’t.
This agent goes through:
-
functions
-
classes
-
endpoints
-
project structures
and generates documentation automatically.
When to use it
After large features or extensive refactors.
4. Test Generator
One of the classics.
Analyzes existing code and proposes:
-
unit tests
-
integration tests
-
edge cases
-
negative scenarios
It can save hours when you inherit projects without adequate coverage.
5. PR Review Agent
Functions as an automatic second opinion.
Reviews:
-
code quality
-
consistency
-
complexity
-
potential regressions
It doesn’t replace human code review, but it helps catch issues before opening the PR.
6. MCP Explorer
One of the most interesting plugins.
Allows you to inspect connected MCP servers and understand:
-
available tools
-
parameters
-
capabilities
-
exposed resources
Particularly useful when you start accumulating MCPs and forget what each one does.
7. Repository Memory Plugins
Persistent memory remains one of the most important topics in the ecosystem.
These plugins allow OpenCode to retain information about:
-
architecture
-
technical decisions
-
conventions
-
recurring patterns
between sessions.
The result is less repetition and fewer explanatory prompts.
8. GitHub Workflow Agent
Automates tasks related to:
-
Issues
-
Pull Requests
-
Releases
-
Changelogs
Very useful for open source projects or small teams.
9. Refactoring Assistant
Specialized in code modernization.
Can help with:
-
framework migrations
-
API updates
-
technical debt removal
-
legacy code simplification
It’s especially effective when combined with reasoning models.
10. Theme Packs and UI Customizations
They don’t directly increase productivity.
But if you spend eight hours a day in OpenCode, a pleasant interface matters.
The community already maintains:
-
dark themes
-
themes inspired by VS Code
-
Catppuccin variants
-
minimalist styles
Small change. Big impact on daily use.
A recommended configuration to get started
If you just installed OpenCode, my recommendation would be to start with:
Productivity
-
Documentation Writer
-
Test Generator
-
PR Review Agent
Quality
-
Architecture Reviewer
-
Security Auditor
Infrastructure
-
MCP Explorer
-
Repository Memory
With just those seven components, you already get a significantly more powerful experience than the base installation.
The interesting part isn’t OpenCode
The interesting part is what’s happening around OpenCode.
For years we evaluated development tools by their internal features.
Today we’re starting to evaluate them by the quality of their ecosystem.
VS Code won because it had extensions.
Terraform won because it had modules.
GitHub won because it had integrations.
And agents seem to be following exactly the same path.
OpenCode is already a powerful tool on its own.
But the real story might be that it’s starting to become a platform.