mirror of
https://github.com/anomalyco/opencode.git
synced 2026-05-13 15:44:56 +00:00
7006de8935
Cleanup pass after sub-agent review.
Correctness fixes:
- WebSocket error messages no longer leak unredacted client frames or
URLs into error output. websocket.ts passes `actual` through
`safeText` (drops content with secret-pattern matches; truncates
at 300 chars) and the "no recorded interaction" die message uses
`redactUrl(request.url)`.
- WebSocket replay sendText: compare-then-advance ordering. Previous
code advanced the cursor before the assertion, so a mid-stream
mismatch left the cursor pointing past the failing frame.
- WebSocket record mode now uses `Stream.tap` (pure side-effect)
instead of `Stream.map` for capturing server frames.
API tightening:
- `Cassette.Interface.append` returns `Effect<void, UnsafeCassetteError>`
directly. The `appendOrFail` helper and `AppendResult` type are
gone — the cassette adapter owns the safety contract. Both
`fileSystem` and `memory` adapters fail with `UnsafeCassetteError`
on findings.
- `UnsafeCassetteError` moved from recorder.ts to cassette.ts.
- `ResolvedMode` type alias dropped — inlined the union.
- Mid-file `import { Schema }` in redaction.ts moved to the top.
Tests added (5):
- passthrough mode bypasses recorder + writes nothing
- auto mode records to disk when cassette is missing
- UnsafeCassetteError blocks the request when recording would write
a known secret
- Cassette.list enumerates recorded cassette names
- WebSocket replay decodes binary frames recorded as base64
Docs:
- Audit example in README compiles (was using `entry.name` after
list() shape changed to plain strings).
- Layout table no longer references the deleted `storage.ts`.
- recorder.ts row reflects current contents (resolveAutoMode +
ReplayState; appendOrFail removed).
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-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-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.
- Built-in opt-in 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.