Beeper vs Slack
Side-by-side trajectory, velocity, and editorial themes.
From chat aggregator to chat platform — Beeper is opening the bridge layer.
Beeper, now part of Automattic, ships a monthly changelog dominated by two parallel arcs: feature parity across the dozen-plus networks it bridges (delete chat, disappearing messages, group creation, Google Voice, LinkedIn on-device) and structural moves that change what Beeper is (On-Device connections, the 'Build a Beeper Bridge' invitation, AI-in-chat experiments, an MCP server). The product is mature on aggregation and now reaching for platform territory.
Two strategic shifts are running in parallel. First, Beeper is trying to convert itself from 'a company that engineers every bridge' into 'a platform where third parties contribute bridges' — a classic scaling move with all the usual moderation and trust questions. Second, by sitting at the universal chat aggregation point and exposing chat content to LLMs (in-app, MCP, Apple Intelligence), Beeper is building a surface no individual chat app can match. The on-device security upgrade is the trust foundation that makes both possible.
X Chat E2E support graduates from 'rolling out soon' to shipped within the next release cycle and becomes a public marketing beat. The bridge SDK will move from blog post to a packaged developer experience with documentation and at least one community bridge as proof point.
Slack rebuilds its developer platform around shipping in-channel AI agents.
Slack is well into a platform pivot, restructuring its CLI, Block Kit, and APIs around AI agent use cases. The 4.0.0 release in April formalized this with an agent-scaffolding command, sample agent apps, and a live-reloading dev workflow. Recent additions — streaming chat APIs, Card/Carousel/Alert blocks, and continued MCP server expansion — show the surface area for in-Slack agents widening fast.
The platform is shifting from 'agents can post messages' to 'agents are first-class UI citizens'. The new chat.startStream / chat.appendStream / chat.stopStream methods change what an agent reply looks like, and the Card and Carousel blocks hint at richer multi-turn agent flows. Security work on PKCE and optional scopes is keeping pace, which tells you third-party agent developers are the audience, not just first-party features.
Expect Slack to publish reference agents and likely a discovery or marketplace surface for agent apps within the next minor cycle, with streaming Block Kit becoming the canonical pattern shown in the docs.
See more alternatives to Beeper →
See more alternatives to Slack →