Skip to main content
An agent is the AI that reads your request, uses your connections to look things up, and answers or acts. Every workspace has one built-in agent, CloudThinker, which can split big tasks across temporary subagents, plus any custom agents your team creates. Every write from any agent follows your workspace’s Approvals.

Talk to an agent

Talk to agents in plain language. The full pattern is:
  • @agent (optional) — leave it out and CloudThinker answers, or mention one of your workspace’s custom agents.
  • #connection (optional) — the connection to use, such as your AWS account or a Kubernetes cluster.
  • / (optional) — run a skill or a command.
  • Your request — what you need, in your own words. Add any context inline.
See Commands for the full list. Who answers depends on the mention: Type @ in the chat box to open the Mention an agent picker. It lists CloudThinker and your workspace’s active custom agents. A first request needs no mention at all:
CloudThinker picks the Kubernetes connection, runs the checks, and replies with the pods, their restart counts, and the reason for each restart it found.

The CloudThinker assistant

CloudThinker is always on. You can’t turn it off, and it can use every connection in the workspace. Use it for anything: questions, investigations, reports, and changes (which wait for approval when your Approvals settings say so).

Subagents

A subagent is a short-lived helper that CloudThinker starts for one part of a bigger task. During an incident, for example, it can check three services at once instead of one after another. Each subagent reports back, and CloudThinker combines the results into one answer. You see subagents in the chat and in the Agents tab of the side panel: Each subagent in the Agents tab shows a status: Subagents exist only for the task that started them. They don’t appear in your agent list and you can’t mention them.

Custom agents

A custom agent is an agent your workspace defines, with its own name, @mention, instructions, and connections. Create one when a team needs the same behavior every time, such as a database reviewer that always applies your naming rules, or an on-call helper that only touches the staging cluster. Workspace Admins and Developers can create one under More → Workspace settings → Agents: click Create agent, then choose Create with AI (describe it in plain words) or Build with form. A custom agent has no approval mode of its own. Its writes follow the workspace’s Approvals like every other agent’s.
A custom agent turns itself off when it has no connection. Attach at least one before you mention it. Team allows up to 5 custom agents, Scale up to 10, and Enterprise has no limit. See AI features by plan.
For a worked example with a test prompt and its expected reply, see Build your first custom agent. The full settings are in Customize agents.

Agents in each product

FAQ

No. CloudThinker is always active in every workspace. You can turn custom agents on and off.
Yes. Write actions from CloudThinker, a subagent, or a custom agent all follow the same workspace Approvals settings.
A custom agent only uses the connections attached to it. Open it under More → Workspace settings → Agents and add the connection.
Older versions had five named specialist agents. CloudThinker now does all of their work as one assistant and spawns subagents when a task needs parallel work. Ask CloudThinker directly.

Customize agents

Create a custom agent with its own instructions and connections

Your first investigation

Watch CloudThinker and its subagents work a real problem

Approvals

Choose which agent actions wait for your sign-off

Commands

Mentions, connections, and the / menu in one reference