Discord scan → Claude → Google Sheet. Runs once a week on its own.
Three steps. Export pulls new Discord messages and counts candidates — free. Submit sends them to Claude — this costs money and is blocked if the estimate exceeds your limit. Collect fetches the results into the sheet — free. Claude answers in batch, so collecting happens later, on its own.
Schedule
Discord servers
Only the servers switched on here are scanned — all their text channels. Each server has its own list of tokens, tried in the order you tick them (a bot only sees servers it was invited to). If one is rejected, the next on that server’s list is tried; once the list is exhausted the scan moves on to the next server instead of stopping. A server with nothing ticked falls back to all tokens. Messages from every token are analysed together at the end. The guild ID is the long number from Discord (right-click the server → Copy Server ID, with developer mode on).
Bot tokens
Backup, not sharing: the first token is used for everything. Only if Discord stops accepting it does the next one get tried. Once saved, a token is never shown again — only a short preview so you can tell them apart.
Run a step now
History
Outreach — sending
Sends the messages that are already written in the lead sheet. No AI is involved here and nothing is charged — the texts were produced in the batch; this only delivers them. These accounts and servers are separate from the Leads tab on purpose: a scanning account only needs read access, a sending account has to be a credible member of the server. Sharing them would mean one suspended account takes the other job down with it.
Discord servers (sending)
An account can only message people it shares a server with. Recipients are matched by guild ID, not by name — so the ID has to be right, or nobody on that server ever gets written to. Tick the accounts that may send for a server; they are tried in the order you tick them.
Sending accounts
Once saved, a token is never shown again — only a short preview so you can tell the accounts apart.
Follow-ups
The next message in conversations that already exist — mostly people who
replied and are waiting on us. Send from the account shown:
the Desktop/Browser buttons open the chat in whichever Discord account is
logged in, and a message from a different account reads as a new stranger.
The text can be edited before sending. In the lead sheet only the Note column
changes (marker [NF-… offen] → gesendet).
Pipeline follow-ups
Follow-up texts the weekly AI run wrote into the lead sheet for people who were contacted but never replied. Read live from the sheet. Sent ticks “Follow-up gesendet”; Discard ticks it too — otherwise the weekly run re-checks the person every Monday and pays for it. These people have not answered before, so the sending account must still share a server with them.
Today’s plan
What would go out today, in priority order (high before medium before low). Anything over the daily limit is listed as deferred, not dropped.
Never contact
People who must not be written to — because they already play with us, or you are in touch another way. They stay out of every future plan, not just today’s. They are also marked as done in the lead sheet, with the real reason in the Note column: otherwise the weekly run keeps paying to re-analyse them, roughly a cent each, every week.
Messages shown as a banner on every page, for every signed-in user.
Warnings and outages cannot be dismissed by users — they stay until you turn them off. Only Info can be dismissed. Changing the text makes a dismissed notice reappear.
Always means you switch the message on and off yourself. Automatic means it appears and disappears on its own, and only for the users whose own agent is affected — users on a healthy agent see nothing. Switching an automatic message on does not show it to anyone; it arms it.
Cannot load hands covers every reason the provider is not delivering (no response, server error, connection lost, blocked, captcha) — for the player the result is the same. Loading slowly means hands still arrive, but the provider is responding much slower than usual.
Right now
Write your own
All messages
Two questions: are new hands being found, and are downloads working?
Handlist scan
—
Downloads
—
Casino login
—
System — live logs and worker operations.
| Status | Label | Login | Interval | Full-Scan | Last refresh | Next scan |
|---|
Hands with unknown SignID — re-route after updating mapping.
| Hand-ID | SignID | Account | Reason | Time | Preview |
|---|
Manage players, edit configuration (Sheet, SignIDs, HUD). HUD fetches data on server sync.
Player list
| Username | User-ID | Role | Active |
|---|
Identity and access
One Agent-Token per PC (Tokens tab). Increase limit for more computers.
Replayer SignIDs
Order determines the replayer table number (1, 2, 3, …). HUD instance N uses table N.
Saving reassigns existing hands automatically when the SignIDs change; the button runs it on demand. It re-links hands in the queue by SignID — it does not touch quarantined hands, those are handled in the Quarantine tab.
Replayer password
Agent tokens (this player)
Token preview + Device-ID. More tokens in Tokens tab (up to max PCs).
| Token | Device | Label | Permission | PC | Status |
|---|
Casino logins (collector accounts). Routing via player SignIDs (Replayer config) or quarantine.
Refresh interval
Casino accounts
| Status | Label | Login | Quick | Full | Last refresh | Active |
|---|
HUD Agent Token: create, unbind PC, revoke or re-activate. Token in .env as POKER_AGENT_DEVICE_TOKEN.
Multiple PCs: one token per computer — limit per player under max_active_devices.
Create token
All tokens
| Player | Label | Permission | Status | Valid until | Last access | Actions |
|---|
Client-submitted error logs (via "Send logs to support" in the HUD dashboard).
| User | Device | Uploaded | Categories |
|---|
Client installer versions. Upload the file to the server via SCP first, then register its metadata here.
Register new release
| Version | Filename | Uploaded | Size | Changelog | Visible |
|---|
FAQ text entries shown on the public /faq page, grouped by the 5 fixed categories. Text only — media is a later stage.
Add FAQ entry
To attach an image, clip or YouTube video, the editor opens right after you add the entry — manage media there.
| Category | Order | Title | Body |
|---|
Hands per player and period (Europe/Berlin days) — click a player for the daily breakdown.
| Player | today | −1 | −2 | 7d | 30d | limit | last activity |
|---|---|---|---|---|---|---|---|
| Σ alle | — | — | — | — | — |
—
| Date | hands | downloads |
|---|