Pushary Plugin for Hermes Agent
Push notifications and human-in-the-loop for Hermes Agent via Pushary.
Install
pip install hermes-plugin-pushary
Or manually (directory install — plugin.yaml and skills/ ship inside the package):
cp -r pushary_plugin ~/.hermes/plugins/pushary
hermes plugins enable pushary
Note: Hermes runs in its own virtualenv, so
pip installmust target that interpreter (e.g.~/.hermes/hermes-agent/venv/bin/python -m pip install hermes-plugin-pushary).hermes plugins enablecurrently only recognizes directory/bundled plugins, not pip-installed ones. If you installed via pip, enable it by adding the plugin to~/.hermes/config.yamldirectly instead:plugins: enabled: - pushary
Setup
Set your API key:
export PUSHARY_API_KEY="pk_xxx.sk_xxx"
Get a key at pushary.com/sign-up.
Tools
| Tool | Description |
|---|---|
pushary_notify |
Send a push notification with optional rich context |
pushary_ask |
Ask a question via push (yes/no, multiple choice, or free text) |
pushary_wait |
Wait for the user's answer |
pushary_cancel |
Cancel a pending question |
Auto-Notifications
The plugin automatically sends push notifications when tools return errors (up to 3 per session).
Set PUSHARY_AUTO_NOTIFY_SESSION_END=1 to also get notified when a session ends.
Set PUSHARY_AGENT_NAME to identify this Hermes instance in notifications (e.g., "Hermes - daily-briefing").
Permission Gating (approve from your lock screen)
Gate dangerous tools behind a yes/no push approval — Hermes pauses on a pre_tool_call
hook, pushes the request to your phone, and only runs the tool if you approve.
export PUSHARY_GATE_TOOLS="terminal,write_file,delete_file" # comma-separated tool names
export PUSHARY_GATE_TIMEOUT_MS=55000 # optional, max 55000
Behaviour for a gated tool:
| Outcome | Result |
|---|---|
| You approve | Tool runs |
| You deny | Tool is blocked, the agent is told why |
| No answer before timeout | Tool is blocked (fail-closed — you were asked) |
| Pushary unreachable / no API key | Tool runs (fail-open — never bricks on our outage) |
Gating is off unless PUSHARY_GATE_TOOLS is set. The Pushary tools themselves are never gated.
License
MIT
Release files for hermes-plugin-pushary 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hermes_plugin_pushary-0.4.2.tar.gz | 14.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hermes_plugin_pushary-0.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.6 kB
Release files / hermes_plugin_pushary-0.4.2.tar.gz
| Download URL | hermes_plugin_pushary-0.4.2.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
211b69bc503e2dd20ad7be6be3f635b3e80bb15f1aea520c346d2bf1acf8681d
|
|
BLAKE2b-256 checksum How to use checksums |
ddbde7fb634b13acdaf480ecd7a04ec48b3ed6ec713981f78957881943ff8e80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency logRelease files / hermes_plugin_pushary-0.4.2-py3-none-any.whl
| Download URL | hermes_plugin_pushary-0.4.2-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b676d990fbc76441788697b34efd5347ef9f5a8ee2363371a7645c6d964c98fb
|
|
BLAKE2b-256 checksum How to use checksums |
b0338bde164bdb1bd6e9aaad502b7898309ddf49ea8a9a687fd7d3742219269a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency log