跳到主要内容

rply-platform

❖ Communityv0.7.0

rply gateway platform: talk to Hermes from the rply inbox on your phone and laptop, with web push. Messages and files both ways, seen/working/done with a live activity note, clarify questions and command approvals as tappable questions, cron delivery, a pinned table of scheduled jobs, a dashboard app with run/pause/resume, and an rply_request_secret tool that saves API keys to the profile's .env without the value passing through the chat. Each profile joins the channel as its own agent.

Open in Hermes Desktop
hermes plugins install rply-platform

What it adds

Tools 1

rply_request_secret

README

From the reviewed commit 932926e ↗; it updates when the author re-pins.

rply for Hermes Agent

A Hermes Agent messaging platform plugin for rply, the inbox for agents that run without you. Write to Hermes from the rply app on your phone or laptop, and get its replies, questions, approvals and scheduled job results there, with push notifications.

Full guide: https://rply.sh/docs/integrations/hermes/

Install

Requires Hermes Agent 0.22.2 or newer.

hermes plugins install https://github.com/joshuaKnauber/rply/tree/main/integrations/hermes --enable
hermes gateway setup     # pick rply, enter the agent code from the rply app (or leave it empty to create a channel)
hermes gateway restart

Without the setup menu (for example when Hermes sets itself up from the rply app's setup prompt):

hermes rply join https://app.rply.sh <agent-code>     # or: hermes rply init https://app.rply.sh --name "Hermes"
hermes gateway restart                                # or hermes gateway install, the first time

For more profiles, repeat with hermes -p <name> .... Each profile has its own copy of the plugin and joins the channel as its own agent.

Features

  • Messages both ways, with seen / working / done and a live note of what Hermes is doing
  • Images and files both ways
  • Clarifying questions and dangerous-command approvals as rply questions
  • rply_request_secret tool: API keys are encrypted on the human's device and saved to .env; Hermes never sees the value
  • Cron delivery (--deliver rply), a pinned table of scheduled jobs and a dashboard app with run / pause / resume
  • One rply agent per Hermes profile, addressed with @name

Disclosures

  • Network: talks only to the configured rply server (RPLY_SERVER, default https://app.rply.sh). It keeps a long-running connection (long-polling) for messages and dashboard calls.
  • Reads outside its own data: Hermes' scheduled jobs and session list (for the pinned table and the dashboard). Dashboard buttons run, pause and resume jobs.
  • Stored credentials: the rply agent token in the profile's .env (written by hermes gateway setup), an X25519 keypair for secrets in <profile>/rply/secret-key.json (mode 0600), and secrets the human sends, saved to the profile's .env.
  • Background processes: none besides the gateway's own tasks. No shell commands, no telemetry, no self-updating.

Files

  • adapter.py: the platform adapter, the secret tool and the registration
  • sealed_box.py: rply's sealed box (X25519 + HKDF-SHA256 + XChaCha20-Poly1305) for opening secrets
  • dashboard.html: the dashboard app

License

MIT (see LICENSE). The rest of rply is AGPL-3.0.

← Back to the catalog · catalog built Oct 19, 2026