סיכום שבועי של נושאי בינה מלאכותית

[Saif (Saif Murtaza)]

Weekly Summary of AI Activity on meta.discourse.org

Period: 2025-10-13 to 2025-10-20

Overview

This week, AI discussions spanned search UX improvements, localization quirks, embeddings configuration, and bug fixes post-upgrade. Administrators and developers delved into making AI search results more discoverable, tweaking Gemini embeddings settings, and resolving errors introduced in the 3.6.0 beta. Community members also explored using Discourse for niche groups, tested local LLM integrations, and reported composer glitches with pasted images. Major themes hit #ai-support, ai-search, Bug, Community, and UX.

“We just deployed a big improvement to the underlying tech that powers semantic search…” — Falco ref
“Many users are still wary of AI so they don’t toggle the switch…” — RBoy ref

Interesting Topics

• Hiding XX results found using AI—enable toggle by default (Support ai ai-search)
  RBoy kicked off the thread by noting that AI search results were hidden by default. NateDhaliwal pointed to existing docs ref, and Falco explained how it now auto-toggles when native results are missing ref. A temporary theme script to force the toggle was also shared ref.

• Falsche Übersetzung, wenn post locale = UI locale (Bug ai dynaloc content-localization)
  Jakob_Naumann reported that English posts were showing up in German after a default-locale change ref. Falco recommended purging and re-creating the localization cache ref.

• Gemini API Embedding Configuration Clarification (Support ai)
  RBoy asked what sequence length maps to in the embedding settings and how to throttle API backfills to avoid 429 errors ref. Falco confirmed sequence length equals the model’s token capacity (2048) and pointed out the hidden ai_embeddings_backfill_batch_size setting ref.

• Exploring Reranking Options for Discourse AI (Support ai)
  In a longer-running thread, Falco rolled out a major semantic search improvement ref, expected to reduce reliance on external rerankers. tpetrov queried support for uploaded RAG documents versus forum topics ref, and Falco confirmed the change covers all embedding use cases ref.

• Would this work for a community of women over 45+ (Community ai)
  bessnlj wondered if Discourse with AI-powered search fits a niche dating/coaching site ref. tobiaseigen clarified that meta.discourse.org is for Discourse hosts but encouraged spinning up a trial for custom use ref and pointed to existing communities for inspiration ref.

• Local Ollama is not working with the Plugin (Support ai)
  Tikkel faced an “Internal Server Error” when Discourse called the Ollama service, despite successful cURL tests ref. Falco asked for container logs ref, and Tikkel confirmed that adjusting DISCOURSE_ALLOWED_INTERNAL_HOSTS syntax to use pipes solved it ref.

• Gemini Embeddings Issue After Discourse Update to 3.6.0 Beta 2 (Support ai)
  Upgrading to 3.6.0.beta2 broke embedding tests for RBoy, who spotted that Gemini’s old embedding-001 model was retired ref. He fixed it by switching to gemini-embedding-001 in the plugin settings ref.

• Embedding error with 3.6.0 beta 2 (Bug ai)
  A related bug, reported by RBoy, showed “invalid input syntax for type halfvec: “[NULL]”” when querying embeddings post-upgrade ref. This points to null-vector handling issues in the new release.

• After sending the image, add this to the beginning of the message: [object InputEvent] (Bug ai)
  kuaza discovered that copy-pasting images into the composer prepends an [object InputEvent] string ref. Uploading via the file selector avoids the glitch, leading to further UX tweaks.

• How to solve discourse ai: No endpoints found that support tool use (Support ai)
  whitewaterdeu saw a 404 “No endpoints found that support tool use” error testing OpenRouter’s qwen3-8b model ref. Disabling native tool integration resolved the issue ref.

Activity

• Falco posted 7 times across:
  Hiding XX results found using AI—enable toggle by default,
  Falsche Übersetzung, wenn post locale = UI locale,
  Gemini API Embedding Configuration Clarification,
  Local Ollama is not working with the Plugin,
  Gemini Embeddings Issue After Discourse Update to 3.6.0 Beta 2,
  Exploring Reranking Options for Discourse AI,
  Exploring Reranking Options for Discourse AI.

• RBoy posted 11 times in:
  Hiding XX results found using AI—enable toggle by default,
  Hiding XX results found using AI—enable toggle by default,
  Gemini API Embedding Configuration Clarification,
  Gemini API Embedding Configuration Clarification,
  Gemini Embeddings Issue After Discourse Update to 3.6.0 Beta 2,
  Gemini Embeddings Issue After Discourse Update to 3.6.0 Beta 2,
  Embedding error with 3.6.0 beta 2.

• tobiaseigen guided new users in:
  Would this work for a community of women over 45+,
  Would this work for a community of women over 45+.

• Tikkel debugged Ollama integration with 3 posts:
  Local Ollama is not working with the Plugin,
  Local Ollama is not working with the Plugin,
  Local Ollama is not working with the Plugin.

• whitewaterdeu resolved model routing in:
  How to solve discourse ai : No endpoints found that support tool use,
  How to solve discourse ai : No endpoints found that support tool use.

• bessnlj explored community use with 3 posts in:
  Would this work for a community of women over 45+,
  Would this work for a community of women over 45+,
  Would this work for a community of women over 45+.

• tpetrov inquired about RAG support in:
  Exploring Reranking Options for Discourse AI.

• dennisjbr voiced interest in tiered AI access in:
  Discourse AI.

• Jakob_Naumann reported locale mismatches in:
  Falsche Übersetzung, wenn post locale = UI locale.

• NateDhaliwal added context on AI search toggles in:
  Hiding XX results found using AI—enable toggle by default,
  Hiding XX results found using AI—enable toggle by default.

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

[Saif (Saif Murtaza)]

Weekly AI Activity Summary: 2025-10-20 → 2025-10-27

---

Overview

This week’s ai discussions on Meta spanned API troubleshooting, content localization, user feedback on translations, and plugin bug fixes.

In the Support category, Enit kicked off a deep dive by encountering a 400 Bad Request Using API error when trying to create a topic via the REST API. supermathie pointed them to the Discourse REST API documentation and requested authentication details ref. Moin then asked for log excerpts ref and clarified whether this was purely an API issue or tied to the AI plugin ref. Ultimately, the mystery was solved when the proper logs surfaced under /logs ref.

On the #Site Management front, the Content Localization - Manual and Automatic with Discourse AI discussion saw cmdntd propose making the tl URL parameter available to all users, not just guests ref. Falco clarified that it currently applies globally across the site ref. wenqin then tested the feature and suggested a “default (no translation)” option for multilingual learners ref, and Moin helped locate the toggle for viewing original content ref. Wenqin confirmed the solution worked perfectly ref.

Community feedback in Community’s Multilingual user feedback on Automatic Translations continued, with FINDarkside calling for per-language translation preferences. A Support query titled 我已关闭Discobot，但它仍然运行 turned out to be about AI Search Discoveries, which NateDhaliwal clarified can be toggled in user preferences ref.

On the plugin side, performance tweaks and bug reports moved forward. In Discourse AI Failing to translate large number of posts and topics, DevTeVe improved throughput by disabling streaming. Meanwhile, the Embedding error with 3.6.0 beta 2 was traced to a ProblemChecks bug and patched by Falco ref. A feature request—Hiding XX results found using AI - enable toggle by default—was moved to Feature for broader discussion.

---

Interesting Topics

• 400 Bad Request Using API (Support rest-api ai): Enit’s API call returned 400 Bad Request, leading supermathie and Moin through authentication checks, log diagnostics, and plugin context clarifications.
• Content Localization - Manual and Automatic with Discourse AI (#Site Management ai content-localization): cmdntd and Falco debated exposing ?tl= to all users, wenqin requested a “no translation” default, and Moin uncovered the timeline toggle.
• Multilingual user feedback on Automatic Translations (Community ai dynaloc content-localization): FINDarkside aggregated user requests for per-language translation preferences and opt-out controls.
• 我已关闭Discobot，但它仍然运行 (Support ai): A misidentified Discobot issue was resolved when NateDhaliwal explained it was the AI Search Discoveries feature, toggleable in preferences.
• Discourse AI Failing to translate large number of posts and topics (Support ai content-localization): DevTeVe boosted translation reliability by disabling streaming calls.
• Discourse AI - Sentiment (#Site Management ai ai-sentiment content): keegan inquired about adjusting the sentiment threshold, only to learn it’s fixed in code.
• Hiding XX results found using AI - enable toggle by default (Feature ai ai-search): tobiaseigen suggested the AI-results-hide toggle ship enabled by default for a cleaner UI.
• Embedding error with 3.6.0 beta 2 (Bug ai): sam and RBoy reported rate-limit spikes and embedding failures; Falco disabled ProblemChecks and issued a patch ref.

---

Activity

• Enit: spearheaded the API deep dive with five posts—initial report ref, plugin context clarification ref, log details ref, solution confirmation ref, and broader AI memory discussion ref.
• supermathie: provided API documentation guidance ref.
• Moin: probed logs ref, clarified plugin scope ref, guided log access ref, and assisted with localization toggles ref.
• NateDhaliwal: translated language support insights ref and AI Discoveries settings help ref.
• wenqin: tested localized views ref and praised the toggle UX ref.
• Falco: explained global locale behavior ref and fixed the embedding bug ref.
• FINDarkside: contributed critical feedback on user-controlled translations ref.
• Jagster: highlighted language support limitations ref.
• keegan: asked about sentiment thresholds ref.
• DevTeVe: optimized translation throughput by disabling streaming ref.

---

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

[Saif (Saif Murtaza)]

Weekly AI Activity Summary: 2025-10-27 to 2025-11-03

Overview

This week on meta.discourse.org saw vibrant discussions across ai, content-localization, Feature, and Support. From multilingual translation preferences and concerns over undisclosed auto-translation, to hidden configuration settings and feature requests for AI-powered formatting, the community dove deep into how Discourse AI can be more flexible and transparent. Contributors also tackled LLM errors, debated structured output requirements, sought cost estimates for AI features, and explored token limits for embeddings. Overall, the focus remained on improving user control, enhancing reliability, and broadening provider support.

Interesting Topics

• Multilingual user feedback on Automatic Translations (ai content-localization Community)
  MiikkaLaitila asked about supporting multiple language preferences in Multilingual user feedback on Automatic Translations, and Moin pointed to the existing multi-language preferences feature request.

• Highly intrusive and undisclosed Auto-Translation (translation content-localization UX)
  Ethaphu flagged that every post on Roblox Devforum was auto-translated without clear indicators in Highly intrusive and undisclosed Auto-Translation. Falco explained translation indicators in post 3, tobiaseigen agreed that signaling needs work in post 4, and nat investigated Roblox’s self-hosting limits in post 5.

• How to configure ai translate of Ai translation backfill hourly rate? (ai Support)
  whitewaterdeu struggled with missing settings in How to configure ai translate of Ai translation backfill hourly rate, NateDhaliwal shared the guide in post 2, the solution was revealed as a hidden setting by Moin in post 4, and Falco noted it can now be unhidden in post 6.

• Button to format post content using AI (ai Feature)
  hameedacpa requested an AI formatting button in Button to format post content using AI. NateDhaliwal pointed to the existing Discourse AI Helper and later demonstrated a custom prompt in post 6.

• An error occurred: Default llm Default LLM model is required prior to enabling Chat (ai Support)
  viswanatha encountered a reset error in An error occurred: Default llm…, and NateDhaliwal linked to the existing thread in post 2 before it was resolved.

• I think discourse-ai API needs a regression (ai Dev)
  MoRanYue proposed dropping structured output for broader provider support in I think discourse-ai API needs a regression. Falco explained why structured output matters in post 2, and MoRanYue offered XML-like separators as an alternative in post 3.

• Exploring Reranking Options for Discourse AI (ai Support)
  tpetrov tested new embeddings in Exploring Reranking Options for Discourse AI, with Falco following up on model availability in post 15.

• Warning of embedding input must have less than 8192 tokens with discourse ai (ai Support)
  whitewaterdeu hit token limits in Warning of embedding…, Falco explained provider rules in post 2, and the discussion continued through post 6.

• Support for AI Bot to Configure for a Support the community forum… (ai Support)
  viswanatha shared LLM and persona setups in Support for AI Bot to Configure…, Falco suggested tool-forced searches in post 2, and model recommendations followed in post 4.

• Estimating cost of enabling Discourse AI for related content and search (ai Support)
  SubStrider asked about cost benchmarks in Estimating cost of enabling Discourse AI…, NateDhaliwal clarified search vs. LLM in post 2, and Falco outlined self-host options in post 3.

Activity

• Falco led technical clarifications, from translation indicators in Highly intrusive and undisclosed Auto-Translation and hidden settings in Ai translation backfill hourly rate to structured-output rationale in API regression discussion, embedding advice in token limit warning, and cost breakdowns in Estimating cost….

• Moin surfaced existing solutions and answered support queries: pointing to multi-language preferences in Automatic Translations and revealing hidden settings in Ai translation backfill hourly rate.

• NateDhaliwal provided guides and prompts, linking to content localization docs for Automatic Translations, answering backfill setup in Ai translation backfill hourly rate, and SEO-friendly AI formatting tips in Formatting button request.

• whitewaterdeu tested features and raised bugs across multiple threads, from translation backfill in Ai translation backfill hourly rate to embedding errors in token limit warning and translation exceptions in Error when translate post by ai.

• hameedacpa championed formatting enhancements in Button to format post content using AI and iterated on desired output in post 5.

• viswanatha shared AI Bot setup details in Support for AI Bot to Configure… and reported reset errors in Default llm model error.

• MoRanYue pushed for API flexibility in API regression discussion and suggested parsing alternatives in post 3.

• MiikkaLaitila spotlighted multilingual needs in Automatic Translations feedback.

• nat investigated external implementations in Automatic Translations UX.

• Ethaphu highlighted UX gaps in undisclosed auto-translation.

• tpetrov tested embeddings in Exploring Reranking Options.

• SubStrider initiated the cost discussion in Estimating cost….

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

[Saif (Saif Murtaza)]

Overview

Over the past week, the community dove into several translation and rate-limit challenges, as well as fresh plugin releases and AI helper configuration issues. Key themes included:

• Content Localization Troubleshooting: Multiple threads tackled backfill misconfigurations and max-age overrides for automated translations, with detailed debugging of rate-limit math and backfill settings (AI translation backfill misconfiguration, Staff override for translation max age, Missing language switcher).
• AI Persona Stability: Reports of the AI bot entering infinite loops and spamming highlighted the need to calibrate LLM temperature parameters (AI bot infinite loop and spamming).
• Plugin Spotlight: The new llms.txt generator plugin promises to make forum content discoverable by LLMs (Discourse llms.txt Generator Plugin).
• AI Helper & LLM Settings: Several users couldn’t find or reset AI helper menus and default LLM dropdowns, especially in localized installs, prompting pointers to enable core settings and rebuild plugins (Resetting Proofreader settings, LLM and AI settings hidden, Default LLM model dropdown empty).
• Rate Limits & Budget Errors: Discussions surfaced around Gemini Pro’s thinking budget constraints and cost-input minimums, uncovering unexpected validation errors in both free and paid tiers (Gemini Pro thinking budget error, AI model cost input restriction).

Below are the 10 most interesting topics from the week, followed by a breakdown of who said what.

---

Interesting Topics

• AI translation backfill misconfiguration (Support ai content-localization)
  In AI translation backfill not working after all settings configured, RBoy initially thanked nat for enabling backfill but encountered a “limit” exception in the logs, which nat traced to integer rounding in post 25.

• AI bot infinite loop and spamming (Support ai-bot)
  wisewords reported that after creating a new persona the AI began delaying responses and posting repetitive spam in AI bugging out, having a mental breakdown, and Falco explained it was due to the LLM hitting an infinite generation loop at certain temperature settings in post 2.

• Staff override for translation max age (Feature translation ai content-localization)
  jrgong requested the ability for staff to bypass the AI translation backfill max age days setting when manually translating older posts in post 1, and Falco tested and confirmed the manual translation button already overrides this backfill restriction in post 3.

• Discourse llms.txt Generator Plugin released (Plugin ai)
  kaktak introduced the Discourse llms.txt Generator Plugin in post 1, which automates the generation of llms.txt files to improve forum discoverability by LLMs.

• Resetting Proofreader settings (Support ai-helper)
  bksubhuti sought guidance on restoring missing Proofreader options in the AI helper menu in post 1, and Moin and OP resolved it by rebuilding after correcting trust level configurations in post 4.

• Missing language switcher after auto-translation (Support ai content-localization)
  After successfully backfilling translations, EasyChen could not see the language switcher on translated posts in post 1, with nat guiding them through enabling the site setting and checking post locale detection in post 2 and post 7.

• LLM and Discourse AI settings hidden (Support ai)
  Nima1 reported missing LLM tabs in the AI plugin on a Persian-locale site in post 1, and nat clarified that the “Discourse AI enabled” setting must be saved first to reveal the rest in post 2.

• Default LLM model dropdown empty (Support ai)
  undasein was unable to select a default model due to an empty dropdown in post 1, and NateDhaliwal pointed them to configure LLMs under “Plugins > AI > LLMs” in post 2.

• Gemini Pro thinking budget error (Bug ai)
  RBoy encountered a “Budget 0 is invalid” error when setting a zero or negative budget for the gemini-pro-latest model in post 1, and the team acknowledged they will investigate in post 2.

• AI model cost input restriction (Bug ai)
  RBoy noted that the cost fields for AI model input and output prevent values below 0.1 in Can’t enter AI model cost of less than 0.1, overriding entries like 0.075 back to zero.

---

Activity

• Falco weighed in on AI translation backfill not working after all settings configured, AI bugging out, having a mental breakdown, and Staff should be able to override/ignore “AI translation backfill max age days” setting (also chipped in at post 4), as well as advising on Support for AI Bot to Configure for a Support the community forum.

• nat was highly active, troubleshooting rate-limit errors on the backfill job in post 25, post 27, post 29, and clarifying paid vs free tiers in post 33, post 38, and post 40. nat also guided the override behavior for manual translations in post 3 and supported others in post 2, post 5, post 7, as well as revealing the AI tab reveal trick in Can’t find Discourse AI and LLM settings.

• kaktak unveiled the new Discourse llms.txt Generator Plugin.

• Moin helped bksubhuti reset their Proofreader settings in How to reset Proofreader settings.

• manuel closed the AI helper menu hiding issue on Android tablets by merging a fix in post 17.

• EasyChen investigated missing language switchers in post 1, post 3, and post 4.

• wisewords kicked off the week’s discussions by reporting the AI persona loop behavior in AI bugging out, having a mental breakdown.

• undasein tested LLM settings and learned to configure them under Plugins > AI > LLMs, with help in Can’t choose default LLM model and post 3.

• RBoy posted extensively on backfill rate limits in post 24, post 26, post 28, post 32, post 34, and post 35, raised cost-limit bugs in Can’t enter AI model cost of less than 0.1, and reported budget errors in Thinking budget for Gemini Pro.

• jrgong initiated the staff override feature request in post 1 and suggested enhanced logging in post 5.

• Nima1 sought help finding AI settings on a Persian-locale site in Can’t find Discourse AI and LLM settings.

• sam acknowledged the budget error report for Gemini Pro in post 2.

• NateDhaliwal resolved the default LLM dropdown issue for undasein in post 2.

• bksubhuti kicked off the Proofreader reset thread and later confirmed a rebuild fix in post 1 and post 4.

• tobiaseigen followed up on an embedding error in Error when translate post by ai.

• viswanatha updated their configuration steps after guidance on AI persona tooling in Support for AI Bot to Configure for a Support the community forum.

---

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

[Saif (Saif Murtaza)]

Weekly AI Activity Summary (2025-11-17 to 2025-11-24)

Overview

In the past week, the ai and ai-bot space on meta.discourse.org saw 36 new posts across 5 new topics, tackling integration errors, spam filtering, plugin flexibility, and content formatting. Highlights include:

• A critical 400 error in Google gemini-3-api helper API response error reported by honeymoose and quickly addressed by sam.
• Deployment and customization of the spam-detection persona in Frustrations on AI spam detector, resolved with insights from nat, NateDhaliwal, and lilydjwg.
• Exploration of provider-agnostic and self-hosted models in Inquiry About AI Plugin Options led by beitmenotyou.
• A disclosure bug exposing hidden tags in summaries in AI Summary leaking hidden tags highlighted by tvavrda.
• Clarity sought on model usage breakdown in Usage not showing LLM models thanks to feedback from RBoy.
• Ongoing feature discussions around custom personas in the composer (Button to format post content using AI) and content-generation plugins ( Discourse llms.txt Generator Plugin).
• An announcement of new image model support in Gemini Flash 2.5 Image - now on Discourse.
• Re-engagement in long-running guides such as PDF support in Discourse AI and the Discourse AI – Large Language Model (LLM) settings page.

Top contributors this week were sam, Falco, lilydjwg, and NateDhaliwal.

---

Interesting Topics

• Google gemini-3-api helper API response error Bug ai ai-bot
  honeymoose discovered a missing thought_signature error in Gemini’s helper calls; sam implemented a fix within days.

• Frustrations on AI spam detector Support ai spam
  lilydjwg grappled with persona prompts and tokenizers; nat provided a working setup and final solution.

• Inquiry About AI Plugin Options Support ai
  beitmenotyou asked about using local LLMs (e.g., Ollama), with Falco and sam showcasing the plugin’s provider-agnostic design and free-model tips.

• AI Summary leaking hidden tags Bug ai
  tvavrda noticed that AI-generated summaries exposed private tags; the issue was triaged for a quick correction.

• Usage not showing LLM models Bug ai
  RBoy reported that the Usage tab lists raw model IDs instead of configured LLM names; sam acknowledged the request for clearer breakdowns.

• Button to format post content using AI Feature ai
  jrgong and community members floated ideas for custom composer personas and formatting templates.

• Gemini Flash 2.5 Image - now on Discourse Announcements ai
  sam introduced Nano Banana 3 image support; NateDhaliwal praised its quality improvements.

• Discourse llms.txt Generator Plugin Plugin ai
  Ivan_Rapekas shared initial tests of the llms.txt generator and requested mind-map formatting.

• PDF support in Discourse AI #Site Management how-to ai
  kuaza asked about embedding and processing PDFs, exploring which models handle attachments best.

• Discourse AI – Large Language Model (LLM) settings page #Site Management how-to ai
  beitmenotyou revisited missing LLM tabs and sought clarity on the configuration interface.

---

Activity

• honeymoose opened Google gemini-3-api helper API response error.
• sam commented on Google gemini-3-api helper API response error, Usage not showing LLM models, and Inquiry About AI Plugin Options.
• Falco chimed in on Google gemini-3-api helper API response error, Inquiry About AI Plugin Options, and Button to format post content using AI.
• lilydjwg led the conversation in Frustrations on AI spam detector, posted follow-ups in Frustrations on AI spam detector, Frustrations on AI spam detector, Frustrations on AI spam detector, and Frustrations on AI spam detector.
• nat provided guidance in Frustrations on AI spam detector and posted the solution.
• NateDhaliwal answered in Frustrations on AI spam detector, and offered insights on Inquiry About AI Plugin Options and Inquiry About AI Plugin Options.
• tvavrda reported the summary bug in AI Summary leaking hidden tags.
• tobiaseigen supported the bug report in AI Summary leaking hidden tags.
• jrgong discussed custom personas in Button to format post content using AI and Button to format post content using AI.
• merefield added perspective in Button to format post content using AI.
• beitmenotyou asked about hosting in Inquiry About AI Plugin Options and revisited settings in Discourse AI – Large Language Model (LLM) settings page.
• RBoy filed the usage-metrics issue in Usage not showing LLM models.
• kuaza checked PDF handling in PDF support in Discourse AI.
• Ivan_Rapekas tested the generator in Discourse llms.txt Generator Plugin.
• viswanatha shared screenshots in Support for AI Bot to Configure for a Support the community forum.
• Nima1 confirmed the fix in Can’t find Discourse AI and LLM settings.

---

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

[Saif (Saif Murtaza)]

Overview

This past week on #discourse-ai saw a mix of new feature rollouts, in-depth configuration guides, localization debates, and crucial bug reports. keegan unveiled Improved Image Generation Support in Discourse AI, making it effortless to hook up OpenAI, Google Gemini, Flux, or custom providers for on-the-fly images. Hosting admins explored credit management options in Running Out of AI credits? as Discourse explained plan upgrades and fallback paths. Translators hashed out formality levels in KI Übersetzungen (formal, informal), while broader localization topics bubbled up in Content Localization - Manual and Automatic with Discourse AI. Support questions ranged from third-party proxy setups in Does Discourse AI support third-party relay/proxy APIs (e.g., NewAPI)? to multisite PM bot regressions in AI Bot PM replies stopped working on one multisite instance. Community members also prototyped automations in AI Triaging & persona and pitched UX enhancements in AI supporting Micro-Features. Finally, key bugs like AI is being cutoff before it finishes writing and Search/Read Private not working for a Persona-driven RAG search on forums? kept everyone on their toes, with Chinese-language troubleshooting captured in 有关ai的问题.

Interesting Topics

• keegan announced Improved Image Generation Support in Discourse AI (Announcements ai ai-helper), introducing a streamlined interface for configuring AI-powered image creation with presets for OpenAI’s GPT-Image 1, Google Gemini Nano Banana, Flux 1.1 Pro, Flux 2 Pro, or custom providers.

• Discourse explained what happens when you Run Out of AI credits (#Hosted_Customers explanation ai), detailing daily credit allotments, plan upgrade paths, and how to connect your own LLM to avoid service interruptions.

• asa kicked off KI Übersetzungen (formal, informal) (Feature ai content-localization), asking if German translations should default to formal “Sie” or informal “Du,” and Falco walked through creating a custom translation persona to suit a “per Du” community.

• DevTeVe reported that the AI is being cutoff before it finishes writing (Bug ai), sharing logs that show complete responses but a UI truncation issue, and sam traced a potential fix landed mid-week.

• tom_eric asked whether Discourse AI supports OpenAI-compatible third-party proxies like NewAPI in third-party relay/proxy APIs (e.g., NewAPI)? (Support ai), and whitewaterdeu demonstrated configuring custom LLM endpoints and personas to resolve 500-level errors.

• Akunna_Ndubuisi experimented with AI Triaging & persona (Support automation ai) to auto-categorize misfiled posts, with NateDhaliwal and RGJ guiding through triggers, logs, and a data explorer query to inspect AI audit records.

• Neil_Evans uncovered a private search issue in Search/Read Private not working for a Persona-driven RAG search on forums? (Bug ai), finding that read/search permissions must align between the user and persona, and testing parent vs. subcategory settings.

• Naman_Gala reported that on one multisite instance the AI chat icon spawns a normal topic instead of a PM in AI Bot PM replies stopped working on one multisite instance (Support chat ai), noting missing AI custom fields and seeking diagnostics on why it regressed.

• iamcapote proposed AI supporting Micro-Features (Feature ai), advocating for per-persona auto-greetings, internal system notes, and richer AI menu metadata (display names, tooltips, docs links) to make each persona self-explanatory.

• 派蒙pm from the Chinese community shared screenshots and 502 errors in 有关ai的问题 (Support ai), asking for help troubleshooting AI connectivity, and offering to provide logs or configs for deeper analysis.

Activity

• keegan (1 post, 11 likes) authored the rollout in Improved Image Generation Support in Discourse AI.

• Discourse (1 post, 5 likes) detailed credit management in Running Out of AI credits?.

• Falco (4 posts, 4 likes) weighed in on KI Übersetzungen (formal, informal), Does Discourse AI support third-party relay/proxy APIs (e.g., NewAPI)?, Search/Read Private not working for a Persona-driven RAG search on forums?, and offered guidance on Support for AI Bot to Configure for a Support the community forum with latest version of Discourse.

• DevTeVe (4 posts, 3 likes) documented and tested UI truncation issues in AI is being cutoff before it finishes writing.

• sam (5 posts, 2 likes) proposed fixes and shared commit references in AI is being cutoff before it finishes writing and offered firewall and proxy advice in API works manually, but AI (Grok/xAI) does not reach VPS.

• whitewaterdeu (4 posts, 2 likes) demonstrated proxy setup in Does Discourse AI support third-party relay/proxy APIs (e.g., NewAPI)? and pinpointed a locale detector mis-persona in Error when translate post by ai （Job exception: undefined method `strip’ for an instance of DiscourseAi::Completions::StructuredOutput).

• asa (1 post, 1 like) flagged translation tone concerns in KI Übersetzungen (formal, informal).

• pmusaraj (1 post, 1 like) confirmed that group titles can’t yet be localized in Content Localization - Manual and Automatic with Discourse AI.

• RGJ (1 post, 1 like) shared a Data Explorer query in AI Triaging & persona.

• 派蒙pm (2 posts, 0 likes) supplied error logs for Chinese AI issues in 有关ai的问题.

• Akunna_Ndubuisi (2 posts) tested automations in AI Triaging & persona.

• NateDhaliwal (1 post) clarified triggers and log expectations in AI Triaging & persona.

• tom_eric (1 post) evaluated third-party proxy support in Does Discourse AI support third-party relay/proxy APIs (e.g., NewAPI)?.

• Neil_Evans (4 posts) debugged private search scopes in Search/Read Private not working for a Persona-driven RAG search on forums?.

• iamcapote (1 post) sketched out micro-feature requirements in AI supporting Micro-Features.

• Naman_Gala (1 post) described PM bot regression details in AI Bot PM replies stopped working on one multisite instance.

• viswanatha (1 post) requested a review in Support for AI Bot to Configure for a Support the community forum with latest version of Discourse.

• typed-sigterm (1 post) inquired about group localization in Content Localization - Manual and Automatic with Discourse AI.

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

[Discourse]

Overview

This week in the ai category saw a blend of bug investigations, support troubleshooting, and feature evolution. Contributors collaborated to:

• Resolve private content retrieval in persona-driven RAG searches (Search/Read Private not working for a Persona-driven RAG search on forums?)
• Patch cost and content-management edge cases—unlocking sub-0.1 model costs (Can’t enter AI model cost of less than 0.1) and sealing hidden-tag leaks in summaries (AI Summary leaking hidden tags)
• Enhance plugin capabilities with PDF ingestion (PDF support in Discourse AI), improved image generation support (I’m having problems with AI image generation …), and removal of legacy rake tasks (Rake tasks in the AI plugin not working)
• Address support queries—from AI bot instabilities (Discourse ai bot not working) to localization gaps in email notifications (Email notifications ignore AI-translated content)
• Advance key feature requests such as usage tracking per persona (Track usage per persona)

“If your AI is getting cutoff before writing everything, and you happen to be using AI Gateway from Cloudflare, the first step is to query the model API directly!”
— DevTeVe (post 8)

---

Interesting Topics

• sam noticed that a persona-driven RAG search fails to return private content when using the main site search, Neil_Evans provided detailed logs to narrow down the issue, and Falco implemented a fix to pass the authenticated user to the search assistant (post 6, post 8, post 15)

• RBoy proposed the ability to track usage per persona—including counts and resource consumption—for system optimization, and sam agreed this would require extending the stats table to include persona IDs (post 1, post 2)

• pierregilles discovered that email notifications still use the original language when AI translation is enabled, resulting in mixed-language messages, and Moin pointed to an existing feature request for translated-post emails (post 1, post 2)

• Shin_210 reported that the Discourse AI bot refuses to respond in the chat interface despite correct LLM configuration, sam suggested toggling the Responses API and updating the endpoint, and after an upgrade, the issue was resolved (post 1, post 4, post 24)

• sam merged a PDF ingestion solution into the Discourse AI plugin, enabling forum content to be indexed directly from PDFs; users can preview the upcoming release via the linked PR (PR 36415, post 22)

• DevTeVe uncovered a bot context exception when using the Discord Persona Bot integration, filed a PR to enforce the correct BotContext, and Yuuki_Mizukami inquired about support for new LLMs like DeepSeek, with Falco confirming existing compatibility (post 243, post 245)

• Falco addressed a 403 error from the Stability.ai generator by linking to the improved image-generation support discussion, guiding users to the updated integration in the Discourse AI plugin (post 5)

• Falco fixed an issue preventing entry of model costs below 0.1 by adjusting the input validation logic in the AI settings page (post 2)

• Falco patched a bug where hidden tags were inadvertently exposed in AI-generated summaries, ensuring tag-level privacy is maintained (post 5)

• DevTeVe traced incomplete AI responses to Cloudflare’s AI Gateway and confirmed that bypassing the gateway restored full outputs, popularizing a workaround for similar outages (post 8, post 9)

---

Activity

• Falco: Investigated the Persona-driven RAG search issue in Search/Read Private not working for a Persona-driven RAG search on forums? and implemented a fix (post 15); submitted cost-threshold bugfix in Can’t enter AI model cost of less than 0.1; patched hidden-tag leaks in AI Summary leaking hidden tags; enhanced image generation support in I’m having problems with AI image generation …; removed legacy rake tasks in Rake tasks in the AI plugin not working; responded on AI bot configuration in Support for AI Bot to Configure for a Support the community forum with latest version of Discourse; provided LLM support guidance in Discourse AI

• sam: Provided debugging guidance for persona-driven RAG search in Search/Read Private not working for a Persona-driven RAG search on forums?; iterated on AI bot tests and settings in Discourse ai bot not working; championed the usage-per-persona feature in Track usage per persona; contributed to PDF support rollout in PDF support in Discourse AI

• pierregilles: Raised the email-localization issue in Email notifications ignore AI-translated content

• Moin: Pointed to an existing feature request for content localization in Email notifications ignore AI-translated content

• RBoy: Proposed persona usage tracking in Track usage per persona

• Neil_Evans: Explored the RAG search private-content quirk, sharing logs and tests in Search/Read Private not working for a Persona-driven RAG search on forums? and post 8

• DevTeVe: Identified the AI Gateway cutoff issue in AI is being cutoff before it finishes writing and confirmed its resolution (post 9); unearthed the Discord Persona Bot context bug in Discourse AI

• NateDhaliwal: Assisted with log diagnostics for the AI bot setup in Discourse ai bot not working

• Shin_210: Reported and debugged AI bot configuration issues in Discourse ai bot not working, ultimately resolving them by upgrading Discourse (post 24)

• rawatkritika: Asked about cost management and free-access strategies in Managing consumable AI costs

---

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

[Discourse]

## Overview

Over the past week, the Discourse AI plugin saw significant enhancements, bug fixes, and community support discussions. Hosted customers can now use an in-house, open-weights LLM at no extra cost thanks to <a class="mention" href="/u/keegan">keegan</a>’s announcement in [Unlock All Discourse AI Features with Our Hosted LLM](https://meta.discourse.org/t/-/390985/1?silent=true) #Announcements #ai. We also shipped **native PDF and document attachment support**—announced in [Native PDF and attachment support in Discourse AI](https://meta.discourse.org/t/-/391007/1?silent=true) and explained in [Using PDF and attachment support with AI bots](https://meta.discourse.org/t/-/391005/1?silent=true) #Site Management #how-to. Several bugs were triaged and resolved: preference toggling in [Toggling the "AI search discoveries" preference doesn't work](https://meta.discourse.org/t/-/391135/1?silent=true) #Bug, a 400 error in AI bot requests fixed after [Ai bot 400 error on 2025.12.0-latest](https://meta.discourse.org/t/-/390794/1?silent=true) #Bug, missing moderator sentiment pages addressed in [Missing sentiment pages for moderators](https://meta.discourse.org/t/-/391033/1?silent=true) #Bug, and a UI glitch on the LLM Usage page corrected as tracked in [Minor UI bug in LLM Usage page](https://meta.discourse.org/t/-/391273/1?silent=true) #UX. Finally, the community dug into advanced topics like third-party model image support in [Qwen3-VL-8b Image Recognition Issues and Gemma3-27b Mixed Text Image Content](https://meta.discourse.org/t/-/391017/1?silent=true) #Support and custom tokenizers in [How to use AI models with custom tokenizers](https://meta.discourse.org/t/-/391238/1?silent=true) #Support, while <a class="mention" href="/u/RGJ">RGJ</a> revived a permissions bug in [Discourse AI does not respect the "everyone" group](https://meta.discourse.org/t/-/292048/5?silent=true) #Bug.

---

## Interesting Topics

- **Hosted, open-weights LLM for all tiers**  
  <a class="mention" href="/u/keegan">keegan</a> unveiled the “CDCK Hosted Small LLM” enabling Starter through Enterprise customers to access every Discourse AI feature without third-party dependencies in [Unlock All Discourse AI Features with Our Hosted LLM](https://meta.discourse.org/t/-/390985/1?silent=true). <a class="mention" href="/u/mcmcclur">mcmcclur</a> inquired about API access in post [2](https://meta.discourse.org/t/-/390985/2?silent=true), and <a class="mention" href="/u/Falco">Falco</a> confirmed it won’t be offered for self-hosters in post [3](https://meta.discourse.org/t/-/390985/3?silent=true). #Announcements #ai

- **Native PDF & attachment support for AI bots**  
  <a class="mention" href="/u/sam">sam</a> delivered the long-awaited ability to upload PDFs and other documents in AI conversations in [Native PDF and attachment support in Discourse AI](https://meta.discourse.org/t/-/391007/1?silent=true), with detailed configuration in [Using PDF and attachment support with AI bots](https://meta.discourse.org/t/-/391005/1?silent=true). #ai #how-to

- **“AI search discoveries” preference toggle bug**  
  <a class="mention" href="/u/Moin">Moin</a> reported that changing the **AI search discoveries** setting didn’t stick in [Toggling the "AI search discoveries" preference doesn't work](https://meta.discourse.org/t/-/391135/1?silent=true). Core maintainer <a class="mention" href="/u/zogstrip">zogstrip</a> proposed a PR with a new `valueTransformer` in post [7](https://meta.discourse.org/t/-/391135/7?silent=true), incorporating feedback from <a class="mention" href="/u/david">david</a> in post [6](https://meta.discourse.org/t/-/391135/6?silent=true). #Bug

- **AI bot 400 error after 2025.12.0 update**  
  <a class="mention" href="/u/MachineScholar">MachineScholar</a> discovered that every AI bot request returned a `400 Unknown parameter` error in [Ai bot 400 error on 2025.12.0-latest](https://meta.discourse.org/t/-/390794/1?silent=true). <a class="mention" href="/u/Falco">Falco</a> noted recent refactors in post [2](https://meta.discourse.org/t/-/390794/2?silent=true), and <a class="mention" href="/u/sam">sam</a> issued a fix (PR 36572) in post [6](https://meta.discourse.org/t/-/390794/6?silent=true), confirmed resolved by post [8](https://meta.discourse.org/t/-/390794/8?silent=true). #Bug #ai-bot

- **Missing sentiment pages for moderators**  
  <a class="mention" href="/u/putty">putty</a> noted that moderators couldn’t see sentiment reports in the sidebar in [Missing sentiment pages for moderators](https://meta.discourse.org/t/-/391033/1?silent=true). <a class="mention" href="/u/awesomerobot">awesomerobot</a> quickly merged a sidebar fix in post [2](https://meta.discourse.org/t/-/391033/2?silent=true). #ai-sentiment #Bug

- **Minor UI glitch on LLM Usage page**  
  <a class="mention" href="/u/RBoy">RBoy</a> spotted that new LLMs show up unnamed under `llm_validator` in [Minor UI bug in LLM Usage page](https://meta.discourse.org/t/-/391273/1?silent=true). <a class="mention" href="/u/zogstrip">zogstrip</a> confirmed PR 36694 will correct the dropdown in post [2](https://meta.discourse.org/t/-/391273/2?silent=true). #UX #pr-welcome

- **Qwen3-VL-8b image recognition limitations**  
  <a class="mention" href="/u/Ivan_Rapekas">Ivan_Rapekas</a> explored how non-Anthropic/OpenAI/Google models handle images in [Qwen3-VL-8b Image Recognition Issues and Gemma3-27b Mixed Text Image Content](https://meta.discourse.org/t/-/391017/1?silent=true). <a class="mention" href="/u/sam">sam</a> clarified that LMStudio lacks PDF support in post [2](https://meta.discourse.org/t/-/391017/2?silent=true), with a follow-up comment from Ivan marking it solved in post [3](https://meta.discourse.org/t/-/391017/3?silent=true). #ai #Support

- **Custom tokenizer configuration**  
  <a class="mention" href="/u/RBoy">RBoy</a> asked whether Discourse AI can use a custom tokenizer for moonshotai/Kimi-K2-Instruct in [How to use AI models with custom tokenizers](https://meta.discourse.org/t/-/391238/1?silent=true). <a class="mention" href="/u/Falco">Falco</a> recommended choosing the closest built-in tokenizer and adjusting the context window in post [2](https://meta.discourse.org/t/-/391238/2?silent=true). #Support #ai

- **AI group-permission bug: “everyone” not respected**  
  <a class="mention" href="/u/RGJ">RGJ</a> revived an old issue where setting **AI bot allowed groups** to `everyone` still blocks the bot in [Discourse AI does not respect the "everyone" group](https://meta.discourse.org/t/-/292048/5?silent=true), and pointed out the faulty `allowed_groups_map` check in core. #Bug

---

## Activity

Below is a breakdown of contributions by our most active community members over the last week:

- **<a class="mention" href="/u/sam">sam</a>**  
  • Announced native PDF & attachment support in [391007/1](https://meta.discourse.org/t/-/391007/1?silent=true) and authored the how-to [391005/1](https://meta.discourse.org/t/-/391005/1?silent=true).  
  • Fixed the AI bot 400 error in [390794/6](https://meta.discourse.org/t/-/390794/6?silent=true) and confirmed the resolution in [390794/8](https://meta.discourse.org/t/-/390794/8?silent=true).  
  • Clarified Qwen3-VL-8b image support in [391017/2](https://meta.discourse.org/t/-/391017/2?silent=true).

- **<a class="mention" href="/u/Falco">Falco</a>**  
  • Advised that the hosted LLM API won’t be available for self-hosters in [390985/3](https://meta.discourse.org/t/-/390985/3?silent=true).  
  • Helped diagnose the 400 error on AI bots in [390794/2](https://meta.discourse.org/t/-/390794/2?silent=true).  
  • Guided on custom tokenizers in [391238/2](https://meta.discourse.org/t/-/391238/2?silent=true).

- **<a class="mention" href="/u/keegan">keegan</a>**  
  • Launched the CDCK hosted LLM in [390985/1](https://meta.discourse.org/t/-/390985/1?silent=true) and detailed configuration in [390985/2](https://meta.discourse.org/t/-/390985/2?silent=true).

- **<a class="mention" href="/u/stephtara">stephtara</a>**  
  • Shared expertise on multilingual translations in [381120/36](https://meta.discourse.org/t/-/381120/36?silent=true).  
  • Offered community-building advice in [385877/8](https://meta.discourse.org/t/-/385877/8?silent=true).

- **<a class="mention" href="/u/zogstrip">zogstrip</a>**  
  • Proposed the core `valueTransformer` for the preference bug in [391135/5](https://meta.discourse.org/t/-/391135/5?silent=true).  
  • Approved the UI fix for LLM Usage filters in [391273/2](https://meta.discourse.org/t/-/391273/2?silent=true).

- **<a class="mention" href="/u/RGJ">RGJ</a>**  
  • Highlighted the “everyone” group permission bug in [292048/5](https://meta.discourse.org/t/-/292048/5?silent=true).

- **<a class="mention" href="/u/awesomerobot">awesomerobot</a>**  
  • Fixed missing moderator sentiment links in [391033/2](https://meta.discourse.org/t/-/391033/2?silent=true).

- **<a class="mention" href="/u/putty">putty</a>**  
  • Reported the missing sentiment pages for moderators in [391033/1](https://meta.discourse.org/t/-/391033/1?silent=true).

- **<a class="mention" href="/u/david">david</a>**  
  • Advised on a core approach for preference value transformation in [391135/6](https://meta.discourse.org/t/-/391135/6?silent=true).

- **<a class="mention" href="/u/MachineScholar">MachineScholar</a>**  
  • Reported the AI bot 400 error in [390794/1](https://meta.discourse.org/t/-/390794/1?silent=true) and confirmed it was resolved in [390794/8](https://meta.discourse.org/t/-/390794/8?silent=true).

Thanks for reading, and I'll see you again next week! :slight_smile:

[Discourse]

Overview

This week the ai category on Meta Discourse saw a blend of critical bug fixes, forward-looking feature proposals, and nuanced usage discussions:

• Bug triage kicked off with the broken silence link directing standard users to an admin-only page “Discourse AI silence link takes you to an inaccessible link as a normal user”, an LLM setup failure complaining that “Target can’t be blank” “LLM error in Discourse AI - “Target can’t be blank””, and a fully restored spam detection “Scan log” after it had been truncated “Discourse AI spam detection “Scan log” is frequently truncated”.

• Feature requests gained traction with calls for branched AI chat threads “Request: AI Bot Chat Threads Support (Threaded/Branched Conversations with AI)” and NVIDIA embeddings support “希望ai插件可以支持nvidia的嵌入向量模型”.

• Usage & economics of hosted LLM credits sparked debate over per-reply costs, daily quotas, and caching strategies “Unlock All Discourse AI Features with Our Hosted LLM”.

• UI feedback surfaced on the semantic clarity of Suggested vs Related topic lists “Do we want to tweak “suggested” and “Related” links at bottom of posts?” and explorations of AI artifact storage synergy with Google’s A2U interfaces “AI Artifact User storage”.

• Search & localization threads examined conversational AI search dialogs “Conversational AI Search coming to Discourse AI” and updated screenshots for Content Localization workflows “Content Localization - Manual and Automatic with Discourse AI”.

• Finally, the announcement Discourse MCP “Discourse MCP is here!” generated enthusiasm for a new modular moderation framework.

---

Interesting Topics

• twofoursixeight discovered that the AI silence link redirects non-admins to an inaccessible admin URL, prompting a collaborative Bug discussion with per1234, NateDhaliwal, and Moin on whether to retarget the link to the machine account profile or conditionally hide it based on permissions.
  Discourse AI silence link takes you to an inaccessible link as a normal user (Bug ai)

• Lilly reported an LLM configuration error when testing a self-hosted model—“Target can’t be blank”—to which zogstrip responded with a link to a pull request that fixes parameter validation.
  LLM error in Discourse AI - “Target can’t be blank” (Bug ai)

• joo proposed threaded/branched AI bot conversations, akin to Discourse Chat threads, allowing sub-topics to inherit context and remain organized under the AI bot’s umbrella.
  Request: AI Bot Chat Threads Support (Threaded/Branched Conversations with AI) (Feature ai)

• 祁同伟 explored integrating NVIDIA’s embedding models via the NIM API, shared API key details, and encountered case-sensitive model naming quirks before Falco posted a working configuration screenshot.
  希望ai插件可以支持nvidia的嵌入向量模型 (Feature ai)

• westes questioned the practicality of 15K daily AI credits for summarize-on-demand, advocating per-post summaries and clearer cost indicators, while Falco and keegan clarified token-to-credit ratios and per-user quota tooling.
  Unlock All Discourse AI Features with Our Hosted LLM (Announcements ai)

• Falco confirmed that the AI spam detection “Scan log” no longer truncates, resolving a months-old moderator pain point.
  Discourse AI spam detection “Scan log” is frequently truncated (Bug ai)

• ToddZ critiqued the ambiguity of “Suggested” vs “Related” links under posts, leading to discussion on tab naming conventions and AI-driven relevance curation.
  Do we want to tweak “suggested” and “Related” links at bottom of posts? (Site feedback #ai-related-topics suggested-topics)

• iamcapote drew parallels between Discourse AI’s artifact storage and Google’s A2UI agent-driven interfaces, suggesting complementary workflows for user-generated AI content.
  AI Artifact User storage (Announcements ai-artifacts)

• tvavrda spotted a non-functional “How does it work?” button in the Conversational AI Search info dialog, highlighting a minor UI oversight ahead of the broader rollout.
  Conversational AI Search coming to Discourse AI (Feature ai-search)

• Jason_Hsia celebrated the launch of the Discourse MCP moderation framework and envisioned Cursor integration, while sam reminded users to simply enable it via the MCP config.
  Discourse MCP is here! (blog ai mcp)

---

Activity

• Falco — confirmed the fixed spam log in #373460/3, clarified token usage and caching in #390985/7 and #390985/9, and guided NVIDIA embedding setup in #391833/2 and #391833/4.

• Jason_Hsia — shared EVP for moderation on #386983/10.

• sam — offered MCP config advice on #386983/11.

• Lilly — reported the blank-target LLM error on #391497/1.

• zogstrip — linked to the fix PR on #391497/2.

• twofoursixeight — filed the initial silence link bug on #391531/1.

• NateDhaliwal — chimed in with config notes on #391531/2, clarified access logic on #391531/4, acknowledged follow-up on #391531/6, and refreshed localization screenshots on #370969/54.

• per1234 — suggested linking to the AI bot profile on #391531/3, outlined alternate link destinations on #391531/5, and emphasized false-positive transparency on #391531/8.

• Moin — advocated permission-based link visibility on #391531/7 and stressed clear AI messaging on #391531/9.

• joo — initiated the threaded-AI feature on #391875/1.

• 祁同伟 — tested NVIDIA embedding models on #391833/1 and shared failure logs on #391833/3.

• westes — challenged credit limits on #390985/6, revisited usage concerns on #390985/8, and probed plan economics on #390985/10.

• keegan — shared quota configuration tips on #390985/11.

• ToddZ — eyed UI semantics on #384030/12.

• iamcapote — connected artifact storage to Google A2U on #369822/19.

• tvavrda — logged the search dialog bug on #355939/16.

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

[Discourse]

Weekly AI Activity Summary: Dec 22–29, 2025

Overview

In the past week, the community engaged in UX refinements, Support queries, Bug triage, and Feature planning across AI‐related discussions.
Lilly’s DMenu drop down selected/hover/focus states are a bit confusing highlighted inconsistent styling in expanded gist mode, leading to a fix by jordan.vidrine. Clarification on core AI functionality came through Does the Discourse source code support AI modes and AI overviews?, and moderation edge-cases such as accounts remaining silenced after deleting spam flags were exposed in Account left silenced without review when user deletes spam flagged post. Meanwhile, automation scripts like “Triage posts using AI” and integrations with local LLMs (ai, chat) spurred bug reports and design discussions.

---

Interesting Topics

• DMenu drop down selected/hover/focus states are a bit confusing (UX ai): Lilly observed inconsistent fill colors for the gist button across active, hover, and disabled states in expanded mode.
• Does the Discourse source code support AI modes and AI overviews? (Support ai): toanvoc asked about built-in AI overviews and mode integrations, prompting detailed clarifications from the team.
• How to change the url of AI chatbot to remove any reference to Discourse (Support ai): m_terenui explored branding tweaks by renaming the /discourse-ai path for the chatbot UI.
• Account left silenced without review when user deletes spam flagged post (Bug moderation ai spam): per1234 demonstrated how auto-silencing can persist unnoticed if a flagged post is removed before human review.
• Discourse AI with local ollama Internal Server Error (Bug ai): luftaquila traced connection errors to model configuration issues when using Ollama locally.
• “Needs Approval” review items from “Triage posts using AI” script of “Automation” plugin not visible to moderators (Bug automation ai moderation): per1234 uncovered that AI-driven flags can be hidden from review queues.
• “Triage posts using AI” script of “Automation” plugin always includes image data in request (Bug automation ai): per1234 flagged excessive payload sizes due to embedded image data sent to the LLM.
• AI translator should translate summaries too (Feature ai content-localization): community members proposed extending the translation plugin to cover post summaries and profile excerpts.
• 希望ai插件可以支持nvidia的嵌入向量模型 (Support ai): 祁同伟 confirmed that adjusting the base URL resolved issues when connecting to NVIDIA embedding models.
• AI Post Analyzer for Chat (Theme component chat ai-bot): Hyteller checked group-based bot access settings and noted deprecation warnings in the widget system.

---

Activity

• chapoi replied in How to change the url of AI chatbot… (Support ai).
• Falco demonstrated existing AI features in Does the Discourse source code support AI modes… and confirmed URL customizability limits in How to change the url of AI chatbot….
• Hyteller raised compatibility questions in AI Post Analyzer for Chat and linked to a deprecation notice in post 18.
• jordan.vidrine debugged the DMenu in post 3 and confirmed the fix in post 6 of DMenu drop down selected/hover/focus states….
• Lilly initiated DMenu drop down selected/hover/focus states… with a detailed repro case.
• m_terenui configured their self-hosted site and opened How to change the url of AI chatbot….
• nat suggested moving translation comments in AI translator should translate summaries too.
• NateDhaliwal guided on LLM settings in Does the Discourse source code support AI modes… and asked for term clarifications in post 8.
• Noah proposed profile translation enhancements in AI translator should translate summaries too.
• per1234 reported multiple moderation and automation bugs in Account left silenced…, “Needs Approval” review items… & post 6, and “Triage posts using AI” always includes image data.
• 祁同伟 confirmed a base-URL fix in 希望ai插件可以支持nvidia的嵌入向量模型.
• sam weighed in on contrast concerns in DMenu drop down selected/hover/focus states… and coordinated deployment timing in “Needs Approval” review items….
• toanvoc opened the core AI integration query in Does the Discourse source code support AI modes… and followed up in post 5.
• luftaquila triaged local Ollama errors in post 1 and isolated model issues in post 2.
• zogstrip asked for term clarifications in Does the Discourse source code support AI modes…, tested fixes in post 6, and reviewed bug reports in Account left silenced…, “Needs Approval” review items…, and “Triage posts using AI” includes images.

---

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

[Discourse]

Weekly AI Activity Summary

Period: 2025-12-29 to 2026-01-05

---

Overview

This week saw four notable AI-related discussions on Meta Discourse:

• A proposal to exclude specific categories from the AI gist summarizer to control costs and noise, led by Lilly (Allow to specify categories to exclude from AI gist summaries).
• Questions around localization support in the new Discourse Moderation Companion (MCP), where jrgong asked about pulling German content with an English translation, sparking a side-request for a locale parameter in the REST API (Discourse MCP is here!).
• A caching/UI bug in the LLM Usage page that prevented time-range changes from refreshing model lists, reported by RBoy (Bug in LLM Usage UI).
• Glitches in the Daily Summary tool, where summaries appear as copy blocks and mis-categorize posts, highlighted by Heliosurge (Daily Summary (On Meta)).

These threads cover Feature requests, Bug fixes, and improvements in ai-summarize, mcp, UX, and #site-management.

---

Interesting Topics

• Lilly requested more granular control over AI features, asking to exclude certain categories (and potentially tags) from the AI gist summarizer for cost management (ai-summarize, Feature).
• jrgong praised the MCP but inquired about a locale argument to fetch German-to-English translations, leading to a suggestion to add a parameter to the read tool (Discourse MCP is here!, support request) ai, mcp.
• Falco supported the locale-parameter idea, linking it to REST API tl-lang parameters for consistency across tools.
• RBoy discovered a persistent caching issue in the LLM Usage UI where selecting “Last 24 hours” still showed last month’s models (Bug in LLM Usage UI, see earlier minor UI bug) Bug, UX, ai.
• Heliosurge reported two Daily Summary anomalies: summaries posted as copy blocks and incorrect classification of a plugin as a theme component (Daily Summary (On Meta), original report here, follow-up here) Bug, #site-management, automation.
• fokx revisited NSFW detection, suggesting pre-submission image scanning to reduce lag in hiding flagged content, possibly acceptable if users wait for moderation (how-to, moderation, automation, ai) Setting up NSFW detection in your community.

---

Activity

• Lilly authored the feature request to exclude categories from AI summarization, earning 5 likes.
• jrgong posted twice in the MCP thread—first asking about locale support at post 12 and later linking to the REST API request at post 14—garnering 2 likes.
• Falco contributed a key suggestion at post 13 on how to implement a locale parameter (2 likes).
• RBoy reported the LLM Usage UI bug in post 1, receiving 1 like.
• Heliosurge flagged Daily Summary issues in post 1, with 1 like.
• fokx chimed in on NSFW detection at post 4, earning 1 like.

---

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

[Discourse]

## Overview

This week on #ai the community tackled a range of topics from integration and setup to bug fixes and feature requests. In #Marketplace, <a class="mention" href="/u/Geenicetea">Geenicetea</a> sought help with [DiscourseConnect & AI setup](https://meta.discourse.org/t/-/393147/1?silent=true), prompting guidance from <a class="mention" href="/u/jahan_gagan">jahan_gagan</a> [ref](https://meta.discourse.org/t/-/393147/2?silent=true) and <a class="mention" href="/u/itsbhanusharma">itsbhanusharma</a> [ref](https://meta.discourse.org/t/-/393147/3?silent=true).  
In #Bug, the mysterious appearance of external links in Discobot search results was diagnosed as an address-replacement quirk by <a class="mention" href="/u/Moin">Moin</a> [ref](https://meta.discourse.org/t/-/393260/3?silent=true) after <a class="mention" href="/u/Lilly">Lilly</a> reported unexpected OOPS pages [ref](https://meta.discourse.org/t/-/393260/1?silent=true).  
On #Support, users dove deep into configuring Discourse AI for *internal-only* usage [ref](https://meta.discourse.org/t/-/393030/1?silent=true) and uncovered hidden web-search costs that led one admin to switch providers [ref](https://meta.discourse.org/t/-/393030/7?silent=true). Meanwhile, a curious 403 error when logged out of AI credits status surfaced in #Bug #ai-summarize [ref](https://meta.discourse.org/t/-/393261/1?silent=true).  
Feature requests spanned automation improvements—triggering AI replies only for topic creators [ref](https://meta.discourse.org/t/-/393157/1?silent=true)—and deeper control over AI bot attachments in #Feature #ai-bot [ref](https://meta.discourse.org/t/-/393178/1?silent=true).  
> “Is there a way to fully restrict file upload for the AI bot?”  
—<a class="mention" href="/u/m_terenui">m_terenui</a>  

For a deep dive on SSO, refer to our [Marketplace thread](https://meta.discourse.org/t/-/393147/1?silent=true).  
You can also revisit the [internal-only Discourse AI discussion](https://meta.discourse.org/t/-/393030/1?silent=true).  
And while investigating UI bugs, see [this console error report](https://meta.discourse.org/t/-/392652/3?silent=true).

---

## Interesting Topics

- **DiscourseConnect & AI single sign-on** (#Marketplace #wp-discourse #discourseconnect #ai)  
  <a class="mention" href="/u/Geenicetea">Geenicetea</a> asked for SSO guidance in [Can someone help me set up discourseconnect & ai](https://meta.discourse.org/t/-/393147/1?silent=true).

- **Discobot search showing external links** (#Bug #search #ai)  
  <a class="mention" href="/u/Lilly">Lilly</a> flagged [The “Discobot discoveries” search results on Meta](https://meta.discourse.org/t/-/393260/1?silent=true) returning non-Meta URLs, with <a class="mention" href="/u/Moin">Moin</a> explaining the URL rewriting [ref](https://meta.discourse.org/t/-/393260/3?silent=true).

- **Internal-only Discourse AI configuration** (#Support #ai)  
  <a class="mention" href="/u/Thefacto">Thefacto</a> explored [How to set up Discourse AI for internal-only usage](https://meta.discourse.org/t/-/393030/1?silent=true) and discovered hidden web-search costs [ref](https://meta.discourse.org/t/-/393030/7?silent=true).

- **403 error on AI credits status** (#Bug #ai-summarize)  
  <a class="mention" href="/u/Moin">Moin</a> reported [403 errors for /discourse-ai/credits/status?features[]=topic_summaries](https://meta.discourse.org/t/-/393261/1?silent=true) when logged out.

- **AI automation only for topic owners** (#Feature #automation #ai)  
  <a class="mention" href="/u/kuaza">kuaza</a> suggested [AI Automation For Topic Creators Only](https://meta.discourse.org/t/-/393157/1?silent=true) so that automated replies only trigger for the topic author.

- **Discourse MCP enhancements** (#Blog #ai #mcp)  
  <a class="mention" href="/u/jrgong">jrgong</a> proposed permission arguments in [Discourse MCP is here!](https://meta.discourse.org/t/-/386983/15?silent=true).

- **Bug in LLM Usage UI** (#UX #ai)  
  <a class="mention" href="/u/zogstrip">zogstrip</a> fixed cache handling in [Bug in LLM Usage UI](https://meta.discourse.org/t/-/392652/3?silent=true).

- **Restricting file uploads in AI bot** (#Feature #ai-bot)  
  <a class="mention" href="/u/m_terenui">m_terenui</a> asked about removing file-upload capabilities in [Exploring blocking file upload while interacting with AI bot](https://meta.discourse.org/t/-/393178/1?silent=true).

- **Filtering AI conversations** (#Feature #ai)  
  <a class="mention" href="/u/kuaza">kuaza</a> revisited [Listing conversations with artificial intelligence on a separate page](https://meta.discourse.org/t/-/362711/10?silent=true).

- **Support for AI modes in source code** (#Support #ai)  
  <a class="mention" href="/u/toanvoc">toanvoc</a> asked if Discourse supports various AI modes in [Does the Discourse source code support AI modes and AI overviews?](https://meta.discourse.org/t/-/392260/10?silent=true).

- **AI contextual menu not updating** (#Support #ai-helper #bug)  
  <a class="mention" href="/u/mcmcclur">mcmcclur</a> described menu-refresh issues in [AI contextual_menu does not update reliably](https://meta.discourse.org/t/-/392930/1?silent=true).

---

## Activity

- <a class="mention" href="/u/Geenicetea">Geenicetea</a> initiated the SSO integration thread [Can someone help me set up discourseconnect & ai](https://meta.discourse.org/t/-/393147/1?silent=true?silent=true).

- <a class="mention" href="/u/jahan_gagan">jahan_gagan</a> offered assistance in [Can someone help me set up discourseconnect & ai](https://meta.discourse.org/t/-/393147/2?silent=true).

- <a class="mention" href="/u/itsbhanusharma">itsbhanusharma</a> also chimed in on SSO setup in [Can someone help me set up discourseconnect & ai](https://meta.discourse.org/t/-/393147/3?silent=true).

- <a class="mention" href="/u/Lilly">Lilly</a> reported the Discobot search anomaly in [The “Discobot discoveries” search results on Meta](https://meta.discourse.org/t/-/393260/1?silent=true) and contributed to the internal-only AI setup thread in [How to set up Discourse AI for internal-only usage](https://meta.discourse.org/t/-/393030/2?silent=true).

- <a class="mention" href="/u/Moin">Moin</a> explained the URL rewrite in Discobot search [ref](https://meta.discourse.org/t/-/393260/3?silent=true) and reported the 403 error in [403 error for /discourse-ai/credits/status](https://meta.discourse.org/t/-/393261/1?silent=true).

- <a class="mention" href="/u/Thefacto">Thefacto</a> led the **internal-only AI** discussion in [How to set up Discourse AI for internal-only usage](https://meta.discourse.org/t/-/393030/1?silent=true), iterated through posts [ref](https://meta.discourse.org/t/-/393030/3?silent=true), [ref](https://meta.discourse.org/t/-/393030/5?silent=true), and closed the loop with a solution [ref](https://meta.discourse.org/t/-/393030/7?silent=true).

- <a class="mention" href="/u/kuaza">kuaza</a> made two feature requests: AI automation for authors in [AI Automation For Topic Creators Only](https://meta.discourse.org/t/-/393157/1?silent=true) and filtering AI conversations in [Listing conversations with artificial intelligence on a separate page](https://meta.discourse.org/t/-/362711/10?silent=true).

- <a class="mention" href="/u/Falco">Falco</a> reviewed PR possibilities in [Discourse MCP is here!](https://meta.discourse.org/t/-/386983/15?silent=true) and welcomed further contributions [ref](https://meta.discourse.org/t/-/386983/16?silent=true).

- <a class="mention" href="/u/zogstrip">zogstrip</a> addressed caching in [Bug in LLM Usage UI](https://meta.discourse.org/t/-/392652/3?silent=true).

- <a class="mention" href="/u/Bruce5051">Bruce5051</a> suggested “AI hallucination?” in [The “Discobot discoveries” search results on Meta](https://meta.discourse.org/t/-/393260/2?silent=true).

- <a class="mention" href="/u/merefield">merefield</a> asked for clarification in [Does the Discourse source code support AI modes and AI overviews?](https://meta.discourse.org/t/-/392260/11?silent=true).

- <a class="mention" href="/u/toanvoc">toanvoc</a> inquired about AI mode support in [Does the Discourse source code support AI modes and AI overviews?](https://meta.discourse.org/t/-/392260/10?silent=true).

- <a class="mention" href="/u/mcmcclur">mcmcclur</a> reported AI menu issues in [AI contextual_menu does not update reliably](https://meta.discourse.org/t/-/392930/1?silent=true).

- <a class="mention" href="/u/m_terenui">m_terenui</a> explored file-upload restrictions in [Exploring blocking file upload while interacting with AI bot](https://meta.discourse.org/t/-/393178/1?silent=true).

---

Thanks for reading, and I'll see you again next week! :slight_smile:

[Discourse]

Weekly AI Activity Summary (2026-01-12 → 2026-01-19)

Overview

This week in ai on Meta Discourse, the community tackled:

• plugin integrations with discourseconnect for WordPress (Can someone help me set up discourseconnect & ai)
• bug squashing for 403 error for /discourse-ai/credits/status?features%5B%5D=topic_summaries
• UX exploration of a chat-based search interface
• accessibility improvements in Encourage/enforce adding image descriptions
• per-user ai quota controls in discourse论坛AI配置限额精确到每个人
• a proposed Feature request: AI-powered “meaningless reply” filter with user-selectable levels to reduce low-signal noise
• advanced persistent memory in Discourse AI persistent memory and pseudo-agent capabilities via Using Tools as Pseudo-Agents for Specialized Directives
• localization nuance in Is ‘in’ translateable in relative_reset_time?
• addressing AI hallucinations in The “Discobot discoveries” search results on Meta

---

Interesting Topics

• Geenicetea kicked off a Marketplace help request in Can someone help me set up discourseconnect & ai, later thanking itsbhanusharma after a complete walkthrough (post #5).
• awesomerobot dissected a 403 error in 403 error for /discourse-ai/credits/status?features%5B%5D=topic_summaries, leading to a quick merge in PR #37070 and resolution at post #2).
• thaidb explored UX by asking Plans to merge Global Search with Discourse AI for a Chat-based UI?, with awesomerobot outlining existing search personas and embeddings in post #2).
• ToddZ refined the Feature discussion on Encourage/enforce adding image descriptions, emphasizing alt text integrity versus narrative context via figcaption (post #21).
• Moin resolved a review of per-user credits in discourse论坛AI配置限额精确到每个人, highlighting the built-in #quota tracking (post #2).
• tom_eric proposed an innovative moderation tool in Feature request: AI-powered “meaningless reply” filter with user-selectable levels, combining regex pre-filtering with LLM classification.
• BrianC showcased long-term context in Discourse AI persistent memory, demonstrating memory.set, memory.get, and a management UI (post #4).
• BrianC also shared a pseudo-agent approach in Using Tools as Pseudo-Agents for Specialized Directives, enabling targeted directive injection.
• Moin dug into localization quirks in Is ‘in’ translateable in relative_reset_time?, clarifying hardcoded prepositions.
• sam flagged an AI hallucination in The “Discobot discoveries” search results on Meta, weighing the complexity of streaming corrections.

---

Activity

• awesomerobot (10 likes, 2 posts): resolved 403 error for /discourse-ai/credits/status?features%5B%5D=topic_summaries (post #2) and expanded on Plans to merge Global Search with Discourse AI for a Chat-based UI? (post #2).
• Geenicetea (6 likes, 1 post): completed the setup guide in Can someone help me set up discourseconnect & ai (post #5).
• ToddZ (5 likes, 2 posts): enriched Encourage/enforce adding image descriptions (post #20 & #21).
• Moin (4 likes, 2 posts): clarified discourse论坛AI配置限额精确到每个人 (post #2) and probed Is ‘in’ translateable in relative_reset_time?.
• tom_eric (3 likes, 1 post): suggested improvements in Feature request: AI-powered “meaningless reply” filter with user-selectable levels.
• BrianC (2 likes, 2 posts): demoed Discourse AI persistent memory (post #4) and outlined Using Tools as Pseudo-Agents for Specialized Directives.
• thaidb (2 likes, 1 post): initiated Plans to merge Global Search with Discourse AI for a Chat-based UI?.
• sam (1 like, 1 post): critiqued The “Discobot discoveries” search results on Meta (post #5).
• zogstrip (1 like, 1 post): verified the fix in Account left silenced without review when user deletes spam flagged post (post #5).
• rey.riel (1 like, 1 post): celebrated enhancements in Discourse MCP is here! (post #17).

---

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

[sam (Sam Saffron)]

Gemini hallucinating ```markdown is so annoying… going to see if there is an easy way to work around it.

[Discourse]

Weekly AI Activity on meta.discourse.org

Period: 2026-01-19 to 2026-01-26

Overview

This week the Discourse community engaged in a diverse set of ai discussions across Support, UX, Plugin, #Self-Hosting, Bug, and Announcements categories. At the core were localization and translation improvements—most notably in Related Topics not translated where multilingual sites regained proper locale-based topic suggestions. Plugin power-users explored write-tool availability in Discourse MCP is here! and proposed enhancements to LLM management in Feature request: improve Discourse AI LLM setup (model discovery) and add AI config import/export. In UX, debates around User Interface Preferences: include setting to disable AI nudges emphasized user control versus built-in guidance. Infrastructure conversations ranged from adding custom HTTP headers in self-hosted LLM setups (Self-Hosting an OpenSource LLM for DiscourseAI) to diagnosing Discobot’s search hallucinations (The “Discobot discoveries” search results on Meta) and translation key tweaks (Is ‘in’ translateable in relative_reset_time?). Developers also tackled schema errors in custom AI tools (AI bot - Custom tools), integration with image generation APIs (Improved Image Generation Support in Discourse AI), and even community-contributed recommendation scripts in Discourse AI.

Interesting Topics

• Related Topics not translated (Support, ai, related-topics, content-localization)
  stance455 kicked off this thread by noting that auto-translated pages still showed English “related topics” ref, Lilly requested reproduction steps ref, Moin provided the #solution to set ai embeddings model to multilingual-e5-large ref, and stance455 confirmed all was well afterward ref.

• Discourse MCP is here! (blog, ai, mcp)
  SkhemaDeveloper verified access to “write” tools after configuring the —allow_writes flag ref and later resolved the issue by regenerating an admin key as system ref. sam announced a new release with considerations for admin-only endpoints ref, while rey.riel proposed and submitted a PR for email and group access behind admin keys ref, later sharing the PR link ref and a doc-caveat on “single user = system” in key creation ref.

• User Interface Preferences: include setting to disable AI nudges (UX, ai-summarize)
  conartist6 asked about disabling AI suggestion buttons via a user setting ref. Moin suggested a local CSS workaround ref. conartist6 then contemplated a PR for a new toggle ref, with Canapin noting the team’s caution on adding settings ref. conartist6 highlighted broader ethical concerns ref, chapoi recommended gauging community traction with a Feature request ref, awesomerobot pointed out the existing admin-level toggle ref, and conartist6 confirmed that hiding the button suffices for personal preference ref.

• Self-Hosting an OpenSource LLM for DiscourseAI (#Self-Hosting, ai)
  pacharanero requested the ability to inject a custom HTTP header (e.g., SubscriptionKey) into LLM requests ref. pfaffman suggested either a Discourse plugin or an NGINX proxy workaround ref.

• The “Discobot discoveries” search results on Meta (Bug, search, ai)
  ondrej reported that Discobot’s AI-powered suggestions pointed to a non-existent category ref, prompting discussion on whether to disable AI discoveries here ref.

• AI bot – Custom tools (#Site Management, how-to, ai)
  jorge-gbs encountered a schema validation error when defining an array parameter in a custom tool ref and asked for known limitations or UI paths.

• Improved Image Generation Support in Discourse AI (Announcements, ai, ai-helper)
  David_Ghost inquired about using Stability API keys in a custom tool for image generation ref.

• Discourse AI (Plugin, official, included-in-core, ai)
  祁同伟 shared a community-built Tampermonkey script integrating Twitter’s open-sourced recommendation algorithm into Discourse’s AI recommendations ref.

• Is ‘in’ translateable in relative_reset_time? (#Translations, ai)
  zogstrip caught a missing %{in} translation key and linked to a fix PR ref, with Moin confirming multilingual behavior works for both time formats ref.

• Feature request: improve Discourse AI LLM setup (model discovery) and add AI config import/export (Support, ai)
  tom_eric proposed UX enhancements for auto-discovering OpenAI-compatible models and adding import/export for AI configurations, to streamline multi-env admin workflows ref.

Activity

• Moin (3 posts, 5 likes) provided the #solution for locale-aware related topics in Related Topics not translated, suggested a CSS workaround in User Interface Preferences: include setting to disable AI nudges, and confirmed translation key behavior in Is ‘in’ translateable in relative_reset_time?.
• stance455 (2 posts, 5 likes) reported the related-topics translation issue here and later confirmed it was resolved here.
• Lilly (1 post, 4 likes) assisted with reproduction steps for related-topics translation in Related Topics not translated.
• SkhemaDeveloper (2 posts, 1 like) debugged write-tool access in Discourse MCP is here! and fixed the API key scope issue here.
• rey.riel (3 posts, 2 likes) proposed behind-admin API enhancements here, created a PR here, and offered key-creation caveats here.
• Canapin (1 post, 1 like) weighed in on balancing new settings vs. complexity in User Interface Preferences: include setting to disable AI nudges.
• ondrej (1 post, 1 like) flagged Discobot’s broken discovery link in The “Discobot discoveries” search results on Meta.
• chapoi (1 post, 1 like) encouraged a feature-request approach for UI toggles in User Interface Preferences: include setting to disable AI nudges.
• David_Ghost (1 post, 1 like) asked about Stability API integration in Improved Image Generation Support in Discourse AI.
• jorge-gbs (1 post, 1 like) reported a schema error for array parameters in a custom AI tool here.
• conartist6 (4 posts, 0 likes) led the discussion on user-level AI toggle preferences in User Interface Preferences: include setting to disable AI nudges, explored PR feasibility here, voiced ethical objections here, and affirmed the CSS-only fix here.
• pfaffman (1 post, 1 like) suggested plugin or NGINX proxy workarounds for custom headers in Self-Hosting an OpenSource LLM for DiscourseAI.
• pacharanero (1 post, 1 like) requested custom-header support for self-hosted LLMs here.
• zogstrip (1 post, 1 like) filed a PR to translate “in” for credit-reset timing in Is ‘in’ translateable in relative_reset_time?.
• sam (1 post, 1 like) released updates to mcp tools and outlined future admin-API expansions in Discourse MCP is here!.
• tom_eric (1 post, 0 likes) proposed LLM model auto-discovery and AI config import/export UX in Feature request: improve Discourse AI LLM setup (model discovery) and add AI config import/export.

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