Matrix vs Slack
Side-by-side trajectory, velocity, and editorial themes.
Matrix is in governance mode — Foundation board elections and conference logistics dominate the feed.
Matrix's recent feed is largely Foundation-governance content: the third Governing Board election cycle is underway (nominations 2–15 May, voting late May to mid-June, results 15 June), the 2026 Matrix Conference in Malmö opened Early Bird ticket sales, and the weekly 'This Week in Matrix' digests track community working groups and ecosystem updates. Product- and protocol-level announcements are notably absent from the recent batch, with most signal coming from Foundation member updates and event scheduling.
Matrix is leaning into its institutional identity rather than its protocol roadmap right now — formalizing governance through periodic elections, growing the Foundation's member base (connect2x as new Silver, with German healthcare TI-Messenger context), and putting weight behind in-person events. Read against the open-source-protocol backdrop, this is the consolidation phase between major spec or implementation pushes.
Once the election cycle closes and the Conference call-for-proposals concludes at the end of June, expect protocol and implementation news (likely from Element or other clients, or fresh Spec Core Team work) to return to the foreground. The composition of the new board may shape which working groups get priority next.
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 Matrix →
See more alternatives to Slack →