Agents

Built-in agents

Every organisation starts with a working set of agents, not an empty catalog. They are ordinary org-ring registry agents โ€” versioned, governed and editable โ€” seeded at sign-in, visible from every workspace, and addressable as @slug from birth.

Who you get on day one

AgentHandleForAutonomy
Orchestrator@orchestratorDeciding who answers; planning goals that need several agentssupervised
Assistant@assistantEverything no specialist ownssupervised
ITHelp@ithelpRaising IT ticketssupervised
IT Fulfilment@it-fulfilmentCarrying an approved change out in the admin consolesupervised
Travel Desk@travel-deskBusiness travel, against policy, through approvalsupervised
Market Watcher@market-watcherPrices, charts and the news behind a movesupervised
Weather Agent@weather-agentForecasts, drawn as chartssupervised
Document Author@doc-authorDrafting a document with you in a live previewsupervised
Finance Agent@finance-agentExpenses, allowances, approval limitssupervised
HR Agent@hr-agentLeave, working patterns, reviews, benefitssupervised
Legal Agent@legal-agentNDAs, signing authority, retentionsupervised
Procurement Agent@procurement-agentPurchase orders, quotes, vendor checkssupervised
Your Avataryour email nameAnswering about you, and for yousupervised

Turned on when you want them

AgentHandleForHow
Deep Research@deep-researchLong investigations that outlive a chat turnBuild โ†’ Capabilities
Agent Architect@architectDrafting a new agent with youBuild โ†’ Capabilities
Google Workspace, Microsoft 365, Slack Assistant, Zoom Meetings@google-workspace, @microsoft-365, @slack-assistant, @zoom-meetingsYour calendar and meetings, mail, files, Slack channels and ZoomSeeded once the connector has an OAuth client

What they have in common

One org-ring copy

Not one per workspace. An org-ring agent is visible from every workspace by design โ€” that is ring visibility doing its job.

A handle from birth

Every agent is addressable as @slug. Mentioning one dispatches the whole message to it before any model call โ€” explicit beats inferred.

Supervised by default

Reads run; writes pause for a person. Only Deep Research ships above that, and even it parks on a destructive call.

No author

Built-ins carry no created_by โ€” they belong to the platform, not to whichever member's sign-in happened to seed them.

Yours to change

Edit the definition, publish a version, roll back. The platform stops re-publishing its own copy once you have taken it over.

Governed like any other

DLP, tool and model allowlists, budgets, approvals, kill switches and the audit log apply identically. Built-in is not a privilege.

How a message finds the right one

You never have to pick. A chat message reaches the Orchestrator, which decides whether one agent owns the request โ€” by an @handle you typed, by a person's name, by a tagged desk, or by a lite-tier classifier that can see every specialist's tools โ€” and otherwise plans the goal across several. Naming an agent always wins.

Replacing a built-in with your own Routing to the support, travel and markets desks is by tag, not by slug. Build your own desk, tag it support, travel or markets, and the router follows it โ€” no platform change, and the built-in can be retired.