Kit Langton
fa8f7a1dca
Adds opt-in `nativeTools?: ReadonlyArray<Tool.Def>` to `LLM.StreamInput` so callers that route through the native path can attach typed opencode tool definitions alongside the AI SDK `tools` record. The gate in `runNative` widens accordingly: a session can use the native path when it has zero tools (existing behavior) OR when it explicitly provides `nativeTools` matching its AI SDK `tools` (new opt-in). When `nativeTools` reaches `LLMNative.request`, the existing `toolDefinition` converter folds each `Tool.Def` into the request's `tools` array and the LLM core lowers it onto the wire. This commit deliberately does NOT include the dispatch loop. A session that opts in by setting `nativeTools` and that triggers a `tool-call` from the model will see the call event but no `tool-result` because the native path has no execute handler yet. That's why no production caller populates `nativeTools`: phase 2 step 2b will land the dispatch loop and only then will real production sessions route through here. What this lays in place: - `StreamInput.nativeTools` typed against `Tool.Def[]` from `@/tool`. Aliased to `OpenCodeTool` at the import to dodge a clash with the AI SDK `Tool` type that the same file already imports. - The `runNative` gate flips from "no tools allowed" to "either no tools, or `nativeTools` is supplied". An AI SDK tool count > 0 with `nativeTools` undefined still falls through, so existing production sessions are unaffected. - `LLMNative.request` already accepted `tools: ReadonlyArray<Tool.Def>` and converts via `toolDefinition`. We just forward the input through; no LLM-bridge change. Smoke coverage: a new test in `llm-native-stream.test.ts` builds a typed `Tool.Def` (Effect Schema parameters), routes it through `LLMNative.request` + `LLMClient.prepare`, and asserts the prepared Anthropic target carries the tool as an `input_schema` block with the expected JSON Schema shape. This validates the conversion path that phase 2 step 2b will exercise from inside `runNative`. Verification: opencode typecheck clean; 35/0/0 across the three bridge-area tests (`llm-native.test.ts`, `llm-native-stream.test.ts`, `llm-bridge.test.ts`).
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.