Discord Community Agent with OpenCode

A community agent answers the same fifteen questions forever, and the fifteenth answer is worth exactly what the first one was. OpenCode lets you choose the model behind that, which is how the running cost of a public server stays sensible. The FAQ notes, the guidelines and the Notion pages are where the quality actually comes from.

Loading preview…
Free to start · guided setup

Watch it work before it's live

Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.

/ask free tier limits

M

Mikaela Santos

/ask does the free tier still let me run two agents at the same time? the pricing page says two and the docs page says one, and i do not want to build around the wrong number

Set up in minutes

Using this template drops you into a guided setup. It asks exactly this, nothing else:

  1. Connect Discord

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Notion

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. Community guidelines

    How your server is run - what is not allowed, how scams and harassment are handled, and which moderators or channels own what. The agent flags against this rather than arguing with anyone.

  4. Faq notes

    The questions your members ask over and over, the answers you are happy to see posted publicly, and which Notion pages hold the rest. Anything outside this, the agent says it is not sure.

  5. Runs on OpenCode

    Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.

  6. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

Why OpenCode for this agent

Repetition, priced sensibly

Nothing about answering the free tier question for the four-hundredth time needs a premium model. Choosing lets you spend where it makes a difference.

Voice comes from the FAQ

How the replies read is set by what you wrote and by the server's own tone, not by the harness underneath.

Before you fork

Will a smaller model get the server's voice wrong?

The likeliest failure is blandness, replies that read like documentation rather than like a member, since the tone comes from your FAQ notes and the instruction to skip greetings and sign-offs. That is fixable by writing a couple of example answers into the FAQ variable in the voice you want. Run the staged commands and check how it sounds before announcing it.

Run it with a different agent

Put Discord Community Agent to work on OpenCode

Free to start. Guided setup, a test run against staged conversations, and it's live.