Give your support channel a break.

Save a moderator’s reply.
ThreadSherpa uses it to answer similar questions in your Discord forum.

How it works

People miss
earlier answers.

A moderator has already answered. The next person starts another thread and asks the same question.

supportForum
Where do I submit my project?

Post your public GitHub repository in #submissions.

Is a GitHub link enough?

Can I just share the repo?

Where should I send my project?

My project is ready. Where do I post the link?

Save an answer.

Right-click a moderator’s reply, then choose Apps → Save this answer.

The bot reuses only the replies a moderator saves.

supportHow do I submit?

Post your public GitHub repository in #submissions.

Apps

The bot watches
the forum.

ThreadSherpa checks new forum posts against saved answers. When one matches, it writes a reply with a link to the original.

supportForum

Is a GitHub link enough to submit?

Can I just share the repo?

Yes. Share your public GitHub repository in #submissions.

Original answer

It reads earlier replies before answering a follow-up.

Questions it
can’t answer.

When no saved answer covers a question, the bot stays quiet and queues it for a moderator.

Architecture.

How the bot checks each new forum post.

  1. Discord

    Read the question

    The forum title, post and replies stay in one conversation.

  2. MongoDB

    Find a saved answer

    Exact match, then text and local embeddings. Scoped to this server.

  3. Paper / Ollama

    Write a short reply

    The model gets the question, context and approved evidence.

  4. Response policy

    Check the source

    Check citations and links before posting. Unsupported answers wait.

No matching saved answer?
Skip the model. Queue it for a moderator.

What gets stored?

The approved answer, its original question, source and scope. Duplicate saves reuse the same knowledge. A moderator chooses any optional web sources. Read the memory code.

Limitations.

It does not learn from every message.

Only replies saved by a moderator are reused.

When the rules change, update the saved answer.

Edit or remove the saved guidance. Future questions use the current facts. The bot does not broadcast corrections into old threads.

The model can still get things wrong.

Replies include their source so a person can check them. Unsupported questions wait. An account or payment issue needs private human support.

You run the bot and choose the model.

Use local Ollama inference, or Paper Instruments for replies with local embeddings. You also choose the database, support channels, and moderators.

I built this after seeing the same support questions in the MLH Discord.

Different people needed the same information, but the useful answer was buried in another thread.

Made for the Hacktoberfest Open-Source AI Challenge: Week 3 on DEV. The theme is Slow and Steady: build something that does the work so you don't have to. This is a hackathon project, so expect rough edges.

Run it in Discord.

A Discord bot token. MongoDB.
Ollama or a Paper Instruments key.

Setup instructions
  1. Create your Discord application.
  2. Add the environment values and start the bot.
  3. Connect a forum. Save the first useful reply.