Skip to content

About

OpenCode integrations: self-contained OpenCode plugins for third-party applications and services

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

OpenCode integrations

OpenCode integrations connect OpenCode to third-party applications and services. Each integration is one self-contained OpenCode V2 plugin, published as one npm package @neuralnomads/opencode-<app> with its tools, skills, data and scripts. An application-side part (an add-on, a panel), when there is one, ships inside the package but is installed separately, by an explicit action, and is checked by version.

Integrations work in every OpenCode client: the terminal UI, the desktop app and CodeNomad. CodeNomad gives the best experience (a catalog, per-integration status, one-click host install and attaching an open application to a conversation), but no integration depends on it.

Status: preview (spec: 0, RPC contract 1). The packages are previews. Nothing is published to npm yet.

Families

Family Principle Examples
native An authenticated loopback host inside the application owns the document state; the plugin exposes bounded <app>_context / <app>_apply intents. The conversation happens in an application panel or in any OpenCode client by attaching the open application. Blender (pilot), Gaffer, Houdini
vendor-mcp The plugin declares the vendor's official MCP server (never redistributed), or connects to it when OpenCode cannot, checks its preconditions and adds tested skills and workflows. DaVinci Resolve, Affinity
api The plugin calls a remote API directly. Microsoft 365

Integrations

None is released yet. The reviewed list lives in catalog.json.

Integration Family Status
OpenCode for Affinity vendor-mcp preview
OpenCode for Blender native preview (pilot)
OpenCode for Gaffer native preview
OpenCode for Houdini native preview
OpenCode for Microsoft 365 api preview
OpenCode for DaVinci Resolve vendor-mcp preview

Installation

Any OpenCode client: add the package to the plugins list of your global OpenCode configuration (~/.config/opencode/opencode.json):

{
  "plugins": ["@neuralnomads/opencode-<app>@^0.2"]
}

An entry with settings is an object: { "package": "@neuralnomads/opencode-<app>@^0.2", "options": { … } }.

OpenCode installs the package on its next start. Integrations of the native family are installed in the global configuration only.

In CodeNomad

Open Status → Plugins, choose Add, and enter the package name; or use the Integrations extension, which lists the catalog, shows each integration's state and installs the application part.

Repository layout

Path Content
spec/ How an integration, CodeNomad and the application part talk to each other
catalog.json Reviewed catalog, published as the asset of a catalog-v<n> release
packages/integration-kit/ Shared core bundled into every integration plugin
packages/testing/ Test helpers, and check:markers (markers, catalog, each plugin's status)
integrations/<app>/ plugin/ (the npm package), host/ (the application part), test/
scripts/ Repository tooling, including the trace scan

Development

Node.js 22.18 or later runs the TypeScript sources directly. The tests of the reference Python discovery client need Python 3 (python3, or python on Windows; set PYTHON to choose another interpreter).

npm ci
npm run lint
npm run typecheck
npm test
npm run check:markers
npm run build && npm run scan

See CONTRIBUTING.md and SECURITY.md.

License

MIT

About

OpenCode integrations: self-contained OpenCode plugins for third-party applications and services

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages