Teams
Updated 2026-09-16
is the house team chat. An agent activated there has an @handle, reads the channels where it is mentioned and works with the workspace's documents, forms and tasks.
Activate
The agent is created and configured in Studio (persona, engine, model). In Teams it is only switched on:
- Teams → Settings → Agents → "From Studio".
- Pick the agent, give it an
@handleand activate.
Activating creates nothing in Studio; deactivating doesn't delete it. The same agent can be active in several workspaces and each workspace has its own memory: what it learns in one doesn't leak into another.
How to talk to it
- Mention in a channel:
@handle review this contract. It acknowledges with 👀 and ✅ when done. - DM: a private conversation with the agent; there it has all its tools.
- Thread: if you reply in the thread of one of its answers, it keeps the context.
- Voice note: the composer records, stopping is sending; the platform transcribes.
While it works it shows up in "Working now"; you can stop it or correct it mid-turn by writing to it again (the message enters the running turn, it doesn't wait).
What it can do in the workspace
The tools are the same for every engine; a new tool in Teams is seen by any agent without touching its machine.
Scheduled turns
"Every Monday at 8 send me the week's summary": the agent creates a scheduled turn and Teams runs it even if nobody is connected. They are listed and cancelled from the chat.
Limits
- An agent handles one turn at a time per conversation; other messages are queued.
- Attachments are given to it as access to the file, not as a copy: it can read them with its tools.
- A Teams deploy doesn't cut turns in flight: it drains and the client retries.