jarvis vs agent-starter-react

Two of the top projects in Voice and realtime, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.

33rd of 18 in Voice and realtime

jarvis

Voice interface that brainstorms specs and drives Claude Code sessions on macOS

#55th of 18 in Voice and realtime

agent-starter-react

Next.js voice assistant frontend for LiveKit Agents

Verdict

jarvis ranks higher, 58 to 54. Of the 4 score parts we measure for both, jarvis leads on 2, agent-starter-react on 1 and 1 is even.

  • Adoptionjarvis leads by 3 points, 42 to 39: close to even.
  • FreshnessEven at 100.
  • Maintenanceagent-starter-react leads by 2 points, 40 to 38: close to even.
  • Agent-readyjarvis leads by 40 points, 40 to 0: a wide gap.

Pick jarvis if you are

Claude Code users on macOS who want to drive builds by voice

  • Runs on the Claude subscription login; strips ANTHROPIC_* env vars so no API key is billed
  • Watches all local Claude Code sessions and can answer a Terminal permission prompt

Pick agent-starter-react if you are

Teams shipping a web UI for a LiveKit voice agent

  • Transcript, media tiles, avatar video and visualizers already composed
  • Agents UI components are installed into components/ and editable in place
jarvis vs agent-starter-react: score parts and facts
What we comparejarvisagent-starter-react
Score parts, out of 100
Adoption42, known39, known
Freshness100, active100, active
Maintenance38, patchy40, patchy
Agent-ready40, minimal0, none
Facts from GitHub and the README
Stars1k969
Licensecustom license (read the license)MIT (permissive)
Last commitSep 2026Oct 2026
Last releaseSep 2026None published
LanguagePythonTypeScript
DockerNoNo
GPUNot neededNot needed
arm64 or Apple SiliconNot statedNot stated

jarvis

JARVIS is a voice front end for Claude Code on macOS. A long-lived `claude -p` process on your own subscription brainstorms a design with you, writes it to a spec file in the project, then starts Claude Code runs that plan, review and execute it. It also watches every Claude Code session on the machine and says aloud which ones are waiting on you. Runs are logged in SQLite and shown on a local dashboard.

Who it is for: Claude Code users on macOS who want to drive builds by voice

Strengths

  • Runs on the Claude subscription login; strips ANTHROPIC_* env vars so no API key is billed
  • Watches all local Claude Code sessions and can answer a Terminal permission prompt
  • Every run is recorded in SQLite with prompt, status, tokens and events; six-tab dashboard
  • Extra tools via any MCP server in connections.json; other MCP configs are ignored

Weaknesses

  • macOS only; terminal control, screenshots and notifications depend on AppleScript
  • Requires Chrome for Web Speech API; no server-side transcription fallback
  • Fish Audio API key is required; without it replies appear only as text
  • Spawned runs use --dangerously-skip-permissions by default, with full privileges on your machine
  • Python, Claude (Sonnet by default, via Claude Code)
  • Needs Claude Code CLI 2.1.224+ (logged in), Fish Audio API key, Google Chrome, Python 3.11+, Node.js 18+, Playwright Chromium, OpenSSL (self-signed certs)
  • env example file

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

More in Voice and realtime

Building with these?

We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.