Discord conversational agent can't emit real @mentions (posts literal "@username" text instead) #68

New issue

Closed

opened 2026-07-24 22:54:54 +00:00 by admin_emi · 0 comments

admin_emi commented

2026-07-24 22:54:54 +00:00

Owner

Observed live: asked to ping a user, the bot's message contained the literal text @vivi_magala rather than a real Discord mention — it didn't render as a mention and didn't notify the user. The owner had to post the mention by hand (<@299809459512016897>) as a workaround.

PR #59 ("daemon: let the conversational agent own @mentions in server channels") is adjacent but does not fix this — per review, it governs which bot answers a given @Thermograph mention (so the gateway bot and the conversational agent don't both reply), not whether the conversational agent's own outgoing messages can construct a real <@id> mention. Two different bugs on the same surface.

Worth checking whether the conversational agent has access to resolve a display name / username to a Discord user ID before composing a reply that's meant to ping someone, and whether its reply-construction path ever wraps that as <@id> rather than plain text.

Observed live: asked to ping a user, the bot's message contained the literal text `@vivi_magala` rather than a real Discord mention — it didn't render as a mention and didn't notify the user. The owner had to post the mention by hand (`<@299809459512016897>`) as a workaround. **PR #59** ("daemon: let the conversational agent own @mentions in server channels") is adjacent but does not fix this — per review, it governs *which* bot answers a given `@Thermograph` mention (so the gateway bot and the conversational agent don't both reply), not whether the conversational agent's own *outgoing* messages can construct a real `<@id>` mention. Two different bugs on the same surface. Worth checking whether the conversational agent has access to resolve a display name / username to a Discord user ID before composing a reply that's meant to ping someone, and whether its reply-construction path ever wraps that as `<@id>` rather than plain text.