Skip to main content
Most of what your coworker can do is always on, and the Capabilities tab holds the few switches you control.

Narrowing a coworker down to research only — five switches off, and it can no longer send, schedule, browse or generate.

What it does

A coworker is only as useful as the things it can reach. Most of that is always on. It works with code and files, schedules its own follow-ups, talks to people, works with the other coworkers in its agent, and runs its agent’s workflows. The Capabilities tab is where you choose the rest: whether it searches the web, reads web pages, generates images or drives a live browser, and which of your apps it may use. If a switch is off, your coworker can’t do that thing, and it tells you so rather than working around it.

The parts of the tab

Open any coworker and choose Capabilities. You’ll find these sections, in this order.
The Capabilities tab showing the eight built-in tool switches and the two Collaboration switches

The Capabilities tab. Built-in tools at the top, Collaboration below the divider — and every line of it is a switch you control.

Below those, when the coworker has any, a read-only list of skill labels. The skills a coworker learns are managed on its Files tab. See What skills are. The note above the switches says what the tab doesn’t list:
Code and files, scheduling, talking to people and working with its agent’s coworkers are always on. The four below are on unless you switch them off; changes apply to new sessions.

The two rules that surprise people

What starts switched on depends on how you hired.A New coworker starts with all four switches on. You narrow it down; you don’t build it up.One of the ready-made coworkers starts with Generate images off, because none of the five roles needs it. The other three switches are on.Either way, check this tab before the first session. It’s the fastest way to understand what you’ve actually hired.
Changes apply to the next session. A session that’s already running keeps the tools it started with. If you switch something on and the coworker still says it can’t do it, start a new session.
The second one accounts for most “why didn’t that work” moments. The note above the switches says so, but it’s easy to miss when you’re mid-flow.

Always on

Every coworker has these, with no switch. Each has its own page here.

Code and files

Actually do the work: open a spreadsheet, run the numbers, hand the file back.

Self-scheduling

Book its own follow-up so nothing waits on you remembering.

Talking to people

Hold a real conversation with a real person and carry on from the answer.

Working with coworkers

Hand work to another coworker in its agent and follow it as it goes.

Running your workflows

Run its agent’s workflows and check on what they did.

Data stores

Read variables, query a database and work in file stores.
A handover to another coworker is a handful of actions, and each one that changes the other coworker’s work asks for your yes first, unless a permission rule allows it. For each action, the saved reports and the permission rules, see Coworker handovers in detail. You can still switch any of these off on one channel, under Capabilities on this channel in the channel’s settings. See Channel settings.
The Collaboration section with Work with coworkers and Dynamic workflows both switched off

Both Collaboration switches start off, and the tab says why — each one puts more than this coworker to work.

The Dynamic workflows row switched on, showing a warning that it needs Code and files

An honest warning rather than a switch that reads as on while nothing happens.

The four switches

Each is on unless you switch it off, and each has its own page here.

Web search

Look things up instead of guessing.

Reading web pages

Open a link and read it properly.

Generating images

Ask for a picture, get a file you can use.

The live browser

Use websites the way you do, and hand you the keyboard at a login.

Learning

How this coworker learns from its work. Both settings are off until you turn them on.
  • Skill consolidation: a periodic review proposes merges and cleanups of the skills this coworker wrote. Every change needs your approval. See Skills that improve themselves.
  • Freeze learning: keeps every run the same. Your coworker still uses what it already knows, but saves no new memories and suggests no improvements. It suits a coworker that a workflow runs on a schedule.
While learning is frozen, skill consolidation pauses, and its row says “Paused while learning is frozen.”

Integrations

Underneath, the apps this coworker may use: Gmail, Slack, your CRM, a spreadsheet. Attaching an app gives your coworker every action it supports by default, and you can narrow that to individual actions whenever you like. This is the part most worth spending five minutes on, because it’s where you decide whether a coworker can read your inbox or also send from it. See Connecting your apps.

What it looks like in practice

Each switch row is the same shape: an icon that lights up in colour when it’s on and greys out when it’s off, the name, one line explaining it, and the switch.
The Web search row shown switched on above the same row switched off

The same row on and off. The colour is the fastest way to read the tab at a glance.

Changes save the moment you flip a switch. There’s no Save button and no confirmation step.

Good to know

Narrowing a coworker makes it better, not weaker. A shorter list of tools is a clearer job description. A coworker with fifteen apps attached spends effort deciding which one to reach for; a coworker with two does the job.
Capabilities are per coworker, not per workspace. Two coworkers can hold the same Gmail connection with completely different actions allowed on each.

Common questions

Because the session was already running when you flipped the switch. A session keeps the tools it started with, all the way to the end. Start a new session and it’ll be there.
Yes, for anything clearly outside its job. A support coworker has no use for image generation. It keeps the coworker focused and means fewer surprises.
Not for the coworker as a whole: they’re always on. You can switch them off for one channel, under Capabilities on this channel in that channel’s settings. To keep a capability on but ask first, use Permission rules.
The switches cost nothing until your coworker uses them. Skill consolidation is different: it reviews skills on its own schedule, which costs a little each time, so it starts off.
A capability is something your coworker can do. A skill is knowing how and when to do it: your way of working, written down. A coworker usually needs both: a “customer follow-up” skill is only useful alongside the ability to send email.
Yes. Permission rules let you keep a capability on but require your approval each time, or block one specific action while allowing the rest. See Permission rules.

Next steps

Connecting your apps

The part worth five minutes of your time.

Permission rules

Keep a capability on, but on your terms.

Approvals

What needs your yes before it happens.

Giving instructions

Capabilities are what it can do. This is what it should do.