Superhuman
Superhuman rebuilt its mobile apps and wired every inbox into AI assistants — the email client is becoming a suite.
A side-by-side editorial comparison of Element and LobeHub — release velocity, themes, recent moves, and the top alternatives to consider.
Element rebuilds its timeline with MVVM architecture while cutting legacy OS support in v1.12.28.
Element, the open-source Matrix messaging client, ships on a stable two-week release cadence and is currently at v1.12.28. The project is mid-way through a multi-part Timeline MVVM refactor (parts 1 and 2 in v1.12.26 and v1.12.27), restructuring the core room timeline component. The v1.12.28 release raises the minimum glibc requirement to 2.34, ending support for Debian bullseye and Ubuntu releases older than 22.04.
LobeHub turned its chat client into an agent operator that delegates to Claude Code and Codex.
Five weeks of weekly releases moving in one direction. CAO, the Chief Agent Operator, turns short exchanges into agents that check their own work, decide the next step and continue without prompting, pausing only when a decision genuinely needs a person. Agent Gateway moved agent execution to the server with WebSocket streaming and session resume across disconnects. Server-side human approval landed for agent actions, alongside a personalised Daily Brief and Notion-style document history. Most recently, coding agents themselves became delegable: Claude Code and Codex are created and controlled from inside LobeHub on desktop, with agent-grouped topics and a Review tab aggregating bulk git diffs. Model and provider additions ride along each release.
Element, the open-source Matrix messaging client, ships on a stable two-week release cadence and is currently at v1.12.28. The project is mid-way through a multi-part Timeline MVVM refactor (parts 1 and 2 in v1.12.26 and v1.12.27), restructuring the core room timeline component. The v1.12.28 release raises the minimum glibc requirement to 2.34, ending support for Debian bullseye and Ubuntu releases older than 22.04.
The Timeline MVVM series is the defining architectural investment of this window — replacing the legacy timeline rendering with a proper view-model separation. This is foundational work that typically precedes faster feature delivery on the timeline surface (thread UX, call integration, richer message types). Parallel work promoting Custom Themes to devtools and updating bundle configurations signals cleanup of the extension and theming surface alongside the core refactor.
A Timeline MVVM part 3 or final integration is the immediate next step; once complete, expect improved thread UX or voice/video call timeline integration as the first beneficiaries of the new architecture.
Five weeks of weekly releases moving in one direction. CAO, the Chief Agent Operator, turns short exchanges into agents that check their own work, decide the next step and continue without prompting, pausing only when a decision genuinely needs a person. Agent Gateway moved agent execution to the server with WebSocket streaming and session resume across disconnects. Server-side human approval landed for agent actions, alongside a personalised Daily Brief and Notion-style document history. Most recently, coding agents themselves became delegable: Claude Code and Codex are created and controlled from inside LobeHub on desktop, with agent-grouped topics and a Review tab aggregating bulk git diffs. Model and provider additions ride along each release.
The client is becoming a control plane rather than a chat window. Server-side execution, session resume, human approval gates and self-directed agents are the components of something that runs work while nobody is watching — and delegating to Claude Code and Codex means LobeHub is not trying to be the best coding agent, it is trying to be where you supervise the ones that exist. The Review tab reads that way too: diff review is a supervision surface, not an authoring one.
Expect more third-party agents to become delegable alongside Claude Code and Codex, and the approval flow to extend into the coding-agent path where reviewing a diff is the natural gate.
Other Comms 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 Element or LobeHub.
Superhuman rebuilt its mobile apps and wired every inbox into AI assistants — the email client is becoming a suite.
Chatwoot is building an AI-first support platform, with Captain gaining audience targeting and macro automation reaching the keyboard-native workflow.
Signal adds granular notification controls: badge content, muted threads, restore defaults
Zoho Cliq 7.0 bets on AI conversation summaries and Neat hardware to close the gap with enterprise messaging platforms
Krisp adds deepfake detection and expands Voice Translation as its Call Center AI platform deepens enterprise compliance tools.
Netcore's recent entries are blog content, not product releases — the signal is a BFSI and ecommerce vertical sales push.
See all Element alternatives → · See all LobeHub alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Element is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. Element is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top Element alternatives in Comms are ranked by recent ship velocity. Browse the "Element alternatives" section above for the current picks, or visit /alternatives/element-web for the full list with editorial commentary on each.
Top LobeHub alternatives in Comms are ranked by recent ship velocity. Browse the "LobeHub alternatives" section above for the current picks, or visit /alternatives/lobehub for the full list with editorial commentary on each.