Hermes Remote Pair

What Hermes Remote Pair does

The repository has two matching skills. hermes-remote-client/SKILL.md goes to the calling agent and covers when to delegate, how to assemble a task, synchronous versus asynchronous strategy, SSE progress listening, and error retry and fallback. hermes-remote-server/SKILL.md is for the administrator of the Hermes machine and covers enabling api_server, authentication keys, an nginx reverse proxy with CDN or WAF protection, the contract implementation and monitoring. Both share one caller contract with a task envelope, a response envelope, a state machine and SSE event names.

The envelope carries a task_id for idempotent retries, an untrusted_data field that keeps content from web pages, comments or logs marked as data rather than instructions, and an expected_output format. Short tasks use chat/completions synchronously, and because the README says free-tier CDN connections are cut at about 100 seconds, tasks over 90 seconds should use the asynchronous /runs endpoint with SSE progress. It presents itself as a lightweight point-to-point alternative to A2A with no SDK. The README is in Chinese and the license is MIT.

Key features

• Client skill for the calling agent and server skill for the Hermes administrator
• Task envelope with task_id, untrusted_data and expected_output fields
• Synchronous calls for short tasks and asynchronous /runs with SSE for long ones
• nginx reverse proxy guidance, including SSE buffering and CDN timeouts
• A curl-based client that needs no SDK

When to use it

• Letting a daily assistant agent delegate server work to a Hermes Agent that has terminal and database access
• Running long Hermes tasks remotely with streamed progress events
• Keeping content from web pages or logs marked as untrusted data when passing tasks between agents

Who it is for: People who run Hermes Agent on a server and want another agent to call it over HTTP in a controlled way.

How it fits with Hermes Agent

Built for Hermes Agent: the server skill configures the Hermes api_server platform, and the client skill lets other agents call it.

Requirements: Hermes Agent with platforms.api_server enabled and an API key; for public exposure an nginx reverse proxy with CDN or WAF protection; the caller needs only curl or another HTTP client

FAQ