DeskRPG Hermes Plugin

DeskRPG backend — install through the DeskRPG setup wizard. It is not a general-purpose Hermes plugin; on its own it only adds HTTP routes that DeskRPG calls.

Connect DeskRPG, a self-hosted virtual office, to Hermes Agent. This standalone Python plugin extends the Hermes API Server; it is not a Hermes Desktop UI extension.

Features

• Manage Hermes profiles, identity, model configuration, toolsets and skills from DeskRPG.
• Expose Hermes kanban boards, task actions, attachments and execution records.
• Manage profile-scoped cron jobs and retrieve automation events.
• Save versioned artifacts with artifact_save, and capture supported tool outputs, response code blocks and links.
• Propose kanban cards with propose_kanban_card.
• Preserve original conversation attachments and prepare verified copies for agent file tools.

Requirements and installation

Python 3.11+ and Hermes Agent >=0.21.1 with the API Server enabled. Runtime dependencies are aiohttp and PyYAML, provided by Hermes. Internal Hermes API availability is checked during registration.

plugin_sha=$(git ls-remote https://github.com/dandacompany/deskrpg-hermes-plugin.git refs/tags/v0.32.0 | cut -f1)
hermes plugins install https://github.com/dandacompany/deskrpg-hermes-plugin --ref "$plugin_sha"
hermes plugins enable deskrpg
hermes plugins doctor deskrpg

Restart your Hermes gateway after installation or updates so the HTTP routes are attached. Connect the gateway from DeskRPG using its API Server credentials.

Once admitted to the Hermes plugin catalog, installation by the catalog name deskrpg will use the reviewed commit. Catalog updates go through a reviewed SHA-bump PR and hermes plugins update deskrpg. The plugin does not download or replace its own code.

Permissions

This plugin runs inside the Hermes gateway with the gateway process’s filesystem authority. It registers an api_server platform handler, four tools (artifact_save, propose_kanban_card, deskrpg_ask_user, conversation_files), two hooks (post_tool_call, post_llm_call), system-prompt sections and an artifact skill. It requires no additional API key to load.

HTTP routes require Hermes API Server authentication. Owner-key routes can manage all profiles and shared kanban boards, dispatch or terminate workers, and read automation results across profiles. Profile routes manage identity, configuration, cron jobs, provider credentials and OAuth flows. Profile-key isolation requires Hermes multiplex profiles; single-profile gateways resolve their own profile prefix to the listener owner key. Keep owner credentials server-side and restrict access to the gateway.