Skip to main content
Plugins extend Harness with tools, UI panels, notifications, and desktop integrations. The desktop app distinguishes required internal plugins from optional preset and community plugins.

Plugin types

Internal plugins currently provide the Tauri bridge, settings UI, worktree support, panel shell, and Skills/MCP management. The Windows Minimal-mode repair is downloaded from its GitHub repository when selected; its source is not embedded in the app.
Plugin manager with status and recovery actions

Manage a plugin

1

Open plugin settings

Review the plugin name, source, installed state, and any reported error.
2

Choose an action

Install a trusted plugin, upgrade an outdated one, or remove an optional plugin you no longer use.
3

Restart if requested

Some host or UI integrations become active only after the Harness service reloads.

Recovery

If a plugin operation is interrupted, use the recovery action shown by the desktop panel. Internal plugins are checked before service startup and re-linked to the bundled copy when their dependency declaration or files are missing.
A Harness plugin can execute local code. Check the repository owner, release history, package contents, and requested capabilities before installation.
Developers can continue with Plugin system architecture.