Slack vs Respond.io

Slack's developer platform runs two tracks. The agent build-out has produced a spark roughly every two weeks since June — MCP client, a skills plugin targeting Claude Code and Cursor, and Slack Code — and now has a consolidation date attached: assistant_view is deprecated in February 2027, replaced by an Agent Sessions API. The second track is platform administration and tooling, and this window belongs to it: Marketplace submissions again require at least ten installed active workspaces, held throughout the review, after a period at a lower temporary threshold. The CLI has shipped three times since late July.

The install requirement moving back up is a distribution decision arriving in the middle of a platform push, and the two point the same way. Slack is making it easier to build agents and harder to list one, which favours developers who already have distribution — existing workspace tools and vendors — over a new app hoping the Marketplace supplies its first users. Combined with the assistant deprecation and the Agent Sessions API, the platform is narrowing on one agent surface and one class of builder rather than widening the funnel.

The threshold is described as a return from a temporary lower bar rather than a new policy, so the open question is what replaces the Marketplace as the discovery path for an app that cannot reach ten workspaces on its own. These entries do not answer it.