discord2sum — meeting minutes for Discord voice, without the busywork
Discord voice calls are where decisions get made — and also where decisions get lost.
Someone says “let’s do it this way”, someone else agrees, a couple of tasks are assigned… and then the call ends. A day later you remember that you agreed on something, but not the exact details, who volunteered for what, or what the next step was.
That’s the problem discord2sum solves.
Repo: https://github.com/toxed/discord2sum
It’s a small Discord bot that quietly turns voice conversations into something you can actually refer to later: a short, structured summary delivered to your chat.
What the bot feels like in daily use
You hop into a voice channel with your team.
When people start talking, the bot joins in the background. It doesn’t interrupt and doesn’t try to be clever in real time. It just listens.
When the channel becomes empty, you get a message with “minutes”:
- what the call was about (a concise summary)
- what was decided
- what’s next (action items)
- who spoke / who was present (where possible)
You end up with a lightweight paper trail that’s easy to scan, easy to search, and easy to forward.
Privacy-first by design
A lot of call‑summary products work by uploading your audio somewhere and letting a cloud service do the transcription.
discord2sum is built around local processing:
- audio is recorded and processed on your own machine/server
- speech-to-text runs locally (Whisper-based)
- transcripts can be stored locally with retention limits
For the summary step, you can choose what you’re comfortable with:
- use a hosted LLM (OpenAI) for higher-quality summaries, or
- use a local LLM endpoint (e.g. Ollama) for an all‑local pipeline
Where the summary can go
Telegram is the default because it’s simple and fast.
But the bot can also deliver the same summary to:
- Slack (via Incoming Webhooks)
- any HTTP webhook (as JSON), if you want to push minutes into your own tooling
That makes it easy to route “call outcomes” into whatever system your team already uses.
Why I like this approach
It’s intentionally small and opinionated.
No calendar integration. No meeting invites. No complex UI.
Just one job: when a Discord voice call ends, send a clear summary.
That’s enough to stop decisions from disappearing — without adding process or forcing people to change how they talk.
Top comments (0)