AI Companion concept
This page explains what the AI Companion is and how it works, so you understand the idea before you set it up or start using it.
The AI Companion is a chat-based assistant built into the admin panel. You describe what you need in plain language, and it does the legwork: it reads your server data on its own, reasons across multiple steps, and drafts the actions you want to take. You stay in control: you decide whether its changes wait for your approval or run straight away, and every change shows up in the chat either way.
Today the Companion is focused on ticket support, but it is built as a general, server-wide assistant. We are gradually opening up more of the platform to it over time.
How it works
The Companion is agentic, not a single-shot chatbot. When you ask it something, it can take several steps on its own before answering:
- it looks things up using read access to your server data (players, factions, tickets, logs, orders, bases, rules, and more)
- it reads this documentation, so "how does X work" is answered from the manual rather than from guesswork
- it correlates what it finds across those sources
- it summarises the result for you and proposes concrete next actions
A single request can trigger many lookups behind the scenes. You see a short trace of which areas it consulted, so you can tell it actually checked the data.
Modes, proposals and approval
This is the most important idea to understand: you decide how much the Companion may do without asking.
- Reading data happens immediately and freely.
- Anything that changes something — a ticket reply, an internal note, a ban, a balance change, a refund, a Discord message, and so on — follows the session's mode:
- Ask (the default): the change is only drafted as a proposal. Nothing happens until a human approves it.
- Execute: the change is carried out straight away, and the chat shows it as an Executed card so you can see what was written and have it corrected.
Every change appears as the same kind of card: a clear summary, the old and new values, the full text or code, a diff for rewritten texts and a link to what it affects. A proposal has Approve, Reject and Reject with comment buttons; a comment goes to the Companion as your next message, and it drafts a corrected proposal. A single answer can contain several proposals at once (for example a reply plus an internal note, or two alternative replies — approve one, reject the other). Each one is decided independently.
Each user has a default mode for new sessions. A session in Discord starts in that default; the switch itself is in the admin panel.
Approving runs the change as the person who approves it, with that person's rights, against the current state. dzbot re-checks that the action is still valid (the ticket is still open, the player still exists, the order can still be refunded) and then carries it out using the same internal logic as the normal admin pages. If something changed in the meantime — the action is no longer valid, or what the card was based on was edited since, for example the rules by hand — the card is marked as failed with a reason instead of doing something half-finished or overwriting the other change. The Companion is told the outcome of every card, so it can react on your next message.
Sessions
A session lives either in the admin panel or in a private Discord thread started with /ai. Both behave the same way: same cards, same approval, same archive.
Conversations with the Companion are organised into sessions, similar to a chat history:
- sessions are private to you — each staff member has their own
- they are named automatically from your first message and can be renamed
- they are append-only — nothing in a session is edited or removed while it exists, which makes every prompt, lookup and approval auditable
- a session's context is fixed when it is created — one session is one task. When the task is done, start a new session for the next one.
You can keep a session open to continue later, or archive it once you are finished. A session that sees no activity for 7 days is archived automatically, so the open list stays a list of live work — the transcript stays readable in the Archived tab. A session is deleted 12 months after its last activity.
Page awareness
The Companion is page-aware: it adapts to where you started it. Opened from a ticket, it already knows that ticket and can read its full conversation without you pasting anything. Opened from the rules page, it knows how your ruleset currently stands — what is configured, what is enforced, whether it is published. With anything else open — an order, a faction, a bounty, a restriction, a booking, a setting, any entry the admin search can find — it knows which one you mean, so "what is going on with this?" needs no id. On a list or overview page it knows which page you are on. The panel says what the new session will be about before you send your first message.
AI credit
dzbot runs the Companion for you — there is no provider to choose and no API key to set up. Usage is paid from your organization's AI credit, shared by all of its servers: every organization with an active or trial server subscription gets 1 € of AI usage included per billing month, and you can top up prepaid credit on top. Each request is charged in euros after it has finished; a typical request costs a fraction of a cent. When the credit is used up, the Companion declines new requests until credit is added.
See AI Companion setup for how credit works in detail, where to see usage and how to top up.
Access and availability
The Companion only appears for users who have the AI Companion access right. A single access right gates the whole feature. A user who has it may use every capability and approve any proposal type — there is no per-action permission split. This is deliberate: because sessions are non-deletable, every action a user takes through the Companion is fully auditable after the fact.
What the Companion may reach, though, is still your own access. It acts as the operator talking to it, not as a service account: it only offers the tools that person's rights allow, and on servers using ticket support levels it can neither read nor act on a ticket in a level that person does not hold. Asking it to fetch such a ticket yields nothing found — the same blind spot the queue has, on purpose, so the Companion cannot become the way around a level. See Support levels.
AI apps over MCP
The same tools the Companion uses are also open to AI apps such as Claude or ChatGPT, over MCP. Such an app works with exactly your rights, brings its own model — so it uses no AI credit — and, if you allow it to write, changes run immediately without Companion cards. See Connect AI apps (MCP).