← Back to home
Comparison · ai-assistants

Cherry Studio vs LiveKit Agents

A side-by-side editorial comparison of Cherry Studio and LiveKit Agents — release velocity, themes, recent moves, and the top alternatives to consider.

Cherry Studio vs LiveKit Agents: at a glance

FeatureCherry StudioLiveKit Agents
Sectorai-assistantsai-assistants
Velocity score5.05.0
Sparks · 30d00
Top themesdesktop-ai-client, v2-rewrite, data-migration, llm-providersvoice-agents, provider-plugins, turn-detection, weekly-releases
Last editorial update1d ago5d ago
WebsiteVisit →Visit →

What is Cherry Studio?

The v2 rewrite has shipped; Cherry Studio is back to patch releases.

Cherry Studio spent late July running a v2.0.0 release train - three betas and five release candidates inside two weeks - to land a rewrite that had merged into main while v1 code still sat alongside it. The August entry is v2.0.6, a single Files-page bug fix, which puts the product past the rewrite and into ordinary patch cadence. The feed never carried a v2.0.0 GA note: it jumps from rc.5 on 4 August straight to v2.0.6 on 17 August.

Read the full Cherry Studio trajectory →

What is LiveKit Agents?

LiveKit Agents ships weekly, and the work is nearly all provider breadth and failure paths.

The two newest entries are bare release tags — 1.6.10 and a 1.6.11 release candidate — with no notes. The releases with content follow one pattern: add speech and avatar vendors (Deepgram Flux, Bland TTS, Spatius avatars, Phonic and Smallest STT options), then fix the ways conversations go wrong. Endpointing and turn detection recur constantly — max_delay held constant under dynamic endpointing, primary speaker preserved through unattributed segments, an Ink-2 speech-onset delay that pushed back STT interruptions. 1.6.8 deprecates the console and dev modes in favour of the lk agent CLI.

Read the full LiveKit Agents trajectory →

Cherry Studio vs LiveKit Agents: editorial side-by-side

C
Cherry Studio
AI-ASSISTANTS
5.0

The v2 rewrite has shipped; Cherry Studio is back to patch releases.

◆ Current state

Cherry Studio spent late July running a v2.0.0 release train - three betas and five release candidates inside two weeks - to land a rewrite that had merged into main while v1 code still sat alongside it. The August entry is v2.0.6, a single Files-page bug fix, which puts the product past the rewrite and into ordinary patch cadence. The feed never carried a v2.0.0 GA note: it jumps from rc.5 on 4 August straight to v2.0.6 on 17 August.

◆ Where it's heading

The release train's substance was migration safety rather than new capability - preserving model endpoint routing, stopping table-recreate migrations from silently deleting child rows, keeping Claude session and workspace continuity, restoring guarded v1 style migration. Provider work continued underneath it, with Gemma 4 thinking in Ollama, a Radeon Cloud integration, and a configurable default endpoint. The priority through the whole train was getting existing users across the v1/v2 boundary with their data and settings intact.

◆ Prediction

With v2 out and the patch stream started, the next entries should shift back from migration repair to provider and agent features - the strand that kept moving quietly through the rc series.

L
LiveKit Agents
AI-ASSISTANTS
5.0

LiveKit Agents ships weekly, and the work is nearly all provider breadth and failure paths.

◆ Current state

The two newest entries are bare release tags — 1.6.10 and a 1.6.11 release candidate — with no notes. The releases with content follow one pattern: add speech and avatar vendors (Deepgram Flux, Bland TTS, Spatius avatars, Phonic and Smallest STT options), then fix the ways conversations go wrong. Endpointing and turn detection recur constantly — max_delay held constant under dynamic endpointing, primary speaker preserved through unattributed segments, an Ink-2 speech-onset delay that pushed back STT interruptions. 1.6.8 deprecates the console and dev modes in favour of the lk agent CLI.

◆ Where it's heading

This is a maintenance train rather than a roadmap: breadth across providers plus relentless correctness work on turn-taking, which is where voice agents actually fail. The one demand on users in the window is the CLI migration. Cadence is roughly weekly and the contributor list is largely external — vendors landing their own plugins.

◆ Prediction

More provider plugins and more endpointing fixes; the deprecated console and dev modes are the next thing likely to be removed outright.

Alternatives to Cherry Studio and LiveKit Agents

Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Cherry Studio or LiveKit Agents.

See all Cherry Studio alternatives → · See all LiveKit Agents alternatives →

Recent activity from Cherry Studio and LiveKit Agents

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoCherry StudioFiles page keeps the upload button in every category
  2. 5d agoLiveKit Agentslivekit-agents@1.6.11.rc1 (#6847)
  3. 6d agoLiveKit Agentslivekit-agents@1.6.10
  4. 11d agoLiveKit AgentsAgents 1.6.9 adds Deepgram Flux and Bland TTS plugins
  5. 14d agoCherry Studiorc.5: Gemma 4 thinking in Ollama, anchor rail navigation
  6. 15d agoLiveKit AgentsAgents 1.6.8 deprecates console/dev modes for the lk agent CLI
  7. 17d agoCherry Studiorc.4: Radeon Cloud provider and configurable endpoints
  8. 19d agoCherry Studiorc.3: knowledge, export, and accessibility fixes
  9. 20d agoCherry Studiorc.2: migration fixes protect routing and child rows
  10. 21d agoCherry Studiorc.1: packaging and onboarding fixes
  11. 25d agoLiveKit AgentsAgents 1.6.7 adds Spatius avatar plugin, fixes endpointing delays
  12. 1mo agoLiveKit AgentsAgents 1.6.6 pools FishAudio sockets to fix cold-start crackle

Frequently asked questions

What is the difference between Cherry Studio and LiveKit Agents?

They serve adjacent needs but don't currently overlap on shipped themes. Cherry Studio and LiveKit Agents are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Cherry Studio better than LiveKit Agents?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cherry Studio and LiveKit Agents are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.

What are the best alternatives to Cherry Studio?

Top Cherry Studio alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Cherry Studio alternatives" section above for the current picks, or visit /alternatives/cherry-studio for the full list with editorial commentary on each.

What are the best alternatives to LiveKit Agents?

Top LiveKit Agents alternatives in ai-assistants are ranked by recent ship velocity. Browse the "LiveKit Agents alternatives" section above for the current picks, or visit /alternatives/livekit-agents for the full list with editorial commentary on each.