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. Historical V1 sharing documentation described manual-by-default history sync to servers. That is historical guidance, not verified current behavior: the sharing-doc URL returned 404 on October 17, 2026; current sharing behavior is unverified.

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 generation-specific allow/ask/deny rules. V2 uses ordered permissions with shell/subagent names and last-match precedence. Allow always saves durable project rules but never overrides a configured deny. Custom subagents use their own permissions, not a subset of the parent's: restrict each one 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. Historical V1 sharing docs described server sync and public-link history, manual sharing by default, and disable/unshare controls. The sharing-doc URL returned 404 on October 17, 2026; those controls and current sharing behavior are unverified. V2 permissions document local read/edit and host-user shell authority, not sharing guarantees or provider retention.

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

Historical V1 documentation described public-link sharing and unshare, not a verified full-state backup. The sharing-doc URL returned 404 on October 17, 2026. Current sharing/export, public-access removal, and portable offline export/restore remain unverified; the 404 doesn't establish that sharing was removed or how V2 behaves.

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-17

Sources on file

Corrections

2026-10-17 · Scoped release metadata to V1 v1.19.3, not a unified V1/V2 latest or an installed upgrade. Added V2's default outside-project access, custom-subagent permission boundary and missing LSP execution/diagnostics. Recast sharing claims as historical V1 documentation because the sharing-doc URL returned 404; current sharing/export remains unverified. Documented, not runtime-tested.

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.