Kit Langton
e1c6bf92fb
Add a `providerExecuted: boolean` flag to `tool-call` and `tool-result` events plus the persisted `ToolResultPart`. When set, the tool runtime skips client dispatch (the provider already executed the tool) and folds both events into the assistant message so the next round's history carries the call + result for context. Anthropic: decode `server_tool_use` blocks and the three server tool result block types (`web_search_tool_result`, `code_execution_tool_result`, `web_fetch_tool_result`) into `tool-call` / `tool-result` events with `providerExecuted: true`. Round-trip the same parts back into the provider when the assistant message is replayed in subsequent requests. Result block error payloads (`*_tool_result_error`) surface as `result.type === "error"`. OpenAI Responses: decode hosted tool items emitted via `response.output_item.done` (`web_search_call`, `file_search_call`, `code_interpreter_call`, `computer_use_call`, `image_generation_call`, `mcp_call`, `local_shell_call`) as `tool-call` + `tool-result` pairs with `providerExecuted: true`. Each tool's input fields are pulled out explicitly; the full item is passed through as the result payload so consumers can read outputs / sources / status without re-decoding. Tool runtime: extend the dispatch decision so provider-executed tool-calls bypass the handler lookup, and tool-result events with `providerExecuted: true` are appended to the assistant content for round-trip rather than being treated as a separate tool message. Tests: 7 new deterministic fixtures cover Anthropic decode (success + error result + round-trip + unknown server tool name), OpenAI Responses decode (web_search_call, code_interpreter_call), and tool-runtime skip-dispatch. AGENTS.md updates the runtime section to describe pass-through behavior and notes the transport-agnostic design that keeps a future WebSocket adapter (e.g. OpenAI Codex backend) as a sibling rather than a core rewrite.
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.