Free Store
Get started

Quox Discord Pro · Built in public

The community server, run by the product.

Discord Pro manages a public Discord server as governed infrastructure. The prototype already runs the official Quox server. This page claims only what has been driven and proven, and labels everything else honestly.

Watch it being builtTelegram Pro, the internal siblingRead the docs
PrototypeDay 0Evidence-first

In plain words

What it is, where it lives, when to reach for it

What is it
A Discord bot daemon for QuoxCORE that manages a server and answers members; today it runs our own server.
Where do I use it
In your Discord server, managed from your terminal with the quox discord command group.
When would I use it
When you run a community server and want feeds, support replies and moderation baselines handled for you.
How do I use it
Run quox discord status to see the daemon, then quox discord bind to point a channel at an agent.

QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE

Proven today

Proven today.

Server management

The whole Quox AI server, categories, channels, roles, Community mode, welcome screen, was built and is managed over the Discord API by the prototype. Every call verified.

Beta

Build feed

Every build outcome from the central build queue posts to an internal channel within seconds: target, terminal, stream, duration. Proven with real builds and assertion-checked captures.

Beta

GitHub feed

27 repositories feed pushes, releases, issues and pull requests into the server. A real push rendered 4 seconds after git push.

Beta

Feed personas

Feeds post under their own name and avatar through webhooks. The build queue and GitHub each have a voice.

Beta

Moderation baseline

Spam, mention floods, scam bait and slurs are blocked by AutoMod rules the prototype manages.

Beta

In the server

The real thing.

The Quox Discord Pro dashboard panel showing the live daemon, bound channels and modes
Manage it from the QuoxCORE dashboard: live daemon status, every bound channel with its mode and agent persona, and open support gaps at a glance.
QuoxSupport answering questions in threads in the support channel
QuoxSupport answers in threads, grounded in the site corpus and running on the production platform. It introduces itself, then threads each question.
The agentic team answering a security incident in a thread
The agentic team on a real incident: CommanderQ convenes specialists (SENTINEL, NOVA and AUDITUS here), each answers in its own voice with concrete steps, then CommanderQ synthesises.
The build feed posting build outcomes to a channel
The build feed posts every outcome from the central build queue: target, terminal, stream and duration, seconds after each build.
The GitHub feed and the server channel structure
The GitHub feed carries commits, pull requests and releases across the quoxai repositories. The left rail is the server the bot built out: internal channels and a full agentic-team category.

The honest roadmap

The honest roadmap.

BETAGrounded support answers

Live in the public server's support channel, answered by the production platform: a question retrieves from a corpus crawled off the live site, answers with the specific page cited, and records the whole exchange as a witnessed evidence chain. A twenty-question quality gate passed twenty out of twenty.

BETAIt learns from what it cannot answer

A weak answer files a support gap for a human to answer, and that official answer is folded back into the corpus so the next person gets it. Low-confidence answers also get a second, harder pass automatically.

BETAApproval policy per channel

Every bound channel chooses its policy. Both paths are proven live: a human approval posting a reply, and a rejection discarding one. Support answers autonomously; sensitive channels can require approval.

BETAReal platform agents in private channels

Private team channels route to the actual QuoxCORE agents. CommanderQ orchestrates and hands specialist work to the agent that owns it, each replying under its own name. One daemon can serve several instances at once.

PLANNEDPublisher and proposals

Changelog, news and roadmap events to public channels, and drafted proposals such as a weekly community update that a human approves before it posts. Internal evidence feeds stay internal.

PLANNEDWitnessed moderation

Mod actions recorded as evidence, AEE-enveloped and WARD-witnessed.

BETADashboard panel and packaging

A dashboard panel shows the daemon's live status and channel bindings. The daemon ships as its own container, the backend-plugin shape, and the bot runs on scoped least-privilege permissions, not administrator.

BETACredential storage

All three Discord credentials sit in QuoxVault. The CLI bug that briefly put one in the wrong org is filed in the open (quox#358), and the affected webhook was rotated the same hour.

How it is proven

How it is proven.

Every claim above traces to a proof-loop run. On 2026-08-07 real builds were queued, real pushes made, captures asserted rather than eyeballed, and a guard fed known-bad input to prove it fires. On 2026-08-08 support was proven live on the production server, answering grounded and cited in the public channel. The maturity map ships as STATUS_AND_LIMITS_DISCORD_PRO in the product repo.

Watch it being builtTelegram Pro, the internal siblingRead the docs

Nothing on this page is a mock-up. If it is not proven, it says so.