Answer: A published plugin is an npm package with the package.json described, and you publish it with npm publish. Build the GUI bundle before publishing and include it through files, and test the installed package rather than only a workspace-linked copy. Status: Confirmed Entry: tool/opencode/integrations/publish-plugin Revision: 2 Digest: sha256:1e00566f6dd340f0 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:55:40Z Last changed: 2026-11-19T13:34:39Z (update instruction: — → Publish a compatible plugin update when you adopt a newer API contract.) Last verified: 2026-11-20T13:44:27Z Next check: 2026-11-21T13:44:27Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of publish command | npm publish | [1] | 2026-11-20 package type | npm package | [1] | 2026-11-20 GUI bundle instruction | Build the GUI bundle before you publish, and include it through files | [1] | 2026-11-20 testing instruction | test the installed package, not only a workspace-linked copy | [1] | 2026-11-20 update instruction | Publish a compatible plugin update when you adopt a newer API contract. | [1] | 2026-11-20 Sources: [1] opencode. "Building plugins | OpenCode". https://opencode.ai/docs/build/plugins/ Role: primary. Accessed: 2026-11-20T13:44:27Z Quote: "Terminal Copy Copied Failed npm publish" (Supports: publish command) Quote: "A published plugin is an npm package with the package.json above." (Supports: package type) Quote: "Build the GUI bundle before you publish, and include it through files ." (Supports: GUI bundle instruction) Quote: "Use versions compatible with the OpenCode release you target, and test the installed package, not only a workspace-linked copy." (Supports: testing instruction) Quote: "Publish a compatible plugin update when you adopt a newer API contract." (Supports: update instruction) Snapshot SHA-256: cd01ddf0d8d31d30564e161e62d75060db203ccfd93fd1243e58ddf6a743f31b (captured 2026-11-18T13:38:04Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:38:06Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:44:27Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:44:27Z Last attempt: 2026-11-20T13:44:27Z Notes and limitations: Extracted automatically from a single official source (section "Publish"). Related: https://latestn.com/tool/opencode/integrations/raycast-console-mcp-server How do I add the OpenCode Console MCP server in Raycast? https://latestn.com/tool/opencode/integrations/raycast-extension-api-key-setup How do I configure the OpenCode extension for Raycast with an API key? https://latestn.com/tool/opencode/integrations/redeem-pairing-code How do I redeem an opencode pairing code? https://latestn.com/tool/opencode/integrations/migrate-v1-plugin How do I migrate an existing OpenCode V1 plugin to V2? https://latestn.com/tool/opencode/integrations/opencode-api-key-variables Which API key environment variables does Hermes use for OpenCode Zen and OpenCode Go? https://latestn.com/tool/opencode/integrations/publish-load-tui-plugin How do I publish and load an opencode TUI plugin? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:34:39Z | changed | update instruction: — → Publish a compatible plugin update when you adopt a newer API contract. | [1] 2026-11-13T03:55:40Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/opencode/integrations/publish-plugin/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/opencode/integrations/publish-plugin POST: https://latestn.com/dispute/tool/opencode/integrations/publish-plugin with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/opencode/integrations/publish-plugin?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I publish an opencode plugin? Revision 2, last verified 2026-11-20T13:44:27Z. https://latestn.com/tool/opencode/integrations/publish-plugin (accessed 2026-11-21T09:50:33Z). @misc{LatestN_tool_opencode_integrations_publish_plugin_r2, title = {How do I publish an opencode plugin?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/opencode/integrations/publish-plugin}}, note = {Revision 2; digest sha256:1e00566f6dd340f0; last verified 2026-11-20T13:44:27Z; accessed 2026-11-21T09:50:33Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/opencode/integrations/publish-plugin