01
The chat operates
Cursor, Claude, or Slack. They ask and they do. They do not say yes.
Agents, collaborators, providers
Nothing changes in production unless it passed through Operator.
The chat operates. A named human says yes. GitHub lets the merge through; Operator lets the change through. If someone reached main anyway, it stays in view.
- Who asks
- A client or a collaborator. The request comes in.
- Who operates
- An agent, a collaborator, or a provider. The model does not approve.
- Who looks
- A named human, by email. Not the PR approve. If you add them, they have to look. If not, whoever operates can ship to production.
How it works
One Operator for every system several people work on, or an agent.
If the work lives in the chat, production belongs to the chat. Here the change closes and stays seen.
02
A human looks
They see what the asker missed, and what the agent could not see alone.
03
The receipt stays
Who asked, who operated, who looked, the sha. That can be shown outside.
The cut
GitHub lets the merge through. Operator lets the change through.
Branch protection is not a look. Yes is a person, by email. If someone reached main anyway, they have to explain it here.
Unique writer, or trail only
If main is locked, only Operator writes. If GitHub cannot lock it, Operator still records what landed. You can see which of the two you are buying.
The deliverable is the receipt
The receipt is the change: trail, sha, who looked. The month is billed together. Use the system.
The chat they already use
Operator is not another model.
The request comes in through the chat. Permission to write production stays here.
Claude
Cursor
OpenAI
Grok
Gemini
Copilot
Perplexity
Windsurf
Slack
GitHub
Whatever comes next, if it can hit an API, it is in.
Anyone can move work. Nobody does it blind.
The request comes in. Someone operates. Whoever looks sees what the asker missed, and what the agent could not see alone. Production, and whatever comes after.
If you do not have access yet, talk to WakeUp Labs.