opencode-plugin-development

A v1 plugin is a function taking PluginInput (client, project, directory, serverUrl, shell) and returning a Hooks object with fields like tool, config, event, and chat.message. Local path plugins must export an id; npm plugins use the package name. Verify hook trigger call-sites in the opencode source at your target tag.

Use client.session.prompt from @opencode-ai/sdk with a parts-based body containing TextPartInput, FilePartInput, or AgentPartInput entries posted to the session message endpoint. Plugin-injected clients take precedence over TUI append methods for message injection.

V1 and v2 use separate permission stores, different event families, and different prompt body shapes; v2 prompt takes a prompt object while legacy takes parts. Several v2 routes are declared but stubbed with 503 errors, so verify each endpoint in openapi.json and handler code before adopting it.

The v2 /api/event stream throws a schema encode error and kills the connection when legacy events like session.status cross the shared bus. Also, Python http.client read(n) aggregates chunks and blocks on quiet streams; use read1() for per-chunk reads, and pass the directory as a query parameter rather than a header.

Grep for deleted method names, routes, event families, and output fields across all files including scripts, since unit tests miss e2e helpers. Classify each mention as executable code path, stale documentation, or allowed explanatory reference, then re-dispatch the audit until a round returns zero findings.

No. The session wait route is a declared but stubbed endpoint that always returns 503. Blocking handoffs must watch for session.status idle events on the legacy event stream or poll the session status map, where an absent entry means idle.