Kit Langton
f59996362e
Closes audit gap #3. The bridge now extracts the encrypted reasoning blob from `MessageV2.ReasoningPart.metadata` and surfaces it on `LLM.ReasoningPart.encrypted`, where the Anthropic and Bedrock adapters lower it to the wire — Anthropic emits `thinking.signature`, Bedrock emits `reasoningContent.reasoningText.signature`. Without this, multi-turn sessions with reasoning models would lose the encrypted state on every step and break the chain. The encrypted blob originates in three different places depending on how the session was started: 1. AI-SDK Anthropic sessions store it as `metadata.anthropic.signature` (per AI SDK provider-keyed convention). 2. AI-SDK OpenAI sessions store it as `metadata.openai.reasoningEncryptedContent`. 3. Future LLM-native sessions will store it as a top-level `metadata.encrypted` string (cleanest shape — provider-agnostic, matches the LLM IR field name). The new `encryptedReasoning` helper probes all three locations in order, so existing OpenCode sessions can be served by the LLM-native path without re-recording reasoning content. The full `metadata` record continues to flow through to `LLM.ReasoningPart.metadata` unchanged, preserving any provider-specific fields adapters might read in the future. OpenAI Responses encrypted reasoning round-trip is intentionally out of scope: the LLM-package adapter doesn't yet model reasoning items in the request body. That's a separate adapter feature requiring new input-item schema variants and is deferred until needed. Tests (5 new in llm-native.test.ts): - AI-SDK Anthropic signature extracted into LLM.ReasoningPart.encrypted. - End-to-end Anthropic lowering: bridge \u2192 client.prepare \u2192 target with `thinking.signature` populated correctly. - AI-SDK OpenAI reasoningEncryptedContent extracted (forward compatibility — useful when the OpenAI Responses adapter gains reasoning-item lowering). - Top-level metadata.encrypted extracted (LLM-native session shape). - No known key in metadata leaves `encrypted` undefined. Verified: 33/0/0 across native + bridge tests (was 28; +5 from the new reasoning extraction tests).
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.