Discourse has introduced new AI content labelling capabilities in the composer to help members identify partially or wholly AI-generated content, aiming to increase trust within online communities. martin explains that users can now label code, quotes, and details blocks using specific syntax or a new composer submenu. For details blocks, users add an ai attribute; for Markdown quotes, they prefix with [!AI]; and for code, they add ai after the language identifier.
per1234 asked if this feature is in core or a separate component, to which southpaw confirmed it is part of core via this PR. Regarding hosted sites, david noted that changes typically deploy within 24 hours for the ‘latest’ channel.
Community feedback highlighted challenges with manual labeling. andresfromsonar suggested automatic detection, but awesomerobot and martin responded that reliable detection remains difficult and often depends on user honesty. efuetatem1 proposed granular options (e.g., “Human-written, edited by AI”), but satonotdead argued such templates are rarely used. Martin emphasized that the current labeling is intended to prevent undiscussed “walls of text” from AI rather than micromanage every editing step.
Bug reports and feature requests led to quick iterations. per1234 identified that the composer hardcoded javascript as the default language for AI-labeled code blocks, ignoring the forum’s default setting. martin fixed this in PR #46430. Additionally, per1234 requested support for the ai attribute in BBCode [quote] tags for easier formatting. Martin acknowledged this and implemented it in PR #46439.
We are living in a world now where forum members may have the need to share content in their posts that is partially or wholly AI generated content.
We already had an AI indicator that the AI plugin used for quotes, but it’s time we expanded this capability and put this labelling in the hands of regular members, it’s an important distinction to make to increase trust between people in online communities.
Code, quotes, and details blocks can be labelled as AI content. There are a few different ways you can now label AI content in posts. The easiest way is to use this new composer submenu that will insert a placeholder with the AI indicator already applied:
I would like to add this to the Discourse-based forum I manage. Can you provide information about that possibility? Is this part of the Discourse core, or implemented as a separate component?
If it is in the core, it would be great if you would provide a link to the GitHub PR or commit where it was implemented. That would allow me to more easily identify when my forum is updated to the Discourse version that has the feature.
For hosted sites on the ‘latest’ channel, changes typically go out within 24h. But we can expedite it on a case-by-case basis. (I’ll drop you a PM about it now)
This is nice! However, at least in my forum, what I see is that some users create posts by copypasting walls of text from their AI agent’s output. I see this is as a low-effort practice, and I assume these are “low-effort users”, so I would guess they’re the least likely to go out of their way to tag this AI content text.
In a case like this, a feature that I would find more interesting would be automatic labeling of AI content. I guess this could be done today with some custom workflow, and I understand that this might be outside of your scope, but yeah, these are just my 2 cents. Thanks for this feature though, it’s nice to have it regardless!
This would be great and many people would appreciate it, but I don’t think anyone’s able to reliably detect it at this point. Some providers like Anthropic are working on APIs to allow detection of their own watermarks, and Google has one for media (SynthID)… so maybe it will be at least partially possible soon?
This is interesting, but I don’t know if people use AI content that way.
Personally, I usually write the post first, then ask AI to proofread it, or sometimes give it basic ideas or guidelines, then refine its output with a few back-and-forths between the AI and me until the final version.
Did you consider an option where the user can manually identify their post with options such as:
We tried a template years ago in our community and it was very similar to this one you posted. Almost nobody used it.
Algorithms can not prevent algorithms, it is a philosophical contradiction. I think about all of it like Matrix descriptions: agents looks like people and they are everywhere. One can not stop them but stop feeding them.
Isolation is the only way, and it is not relatable to Discourse. Hardening the signups and being really creative about what we ask about, can improve the overall experience but there is no way to prevent them from the scratch. They are on the money and money decides how is Internet today.
This is interesting, kind of another level up in the ladder to identify the whole post as AI assisted. The change in the OP was mainly done to avoid people dumping giant screeds of AI content without properly labelling it.
I would posit that if you have written it yourself and edited with AI or vice-versa, depending on the degree of your involvement labelling may not even be required.
For communities, I think if people are posting purely AI generated posts, and people are tolerating or even apathetic about it, you have a big problem with the health of your community.
Yes would be nice but it’s a tricky problem…as humans, how easy it is to detect it depends on how well someone uses AI to write. If they leave all the claudisms in there, you can tell instantly, but if someone has actually used AI really well then it’s very hard to tell as a human let alone using AI to detect it.
I see that the “post menu > Add AI Content… > Code” feature adds the javascript language identifier to the inserted code fences:
Having this language identifier hardcoded is not very friendly to forums where code blocks are used for things other than JavaScript code.
Please remove the hardcoded language identifier, so that the feature instead adds code fences without a language identifier:
``` ai
// AI content
```
This will allow each forum’s Default code lang site setting to apply to the code block (and of course the user can still specify a different language if needed).
Some additional feedback: it would be nice if support was added for labeling via BBCode quote tags, in addition to the current support for labeling quotes using Markdown.
If the convention established for the details tag was followed, it would look something like this:
[quote ai]
This is a quote made by AI
[/quote]
I love Markdown, but I do end up using BBCode quote tags for larger content because I find it faster and easier than adding the > to the start of each line (I always use the Markdown editor and manually type markup).