Kit Langton
0ba8ca63b6
Five review findings; all small, all independent. H2: Bedrock used raw `JSON.parse` and `JSON.stringify` despite the package rule against ad-hoc JSON encoders. The in-loop parse on each event-stream frame goes through `ProviderShared.parseJson` (yielded inside `Effect.gen`); the `decodeChunk` error fallback uses `ProviderShared.encodeJson` instead of `JSON.stringify` for the raw field on `ProviderChunkError`. No behavior change — just channels JSON through the shared Schema-driven codec. H3: `BedrockConverse.toHttp` built a `baseHeaders` record with `content-type: application/json` and passed it through both auth paths. The bearer path called `jsonPost` with the raw model headers (no manual content-type), the SigV4 path used `baseHeaders` plus the signed result. Two paths produced subtly different header sets and both relied on `jsonPost` overwriting/adding the same content-type key. Simplify: drop the unused bearer-side construction; rename the SigV4 input to `headersForSigning` and document why content-type must be present at signing time (signature covers it). M4: Lift `isRecord` from `gemini.ts` into `ProviderShared.isRecord` so adapters share one definition. The duplicates in `llm.ts` (LLM IR layer) and `llm-native.ts` (OpenCode bridge) stay where they are — those are at different layers and importing from `provider/` would invert the dependency direction. Net effect: the provider layer goes from 2 copies to 1. L8: `TransportError` lost everything but the message string. Surface the originating reason tag (`Timeout` / `TransportError` / `ResponseError` / `RequestError`) and the request URL when available, both as optional Schema fields. Consumers that don't care keep getting the same `message` rendering; consumers that do can finally render "timed out connecting to https://..." instead of "HTTP transport failed". M9 + L3: Two dead branches. Anthropic's `processChunk` had `?? ""` fallbacks for `partial_json` after an early-return guard already proved it non-empty. OpenAI Chat's `mapFinishReason` had `if (reason === undefined || reason === null) return "unknown"` followed by `return "unknown"` — both branches went to the same place. Drop the unreachable code. 120 LLM-package tests + 33 OpenCode bridge tests still green.
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-darwin-aarch64.dmg |
| macOS (Intel) | opencode-desktop-darwin-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.
- Out-of-the-box 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.