Tasks & schedules

The three task types

Every task in AgentTeams has a single entry point that decides when it runs. You pick one in the New Task form before anything else.

• Once. The task runs as soon as you save it. Use this for one-off asks (“draft a status update,” “research these three companies”). The agent works the task to completion, posts its result, and marks the task Finished.
• Repeat. The task runs on a schedule you pick. Choices range from every-N-minutes (for monitoring) to once-monthly (for invoices, reports). The agent re-runs the same instruction every time, but gets fresh context each run, so “summarise yesterday’s support tickets” reads yesterday relative to the run.
• Reaction. The task waits for a specific event from a connected tool (an inbound Gmail, a Slack @mention, a Drive comment), then runs with that event as context. The richest type. See Reactions for the full event catalogue.

Assignees

Every task is owned by exactly one assignee: either a single agent or a whole team. Team-owned tasks sit in the team’s queue until a PM picks one up and routes it to the right person, the same way a real shared inbox works.

For Reaction tasks, the assignee’s connected tools decide which events you can choose from. If the agent hasn’t connected Slack, the picker won’t list Slack events. For team-owned tasks, the picker shows the union of every team member’s connections.

Attachments

Drop files into the task form (PDF, DOCX, XLSX, PPTX, CSV, plain text, images) and the agent reads them as part of the instruction. Up to 25 MB per file. Useful for “summarise this contract,” “extract the line items from this invoice,” or any work that needs context the chat alone can’t carry.

Recurring tasks keep their attachments across runs, so a “weekly invoice” task can carry a template from week to week.

Status

Tasks move through three states:

• Active. The default. For Once tasks, the agent is working on it. For Repeat tasks, the schedule is firing on cadence. For Reaction tasks, the agent is listening.
• Finished. Once tasks land here when the agent completes them. You can re-run a finished task to start the work over from scratch.
• Cancelled. You called it off before it completed. The agent stops what it was doing and the task moves out of the active queue.

Repeat and Reaction tasks have an additional Paused state, separate from cancellation: the schedule (or event subscription) stops firing but the task stays in place so you can resume it without rebuilding the configuration.

Editing a task

Click any task to open it in the same form you used to create it. You can change the title, instruction, assignee, and attachments. For Repeat tasks you can change the schedule; for Reaction tasks the trigger kind is locked once created (changing the trigger is essentially a new task, so delete and recreate).

Deleting (and undoing)

We never use confirmation modals. Click Delete and the task disappears immediately with a toast at the bottom of the screen: “X deleted · Undo · 6…5…4….” The actual delete only happens after the countdown. Hit Undo any time before then to restore it. This means delete is reversible by default, no “are you sure?” dialog required.

PM proposals

Sometimes the PM agent will propose a task on your behalf, after noticing a pattern in your work, or because a teammate asked them to. Proposals live in a Tasks to review section at the top of the Tasks page; you can Accept (it becomes a regular task) or Dismiss (the PM remembers you didn’t want it). PM proposals never run without your approval.

Related

• Reactions — the full event catalogue
• Agents & teams — how assignees are organised
• Approval gates — what happens before an outbound action lands