Installation

Desktop app (recommended)

Download the installer for your platform from the latest release — always built from the prod branch.

Platform	File	Notes
Windows	opencode-desktop-win-x64.exe	NSIS installer — download and run, no script needed
macOS (Apple Silicon)	opencode-desktop-mac-arm64.dmg	Unsigned build — see note below
macOS (Intel)	opencode-desktop-mac-x64.dmg	Unsigned build — see note below
Linux (Debian/Ubuntu)	opencode-desktop-linux-x64.deb	sudo dpkg -i opencode-desktop-linux-x64.deb
Linux (Fedora/RHEL)	opencode-desktop-linux-x64.rpm	sudo rpm -i opencode-desktop-linux-x64.rpm
Linux (universal)	opencode-desktop-linux-x64.AppImage	chmod +x and run

macOS Gatekeeper

macOS builds are not signed or notarized by this fork (no Apple Developer account). On first launch Gatekeeper will warn that the app “cannot be verified” — right-click the app and choose Open to allow it manually.

The app updates itself automatically, checking for new releases against the fork’s repository (alltomatos/opencode) — not the original project.

CLI via npm

The fork’s CLI is published on npm under the @alltomatos scope, separate from the original project’s packages. Pick a channel with npm’s @tag syntax:

npm install -g @alltomatos/opencode@latest   # stable, published from prod
npm install -g @alltomatos/opencode@dev      # bleeding edge, published from dev

Publication is automatic on every push to the respective branch. Useful for testing dev changes via CLI/server without installing the desktop app.

From source (development)

To validate changes before they are promoted from dev to prod:

git clone https://github.com/alltomatos/opencode.git
cd opencode
git checkout dev
bun install
cd packages/desktop
bun run dev

This opens the Electron app in development mode (dev channel, auto-update disabled, dev icon).

Next steps

• Desktop App — tour of the interface
• Routines — put your first routine to work
• Remote Servers — run OpenCode on a VPS