Extensions guides

How Hermes plugins extend Rocky with reusable integrations while keeping capabilities, dependencies, and operational boundaries clear.

A practical guide to native mcp client in a verified Hermes/Rocky workflow.

A practical guide to mcp server setup in a verified Hermes/Rocky workflow.

Build a maintainable Hermes plugin with a clear manifest, precise tool schemas, safe handlers, lifecycle hooks, and a verification path.

Implement a cloud-browser provider that owns remote session lifecycle while Hermes keeps the common browser tool surface.

Connect a search or extraction backend to Hermes with explicit capability flags, normalized results, and independent search/extract routing.

Use the host-owned `ctx.llm` surface for bounded plugin-side model calls without duplicating provider credentials or bypassing operator trust controls.

Evaluate and enable bundled Hermes plugins explicitly, with attention to discovery order, hooks, authority, observability, and rollback.

Integrate an external vault as a standalone Hermes plugin while leaving precedence, timeouts, provenance, protected variables, and environment writes to the core orchestrator.

Set up a profile-safe Hermes development environment, choose the right extension surface, test cross-platform behavior, and prepare a reviewable contribution.

Develop TUI and desktop branches from isolated worktrees while safely sharing dependencies only when lockfiles match.

Create a maintainable dashboard theme with deliberate palette, typography, layout, assets, and rollback checks instead of fragile global CSS.

Add dashboard tabs, shell slots, or page augmentations with a manifest, SDK frontend, scoped backend routes, and explicit reload verification.

Launch and supervise plugin-owned child sessions through opaque handles, narrow toolsets, cooperative cancellation, and honest process-lifetime limits.

Build a hot-reloading Hermes Desktop extension with the official SDK while keeping disk-plugin imports and optional Python backends inside their documented security boundaries.

Implement the Hermes MemoryProvider contract with non-blocking synchronization, explicit privacy disclosure, profile-safe storage, and lifecycle verification.

An architecture for scheduled GitHub pull-request analysis that begins report-only and adds authenticated review actions only behind explicit approval policy.