They didn't call it that. The pitch is "Workspace Agents" — shared team agents that live in Slack, run on a schedule, and operate within your org's permission scope. Powered by Codex, launched Wednesday for Business, Enterprise, and Edu plans. Free until May 6, then credit-based.
The Custom GPT layer has been dead on arrival at every company I've talked to for a year. I'd ask teams "do people use your custom GPTs?" and the honest answer was always some flavor of "not really." Not because the models weren't capable. Because nobody logs into a GPT Store to get work done. You do work in Slack, in your ticketing system, in your CRM. A separate chat UI was the wrong distribution.
Workspace Agents fix that by showing up where the work already happens. An agent that picks up a Slack request is 10x more useful than the same agent hidden inside a tab you have to remember to open. Distribution was always the product problem, not capability.
We've been building exactly this shape at Upswing — hotel ops agents that live inside each property's own messaging tool rather than behind our dashboard. The usage delta between "log into our portal" and "DM the agent in Slack" isn't 2x. It's closer to 20x. Once the agent is in the channel, people treat it like a teammate. Once it's behind a login, they forget it exists.
The larger shift: Custom GPTs felt like Clippy — a novelty parked in the corner of a tool. Workspace Agents feel like headcount. Shared, scheduled, role-scoped, permissioned. This is the form factor enterprises will actually adopt.
My bet: six months from now, "workspace agent" is the default unit of internal automation, and the GPT Store is a footnote.
Top comments (0)