Release Channels

The fork ships through two channels, mapped directly to its branches. Understanding the mapping helps you decide what to install and when to promote changes.

Branch → channel mapping

Branch	Desktop releases	npm tag	Auto-updater
prod	Yes — every push builds Windows, macOS and Linux installers	@alltomatos/opencode@latest	Stable installs update from here
dev	No published installers (dev builds run locally)	@alltomatos/opencode@dev	Disabled in dev mode

Desktop releases

When dev is promoted to prod, the release-desktop.yml workflow fires automatically:

1. Builds Windows (windows-latest), macOS (macos-latest) and Linux (ubuntu-latest) in parallel.
2. Publishes all three installers in a single GitHub release.
3. Versions follow packages/desktop/package.json at the moment of the push.

No manual builds are needed — bump the version, commit, and promote. To re-run a platform manually (e.g. retry a failure), use gh workflow run release-desktop.yml.

npm publication

The release-npm-fork.yml workflow cross-compiles the CLI binaries on a single runner and publishes them with the tag matching the branch:

npm install -g @alltomatos/opencode@latest   # from prod
npm install -g @alltomatos/opencode@dev      # from dev

Isolation between channels

Each channel keeps its own local project database — projects opened in a dev build never appear in the production install, and vice-versa. Providers, global config and cache remain shared across channels.

Choosing a channel

• Daily corporate use — install the desktop app from the latest release. It updates itself from prod.
• Testing new features — npm install -g @alltomatos/opencode@dev or run the desktop app from source on the dev branch.