Source: https://harnsy.dev/features/plugins

> Extend harnsy with Lua plugins: buttons, board numbers, pages in the dashboard and in task cards, windows in the terminal. A signed catalog, rights you choose, a sandbox for unverified pages.

# Add what harnsy does not do out of the box.

A plugin is a small piece of Lua code: a button, a number on the board, a page of its own, a check before a result is handed in. Install one from the catalog and see what it asks for before you switch it on.

## It reacts to your work.

A plugin wakes on an event of a task, on a schedule or on a button. It can read the web and MCP servers you allowed, write to the lead, call other plugins and give agents tools of its own.

## Pages where you work.

A plugin can add a page to the dashboard, a tab in a task card, a widget on the board, buttons under its message in a chat, and a window in `harnsy term`, one window for all projects if it likes.

## You choose what it may use.

A plugin built on this machine (by you or by one of your agents), or one verified by harnsy, switches on in a project with one button and gets every right it asks for; for a verified one you see where it sends data. The key, mail or chat it uses you pick yourself. A plugin that is not verified asks for each right, and you tick what it gets. Resources shows how much each plugin takes.

You see what a plugin asks for before you install it.

## A signed catalog.

The catalog at plugins.harnsy.dev is signed: install, update and recall from one place. “Verified by harnsy” means harnsy's AI security reviewer read that version's code and found it matches what it declares. It is a review of one version, not a guarantee.

[Open the catalog](https://plugins.harnsy.dev/) →

## Unverified pages run apart.

The page of a plugin without a verified signature runs in a sandbox of its own, away from the rest of the dashboard. A verified version, or one built on this machine, runs in the dashboard itself, with your session and rights. Switch on only plugins whose publisher you trust.

## One version in a project.

Switch on a new version and the old one in that project turns off; you can bring it back. Install a new version right from the plugin’s page with “Install a version…”. “Versions by project” shows which version each project runs, and “Update everywhere” moves them all at once.

[How to install and write one](https://harnsy.dev/docs/plugins) →

## Limits, honestly

- Plugins are off until you turn them on in Settings.
- Installing and using plugins is free; some parts use harnsy Max features: chats, Inbox feeds, keys, incoming webhooks.
- Plugins are made by their publishers, not by harnsy. A plugin acts with the rights it was given; harnsy shows what it asks for and does not vouch for its code beyond the review.

## Your first team is one prompt away.

Installing takes one sentence to your agent. To run your agents, harnsy drives a terminal: tmux if it is installed, otherwise its own terminal host (on Windows, always its own).

`Install harnsy following https://harnsy.dev/llms.txt`
