The steps of a task
- It reads the task. The agent reads your message, the earlier messages of the conversation, any files you attached, and its own instructions and guardrails.
- It decides what it needs. Some questions it can answer straight away. For others it needs to look something up or do something first.
- It uses a tool. It searches its knowledge bases or the web, loads a skill, runs code, works in a connected service, or hands part of the work to a subagent. You do not have to name the tool; the agent picks it.
- It looks at the result. If the result is not enough, it goes back to step 2 and tries something else.
- It may pause to ask you. When something is unclear, or a guardrail says an action needs your approval first, it stops and asks.
- It answers. The answer can include numbered sources, files it made, or a question back to you.
An example
You ask a finance agent: “Which supplier invoices from March are still unpaid?” It searches its knowledge base of invoices, runs a short piece of code to add up the amounts, and answers with a table, the total and the invoices it used as sources. Suppose you also ask it to remind the suppliers, it has a mail toolkit, and its Needs approval first guardrail names sending email. It then stops and asks you before it sends anything.What you see while it works
- The answer area names what the agent is doing: Queued…, Starting…, then the current step with a seconds counter, such as Thinking… or Searching…. The answer then appears as it is written.
- The Execution Trace panel (the monitor button in the top bar) lists every step: model calls, tool calls and searches.
- When the agent pauses, a box above the composer says The agent is waiting for your input. Reply in the message box and it carries on from where it stopped.
The limits of a task
- By default a task may work for about an hour and use a bounded number of tokens (the units models measure text in). Time spent waiting for you does not count. A task that reaches a limit stops and says so.
- A paused task waits up to 72 hours by default. If nobody answers in time, the task ends as failed.
- One message may take at most half of the model’s context window, the amount of text the model can consider at once. A longer message is refused before any work starts.
- How many tasks can run at the same time is limited per person and per organization:
- SaaS: set by your plan. Free 1, Pro 10, and 30 for a whole Business organization.
- Enterprise: by default 10 per person and 25 for the organization, unless your installation sets other values.
- A task that waits for your answer does not count toward the tasks running at once.
Where you see this in the app
- New task: send the task and follow it. See Starting a task.
- Tasks: come back to a task that is running or done. See Tasks.
- Inbox (Admins and Members): tasks that wait for your answer. See Inbox.