Skip to main content
Every request goes to CloudThinker, the assistant built into each workspace. It answers directly, splits large tasks across temporary subagents, and hands off to any custom agent your team builds.

​
Why one assistant

  • One place to ask. You don’t pick a specialist first. Type your request, and CloudThinker works out which connections and skills it needs.
  • Parallel work when it helps. CloudThinker spawns short-lived subagents to check several things at once, then combines what they found.
  • Your own experts. Custom agents carry your team’s instructions and only the connections you attach.
  • The same guardrails everywhere. Every agent’s write actions follow your workspace’s Manual or Auto setting and Tool Permissions.

​
The CloudThinker assistant

CloudThinker is always on. You can’t turn it off, and it can use every connection in the workspace. Mention @CloudThinker or just type. This table shows who answers a message: The @ picker, titled Mention an agent, lists CloudThinker and your workspace’s active custom agents.

​
Subagents

For a task with several independent parts — say, checking three services during an incident — CloudThinker spawns temporary subagents that work in parallel. Each one reports back, and CloudThinker combines the results into one answer. Subagents exist only for the task that started them. They don’t appear in your agent list.

​
Custom agents

A custom agent is an agent your workspace defines: its own name, @mention, role, instructions, and connections. Use one when a team needs consistent behavior — a database reviewer that always follows your naming rules, for example. Create one under Settings → Agents (in the Agent Configuration group). Click Create agent, then choose Create with AI or Build with form. Each custom agent has: A custom agent turns itself off when it has no connection. The number of custom agents depends on your plan — see Customize agents for the full setup.

​
Agents in each module

See Modules for what each one needs before it starts.

​
FAQ

Earlier versions showed five named agents. CloudThinker now handles their work as one assistant and spawns subagents when a task needs parallel expertise. Ask CloudThinker directly instead of picking a specialist.
No. CloudThinker is always active in every workspace. You can turn custom agents on and off.
Yes. Write actions from any agent — CloudThinker, a subagent, or a custom agent — follow the same workspace approval setting.

How CloudThinker fits together

See where agents sit among workspaces, connections, and guardrails

Customize agents

Create a custom agent and attach its connections

Auto Mode

Choose whether write actions wait for approval

Commands

Save reusable prompts and run them with /