All plugins

pushary

Phone notifications, questions and approvals through Pushary's native Hermes approval transport, with optional per-tool gates and a Hermes Desktop status-bar panel. Disclosure — approval transport and per-tool gates hand dangerous-command approvals to whoever holds the devices or Slack channel paired to your Pushary account, or to the approvers a Pushary Team route names (fails closed); the Hermes Desktop panel answers an approval this Hermes is carrying by withdrawing it on pushary.com and uses the answer only when Pushary confirms that withdrawal won; each approval is recorded owner-only in plugin-data/pushary/approvals (redacted command, choices, outcome; removed after a day); messages queued in the Pushary app or Mac notch are injected into the next turn as operator instructions and wait in ~/.pushary/run/hermes-commands; when the user has turned on Pushary's encrypted conversation history and installed Pushary's helper, a background thread reads the session through Hermes's SessionDB, keeps owner-only snapshots in ~/.pushary/hermes-history (removed after 48 hours unchanged) and runs that helper (pushary-native-transcripts inside Pushary.app, or pushary-transcript-register at the owner-only path record ~/.pushary/hermes-history-helper.json that Pushary setup writes, else on PATH) with the API key so Pushary's uploader can encrypt and send them; sends session events with a machine id (~/.pushary/machine-id when present, else a hashed hostname) on every turn, the redacted command and description of each approval it carries, the redacted reason when Hermes marks a turn failed (max 200 characters), redacted gated-tool arguments and pushary_remind reminder text to pushary.com; reads PUSHARY_API_KEY only through Hermes.

Pushary1Automationv1.0.5Updated 1 day ago

About

Phone notifications, questions and approvals through Pushary's native Hermes approval transport, with optional per-tool gates and a Hermes Desktop status-bar panel. Disclosure — approval transport and per-tool gates hand dangerous-command approvals to whoever holds the devices or Slack channel paired to your Pushary account, or to the approvers a Pushary Team route names (fails closed); the Hermes Desktop panel answers an approval this Hermes is carrying by withdrawing it on pushary.com and uses the answer only when Pushary confirms that withdrawal won; each approval is recorded owner-only in plugin-data/pushary/approvals (redacted command, choices, outcome; removed after a day); messages queued in the Pushary app or Mac notch are injected into the next turn as operator instructions and wait in ~/.pushary/run/hermes-commands; when the user has turned on Pushary's encrypted conversation history and installed Pushary's helper, a background thread reads the session through Hermes's SessionDB, keeps owner-only snapshots in ~/.pushary/hermes-history (removed after 48 hours unchanged) and runs that helper (pushary-native-transcripts inside Pushary.app, or pushary-transcript-register at the owner-only path record /.pushary/hermes-history-helper.json that Pushary setup writes, else on PATH) with the API key so Pushary's uploader can encrypt and send them; sends session events with a machine id (/.pushary/machine-id when present, else a hashed hostname) on every turn, the redacted command and description of each approval it carries, the redacted reason when Hermes marks a turn failed (max 200 characters), redacted gated-tool arguments and pushary_remind reminder text to pushary.com; reads PUSHARY_API_KEY only through Hermes.

Pushary for Hermes

Ask a question in Hermes and answer it on your phone. Try it with your own device before routing command approvals there.

Connect your phone

  1. Set up your Pushary Agent account. Pair your phone with that account and get its API key from Agent settings.

  2. In your terminal, install the catalog plugin:

    hermes plugins install pushary
    
  3. Enter PUSHARY_API_KEY when Hermes prompts for it. If you missed the prompt, save the key in the plugin’s settings in Hermes Desktop. Keep it out of chat. Start a new Hermes session (for a running gateway, use hermes gateway restart).

Try one question

Tell Hermes: Use pushary_ask to ask me “Did this test reach your phone?” Report my answer and do nothing else. Open the question on your paired phone and tap Yes or No. Hermes should report the answer you tapped.

If nothing arrives, check the account and notification permissions on your phone. A pending question is still live: wait for the same question rather than sending another. If Pushary hands it back to Hermes, answer the local prompt instead. No answer is not approval.

Command approvals are separate from this test. To route them to your phone, set security.approval.transport to pushary. Set security.approval.transport_fallback to builtin if you want Hermes’s local prompt after a safe handoff; an unconfirmed withdrawal does not authorize the command. See the plugin guide for approval routing and what the plugin reads and sends.

README from the reviewed commit b7b1b72; it updates when the author re-pins.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section