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
# 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 branchTip
Remove versions older than 0.1.x before installing.
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-desktopThe 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 | bashOpenCode 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.
Subagents are specialized agent types that a primary agent can invoke for a task. Teammates are different: they are background child sessions in an agent team, each with its own name, agent type, role prompt, dependencies, mailbox messages, and optional plan approval. A teammate can run a subagent type, but "teammate" is the team coordination role, not an agent mode.
Learn more about agents.
Agent teams let one lead session coordinate multiple background teammate sessions for work that can be split across specialists.
- Enable with
"experimental": { "agent_teams": true }inopencode.json - Spawn teammates with their own agent type, model, role prompt, dependencies, and optional plan approval
- Coordinate through mailbox messages, broadcasts, shared task lists, and automatic dependency unblocking
- Use the TUI team panel to inspect teammate status, pending questions, shared tasks, messages, and shutdown controls
- Generate post-run effectiveness reports with
team_reportor/team-report, including throughput, lifecycle, dependency, messaging, cost, token, and evaluation summaries - Inspect teams through the HTTP API and generated JavaScript SDK, including
/team/{teamID}/evalfor deterministic DAG-based evaluation findings
Subagents cannot create nested agent teams, and team tools stay scoped to lead and teammate sessions.
Learn more in the agent teams docs.
opencode export now includes child sessions recursively, so exported JSON captures subagent and teammate work along with the lead session.
Repository memory indexes local git history and high-activity file summaries so agents can use historical localization hints before reading source. It is enabled by default, but tools require an index from opencode memory index. Disable it with "memory": { "enabled": false }. Memory is historical, so agents must verify every hint against current source before editing.
Learn more in the memory docs.
For more info on how to configure OpenCode, head over to our docs.
If you're interested in contributing to OpenCode, please read our contributing docs before submitting a pull request.
Useful contributor helpers:
bun run dev:buildbuilds the OpenCode package with the single-binary build shortcut/clarifynarrows underspecified requests before planning or implementation/spec-plannerdrafts repo-style implementation specs with verification slices/initruns guidedAGENTS.mdsetup and adds the repo's required coding principles/team-reportruns the team report tool for the active or most recent team session
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.
