Reference

Agents

Agents are your governed digital workforce. Each one runs a published, immutable version, and by default every side-effecting action it proposes waits for human approval.

The agents list

The Agents page lists every agent in your organisation. Status tabs across the top filter by lifecycle state (Draft, Active, Paused and Archived), and the default view shows Active agents, so archived ones stay out of the way until you ask for them.

• Filter by name (search) and by type, and sort by name, status, current version, last run or created date. Sorting and filtering happen on the server, and every control is reflected in the URL, so a filtered view is shareable and bookmarkable.
• Each row shows the agent's name and slug, its type, status, current published version, and the status and time of its last run.
• Viewing the list requires the agents.view permission; the New agent button only appears if you hold agents.create.

Creating an agent

New agent opens the guided setup. It takes you from a description of the job to a published agent in six steps, and nothing goes live until you publish. Nothing is kept until you continue from Check the draft, which creates the agent. From then on you can leave with Finish later and pick it up under Finish setting up at the top of the agents list; each step is saved when you continue from it.

1. Describe the job. Say in a sentence or two what the agent should do, and the assistant drafts it once. Or start from one of the seven presets (Documentation, Research, Content, Reporting, Support, Sales or Compliance).
2. Check the draft. Change the name, what it's for, its instructions and its model. Nothing is created until you continue.
3. Choose what it can use. Each tool says whether it only reads, makes changes or always needs sign-off. If the job needs an app you haven't connected, you can connect it there (owners and admins), or ask an owner to.
4. Decide what needs your sign-off. Ask before every change (recommended) or Let low-risk changes happen on their own. You also choose who can approve and what happens if nobody decides. Reading never needs sign-off.
5. Try it on an example. A dry run shows exactly what the agent would do. Nothing is read from or changed in your connected apps; each change it would make says whether a live run would do it on its own or ask a person first. Your plan includes a daily number of dry runs, and dry runs and evaluations share a daily usage limit; both reset at midnight (UTC).
6. Publish. Check the summary and publish version 1. Publishing needs a dry run of exactly what you are publishing, and only owners and admins can publish — operators can send it to them instead.

Start from a blank editor

Know exactly what you want? Start from a blank editor (linked from the first step) is the full-editor route: choose a library preset or Start blank, name the agent, and you land in the version editor with draft version 1.

• Library presets pre-fill a working specialist configuration (objective, instructions and suggested tools) for a given type. The preset's built-in tools (documents and web) arrive already assigned; tools for an app (Gmail, Teamwork and so on) are highlighted in the version editor's Tools tab, to assign once the app is connected.
• Start blank gives you an empty definition with the default policies. You pick the closest library type and write the objective and instructions yourself.
• The slug is optional — a URL-safe identifier, unique within your organisation, generated from the name if you leave it empty.

The AI Agent Builder

The Builder is a chat-first way to author an agent by describing what you need in plain language. It interviews you, drafts an objective and instructions, suggests tools (showing each tool's risk level and side-effect flag) and proposes an approval policy. All of it is presented as a live draft preview as the conversation progresses. If voice is configured, you can also speak your message with push-to-talk; the transcript is shown for you to confirm or edit before it is sent.

• The Builder never auto-publishes. The draft preview carries a hand-off link into the same version editor used everywhere else, where a human reviews and publishes through the unchanged approval gate.
• It can also draft workflows (ordered, multi-agent sequences), handing them off to the workflow editor for human review and activation.
• Builder sessions and turns are gated by agents.create, and assistant usage is metered and capped by your plan and per-session limits.

Trust score

Every agent carries an advisory trust score: a single figure, computed from the agent's audit, run and evaluation evidence, that helps you judge how much it has earned your confidence. A compact gauge appears on the agent overview, deep-linking to the full breakdown.

• Scores fall into three bands: good (75 and above), caution (50–74) and poor (below 50). The card also shows a confidence percentage and the trend since the last computation.
• The score is read-only and explainable: the full panel breaks it into components, each linked to the evidence that produced it. It is recomputed on a schedule, not on demand. Until the first nightly sweep runs for a fresh agent, the panel shows an empty state rather than a guessed figure.
• The trust panel sits behind agents.view — if you can see the agent, you can see its trust.

The trust score is advisory. It informs your judgement and never changes the approval gate by itself. What does change it is the agent's sign-off setting (for example, letting low-risk changes happen on their own) or earned autonomy, which you turn on separately.

The agent overview

An agent's overview page is its hub. From here you can:

• Run the agent (requires runs.execute, and only while it is active with a published version) or Dry-run it in the sandbox. The agent reasons for real, but every change and every call to a connected app, MCP server or custom tool is simulated, with no approvals and no real actions. Dry runs don't use your monthly run allowance, but your plan includes a set number each day.
• Open the draft or start a new draft version (agents.update), and edit the agent's metadata.
• Browse the full version history, compare any two versions field-by-field, and review recent runs (runs.view).
• Jump to Performance, Evaluations, Trust and Earned autonomy, or submit the agent as a marketplace template (agents.publish) — a config-only snapshot, never credentials or tenant data.

Published versions are immutable: every change becomes a new version, and the whole lifecycle is recorded in the audit log.

Next steps