hermes - 💡(How to fix) Fix Render "clarify" multiple-choice questions as Discord buttons [1 comments, 2 participants]

When an agent uses the clarify tool with multiple-choice options on Discord, the choices are rendered as plain text (e.g., "1) Option A, 2) Option B..."). Users must type a number or text reply, which feels clunky compared to native Discord UI patterns.

Proposed solution: When clarify is invoked with a choices array, render the options as Discord ActionRow + Button components instead of plain text. The agent waits for an interaction_create event (button click) and maps the selected choice back into the tool result.

Text-only clarify (no choices array) continues to work exactly as it does today — no breaking change. Multiple-choice clarify gets the button treatment automatically on Discord.

Why this matters: UX parity — Other AI tools on Discord (e.g., Claude's askuserquestion integrations) use buttons for structured input. Hermes feels less polished without them. Error reduction — Typing a choice number is prone to typos. A button click is unambiguous. Discoverability — Buttons make it obvious what actions are available without reading a formatted list.

Suggested implementation notes: In gateway/platforms/discord.py, detect when an outgoing message is a clarify tool call containing a choices array. Render the message with components: [ActionRow[Button, Button, ...]]. On interaction_create, resolve the interaction (to prevent the "interaction failed" spinner) and inject the button's custom_id / label as the user's reply into the session stream. Timeout handling: if no button is clicked within the clarify timeout window, fall back to the existing text-reply behavior or auto-cancel.(1/2) Backward compatibility: No changes to the clarify tool schema or agent loop. Only the Discord gateway's rendering layer changes. Other platforms (Telegram, Slack, etc.) can adopt the same pattern later if desired.