Gemini
Gemini is adding host surfaces faster than it documents them — Chrome, macOS, robots, video.
A side-by-side editorial comparison of LiveKit Agents and Docling — release velocity, themes, recent moves, and the top alternatives to consider.
LiveKit Agents keeps absorbing voice vendors while turn detection stays the real product
Releases land roughly weekly and most of the diff is provider plugins: Deepgram Flux and Bland TTS arrived in 1.6.9, with Phonic, FishAudio, Cerebras, AssemblyAI, ElevenLabs and Gemini all tuned across the window. Underneath that churn the recurring engineering problem is turn-taking, with speech onset, endpointing delay, interruption handling and tool-call preservation accounting for most of the fixes from 1.6.4 onward. 1.6.8 also deprecates the console and dev run modes in favor of a single lk agent CLI.
Docling is turning a document parser into a general ingestion layer — video now included.
Docling ships a tight semantic-release train, roughly weekly, where each version pairs one or two format or pipeline features with a long tail of fidelity fixes. The fixes are the real product: reading order in docx lists, section headers and footers, ODF text after inline elements, PPTX shapes in visual order, dehyphenation of hard continuations. Alongside the library, a service layer is taking shape — chunking options and targets, PDF heading-level inference, and batch connector sources are all being exposed through the service API rather than only the Python interface.
Releases land roughly weekly and most of the diff is provider plugins: Deepgram Flux and Bland TTS arrived in 1.6.9, with Phonic, FishAudio, Cerebras, AssemblyAI, ElevenLabs and Gemini all tuned across the window. Underneath that churn the recurring engineering problem is turn-taking, with speech onset, endpointing delay, interruption handling and tool-call preservation accounting for most of the fixes from 1.6.4 onward. 1.6.8 also deprecates the console and dev run modes in favor of a single lk agent CLI.
The bet is breadth: be the layer that speaks to every STT, TTS and LLM vendor so the model choice stays with the developer rather than the framework. That makes turn detection the part LiveKit actually owns, which is why the Turn Detector shipped as a versioned component in 1.6.1 and why endpointing keeps getting revisited. Tooling is consolidating in the same direction, moving from per-script Python entry points to one CLI.
The deprecated console and dev modes should be removed once the lk agent migration has had a release or two to settle. Expect the plugin list to keep growing and the turn-detection path to keep absorbing fixes, since that is where provider differences surface.
Docling ships a tight semantic-release train, roughly weekly, where each version pairs one or two format or pipeline features with a long tail of fidelity fixes. The fixes are the real product: reading order in docx lists, section headers and footers, ODF text after inline elements, PPTX shapes in visual order, dehyphenation of hard continuations. Alongside the library, a service layer is taking shape — chunking options and targets, PDF heading-level inference, and batch connector sources are all being exposed through the service API rather than only the Python interface.
Format coverage is expanding outward from PDF and Office into anything an enterprise has lying around: legacy binary Office formats, an EBCDIC backend for mainframe data, and video as a declared input format with ASR presets behind it. The model layer is broadening in parallel — RapidOCR refactored to resolve all PP-OCR languages, a layout-driven OCR pipeline with configurable modes, and VLM output now carrying OpenAI logprobs through to predictions. Packaging is being taken seriously too, with chart extraction lazy-loaded so the slim build needs no torch, and agent skills shipped for driving Docling directly.
With VideoPipeline declared and ASR presets in place, the next step is likely fleshing out what a video actually converts into — transcript segments tied to frames — rather than adding another document format.
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 LiveKit Agents or Docling.
Gemini is adding host surfaces faster than it documents them — Chrome, macOS, robots, video.
LangGraph's real work is happening in the checkpoint layer, not the graph runtime
Comet is annexing AI cost governance from the observability side.
Two platform rewrites in four months, then the feed went quiet.
The feed is an SEO content mill, not a changelog — no Botsify release has been published here.
OpenRouter is moving past routing tokens into telling you which model to use
See all LiveKit Agents alternatives → · See all Docling alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Docling is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Docling is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
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.
Top Docling alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Docling alternatives" section above for the current picks, or visit /alternatives/docling for the full list with editorial commentary on each.