Files

T

Brooklyn Nicholson 44790bc9c8 feat(desktop): plugin descriptions + open the agent plugins folder

HermesPlugin/PluginRecord gain a description one-liner (kanban gets
one) shown in the inventory instead of the raw file path, and the
agent plugins section can open the backend's plugins dir — path from
config.get profile so it's profile-aware, local backends only since
openDir mkdir-creates.

2026-08-08 17:34:20 -05:00

example

fix(desktop): ship example plugin off by default

2026-08-01 15:46:36 -05:00

hello-runtime

feat(desktop): SDK — useGrabScroll export + dogfood plugin touch-ups

2026-07-30 07:18:08 -05:00

kanban

feat(desktop): plugin descriptions + open the agent plugins folder

2026-08-08 17:34:20 -05:00

README.md

fix(desktop): drop the gateway-pill dogfood plugin

2026-08-06 22:29:33 -05:00

README.md

Bundled plugins

Drop a <name>/plugin.{ts,tsx} here that default-exports a HermesPlugin and it registers automatically at boot (vite glob in ../contrib/plugins.ts), with the same inventory + live enable/disable contract as runtime plugins.

Keep this tree for real shipped plugins (and the small authoring fixtures that dogfood the SDK). One-off demos that rebuild a core chrome piece 1:1 do not belong here — they double the UI and confuse Settings ▸ Plugins. Publish those in the companion hermes-example-plugins repo instead.

User- and agent-authored plugins load at runtime from $HERMES_HOME/desktop-plugins/<name>/plugin.js (the disk door) — see the hermes-desktop-plugins skill.