A fork of sst/opencode - The AI coding agent built for the terminal.
This fork serves as an integration testing ground for upstream PRs before they are merged into the main opencode repository. We merge, test, and validate promising features and fixes to help ensure quality contributions to the upstream project.
The following PRs have been merged into this fork and are awaiting merge into upstream:
| PR | Title | Author | Status | Description |
|---|---|---|---|---|
| #4898 | Search in messages | @OpeOginni | Open | Ctrl+F to search through session messages with highlighting |
| #4791 | Bash output with ANSI | @remorses | Open | Full terminal emulation for bash output with color support |
| #4900 | Double Ctrl+C to exit | @AmineGuitouni | Open | Require double Ctrl+C within 2 seconds to prevent accidental exits |
| #4709 | Live token usage during streaming | @arsham | Open | Real-time token tracking and display during model responses |
| #4773 | Configurable subagent visibility | @Sewer56 | Open | Allow agents to restrict which subagents they can invoke |
| #4865 | Subagents sidebar with clickable navigation | @franlol | Open | Show subagents in sidebar with click-to-navigate and parent keybind |
| #4515 | Show plugins in /status | @spoons-and-mirrors | Open | Display configured plugins in /status dialog alongside MCP/LSP servers |
Last updated: 2025-12-07
The AI coding agent built for the terminal.
# YOLO
curl -fsSL https://opencode.ai/install | bash
# Package managers
npm i -g opencode-ai@latest # or bun/pnpm/yarn
scoop bucket add extras; scoop install extras/opencode # Windows
choco install opencode # Windows
brew install opencode # macOS and Linux
paru -S opencode-bin # Arch Linux
mise use --pin -g ubi:sst/opencode # Any OS
nix run nixpkgs#opencode # or github:sst/opencode for latest dev branchTip
Remove versions older than 0.1.x before installing.
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 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,
you can switch between these using 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 multi-step tasks.
This is used internally and can be invoked using @general in messages.
Learn more about agents.
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.
If you are working on a project that's related to OpenCode and is using "opencode" as a 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 anyway.
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 can drive it remotely from a mobile app. Meaning that the TUI frontend is just one of the possible clients.
The other confusingly named repo has no relation to this one. You can read the story behind it here.