Codex is OpenAI's agent for getting work done on a computer, and in 2026 it is openly courting people who do not write code: it asks what kind of work you do, ships plugins for marketing and finance, and knowledge workers are now about a fifth of its users, growing three times faster than developers. ChatGPT Business is how a team is supposed to get it: $20 per seat per month on annual billing ($25 monthly), two-seat minimum, Codex included. A room in muti is the other way: one developer's Codex, on their machine, that the marketing lead, the ops person and the founder can send work to from Slack or the web, with the developer approving what runs.
If your team has one person who lives in Codex and six who want its output, the room costs one seat instead of seven.
An operations teammate attaches a vendor export and asks the team's Codex agent to dedupe it; the request runs on the developer's Mac mini, and a shell command pauses for the developer with Allow, Allow always and Deny.
Why Codex for non-technical teammates is harder than it looks
Codex is genuinely usable by a marketer now. What is not easy is everything around it:
- A seat each. Every person who wants to ask needs a Business seat, a laptop with Codex installed and signed in, and enough patience to learn where the files go.
- A machine each. Codex works in a directory on a computer. The marketer's laptop has none of the repositories, data exports, API keys or internal tools the job needs. The developer's does.
- Permissions each. Every seat decides for itself what Codex may run. There is no one in the loop when the ops lead's Codex reaches for a delete.
The room removes all three. The work runs where the tools and data already are, under one person's account, with that person able to say no.
What it looks like for the asker
Mia in operations opens Slack and messages the agent, which has its own name and avatar there, or opens the room in a browser. She attaches the vendor export and writes what she wants in plain language. Nothing to install, nothing to sign into beyond the workspace she already uses.
Then she watches. The agent reads the file, writes a small script, runs it, and pauses on the shell command because the developer has not allowed python3 for this agent yet. The developer gets the card, on the web, on their phone or in their own Slack DM, and presses Allow always. The script runs, the cleaned CSV comes back into the thread, and the next time Mia asks, nothing pauses.
For Mia, Codex became a colleague she can message. For the developer, it stayed their tool.
What the developer keeps
- The account. The subscription, the sign-in and the Codex client are the developer's. Nobody else holds a credential.
- The boundary. The agent is pinned to one directory. Mia's request cannot read the developer's other projects, keys or mail. Rooms do not leak into each other.
- The veto. Pushes to shared branches, destructive deletes, privilege escalation, publishing and anything touching credential paths always pause, and "Allow always" is never offered for them. Everything else becomes a rule after the first approval.
- The record. Every request has an id, a requester, an approver, a tool-by-tool timeline and a cost. When someone asks what the team did with Codex last month, the answer is a page, not a guess.
Editing the agent: the working directory it is pinned to, its permission mode, and the standing rules created by Allow always, each revocable.
Cost for a seven-person team
One engineer, six people who ask.
The engineer will use more of their plan than before, because six people's errands now run through it. Cost per request is shown next to each request so nobody has to guess; when the errands start to crowd out the engineer's own work, that is the moment to add a second producer seat. A second seat, not a seventh.
Where the line is
ChatGPT Business exists for a reason, and OpenAI's terms prohibit sharing credentials and reselling access. A room does not share a credential: the developer signs in, the developer's Codex runs, on the developer's machine, and other people's requests are work the developer chose to accept and can stop at any time. If your six askers become six daily users, buy them seats, that is what the plan is for. If you need workspace-level data controls for every person, buy Business. The room is for the shape most small teams actually have: one instrument, many errands.
Frequently asked questions
Does the asker need a ChatGPT account? No. They need a muti account, or just Slack if the agent has a bot there.
What can the agent see of the asker's file? The attachment is downloaded into the agent's working directory for that request and deleted when the request ends. It is not kept on the machine.
Can the developer see what people asked? Yes, everything: the request, the timeline, the result, the cost. That visibility is the deal. Askers see only the rooms they are in.
Does this only work with Codex? No. The same room runs Claude Code, Cursor, OpenCode and others; see the cheaper Claude Team alternative for the Claude version of this arithmetic.
Give Codex to the one person who uses it. Give the other six a way to ask.
Published