OpenCode

Plan

1. SupportsWork planning: Supports

   Work planning, supports. The built-in plan agent reads the codebase and drafts an approach, and in OpenCode 2 it may write only under ~/.opencode/plan; planning stays in the team's tracker.

Build

1. Codebase context: Supports

   Codebase context, supports. OpenCode reads and searches files, loads AGENTS.md rules, and feeds diagnostics from built-in LSP servers back to the model; it keeps no hosted index of the repository.

2. OpenCodeCoreCoding: Core

   Coding, core. This is OpenCode's primary role: editing code across a repository from the terminal UI, desktop app, web client, an IDE extension, or opencode run in a script.

3. Agent runtime: Core

   Agent runtime, core. In OpenCode 2 one background server holds every session. The terminal UI, desktop app, web client, and VS Code, Cursor, Zed, and Windsurf extensions attach to it, and ACP brings it into other editors.

4. Tool execution: Core

   Tool execution, core. OpenCode runs shell commands, MCP servers, custom tools, and plugins under allow, ask, or deny rules, and its default policy allows every action except .env reads.

Validate

1. Debugging: Supports

   Debugging, supports. OpenCode investigates failures by reading code, running commands, and reading LSP diagnostics; debuggers and tracing stay with dedicated tools.

2. Testing: Supports

   Testing, supports. OpenCode runs test suites from the shell and fixes failures it finds, while test infrastructure and coverage stay with the team's tooling.

3. TouchesCode review: Touches

   Code review, touches. A /opencode comment on a pull request runs OpenCode in GitHub Actions against that change, but OpenCode is not a dedicated review product.

4. Application security: Touches

   Application security, touches. Permission rules limit which tools and paths the agent may use, but OpenCode ships no sandbox and does no application security scanning.

Ship

1. Source control: Touches

   Source control, touches. The GitHub integration works on a new branch and opens a pull request, and OpenCode 2 can move a session into a git worktree; Git stays the system of record.

2. CI/CD: Touches

   CI/CD, touches. opencode run and the server's OpenAPI endpoint run the agent headless in scripts and GitHub Actions; build and delivery stay in the team's CI/CD.

Operate

1. Observability: Touches

   Observability, touches. OpenCode can read logs and run diagnostic commands it is given access to, but it provides no monitoring or alerting for your systems.