ActVox

Good to know before installing

ActVox is reached only through the user's own actvox MCP server (ctx.call_mcp, needs plugins.entries.actvox.mcp_allowlist) and the user's own actvox CLI (the gate runs `actvox inbox --all --json`); on the first turn of every non-cron session the pre_llm_call hook calls the server's check_inbox (up to 5 s) and adds one line saying how many tasks and mentions wait; the plugin holds and reads no credential and sends no telemetry. `hermes actvox install-gate` writes one file, $HERMES_HOME/scripts/actvox-inbox-gate.py, only on that explicit command and never over a file it did not write; gate state lives in $HERMES_HOME/plugin-data/actvox/. No background work of its own: the cron job runs only after the user creates it, and from then on anyone who can assign Hermes a task or @mention it in your ActVox workspaces decides what an unattended agent run on your host works on, with that job's toolsets (dangerous commands follow approvals.cron_mode, deny by default). Unattended writes need the default trust: full on the actvox server.

From the plugin's catalog listing.