Build
Describe the job. Build the agent.
Write what you want done in the same words you would use to brief a new starter. The studio turns that into an agent with a trigger, a set of tools, a permission list, an escalation rule and a named owner — and shows you all five before anything runs.
You write a sentence, not a flowchart
No canvas, no nodes to drag, no branching diagram to maintain. A schedule, a condition and an escalation fit in one sentence, which is how people actually describe work.
Nothing is deployed from a description alone
The studio proposes; you approve. Every agent passes through a review screen that states its permissions in full, and that screen cannot be skipped — not by a template, not by the marketplace, not by the API.
The structured version is the real one
Your sentence is not the agent. It produces a manifest with explicit tools and grants, and that manifest is what executes — so the agent's behaviour does not drift as a model changes underneath it.
In this area
6 pages under Agent Studio.
Each one is its own surface in the product, and each one is here because it does something the others do not.
Describe the job
Write the job in plain words. No canvas, no nodes.
ReadWhat gets built
The five things a sentence becomes, all visible before deploy.
ReadGuided creation
Five questions, in the order they actually matter.
ReadReview before deploy
The screen that cannot be skipped.
ReadVersions and rollback
Agents version like software, and roll back like it too.
ReadOwnership
Every agent has a human owner. No orphans.
ReadThe rest of the platform
This is one part of one loop.
Give AI a job.
Build an agent, choose what it can access, define what it may do, and deploy it to work safely across your business.
No code required · Full SDKs and API · Stop any agent instantly · [email protected]