Bots and tasks
Organize persistent agents, focused tasks, shared rooms, and delegated work.
Bots are persistent teammates
A bot keeps its own conversation, model, instructions, working folder, memory, connected tools, and computer preference. Create separate bots when the role, access, or project context should differ.
- A coding bot attached to one repository
- A research bot with browser and document tools
- An operations bot with Gmail, Calendar, and Slack
- A local-model bot for private or offline work
Tasks are focused runs
Use Task when the work should have a clear beginning and result. Tasks are easier to track than mixing every request into the bot's main conversation, and scheduled runs create tasks automatically.
Rooms and teams
Rooms let multiple bots and people share context. Use a room when several specialists need the same brief or should hand work to one another. A chief-of-staff pattern works well: one bot receives the request, delegates focused tasks, and summarizes the result.
Delegation
Delegation asks another bot to handle a bounded subtask. The delegated task keeps its own activity and returns a result to the originating conversation. Give each delegate a narrow outcome and avoid assigning two bots ownership of the same files.
| Need | Use |
|---|---|
| Ongoing relationship and memory | Bot |
| One deliverable with a status | Task |
| Several participants sharing context | Room |
| A specialist handling one branch of work | Delegation |
| Repeated work at a known time | Schedule |