Docs · Discord bot
LorePanic for Discord
The LorePanic Discord bot sits in your voice channel and transcribes the session with Mistral Voxtral. When you stop, a structured recap shows up in your campaign. This page covers everything from inviting the bot to configuring auto-record.
Getting started
You need two things to use the bot:
- A LorePanic account, signed in with Discord.
- The bot invited to a server where you have Manage Server permission.
Click the button below and pick the server you want to record in. Discord will show you exactly which permissions are being requested.
Link your Discord account
The bot needs to know which LorePanic account to charge credits to and which campaign to file the session under. It works that out from your Discord user ID. No IDs to paste.
- Go to LorePanic → Sign in and use the Sign in with Discord button, or link Discord from your profile if you already have an account.
- Back in Discord, run
/lp-link. The bot echoes back your Discord ID so you can confirm the link worked.
Only the person who starts the recording needs a linked account. Players in the voice channel don't need LorePanic accounts at all.
Recording a session
The easy way: /lp
Run /lp from any text channel. The bot replies with an ephemeral menu (only you
see it) with buttons for every action:
- Record a Session. Pick a campaign, pick a mode, name the session, join the channel.
- Session Status. Show how long the current recording has been running.
- Stop Recording. End the recording, upload tracks, trigger notes.
- Auto-record. Open the auto-record configuration wizard.
- Link Account. Instructions for linking your Discord account if you haven't already.
The direct way: /lp-record
If you prefer typed commands, you can skip the wizard:
/lp-record start campaign:<campaign_id> [name:<session name>] [mode:<mode>]
/lp-record stop
You have to be connected to a voice channel when you run start. The bot
joins whichever channel you're already in.
What happens while the bot is in the channel
- The bot joins self-muted and self-undeafened. It listens, it never speaks.
- Each speaker's audio is captured as a separate Opus stream at 48 kHz.
- In live mode, the audio is mixed into a mono 16 kHz stream and pushed to LorePanic via WebSocket for real-time transcription.
- Per-speaker tracks are buffered on disk and uploaded when you stop.
- Transcript and suggestions show up live in your LorePanic campaign tab.
Stopping
Click Stop Recording in /lp, or run /lp-record stop.
The bot leaves the channel, uploads the tracks, and queues diarized transcription. A
minute or two later, the structured recap shows up in the campaign dashboard.
Recording modes
Every session picks one of three modes. You can set it per-session (via the wizard or the
mode: option on /lp-record start) or per-rule for auto-record.
Free. The bot records per-speaker tracks and uploads them to LorePanic's object store. No transcription runs, no suggestions, no notes. Great for archival or when you plan to transcribe later.
~80 credits / hour. Records the whole session, then runs Voxtral's higher-quality batch model on the full audio after you stop. Chunked into 10-minute pieces with 15-second overlaps. This is the quality that becomes your canonical transcript.
~240 credits / hour. Streams audio to voxtral-mini-transcribe-realtime
as you play. Partial words arrive in under a second. The suggestions engine wakes up
every 8 seconds on a rolling transcript window and proposes questions, NPCs, and
rule lookups.
See pricing for current credit packs and plan limits.
Auto-record
Auto-record tells the bot to join specific voice channels on its own as soon as your
group gathers. You don't run /lp-record start at all. The bot is ready by
the time you are.
Setting it up
- Run
/lp-autorecord(or open/lpand click Auto-record). - Pick a voice channel (or any channel in the server).
- Pick the campaign to associate auto-recorded sessions with.
- Pick a recording mode.
You can add multiple rules (one per channel, one per campaign) and toggle them independently.
How the trigger works
- The rule fires once the channel hits at least two non-bot members.
- The bot starts a session in the chosen mode, tagged
auto. - A voice-activity watchdog stops the recording on its own after an extended silence, so an empty room doesn't burn credits.
- Running
/lp-record stopmanually still works for ending an auto-recorded session early.
Command reference
| Command | What it does |
|---|---|
/lp | Open the main menu. Record, check status, stop, auto-record, or link account via buttons. |
/lp-record start | Start recording the voice channel you're in. Options: campaign (required), name, mode. |
/lp-record stop | End the active recording, upload tracks, trigger diarized transcription. |
/lp-status | Show what the bot is currently doing in this server: channel, duration, who started it. |
/lp-link | Show your Discord ID and the steps to link your Discord account to LorePanic. |
/lp-autorecord | Configure auto-record rules for this server. |
Options on /lp-record start
campaign. The LorePanic campaign ID this session belongs to. The wizard in/lpfills this for you.name. Optional human-readable session name. Defaults to a timestamp.mode. One ofaudio_only,batch, orrealtime. Defaults torealtime.
Permissions the bot needs
The invite link asks for exactly what's required, nothing more:
- View Channels, so the bot can see voice channels.
- Send Messages, Embed Links, Use Application Commands, for slash-command responses.
- Connect and Speak, to join voice channels. The bot joins self-muted; Speak is only there because Discord requires it to subscribe to voice.
- Use Voice Activity, required to capture per-speaker audio.
The bot does not need Administrator, and it doesn't read messages outside of the slash-command interactions you send it.
Privacy & data
- Audio capture is opt-in per session. The bot only records when you explicitly start a session or when an auto-record rule you set up fires.
- Tell your players. Like any recording, make sure everyone in the voice channel knows the session is being recorded.
- Storage. Per-speaker tracks go to LorePanic's object store. Transcripts, suggestions, and structured notes live in the database, scoped to the campaign.
- Deletion. Delete a session from the LorePanic campaign dashboard and its audio, transcript, and notes go with it.
- Third parties. Audio is sent to Mistral for transcription (Voxtral) and summarization (Mistral Small / Ministral-3B). The privacy policy has the full breakdown.
Troubleshooting
"This Discord account isn't linked to LorePanic"
Sign into LorePanic using the Sign in with Discord
button, or link Discord from your profile, then try again. Run
/lp-link to confirm your Discord ID matches.
The bot won't join the voice channel
- Make sure you are connected to the voice channel when you run
/lp-record start. - Check the channel permissions. The bot needs Connect, Speak, and Use Voice Activity on that specific channel, not just server-wide.
- If the channel is full (user limit reached), the bot can't join. Raise the limit or use a different channel.
Transcript isn't showing up in my browser
Open the LorePanic campaign tab, go to the session page, make sure the live-transcription panel is open. If the WebSocket dropped, refresh. The bot's buffer is untouched and the transcript catches up. Audio is also persisted every 2 minutes, so nothing is lost.
I stopped but no session notes appeared
Note generation runs after the batch transcription finishes, which takes about a minute per 10 minutes of session. If it's been longer than that and nothing has shown up, check the session page. Errors are surfaced inline. If credits ran out mid-session, the transcript still completes but notes may be skipped.
How do I kick the bot mid-session?
Run /lp-record stop. Discord's right-click → disconnect also works,
but it skips the graceful upload step. The command is safer.
Still stuck?
Read the engineering blog post for a deep dive into how the bot works, or get in touch via the contact link in our legal notice.