Skip to content

HomePlugins

Extend the workspace without widening what it may do.

A plugin declares the Cognia capabilities it needs in its manifest. Undeclared Cognia APIs are denied, and you can read the declaration before installing.

On this page

01

What a plugin can contribute

Surfaces a plugin can add, each under the same permission rules.

  • Tools

    New tools an agent may call, with the capabilities they need spelled out.

    Learn more

  • Panels and views

    Their own surfaces inside the workspace, next to the task they belong to.

    Learn more

  • Workflow nodes

    Steps other people's workflows can use, contributed the same way as tools.

    Learn more

  • Slash commands

    Named entry points in the composer for work the plugin knows how to do.

    Learn more
02

How permission works

The declaration is the contract, and it is enforced rather than advertised.

  • Declared capabilities

    The manifest lists every capability. Requesting one outside the list fails rather than prompting.

    Learn more

  • Signing and provenance

    Where a plugin came from, and what that means for what it is allowed to do.

    Learn more

  • Host-page execution

    Plugin bundles currently execute in the host page through indirect eval. Capability checks constrain Cognia APIs, but ambient browser globals remain available; this is not a code-isolation sandbox.

    Learn more

From existing capability to installed extension.

A skill, MCP server, CLI, or purpose-built bundle can enter through the same manifest-driven lifecycle and surface only what it declares.

  1. Bring the source

    Start from the SDK or adapt an existing skill, MCP server, or CLI. Impeccable follows this path as an installable design-review skill.

    Learn more

  2. Declare the contract

    The manifest names activation events, bundled resources, contribution points, and every Cognia capability the extension may request.

    Learn more

  3. Contribute surfaces

    Register skills, tools, commands, panels, workflow nodes, hooks, or providers through the host bridges instead of patching the application.

    Learn more

  4. Package and install

    Build a versioned archive, validate its contents, install it locally, and let Cognia activate or remove it through one lifecycle.

    Learn more

Writing one

The plugin CLI scaffolds, builds and packages a plugin, and can convert an existing MCP server, skill or CLI into one without writing plugin code.

  1. Scaffold the plugin and declare the capabilities it needs.
  2. Build the surfaces it contributes — tools, panels, workflow nodes, commands.
  3. Package it, and install it locally to check the declaration against what it actually calls.