Weekly Summary of AI topics

[Discourse]

Overview

This week’s AI conversations on Meta centered on making Discourse AI clearer to users and easier to operate at scale. On the product side, there was strong momentum to rename “AI Persona” to the more widely understood “AI Agent” (with translation workflow implications) in Renaming AI Persona → AI Agent and follow-ups like Renaming AI Persona → AI Agent. Admin experience also got attention: sites with AI disabled were still seeing AI dashboards/reports, which was confirmed as a bug and routed into broader reporting work in Don’t show AI reports if AI is not enabled and the related umbrella thread Admin Reporting & Analysis: Incremental Changes.

Operationally, the community dug into cost/performance controls and scaling pain points: Discourse rolled out OpenAI/Azure provider service tiers in Service tiers on Open AI providers, while a large self-hosted instance reported severe load when turning on semantic embeddings search in Enabling AI search crippled my server. There was also continued refinement around AI-assisted UX—especially where AI touches localization and editor UI—in Saving translations by AI-helper as content localization and The title suggester button is placed outside of the title field when editing a translated title.

Finally, AI adjacent ecosystem work continued with MCP tooling: a practical setup guide landed for Codex CLI in Discourse MCP Setup in OpenAI Codex CLI, and was cross-linked back into the canonical announcement thread Discourse MCP is here!.

---

Interesting Topics

• Rename “AI Persona” to “AI Agent” (and handle the translation fallout)
  sam argued that “AI Persona” is confusing while “AI Agent” is broadly understood in Renaming AI Persona → AI Agent, with Falco backing an ASAP change in Renaming AI Persona → AI Agent. Moin raised the practical issue of updating lots of translations and asked about efficient translator workflows in Renaming AI Persona → AI Agent and Renaming AI Persona → AI Agent, while sam pressed for whether the terminology aligns with industry usage across languages in Renaming AI Persona → AI Agent.

• Bug: AI emotion/sentiment reports appear even when AI is disabled (bug, ai-sentiment)
  one1 spotted AI-related reports showing up on the admin dashboard with AI turned off in Don’t show AI reports if AI is not enabled, and sam confirmed it’s a bug in Don’t show AI reports if AI is not enabled. chapoi noted it’s part of a broader “all plugins” reporting visibility issue, and routed follow-up feedback into Admin Reporting & Analysis: Incremental Changes (see also Admin Reporting & Analysis: Incremental Changes).

• OpenAI/Azure provider “service tiers” added (cost vs latency controls) (#Announcements, ai)
  Discourse shipped the ability to pick service tiers (standard/flex/priority) for OpenAI and Azure in Service tiers on Open AI providers, and pointed admins to the core configuration surface in Discourse AI - Large Language Model (LLM) settings page. The announcement also clarified reliability tradeoffs (especially flex) in Service tiers on Open AI providers.

• UX bug: title-suggester star button mispositioned for translated titles (ux, ai-helper, content-localization)
  Moin reported the AI “” title suggester button renders outside the title input when editing a translated title in The title suggester button is placed outside of the title field when editing a translated title, with repro context pointing at translation UI states (example thread: Request for Croatian language).

• Feature idea: let AI Helper save a generated translation into Content Localization (#Feature, ai-helper, dynaloc)
  After using AI Helper to translate older posts, Moin proposed a “save translation” flow right from the helper modal in Saving translations by AI-helper as content localization, suggesting parity with AI Helper’s “explain → add footnote” pattern as precedent in Saving translations by AI-helper as content localization.

• Mobile UX regression around Suggested/Related tabs (AI suggested topics UI) (ux, suggested-topics)
  Falco noticed the tabs disappearing on mobile and asked if it’s related in The underline indicator below the “Suggested” and “Related” tabs. awesomerobot confirmed it is related and pointed to an incoming fix in The underline indicator below the “Suggested” and “Related” tabs.

• Theme component maintenance: AI Gists button compatibility with Modernized Foundation (#Theme-component, ai)
  Lilly refactored a theme component so formatting works with Modernized Foundation while keeping compatibility with the old Foundation theme in Discourse Topic Excerpts & AI Gists Button, tying into the broader theme effort in Modernizing the Foundation theme.

• Performance/scaling: semantic embeddings search triggering high CPU and backlog (Support, ai-search)
  A large instance reported search disruption and sustained CPU spikes after enabling semantic search in Enabling AI search crippled my server. sam explained that long-running embedding jobs can be expected due to external API calls, but that high CPU is surprising and likely tied to DB/resource constraints in Enabling AI search crippled my server. Falco asked for provider and DB details in Enabling AI search crippled my server, while SubStrider shared specs and dataset size (2.5M posts / 250K topics) in Enabling AI search crippled my server. rburkej also requested more “hardware profile” info for planning self-hosting in Enabling AI search crippled my server.

• MCP tooling: Codex CLI setup guide for Discourse MCP (users, mcp)
  pacharanero published a step-by-step guide for using Discourse MCP with OpenAI Codex CLI in Discourse MCP Setup in OpenAI Codex CLI and linked it back into the main announcement thread in Discourse MCP is here!.

• Permissions hardening: Discourse AI bot groups shouldn’t allow “everyone” (bug, ai-bot)
  In the ongoing thread, Moin asked whether the “everyone” group should be disallowed for ai_bot_allowed_groups in Discourse AI does not respect the “everyone” group, and sam agreed it should be removed (noting cleanup work planned) in Discourse AI does not respect the “everyone” group.

---

Activity

• sam drove several core decisions and debugging threads this week: pushing hard on terminology clarity in Renaming AI Persona → AI Agent and aligning language/translation concerns in Renaming AI Persona → AI Agent; confirming the admin dashboard issue in Don’t show AI reports if AI is not enabled; shipping provider tier controls in Service tiers on Open AI providers (with configuration context via Discourse AI - Large Language Model (LLM) settings page); and troubleshooting embeddings performance in Enabling AI search crippled my server. He also backed tightening AI bot group options in Discourse AI does not respect the “everyone” group.

• Moin focused on localization + AI UX polish: raising translation workflow concerns for the proposed rename in Renaming AI Persona → AI Agent and clarifying Crowdin complications in Renaming AI Persona → AI Agent; reporting a translated-title UI glitch in The title suggester button is placed outside of the title field when editing a translated title (with a real-world translation context example in Request for Croatian language); proposing a workflow improvement to persist AI Helper translations in Saving translations by AI-helper as content localization; and suggesting permissions hardening around “everyone” for AI bot allowed groups in Discourse AI does not respect the “everyone” group.

• Falco reinforced product direction and helped triage UX/perf: endorsing the terminology switch in Renaming AI Persona → AI Agent; flagging mobile behavior changes in The underline indicator below the “Suggested” and “Related” tabs; and requesting deeper environment details to diagnose load in Enabling AI search crippled my server.

• one1 raised an admin-facing quality issue: AI sentiment/emotion reports appearing with AI disabled in Don’t show AI reports if AI is not enabled, which helped confirm a bug and consolidate feedback into the broader reporting workstream in Admin Reporting & Analysis: Incremental Changes.

• chapoi provided important context that the reporting visibility issue extends beyond AI to all plugins, and redirected follow-up discussion into the main reporting thread via Don’t show AI reports if AI is not enabled and Admin Reporting & Analysis: Incremental Changes.

• SubStrider shared a concrete scaling report from a large forum, including a clear “semantic search → CPU spike → search disruption” sequence in Enabling AI search crippled my server, and later provided hardware specs and corpus size details for diagnosis in Enabling AI search crippled my server.

• rburkej added a self-hosting perspective by asking for a detailed hardware profile and operational impact notes in Enabling AI search crippled my server, reinforcing that semantic search rollout needs clear sizing guidance.

• pacharanero advanced the MCP ecosystem by publishing a tested Codex CLI setup guide in Discourse MCP Setup in OpenAI Codex CLI and then cross-linking it into the main MCP announcement thread in Discourse MCP is here!.

• Lilly kept AI-adjacent theming healthy by refactoring a component so the AI Gists button formatting works on Modernized Foundation in Discourse Topic Excerpts & AI Gists Button, tying the work to the upstream theme direction in Modernizing the Foundation theme.

• awesomerobot confirmed the mobile tabs disappearance was related to the “Suggested/Related” UI changes and noted a fix was incoming in The underline indicator below the “Suggested” and “Related” tabs.

• NateDhaliwal closed the loop on an AI-assisted tagging annoyance by acknowledging a fix for an error popup in Error popup when suggesting tags in topic already having tags.

• jdc20181 shared progress on automation work that leverages AI-assisted development: porting a Python script into a Discourse plugin to move topics based on triggers (including scheduled automation) in Creating a system to move topics based on given criteria such as a timestamp.

In total (last 7 days): 6 new topics and 25 posts, with the heaviest engagement around naming/UX polish and practical scaling/cost controls for embeddings and OpenAI usage—see Renaming AI Persona → AI Agent, Service tiers on Open AI providers, and Enabling AI search crippled my server.

Thanks for reading, and I’ll see you again next week!