How are plugins isolated?

Each plugin runs sandboxed in a Web Worker, capability-scoped to the workspace that installed it. It can only reach the slots and APIs its manifest declares and the user granted — there is no ambient access to the rest of the app.

What can a plugin extend?

UI slots like the issue panel, the board sidebar, the command palette, and a settings tab. Plugins call the same typed tRPC API and MCP tools the product itself uses, so there is no second-class surface.

What does the manifest declare?

planoda.plugin.json declares the plugin's id, name, version, the UI slots it mounts, and the capabilities it requests (e.g. issues:read, comments:write). Requested capabilities are shown to the installing admin for consent.

Build and test locally, then submit at /developers/plugins/submit. We review the manifest and code, then handle distribution, install flows, and versioning in the marketplace.

How are updates handled?

Ship a new version; installs roll forward under the same capability grants. If a new version requests additional capabilities, admins are re-prompted to consent before it activates.

Developers

Extend Planoda with plugins.

Build on a typed plugin API and MCP tools, then publish to the marketplace. Manifest, review, and distribution are handled for you.

Submit a plugin Read plugin docs

Plugins in short

Plugins are sandboxed UI + logic extensions: each runs in a Web Worker, capability-scoped to the workspace, and calls the same typed tRPC API and MCP tools the product uses.
A declarative planoda.plugin.json manifest declares the plugin's id, the UI slots it mounts (issue.panel, board.sidebar, command.palette, settings.tab), and the capabilities it requests.
definePlugin() wires render functions to slots; capabilities are shown to the installing admin for consent before the plugin activates.
Build with npm create @planoda/plugin, test locally with a scoped token, then submit at /developers/plugins/submit for review and marketplace distribution.

The plugin model

A plugin is a sandboxed bundle that mounts into named UI slots and talks to the workspace through the same typed API the product uses — scoped to exactly the capabilities it declares.

Manifest — `planoda.plugin.json`

planoda.plugin.jsonjson

{
  "id": "acme.figma-preview",
  "name": "Figma Preview",
  "version": "1.0.0",
  "slots": ["issue.panel"],
  "capabilities": ["issues:read"],
  "entry": "./dist/plugin.js",
  "icon": "./icon.svg"
}

The installing admin sees capabilities and consents before the plugin activates.

Hello world — `definePlugin`

src/plugin.tsxtsx

import { definePlugin } from "@planoda/plugin-sdk";

export default definePlugin({
  slot: "issue.panel",
  render: ({ issue }) => (
    <div>
      <h3>Figma</h3>
      {issue.figmaUrl ? (
        <FigmaPreview url={issue.figmaUrl} />
      ) : (
        <p>No Figma link on this issue.</p>
      )}
    </div>
  ),
});

Runs sandboxed in a Web Worker — no ambient access beyond the granted capabilities.

Extension slots

issue.panelA panel inside the issue detail view
board.sidebarA pane alongside a board
command.paletteCustom commands in ⌘K
settings.tabA workspace-settings tab for config

FAQ

Plugin questions, answered

Build with us

Ship your plugin to thousands of teams.

Submit a plugin Developer docs

Developer resources

Everything you need to build on Planoda.

API referenceREST + tRPC, OAuth, rate limits.TypeScript SDKTyped client, retries, webhooks.MCP serverAgents with propose/approve guardrails.WebhooksSigned events, at-least-once delivery.PluginsSandboxed extensions, marketplace.Full docsGuides, recipes, and the catalog.

Extend Planoda with plugins.

The plugin model

Manifest — `planoda.plugin.json`

Hello world — `definePlugin`

Extension slots

From idea to marketplace

Read the guide

Build & test

Submit to the store

Plugin questions, answered

Ship your plugin to thousands of teams.

Developer resources

Extend Planoda with plugins.

The plugin model

Manifest — `planoda.plugin.json`

Hello world — `definePlugin`

Extension slots

From idea to marketplace

Read the guide

Build & test

Submit to the store

Plugin questions, answered

Ship your plugin to thousands of teams.

Developer resources

Extend Planoda with plugins.

The plugin model

Manifest — planoda.plugin.json

Hello world — definePlugin

Extension slots

From idea to marketplace

Read the guide

Build & test

Submit to the store

Plugin questions, answered

How are plugins isolated?

What can a plugin extend?

What does the manifest declare?

How do I publish?

How are updates handled?

Ship your plugin to thousands of teams.

Developer resources

Extend Planoda with plugins.

The plugin model

Manifest — planoda.plugin.json

Hello world — definePlugin

Extension slots

From idea to marketplace

Read the guide

Build & test

Submit to the store

Plugin questions, answered

How are plugins isolated?

What can a plugin extend?

What does the manifest declare?

How do I publish?

How are updates handled?

Ship your plugin to thousands of teams.

Developer resources

Manifest — `planoda.plugin.json`

Hello world — `definePlugin`

Manifest — `planoda.plugin.json`

Hello world — `definePlugin`