Overview
This week’s AI activity on Meta Discourse centered on making AI-powered localization more accurate and predictable, especially for small-but-important UI surfaces like tags and categories. Moin surfaced several “LLM-without-context” translation failures in AI-generated tag translations do not work perfectly, prompting nat to consider prompt improvements and adding extra grounding context such as tag descriptions (reply), while Falco explored tool-assisted approaches like letting the agent read relevant sources (idea, follow-up). Related “keep translations in sync” feedback also landed as feature requests for category name and category description updates (category names, category descriptions).
On the configuration side, a troubleshooting thread revealed confusion around what kinds of PMs get translated and how the UI communicates that. In Help me troubleshoot why AI is not translating PMs on my site, Moin clarified the current limitation (group PMs vs 1:1 PMs) (details), while Falco proposed a clearer multi-choice setting (proposal) and nat hinted that upcoming “translate these categories” controls could reshape the settings UX (plan).
Finally, there were incremental improvements and ecosystem enhancements: clearer messaging for semantic vs exact search results (search clarification), interest in refining AI persona behaviors to reduce noise (mention-only request), and continued adoption of AI summaries in UI via a theme component (feedback).
Interesting Topics
-
AI tag translations lack product/context grounding (and can get hilariously wrong)
Moin documented how AI translations treat tags as isolated words, leading to incorrect or ambiguous results in AI-generated tag translations do not work perfectly. nat committed to improving prompts (response), and the discussion expanded into “how do we ground tag/category translations?” including feeding tag descriptions (idea), leveraging Crowdin glossary/localization choices (glossary suggestion), and giving the agent the ability to consult existing translations or sources (agent-access idea, code-grounding follow-up). -
PM translation confusion: “100% translated” but nothing happens for 1:1 messages
In Help me troubleshoot why AI is not translating PMs on my site, tobiaseigen found PMs weren’t auto-translating despite the UI implying completion. Moin explained that current settings cover group PMs rather than direct 1:1 PMs (clarification), leading to a UX/settings rethink: Falco proposed replacing a boolean with explicit targets (settings proposal), and nat connected this to upcoming category-scoped translation controls (notes). -
Search results: better messaging for semantic (“AI”) matches vs exact matches
In the resolved support thread Discourse’s search broken? It is returning ‘similar’/‘partial’ matches rather than ‘exact’ matches, awesomerobot added UI messaging to clarify when “AI semantic results” begin, reflecting feedback quoted in-thread (referenced feedback). -
Feature request: auto-update translated category names when the original category is renamed
Moin noticed a renamed category wasn’t reflected in localized category names and requested automatic updates in Automatically update translations of category names when the original is changed (dynaloc, categories, ai). -
Feature request: keep translated category descriptions in sync with the “about” topic banner source
In Automatically update translated category descriptions, Moin highlighted a mismatch where the localized “about topic” translation updated, but the category banner description remained stale—suggesting translation sync should cascade to banner data. -
AI agent/persona noise control: respond only when explicitly @mentioned
saurabhmithal proposed a persona setting to avoid auto-replies when users merely reply to the bot’s posts, in Allow AI Persona/Agent to respond only to @mentions, not to replies to its posts (ai-bot). -
Theme component: “AI summary in topic header” getting positive field feedback
kaktak reported strong results with the component in AI summary in topic header (ai-summarize), signaling ongoing appetite for in-context AI summarization UI. -
“Do we need an official OpenClaw skill?”—workarounds via scoped credentials
In Discourse官方会出个官方的openclaw skill么？, sniper756 concluded they could solve their integration need without a dedicated skill by provisioning a user with specific permissions and securely storing credentials. -
Localization update: translated tags are now live (with a pointer to the main localization feature)
In the older feature thread Tags übersetzen, nat posted an update that tags are now translated, pointing readers to the main localization/translation feature announcement (related feature hub).
Activity
-
Moin drove a deep-dive on translation quality and localization fidelity, starting with real examples of broken tag translations in AI-generated tag translations do not work perfectly and advocating for grounding via existing localization decisions like a Crowdin glossary (glossary angle) and consistent UI terminology (localization vs translation). They also suggested guardrails about where unsupervised MT is most risky (documentation/news concern) and raised two follow-on sync issues for localized categories: Automatically update translations of category names when the original is changed and Automatically update translated category descriptions. In the PM translation thread, they diagnosed the setting mismatch in Help me troubleshoot why AI is not translating PMs on my site.
-
nat acknowledged the tag translation problems and committed to prompt improvements in AI-generated tag translations do not work perfectly, then explored more predictable grounding strategies like passing the tag description to the model (idea). In the PM translation discussion, they pointed to upcoming category-scoped translation controls and suggested the settings UI could be redesigned accordingly (reply). They also posted a status update that tag translation is now live in Tags übersetzen, referencing the broader localization initiative (content localization hub).
-
Falco focused on productizing improvements: in the tag translation thread they proposed giving the agent access to contextual tools (like a read tool) to self-gather context (proposal), endorsed combining approaches (“let’s do both”), and explained how searching existing translation sources could ground terms without loading everything into context (grounding mechanics; see also code reference point). In the PM troubleshooting topic, they proposed replacing a confusing boolean with a multi-target option list in Help me troubleshoot why AI is not translating PMs on my site. (They also referenced checking translation quality on a real example topic: Calendar subscription URLs for external calendar apps.)
-
tobiaseigen reported a real-world admin UX gap where PM translation appears “done” but requires manual per-post translation in Help me troubleshoot why AI is not translating PMs on my site, then highlighted that the UI doesn’t clearly communicate the 1:1 PM limitation (follow-up).
-
jrgong chimed in to emphasize the importance of improved PM/category controls for adoption, calling it a blocker for fully using the feature in Help me troubleshoot why AI is not translating PMs on my site.
-
awesomerobot shipped a small but impactful UX improvement by adding messaging to clearly distinguish semantic AI search results from exact matches in Discourse’s search broken? It is returning ‘similar’/‘partial’ matches rather than ‘exact’ matches, directly responding to feedback captured in-thread (quoted feedback context).
-
saurabhmithal proposed a new control to reduce bot noise by requiring explicit @mentions for AI personas to respond in Allow AI Persona/Agent to respond only to @mentions, not to replies to its posts.
-
kaktak shared positive usage feedback on a summarization UI enhancement in AI summary in topic header (and the component itself is introduced in the topic’s opener: AI summary in topic header).
-
sniper756 closed the loop on an integration question by explaining they didn’t need an official skill after all, using a permission-scoped user credential approach in Discourse官方会出个官方的openclaw skill么？.
Thanks for reading, and I’ll see you again next week! 