← Back to home
Comparison · Comms

LobeHub vs Slack

A side-by-side editorial comparison of LobeHub and Slack — release velocity, themes, recent moves, and the top alternatives to consider.

LobeHub vs Slack: at a glance

FeatureLobeHubSlack
SectorCommsComms, Collab
Velocity score0.06.3
Sparks · 30d01
Top themesagent orchestration, coding agents, self-directed agents, approval flowagents, a2a, mcp, slackbot-skills
Last editorial update3mo ago3d ago
WebsiteVisit →Visit →

What is LobeHub?

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.

Read the full LobeHub trajectory →

What is Slack?

Slack now hosts any A2A agent without Slack-specific code.

Slack's developer channel is almost all agent plumbing. On 10 November Slack became an A2A (Agent2Agent) client: a team hosts its own agent, publishes an Agent Card, and Slack calls it when people talk to it, with no request URL, event handling or Slack-specific logic. This follows Slackbot skills managed through Web API methods, a Slack CLI that points coding agents to the Slack MCP server, and a new requirement that Work Objects embeds allow the slack-mcps.com frame ancestor.

Read the full Slack trajectory →

LobeHub vs Slack: editorial side-by-side

L
LobeHub
COMMS
0.0

LobeHub turned its chat client into an agent operator that delegates to Claude Code and Codex.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Slack logo
Slack
COMMSCOLLAB
6.3

Slack now hosts any A2A agent without Slack-specific code.

◆ Current state

Slack's developer channel is almost all agent plumbing. On 10 November Slack became an A2A (Agent2Agent) client: a team hosts its own agent, publishes an Agent Card, and Slack calls it when people talk to it, with no request URL, event handling or Slack-specific logic. This follows Slackbot skills managed through Web API methods, a Slack CLI that points coding agents to the Slack MCP server, and a new requirement that Work Objects embeds allow the slack-mcps.com frame ancestor.

◆ Where it's heading

Slack is lowering the cost of putting outside agents in front of its users: first skills as code, then MCP pointers for coding agents, now a standard protocol in place of the Slack app model for agents. The platform is positioning itself as the place where agents built anywhere meet the people who use them.

◆ Prediction

Expect more A2A follow-ups, such as agents appearing in Slackbot or skills surfaces and richer Agent Card features, given how fast the agent releases have stacked up since October.

Alternatives to LobeHub and Slack

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 LobeHub or Slack.

See all LobeHub alternatives → · See all Slack alternatives →

Recent activity from LobeHub and Slack

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

  1. 4d agoSlackBring your A2A agents to Slack ⚡
  2. 8d agoSlackWork Objects embeds require the slack-mcps.com frame ancestor
  3. 10d agoSlackSlack CLI 4.13 tells coding agents about Slack MCP and Skills
  4. 10d agoSlackSlack Skills Plugin installs in Claude Code from its own marketplace
  5. 12d agoSlackUpdated low-usage submission criteria for Slack Marketplace apps
  6. 15d agoSlackSlack CLI 4.12.0, the fourth CLI release in October
  7. 6mo agoLobeHubDelegate Claude Code and Codex ⚡
  8. 6mo agoLobeHubClaude Code & Codex on Desktop
  9. 6mo agoLobeHubDaily Brief, Document History & Approval Flow
  10. 7mo agoLobeHubAgent Gateway & Customizable Sidebar
  11. 7mo agoLobeHubAI Auto-Completion & Real-Time Gateway

Frequently asked questions

What is the difference between LobeHub and Slack?

They serve adjacent needs but don't currently overlap on shipped themes. Slack is currently shipping more aggressively (velocity 6.3 vs 0.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.

Is LobeHub better than Slack?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Slack is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.

What are the best alternatives to LobeHub?

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.

What are the best alternatives to Slack?

Top Slack alternatives in Comms are ranked by recent ship velocity. Browse the "Slack alternatives" section above for the current picks, or visit /alternatives/slack for the full list with editorial commentary on each.