/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

anomalyco/opencode

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-29T21:32:25.078Z

3mo ago

anomalyco/opencode

anomalyco/opencode is an actively maintained, MIT-licensed open source coding agent with very high adoption: 132,333 stars, 14,176 forks, and a recent push on 2026-03-29. It is built as a multi-package Bun/TypeScript monorepo with CLI, web, desktop, console, storybook, SDK, plugin, and Slack-related packages, plus docs and install tooling. Forks are most interesting if you want a fast-moving AI coding-agent codebase with a broad surface area for product, integrations, and UI work.

Loading tags...

Stars132,333

Forks14,176

Default branchdev

Last pushed2026-03-29T20:26:21Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you want a more permissive agent and are prepared to own the divergence. If you value upstream safety, stability, and fast parity with mainline, the upstream project is the safer choice.

Choose this fork if you want a more opinionated, product-oriented OpenCode derivative with mobile/push/integration work already underway. Choose upstream instead if you want the fastest path to current fixes, the lowest merge burden, and maximum compatibility.

Prefer this fork if you want a customized opencode base with extra workflow automation and are willing to own merge debt. Prefer upstream if you want the newest mainline fixes, broader platform coverage, and less maintenance risk.

Choose this fork if you want a more customized OpenCode with workflow automation, desktop refinements, and deeper integration work. Choose upstream if you want the latest broadly tested fixes and a smaller maintenance burden.

Choose this fork if you want a more customized OpenCode base and are willing to maintain divergence. Choose upstream if you want faster updates, broader documentation/localization coverage, and lower maintenance burden.

Prefer this fork if you need the specific plugin/session/desktop changes and are prepared to maintain a long-lived divergence. Prefer upstream if you want the latest fixes, broader compatibility, and lower merge cost.

Fork comparison

winmin/evil-opencode

70/100

active

significant_divergence

Prefer this fork only if you want a more permissive agent and are prepared to own the divergence. If you value upstream safety, stability, and fast parity with mainline, the upstream project is the safer choice.

Likely purpose

Unleash the upstream coding agent by stripping or relaxing safety behavior, while keeping the project buildable across more release targets and CI setups.

Best for

Developers who explicitly want a stripped-down or less-restricted coding agent.; Teams that are comfortable maintaining a large fork of a fast-moving monorepo.; Experimenters comparing alternative agent behavior or prompting policies.; Operators who need custom build/release handling and can absorb divergence risk.

Additional features

Less-restricted agent behavior intended for users who want the model to operate with fewer safety guardrails.
CI and release workflow updates, including separate macOS Intel/x64 build handling.
Startup/runtime robustness fixes such as cache-directory handling.
Compatibility maintenance for newer Bun versions and related build tooling.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

Large upstream drift: the fork is 200 commits ahead and 200 behind, so adopters should expect missing recent upstream fixes and features until they are merged.
Upstream safety guardrails and policy constraints appear to be removed or weakened, which is a loss for users who want the original safety model.
Some upstream parity is likely harder to rely on because the fork has a very different branch history and default branch naming.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Good fit for experimentation with a more permissive agent.
Shows active maintenance and recent pushes.
Invests in release/build portability across platforms.
May be useful for teams that need to own their own forked behavior end to end.

Risks

Weaker safety posture can increase misuse risk or produce outputs that upstream would have blocked.
Heavy divergence raises merge and maintenance cost.
Upstream regressions or security fixes may lag behind.
Behavioral compatibility with upstream docs, prompts, or plugins may not hold.