[Question] UI Plugins & Connectors for the Tauri Desktop App

[qvdp]

Question

First of all, I absolutely love the OpenCode project, and the recent beta of the Tauri-based desktop app is fantastic! Great work, thank you.

Description

I'm interested in building integrations for services like Linear or Slack directly into the OpenCode desktop app. To make these truly useful, they would need custom UI elements. Since these are highly specific third-party integrations, submitting a PR to add them directly to the core codebase wouldn't be appropriate.

I am aware that OpenCode currently supports a robust backend/core plugin system (⁠@opencode-ai/plugin) to add custom tools, lifecycle hooks, and logic.

I would love to be able to extend the visual experience—for example, by injecting a sidebar panel for Linear issues, a dedicated view for Slack messages, or building visual extensions directly on top of the Tauri app to add new features.

Is this something that is currently possible (perhaps undocumented), or is it on the roadmap for future releases?

Thanks for your hard work!

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Is it possible to add commands and a custom UI using plugins? #15007: Very similar question about adding custom UI using plugins in OpenCode
• Plugin API for custom sidebar panels #5971: Feature request specifically for a Plugin API for custom sidebar panels (closely matches the sidebar panel use case you described)

[m13v]

a plugin API for the Tauri app would be awesome. we built our desktop app with a similar extensibility model using skills (structured markdown files that define what the agent can do) and MCP servers for the actual tool implementations. the key design decision is whether plugins run in the same process or as separate processes, we went with separate processes (MCP servers over stdio) which gives isolation but adds IPC latency. for UI plugins specifically, Tauri's IPC bridge lets you expose Rust functions to the webview which is a natural extension point.

[m13v]

our skill/plugin system and MCP server architecture: https://github.com/m13v/publish-skill for skill publishing and https://github.com/m13v/skill-registry for discovery. the MCP server that runs as a separate process: https://github.com/mediar-ai/mcp-server-macos-use/blob/main/Sources/MCPServer/main.swift