Summary
On Discord, permission approval prompts render as tappable buttons (great UX), but the clarify tool's multiple-choice questions fall back to plain text — users have to type "A", "B", "C" back into chat.
Expected
When an agent calls clarify with a choices array on Discord, the choices should render as Discord message components (buttons or select menu), matching the UX of permission approval prompts.
Actual
The agent receives {"error": "Clarify tool is not available in this execution context."} when called from a Discord DM, OR the prompt is delivered as plain text with no interactive component, forcing the user to type their answer.
Why it matters
- Permission prompts already have this pattern working on Discord — the rendering infra exists
- Clarify is used constantly for low-friction disambiguation; typing back is clunky on mobile
- Telegram has inline keyboard support in the platform, which could benefit from the same treatment
Platforms to consider
- Discord: message components (buttons for ≤5 choices, select menu for more)
- Telegram: inline keyboards
- Slack: block kit actions
Environment
- Hermes Agent (latest as of May 2026)
- Discord DM context
- Model: Claude Opus 4.7 via OpenRouter
- Reported while using Hermes through a Discord DM bot integration
Summary
On Discord, permission approval prompts render as tappable buttons (great UX), but the
clarifytool's multiple-choice questions fall back to plain text — users have to type "A", "B", "C" back into chat.Expected
When an agent calls
clarifywith achoicesarray on Discord, the choices should render as Discord message components (buttons or select menu), matching the UX of permission approval prompts.Actual
The agent receives
{"error": "Clarify tool is not available in this execution context."}when called from a Discord DM, OR the prompt is delivered as plain text with no interactive component, forcing the user to type their answer.Why it matters
Platforms to consider
Environment