Kit Langton
cb588ab4b9
`bus.subscribe(def)` and `bus.subscribeAll()` previously returned a `Stream` whose underlying `PubSub.subscribe` ran lazily on first pull (via `Stream.unwrap`). When a Stream was built in one place and consumed in another — e.g. the `/event` SSE handler, which returns the stream inside `HttpServerResponse.stream` for the body-pump fiber to consume later — any publish in the hand-off window was lost. The `/event` handler's `Stream.concat(server.connected, events)` shape made this concrete: the events stream's PubSub.subscribe was only run *after* `server.connected` was emitted and flushed to the socket, so publishes that landed between the client receiving `server.connected` and the body-pump fiber pulling from `events` were silently dropped. SDK consumers (`client.event.subscribe()`, the Slack bot, `opencode run --attach`) hit this routinely because they typically subscribe and then trigger something that publishes (e.g. `sdk.part.update`). Change the bus interface so subscribe / subscribeAll return `Effect<Stream, never, Scope>`. The subscription is now acquired eagerly when the caller yields the effect, lives in the caller's scope, and is released by the scope's finalizer. Any publish after `yield*` is buffered into the subscription queue regardless of when the consumer activates. Migrated callers: - /event handler (handlers/event.ts) - plugin/index.ts - project/project.ts - project/vcs.ts - share/share-next.ts Regression tests added: - test/bus/bus-effect.test.ts — 3 unit tests for eager subscribe, including the /event-shape Stream.concat pattern. - test/server/httpapi-event-diagnostics.test.ts — 7 diagnostic tests (D1-D7) isolating each variable in the publisher chain. D7 (no-op AppRuntime warmup) is the smallest regression trigger. - test/server/httpapi-sdk.test.ts — end-to-end SDK subscription through /event during a sync.run-driven publish.
The open source AI coding agent.
English | 简体中文 | 繁體中文 | 한국어 | Deutsch | Español | Français | Italiano | Dansk | 日本語 | Polski | Русский | Bosanski | العربية | Norsk | Português (Brasil) | ไทย | Türkçe | Українська | বাংলা | Ελληνικά | Tiếng Việt
Installation
# YOLO
curl -fsSL https://opencode.ai/install | bash
# Package managers
npm i -g opencode-ai@latest # or bun/pnpm/yarn
scoop install opencode # Windows
choco install opencode # Windows
brew install anomalyco/tap/opencode # macOS and Linux (recommended, always up to date)
brew install opencode # macOS and Linux (official brew formula, updated less)
sudo pacman -S opencode # Arch Linux (Stable)
paru -S opencode-bin # Arch Linux (Latest from AUR)
mise use -g opencode # Any OS
nix run nixpkgs#opencode # or github:anomalyco/opencode for latest dev branch
Tip
Remove versions older than 0.1.x before installing.
Desktop App (BETA)
OpenCode is also available as a desktop application. Download directly from the releases page or opencode.ai/download.
| Platform | Download |
|---|---|
| macOS (Apple Silicon) | opencode-desktop-mac-arm64.dmg |
| macOS (Intel) | opencode-desktop-mac-x64.dmg |
| Windows | opencode-desktop-windows-x64.exe |
| Linux | .deb, .rpm, or .AppImage |
# macOS (Homebrew)
brew install --cask opencode-desktop
# Windows (Scoop)
scoop bucket add extras; scoop install extras/opencode-desktop
Installation Directory
The install script respects the following priority order for the installation path:
$OPENCODE_INSTALL_DIR- Custom installation directory$XDG_BIN_DIR- XDG Base Directory Specification compliant path$HOME/bin- Standard user binary directory (if it exists or can be created)$HOME/.opencode/bin- Default fallback
# Examples
OPENCODE_INSTALL_DIR=/usr/local/bin curl -fsSL https://opencode.ai/install | bash
XDG_BIN_DIR=$HOME/.local/bin curl -fsSL https://opencode.ai/install | bash
Agents
OpenCode includes two built-in agents you can switch between with the Tab key.
- build - Default, full-access agent for development work
- plan - Read-only agent for analysis and code exploration
- Denies file edits by default
- Asks permission before running bash commands
- Ideal for exploring unfamiliar codebases or planning changes
Also included is a general subagent for complex searches and multistep tasks.
This is used internally and can be invoked using @general in messages.
Learn more about agents.
Documentation
For more info on how to configure OpenCode, head over to our docs.
Contributing
If you're interested in contributing to OpenCode, please read our contributing docs before submitting a pull request.
Building on OpenCode
If you are working on a project that's related to OpenCode and is using "opencode" as part of its name, for example "opencode-dashboard" or "opencode-mobile", please add a note to your README to clarify that it is not built by the OpenCode team and is not affiliated with us in any way.
FAQ
How is this different from Claude Code?
It's very similar to Claude Code in terms of capability. Here are the key differences:
- 100% open source
- Not coupled to any provider. Although we recommend the models we provide through OpenCode Zen, OpenCode can be used with Claude, OpenAI, Google, or even local models. As models evolve, the gaps between them will close and pricing will drop, so being provider-agnostic is important.
- Built-in opt-in LSP support
- A focus on TUI. OpenCode is built by neovim users and the creators of terminal.shop; we are going to push the limits of what's possible in the terminal.
- A client/server architecture. This, for example, can allow OpenCode to run on your computer while you drive it remotely from a mobile app, meaning that the TUI frontend is just one of the possible clients.