Hermes profiles and Voice Follow-up

Complete the standard Hermes setup guide first. This page covers the two parts of the Hermes integration that differ from the other plugin integrations: profile selection and the execution modes that can accept Voice Follow-up.

Choose Hermes profiles

Run:

npx agentapprove profiles

The command shows the Hermes profiles found on the computer. Enable the full Agent Approve plugin for the profiles you want to supervise and disable it for the others.

Profile selection controls which profiles send Agent Approve events. Voice Follow-up is set separately. The account setting is the default, and each Hermes profile can override it with its own On or Off from the Agents tab. See Voice Follow-up.

Voice Follow-up requirements

Hermes can return a follow-up message only to its classic interactive CLI. Keep that CLI session open until the reply returns.

Voice Follow-up does not currently return messages to:

• Gateway sessions, including conversations started through Telegram, Discord, Slack, or another gateway channel
• The Hermes desktop app and hermes dashboard web sessions, which deliver replies the same way as gateway channels
• hermes chat -q and --oneshot runs
• Cron jobs and Kanban workers that use a single-query process

These execution modes can still use Agent Approve for approvals, policy enforcement, activity monitoring, Agent Completion notifications, and push notifications. The limitation applies only to sending another instruction back to Hermes. Continue the conversation through its original gateway channel when needed.

You need:

1. A Hermes profile with the Agent Approve plugin enabled
2. Voice Follow-up resolving to on for that profile, through the account setting or the profile's own On
3. A classic interactive Hermes CLI session that remains open until the mobile reply returns

The Mobile Q&A setting is not part of this Hermes flow. It controls supported Claude Code questions.

The plugin reports whether the finished session can accept a reply, so no follow-up prompt opens for the execution modes listed above. Those sessions send an Agent Completion notification instead, and so does any session the plugin cannot positively identify as an interactive CLI. In the rare case where the session looked interactive but Hermes still rejects the injection, the plugin records accepted=False in the hook debug log and the message does not become the next Hermes turn.

Update or repair

Run npx agentapprove install again to refresh the plugin. Run npx agentapprove status to check the saved setup. If the selected profiles are wrong, run npx agentapprove profiles.