Hermes Agent does not appear in Slack or Telegram for dangerous command approval buttons, check the version, gateway permissions, and platform event configuration first. v0.8.0 made Slack/Telegram dangerous command approval a native button; If you have an older version or permissions that are not configured, you may still need to manually enter the /approve or even not receive approval messages at all.
Check if the button should appear first
- Whether the Hermes Agent version is v0.8.0 or later.
- Whether the task actually triggers a hazardous command approval, not a normal security command.
- Are you configured in the allowlist to approve the agent?
- Whether the Slack bot or Telegram bot has permissions to send messages, send interaction buttons, and read channel messages.
Slack FAQs
The button does not appear in Slack, focusing on Socket Mode, Bot Token, App-Level Token, Event Subscription, and Channel Invitation. If the bot is not in the channel, the event is not subscribed, and the interaction callback is not opened, the Hermes Agent will only be able to see part of the message. The team environment also confirms that the admin hasn't restricted app permissions.
Telegram FAQs
The easiest thing to make in Telegram is User ID. Hermes Agent uses a numeric ID, not a username, for access control. The group also depends on privacy mode and whether the bot can read commands. If the approval status is unresponsive, checking the gateway log is usually faster than repeating the dot button.
In terms of safety, don't open the global yolo for convenience. The approval button is meant to make mobile easier to use, but it shouldn't replace least privilege, sandboxing, and allowlist. If the button does not appear, first fix the gateway and platform permissions, and do not close the approval as soon as possible.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entrance: https://hermes-agent.nousresearch.com/.
