Introduction
Most AI voice agents are slow, inaccurate, miss specialized vocabulary, or chat back so verbosely that they’re actively annoying. That’s a shame — voice is the most natural input we have, and a good voice agent saves real time. The problem is almost never the underlying language model. It’s the speech-to-text and text-to-speech layers in between, which most generalist tools treat as an afterthought.
Deepgram’s Saga is a voice-first AI workspace built around their own best-in-class STT and TTS models. Real-time dictation, accurate handling of domain-specific vocabulary (medical, legal, technical), instant tool integrations through Composio, and a desktop app that lets you drive other applications by voice. It’s free at the time of writing.
📚 Table of contents
- Why voice is hard (and what most tools get wrong)
- What Saga is
- Real-time dictation vs batch transcription
- Voice mode — direct, concise, in-chat transcript
- The Saga vs ChatGPT voice comparison
- One-click integrations via Composio
- The desktop app and the “voice operating system”
- Adding custom MCP servers
- Use cases worth setting up first
- Common mistakes
- FAQs
Why voice is hard (and what most tools get wrong)
Three things have to be right for a voice agent to feel good:
- Latency. If the transcript shows up two seconds after you speak, you can’t correct yourself mid-sentence. Real-time means under ~300ms.
- Accuracy on the long tail. Drug names, surgical procedures, contract clauses, technical jargon — this is where general models fall over. Deepgram’s medical-transcription benchmark vs OpenAI/AWS/11Labs is the chart that justifies their existence.
- Conversational discipline. A voice agent that fills space with “I get what you mean, in that case I’ll keep things really concise into the point, no fluff, no rambling” is doing both fluff and rambling. Good voice agents are terse by default.
Most voice products optimize for the first one and miss the other two. Saga is unusual because it treats all three as load-bearing.
What Saga is
Saga lives at saga.deepgram.com — free, no paid tier yet. The architecture
layers Deepgram’s own STT/TTS on top of standard frontier LLMs (GPT-4.1 default, swap-able
from the model picker). The split matters: Deepgram doesn’t try to train a competing chat
model. They focus on the speech layer where they have a measurable edge.
You get three modes:
- Text chat — normal LLM chat, models selectable.
- Dictation — speak, watch the transcript populate in real time, submit when ready.
- Voice mode — full conversational interaction with the transcript displayed inline.
Real-time dictation vs batch transcription
Most voice tools (ChatGPT’s dictate button included) record audio, then send the whole recording to a transcription model when you press stop. That’s batch transcription — you wait for the file to come back. Saga streams the audio as you speak. The transcript appears with a few hundred milliseconds of delay, complete with punctuation, capitalization, and question marks derived from your intonation.
The practical benefit shows up on long prompts: you can self-correct mid-sentence, pause and restart, see a typo immediately. Try dictating a technical paragraph with terms like peripatetic polymath, antinomic implications, quasi-syncretic codex, and Saga catches the words; the same passage often trips up batch transcription on competing tools.
Voice mode — direct, concise, in-chat transcript
Saga’s voice mode does two things ChatGPT’s doesn’t:
- Renders the transcript inline as the conversation happens — both your words and the assistant’s. ChatGPT voice mode hides this, which is fine for casual chat and awful for any task you actually want to act on later.
- Has a system prompt tuned for brevity — the default agent answers tightly, no “Great question!” preamble, no closing flourishes you didn’t ask for.
The combined effect is that voice mode feels like talking to a competent assistant instead of a customer-service script.
The Saga vs ChatGPT voice comparison
| Dimension | Saga | ChatGPT |
|---|---|---|
| Real-time transcript | Yes, streaming | No, batch on stop |
| Domain vocab accuracy | High (Deepgram models) | Variable |
| Voice mode transcript | Visible in chat | Hidden |
| Response style | Terse by default | Verbose, often padded |
| Integrations | One-click via Composio | Limited / connector-based |
One-click integrations via Composio
Saga uses Composio under the hood for tool connectivity. The user experience is unusually clean: ask Saga to do something that needs a tool it isn’t connected to (“send a Slack message to my editor,” “what’s on my calendar this week”), and it responds with a one-click authorization link. Click it once, the tool is permanently available.
Connectors that ship out of the box include Slack, Discord, Google Calendar, Gmail, Notion, Asana, GitHub, and several hundred more. Multiple connectors can compose in a single prompt: “Read the latest brief in Notion, schedule a 30-minute call with the client tomorrow, and email them the invite.”
Compare to MCP-based setups where you typically download a server binary, configure JSON, restart the client, and authenticate manually. The link-and-authorize flow is what unblocks non-developer users.
The desktop app and the “voice operating system”
A separate desktop app extends Saga beyond the browser. Once installed, you can dictate into other applications — Cursor, VS Code, Slack, your email client — with the same real-time transcript quality. Deepgram describes this as a voice operating system: the same speech layer applies wherever you’re working.
Useful in practice for: long-form coding by voice in Cursor, generating meeting notes inline in your note app, drafting Slack messages without context-switching to a chat window.
Adding custom MCP servers
For tools that aren’t in the default Composio catalog — internal company APIs, custom databases, niche services — you can plug in your own Model Context Protocol (MCP) server. Standard MCP transport, so any server you build for Claude or another MCP-aware host works in Saga.
Practical: stand up an MCP server that wraps your company’s ticketing system, plug it into Saga, and your engineers can voice-create JIRA tickets while debugging.
Use cases worth setting up first
- Long-form dictation for blog posts, emails, brain-dumps. Real-time transcript means fewer rewrites.
- Calendar / task management by voice. “What’s on my calendar today?” “Move tomorrow’s standup to 10am.”
- Slack/Discord/email triage. “Summarize the last 10 messages in #engineering.”
- Domain-specific transcription. Medical notes, legal dictation, technical interviews — anywhere accurate vocabulary matters.
- Coding by voice. Through the desktop app into Cursor or VS Code.
❌ Common mistakes
- Using voice for short queries that you’d type faster anyway. Voice wins on anything over ~30 words; below that, type.
- Treating Saga as a replacement for ChatGPT chat. It’s a voice-first workspace — if you don’t use voice, you’re mostly paying for a generic chat UI.
- Connecting integrations you don’t need. Each one adds a surface area for prompt injection. Connect what you actually use.
- Skipping the desktop app. The browser version covers ~60% of the value; the desktop app gets you the rest.
- Treating it as a finished product. It’s evolving fast — check the changelog occasionally for new features and revisit your integrations.
💡 Pro tips
- Use dictation mode for first drafts of blog posts and emails. Speak fast, clean up after.
- Switch the underlying LLM when the task changes — Claude for nuanced writing, GPT-4.1 for general, smaller models for fast back-and-forth.
- Build a personal system prompt that captures how you talk and want responses — tone, length, formatting.
- Pair calendar + email integrations for one-shot “reschedule, notify, follow up” flows.
- Run the desktop app at startup so voice is available anywhere on the OS, not just in the browser tab.
Conclusion
Voice as an AI input modality has been “coming” for years. The reason it hasn’t crossed over is usually some combination of slow transcript, bad accuracy on real-world vocabulary, and verbose agents that waste your time. Saga is the first product that gets all three right at once — and the free price tag and one-click integrations make the trial cost approximately zero.
Worth trying if you spend any meaningful chunk of your day talking to AI or dictating text. Especially worth trying if you’ve given up on voice tools before — the bar has moved.
Related reading: how AI actually works (tokens & context) — MCP explained: build your own server — ElevenLabs review