OpenCode
Study OpenCode’s task modes, tool feedback, and review flow to improve repository investigation, implementation, and validation stages in your own development workflows.
- Coding
- Development Workflows
- Agent Workflows
- Code Review
- Debugging
Anomaly: OpenCode and Coding Tools
Explore Anomaly as the publisher of OpenCode. Learn the organization’s coding-agent project, its interactive workflow, and how official software, community integrations, and connected model services differ.
About Anomaly
Anomaly is the organization behind the official OpenCode repository. Its representative project is an open-source coding-agent application, built around the interaction between a developer, a workspace, and model-driven tools. That application layer is a distinct subject from the model provider.
OpenCode offers multiple ways to engage with coding tasks and documents different agent modes. When evaluating Anomaly’s work, focus on how the tool organizes tasks, feedback, and review, rather than reducing the project to a model name or a list of prompts.
The official application source uses MIT. Community integrations and services associated with an installation can have different maintainers or terms. Each integration has its own maintainer and support scope, even when it builds on OpenCode.
Anomaly Projects
OpenCode is a coding agent whose task modes and extension surfaces can inform repository workflows. Compare its model access, execution environment, and review feedback separately before borrowing an integration pattern or assuming that one layer provides the responsibilities of another.
Related Agent Publishers
Explore other teams developing agent runtimes, coding tools, and reusable working environments.
Anomaly FAQ
What is Anomaly’s verified project here?
OpenCode is published at anomalyco/opencode. Community integrations have their own maintainers and should be checked individually for ownership and support.
Is Anomaly the model behind every OpenCode session?
The application publisher and the model provider are different roles. Check the provider configured for the particular session instead of inferring model ownership from the tool’s branding.
How should community OpenCode tools be attributed?
Use their actual repository maintainers and document the relationship to OpenCode. An integration can build on a public interface without being officially maintained or endorsed by Anomaly.
What makes a coding agent different from a prompt library?
A coding agent supplies an application and execution workflow around model calls. Prompt instructions can guide that workflow, but do not by themselves supply the interface, state, and tool execution.
Does the organization’s project license include services?
The OpenCode source is MIT licensed. Accounts, hosted features, model usage, and third-party integrations must be evaluated under their own terms.
How should a team evaluate OpenCode?
Compare it against a specific repository task, the desired review process, provider access, and the integration requirements. A broad reputation is not a substitute for that workflow fit.
Define an OpenCode Investigation Handoff
Use the project guide to specify what investigation should return, which tools each stage may use, and what evidence a reviewer needs before accepting a change.