> For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt.

# Plugins and Apps

Plugins extend Sero. They can add an app UI, agent tools and commands, background services, model or service providers, and dashboard widgets.

> **Warning:** An installed plugin can execute code on your device and access your workspace. Install plugins only from sources that you trust.

## Use plugin apps

Core apps, such as Dashboard, Agent Board, and Explorer, are part of the desktop shell. Plugin apps can be built into Sero or installed from an external source. An external plugin is not a built-in Sero feature.

Use [App Store, Favorites, and Installed Plugins](/guide/app-store-favorites.md) to find, install, favorite, and uninstall plugin apps. Use the [Plugin Catalog](/plugins/catalog.md) to check whether a documented plugin is built in or external.

Portable **Agent Plugins** are separate. They add Agent Skills and MCP servers, but they do not add an app or sidebar entry. See [Agent Plugins](/reference/agent-plugins.md).

The local plugin management view shows installed development plugins and their attached source folders.

![Local Plugin Management](/static/image/local-plugin-preview.f2dbc924ec.jpg)
Plugin apps can provide focused work surfaces. The following group shows the agent board, design generation, and a plugin app.

![Agent board](/static/image/agent-board.1e967516b3.jpg)
![Design generation](/static/image/design-library.f4cfd5f3bb.jpg)
![Design generation](/static/image/design-library-2.6e8f67d370.jpg)
![Plugin app](/static/image/loom.4c4acd3221.jpg)
## Build a plugin

A plugin package uses `sero` manifest fields to declare its Sero features. It can contain a Pi extension, a federated React UI, a background runtime, shared types, and widget metadata.

```mermaid
flowchart LR
  Plugin[Plugin package] --> Manifest[sero manifest fields]
  Plugin --> UI[React federated UI]
  Plugin --> Extension[Pi extension]
  Plugin --> Runtime[Optional background runtime]
  Plugin --> Widgets[Dashboard widgets]

  Manifest --> Host[Sero desktop host]
  UI --> Remote[Module Federation remote]
  Remote --> AppArea[Active app area]
  Extension --> Pi[Pi runtime]
  Pi --> Tools[Agent tools and commands]
  UI --> AppRuntime["@sero-ai/app-runtime"]
  AppRuntime --> State["Profile/workspace app state"]
```

The anatomy diagram shows how one plugin package connects its manifest, UI, extension, runtime, and widgets to Sero.

![Sero plugin anatomy](/static/image/img6.0a6dc364a2.jpg)
Plugin UIs use `@sero-ai/app-runtime` to read app identity, use host-backed app state, send prompts, call tools, read available models and themes, and register widgets. Do not use browser storage for persistent plugin state.

Start with [Plugin Quickstart](/reference/plugin-quickstart.md). Use [App Runtime Reference](/reference/app-runtime.md) for the React API and [Plugins](/reference/plugins.md) for manifests, compatibility, installation, and development.
