agent-starter-react vs agent-starter-python
Two of the top voice and realtime, side by side: score, setup, license, activity and what each review found.
agent-starter-react
Next.js voice assistant frontend for LiveKit Agents
agent-starter-python
Python voice agent on LiveKit Agents with turn detection and simulations
| What we compare | agent-starter-react | agent-starter-python |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 56, popular | 27, niche |
| Freshness | 100, active | 100, active |
| Maintenance | 32, patchy | 24, weak |
| Easy to run | 33, some setup | 33, some setup |
| Agent-ready | 0, none | 85, ready |
| Facts from GitHub and the README | ||
| Stars | 949 | 264 |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Sep 2026 | Oct 2026 |
| Last release | None published | None published |
| Language | TypeScript | Python |
| Docker | No | Yes |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
agent-starter-react
Next.js app on LiveKit Agents UI components and the LiveKit JS SDK: welcome and session views, chat transcript, media tiles, camera, screen share, avatar rendering and five audio visualizer styles. A route at app/api/token issues LiveKit tokens from your project credentials. Frontend only; pair it with a LiveKit agent such as agent-starter-python or agent-starter-node.
Who it is for: Teams shipping a web UI for a LiveKit voice agent
Strengths
- Transcript, media tiles, avatar video and visualizers already composed
- Agents UI components are installed into components/ and editable in place
- Token route included; development token server also supported
- Matching Android, Swift, Flutter and React Native starters exist
Weaknesses
- Needs a separate LiveKit agent and a LiveKit Cloud or self-hosted server
- Token route has no authentication; add one before production
- No tests or Docker
- TypeScript
- Needs LiveKit Cloud or self-hosted LiveKit server, a LiveKit agent
- GitHub template
- env example file
agent-starter-python
uv-managed Python voice assistant on LiveKit Agents using LiveKit Inference for STT, LLM (default Gemma 4 31B) and TTS (default Fish Audio S2.1 Pro), with the LiveKit turn detector, adaptive interruption handling and noise cancellation. Ships a Dockerfile for LiveKit Cloud, an AGENTS.md with LiveKit skills, and scenarios.yaml simulations run in CI on merges to main. Backend only; pair with a LiveKit frontend starter.
Who it is for: Python teams building a production voice agent on LiveKit
Strengths
- Turn detector, adaptive interruption handling and noise cancellation preconfigured
- Conversation simulations in scenarios.yaml run in CI on merge to main
- Dockerfile and lk CLI flow for LiveKit Cloud deployment
- AGENTS.md and LiveKit skills for Claude Code, Cursor and Codex
Weaknesses
- Defaults rely on LiveKit Inference and Cloud noise cancellation; self-hosting needs plugin swaps
- CI simulations use real inference and need LiveKit secrets
- uv.lock is not tracked; commit it yourself
- No frontend; a separate client starter is required
- Python, LiveKit Inference (OpenAI, Cartesia, Deepgram and others), LiveKit realtime model plugins
- Needs LiveKit Cloud (or self-hosted LiveKit plus model plugins)
- GitHub template
- Docker
- env example file