# Using forum researcher to help organize and split large topics

**URL:** https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188
**Category:** Community Building
**Tags:** ai
**Created:** [May 15, 2025, 1:06am UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188 "2025-05-15T01:06:24Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [May 15, 2025, 1:06am UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/1 "2025-05-15T01:06:24Z")

</div>

I am working on a new (default disabled) persona for Discourse AI that specializes in deep research.

The key differentiator is that this persona is given permission to work through very large bodies of text, this unlocks a large amount of previously extremely complicated use cases.

Today I was looking at our main [Kanban topic](https://meta.discourse.org/t/kanban-board/118164), it has gotten quite enormous and splitting it off into sub topics (features / bugs / support) can take an enormous amount of manual work.

Here is a link of how I leaned on Forum Researcher to help prep for the manual work:

### [Taming the big Kanban Topic](https://meta.discourse.org/discourse-ai/ai-bot/shared-ai-conversations/C1UOooFbHHU3M_NtlBe3JQ)

It is a prime showcase of how this kind of tooling can assist us in working through some of the more complex parts of managing a forum.

Happy to take questions, the feature itself is now in Discourse AI but the persona is default disabled and I am holding off on documenting for a bit more while I refine the feature.

Hope you all are as impressed as I am at the general usefulness of this tool.

---

<div class="post-metadata">

### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [May 15, 2025, 4:56am UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/2 "2025-05-15T04:56:59Z")

</div>

This looks really interesting and promising! I would love to see what could come out of this!

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [May 15, 2025, 5:00am UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/3 "2025-05-15T05:00:32Z")

</div>

Breaking down those long-tailed topics was pretty brutal. 🙂 Something like this would have helped immensely. 🙌

I found some advice I wrote about the manual way (though I appreciate that there are multiple ways to tackle the job) and thought it could be fun/useful to compare against the AI assisted version:

> [@Kanban Board](https://meta.discourse.org/t/kanban-board/118164/266):
>
> Splitting these theme component topics out into digestible ‘one issue per topic’ chunks is what I’ve been aiming for. It is a little slow-going though. 🙂
> 
> Ideally, when I tackle one I’m looking to:
> 
> - Update the OP to match the current ‘style’ with the settings and hosted blurb included (eg.[DiscoTOC - automatic table of contents](https://meta.discourse.org/t/discotoc-automatic-table-of-contents/111143))
> - Update and name screenshots
> - Refresh and include info on any new features
> 
> For the replies, ‘one issue per topic’ as if they were created in their respective categories and tagged properly from the get-go. I’m looking to preserve #Support and solutions, group #ux::category and #feature::category requests, #Development workarounds if there are any non-ui code tweaks suggested, and any #bug::category. If something is resolved (bug fixed, question answered, feature implemented) then those split topics get tied off just the same as usual (#completed tag/solution marked/closed, as appropriate). Other posts that offer no value can be deleted.
> 
> Also, contemplate whether something requires a guide. Not normally one for theme components, but this one may fit the bill.
> 
> Sometimes a post can contain multiple issues. This can make splitting harder, but I try and handle the easy ones first and thin the replies out before weighing up what to do with the more muddled ones.
> 
> Reset bump date is also a big friend of mine. 🙂

---

<div class="post-metadata">

### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [May 19, 2025, 12:44am UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/4 "2025-05-19T00:44:39Z")

</div>

Thanks, James! Lots of great advice there. Looks like splitting the Kanban Board topic is going to be a pretty big project, with or without AI help.

> [@Kanban Board](https://meta.discourse.org/t/kanban-board/118164/266):
>
> > [@Kanban Board](https://meta.discourse.org/t/kanban-board/118164/266):
> >
> > Reset bump date is also a big friend of mine. 🙂

You have a friend in @NateDhaliwal in this.

A feature request I have been considering is making this an allowed by group setting, so we can let our TL3 members reset bump date. It happens alot on meta, mostly because of spam but also because of topic gardening like in this case.

> [@sam](#):
>
> Today I was looking at our main [Kanban topic](https://meta.discourse.org/t/kanban-board/118164), it has gotten quite enormous and splitting it off into sub topics (features / bugs / support) can take an enormous amount of manual work.

I’ve assigned this to myself and will be looking at it more closely this week.

Thanks for looking into this, Sam! Yes, I am impressed.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [May 19, 2025, 5:20am UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/5 "2025-05-19T05:20:34Z")

</div>

> [@tobiaseigen](#):
>
> Thanks, James! Lots of great advice there. Looks like splitting the Kanban Board topic is going to be a pretty big project, with or without AI help.

An individual topic shouldn’t be too bad. 🤞 But having some extra tools on hand to tackle all the other outstanding ones too may tip the balance and help speed the task up (probably worth another ‘🤞’ for extra luck 🙂)

[ActivityPub Plugin](https://meta.discourse.org/t/activitypub-plugin/266794) may be a good test topic for this as well.

* * *

Though I think my main advice for any newer sites reading this is, ‘avoid creating kitchen sink topics in the first place’. 🙂 Improvements to the cure is nice, but I think prevention is still the best option if you can nip it in the bud early enough.

---

<div class="post-metadata">

### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [May 20, 2025, 6:24pm UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/6 "2025-05-20T18:24:06Z")

</div>

I deleted or moved all the replies from the kanban topic, so it has no replies currently.

The next step for the topic will be to update the first post which is also a big task! It’s gotten quite long and has outdated screenshots and instructions, instructions are technical and a bit confusing, and does not explain how to set it up for various purposes. If anyone wants to help out with this, let me know!

The forum helper was helpful. In the end however it is still a manual process of reading each post and deciding:

- keep as a new related topic (still relevant)
- delete and include in first post (still relevant, likely common ho)
- just delete (not worth keeping/no longer relevant)

@sam I noticed alot of duplicate posts - would be interesting to see if AI can help identify these. These should be easily identified because they are from the same user and typically repeat the same questions in the same topic or a new topic.

I’m now looking at the [ActivityPub Plugin](https://meta.discourse.org/t/activitypub-plugin/266794) topic, and asked the forum helper about it. The topic is a bit out of control but is also not an official plugin. @angus do you have thoughts on how you’d like to tidy it up and does this AI report help?

> **[ActivityPub Plugin Topic Analysis](https://meta.discourse.org/discourse-ai/ai-bot/shared-ai-conversations/t7qffjbUy7DVlzLRsq2_5A)**
>
> tobiaseigen: Identify the main ‘activitypub’ plugin topic (most likely the one with the most posts/replies or initial release announcement). Summarize distinct bug reports, feature requests, and recurring support questions in this topic, and recommend clear, logically extractable new topics in appropriate ‘bug’, ‘feature’, and ‘support’ categories. Ensure each recommended extraction is based on meaningful, rep…

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [May 23, 2025, 1:10pm UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/7 "2025-05-23T13:10:47Z")

</div>

Great question!

Honestly, my current inclination is to keep the replies for archival purposes, but minimize them somehow so the topic feels a bit less intimidating. Most of the replies are just no longer relevant for the current plugin, and if folks read them for any practical purpose, i.e. using the plugin, then they may get the wrong impression.

I think deleting the replies would be regrettable as it’s nice to have a record of the plugin’s development over time, but if there were some way to easily minimize them by default, that would be ideal.

We are already handling ActivityPub support and documentation in other topics, and the OP already reflects that in its brevity and use of links. The plugin topic itself is more of a “catch-all” for folks wanting to discuss/ask about the plugin.

---

<div class="post-metadata">

### Author: ![MachineScholar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/machinescholar/32/424719_2.png) [@MachineScholar](https://meta.discourse.org/u/MachineScholar)
#### Post date: [June 3, 2025, 9:49am UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/8 "2025-06-03T09:49:44Z")

</div>

This is a wonderful tool. Is it just me or does it kind of replace search+read tool calls?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 5, 2025, 8:02am UTC](https://meta.discourse.org/t/using-forum-researcher-to-help-organize-and-split-large-topics/366188/9 "2025-06-05T08:02:41Z")

</div>

I wrote a bit about it here, it can replace, but really it is used for “deep research” use cases vs extractive summary and quick answers.

> [@Forum Researcher AI Agent guide](https://meta.discourse.org/t/forum-researcher-ai-persona-guide/368942):
>
> bookmark This guide explains the Forum Researcher agent in Discourse AI, how it works, and how to configure it for in-depth forum content analysis. person_raising_hand Required user level: Administrator (to enable and configure), All users (to interact, if granted access) Understanding and using the Forum Researcher agent The Discourse AI plugin includes the Forum Researcher agent, a powerful tool designed for conducting in-depth research on the content within your forum. This agent can …
