OpenCode

Open-source coding agent for terminal, desktop and IDE sessions, with configurable tool permissions.

No product visual on file

Choose it when

You want a session-led coding agent and are willing to match permission and plugin configuration to your chosen OpenCode generation.

Skip it when

You need a proven unattended service, or assume a local client means code never reaches a model provider or a sharing server.

01 / Classification

Autonomy evidence

This is our classification, not a vendor badge. The record says what the product normally does. The gaps stay visible.

How we classify it

Tool use + multi-step plans, still human-gated per session.

Runs unattended

No — the current record treats it as session-gated.

Trigger

A developer starts a terminal, desktop or IDE session. Subagents may be invoked within it; permissive tools or auto-approval don't alone establish a scheduler with a failure owner.

State

Conversation sessions and child sessions carry work context. V1 sharing can sync conversation history to servers; it is manual by default, not absent.

Tools

README describes Build as full-access and Plan as restricted; code edits, shell and MCP permissions need generation-specific review. Plan isn't a cross-generation no-write guarantee.

Human control

Switch agents and set allow/ask/deny rules. V2 uses ordered permissions with shell/subagent names and last-match precedence; saved approvals are durable project rules. Restrict authority and sharing explicitly.

02 / Operations

Control reality

Useful agents eventually touch something real. This is the operational picture we have, not a promise hidden in a sales page.

Where it runs

Local terminal/desktop client or IDE extension; V2 has separate server/client contracts. A local UI doesn't make every configured service local.

Data boundary

Selected remote providers receive context. Root sharing docs say shared history is synced to servers and publicly accessible by link; manual is the default, with disable/unshare controls. Those aren't a complete provider-retention policy.

Identity & permissions

This listing is anomalyco/opencode at opencode.ai. Model-account and tool authority depend on your chosen providers and configuration; no account compatibility was tested.

What it can write

project files · shell commands · configured MCP tools

Surfaces

Terminal · Desktop · IDE extension

Export / lock-in

Documented sharing creates a public conversation URL, not a verified full-state backup. Unshare removes public access per root docs; portable offline export and restore weren't established by this packet.

03 / Receipts

Evidence ledger

Here is what this brief is built on. “Documented” means we found a source. “Tested” means this desk actually ran it. Those are different things.

Evidence status

documented

Source set

11 primary sources

Evidence review

2026-10-13

Sources on file

Corrections

Not recorded yet. If we change a material claim, the correction belongs here.

04 / Change log

Related coverage

The brief tells you what the product is. Payloads track the changes that may alter the decision.

No linked change coverage on file yet.