← Back to all sparks
LiveAgent logo

LiveAgent

SUPPORT
Velocity6.3

Helpdesk software with live chat and ticketing

LiveAgent launches Svelte 5 frontend migration and multi-model AI simultaneously.

multi-model-aimcp-integrationfrontend-modernizationcustomer-supportwhatsapp-channel
Current state
LiveAgent is in a structural consolidation phase with two parallel tracks running at once. The August 27 release was its most significant in the window — launching a Svelte 5 umbrella to progressively replace a decade-old GWT frontend, adding Gemini and Anthropic as selectable AI providers, shipping voice call transcription, and connecting Answer Suggestion to ticket context via MCP. The weeks since have been operational cleanup: fixing a DB query that hit 1.83 million rows per poll at 92% CPU, patching stuck-chat queue logic, and closing multiple MCP authorization gaps.
Where it's heading
Two architectural moves are now running in parallel. The GWT-to-Svelte 5 migration is a multi-year undertaking that will unblock faster UI iteration once the foundation is stable — the 'progressive replacement' framing means it won't land visibly for a while, but it signals intent to shed significant technical debt. The multi-model AI support (Anthropic, Gemini, OpenAI, MCP-based context) suggests LiveAgent is positioning AI as customer-configurable infrastructure rather than a fixed feature, letting enterprise buyers bring their own models.
Prediction
The next likely moves are broader Svelte-based agent panel rollout and tighter MCP governance — permission scopes and authentication hardening are already recurring themes in recent fixes. The WhatsApp channel has absorbed an unusually high volume of bug fixes, suggesting a WhatsApp reliability sprint or a targeted feature push (auto-replies just shipped) is close.

Recent moves

  1. 5d ago

    GA4 event tracking added; queued chat routing and FlowHunt chatbot fixed

    GA4 named events land for key agent-panel and channel integration pages, giving operators better adoption measurement. The more operationally significant fix is the available-agents queue bug: agents were not receiving queued chats due to stale queue entries that never cleared. A FlowHunt chatbot attachment crash and a rule editor TypeError on reopen are also addressed.

    View source ↗
  2. 9d ago

    Widget asset caching, DB performance fix, and security hardening

    The 5.68 branch gets the same DB and caching fixes as 5.67, plus a security improvement and corrections to ticket attachment and inline-image caching that were serving uncacheable responses. The parallel branch releases on the same day reflect LiveAgent's multi-track maintenance model for different customer tiers.

    View source ↗
  3. 9d ago

    92% DB CPU from full-table chat COUNT(*) fixed; widget asset caching hardened

    The critical fix here is a chat-list poll query that was scanning 1.83 million rows on every poll cycle, saturating the DB master at 92% CPU — a production stability issue, not a feature regression. Widget asset caching is also corrected (GWT permutations, fonts, SVG) to reduce redundant reloads. Part of the same infrastructure cleanup arc as the September 7 release.

    View source ↗
  4. 14d ago

    FlowHunt ticket ID passthrough; widget font and email decoding fixes

    FlowHunt now receives the ticket ID when a chatbot session starts — minor context enrichment for the integration. The remaining changes are internal: a FOIT fix for widget fonts, a security patch, and three bug fixes (agent name showing wrong after chat takeover, incoming email lost on subject-line decode error, and a chat button activation error).

    View source ↗
  5. 14d ago

    FlowHunt button fix and private API usage stats endpoint repaired

    The 5.68 branch gets the same baseline fixes as 5.67, plus a repair to the private API account-usage-stats endpoint that was missing authorization and breaking CRM usage reporting. The FlowHunt chat window button integration is also fixed. These are integration-plumbing corrections rather than visible improvements.

    View source ↗
  6. 20d ago

    Svelte 5 frontend, Gemini and Anthropic AI providers, and voice transcription ship together

    ⚡ SPARK

    The August 27 release is the most directional in this window: Svelte 5 launches as a progressive replacement for the GWT agent panel, Gemini and Anthropic join OpenAI as selectable AI providers, and voice call recording transcription ships as a first-class feature. Answer Suggestion now fetches ticket context via MCP instead of embedding it in the prompt — a structural change to how AI context is managed.

    View source ↗