How tasks work
A task’s life in Nested: running, needs you, completed, canceled, failed, or rejected — plus reopening, queued messages, subtasks, and automated tasks.
Every piece of agent work in Nested is a task — whether you start it, an automation starts it, or another agent starts it. Knowing the states tells you when to act and when to leave the agent alone.
The caller decides when a task is done#
When an agent finishes a turn, the task does not close by itself. It waits for you, so you can ask a follow-up in the same thread instead of opening a new task each time. You close it when you are satisfied, with Complete.
Task states#
| State | What you see | What to do |
|---|---|---|
| Working | The task is under Running. The composer shows Working… | Nothing. You can still send a message; it waits in the queue. |
| Waiting for input | The task moves to Needs you | Answer in the thread, or select Complete if the work is done. |
| Needs sign-in | The task moves to Needs you with a sign-in prompt | Sign the agent in, then continue. |
| Completed | Task completed | Nothing. The task moves to Archived. |
| Canceled | Task canceled | You or someone else aborted it. Reopen it or start a new task. |
| Failed | Task failed | Read the last message, then start a New task. Failed tasks cannot be reopened. |
| Rejected | Task rejected | The agent declined the request. Rephrase it in a new task. |
Closing and reopening#
- Complete stops the agent and closes the thread. “You can always start a new task in this workspace.”
- Abort stops the agent right where it is and marks the task canceled. Anything already written stays in the thread.
- A closed task replaces the composer with New task. When the task can continue, you also get Reopen task.
- In the task list, each row has quick actions to mark a task done, abort it, or reopen it.
Queued messages#
You do not have to wait for a turn to end. Messages you send while the agent works go to Queued messages and send after the current turn. Press Esc to stop the current turn instead. If the task ends or fails before the queue sends, Nested holds the messages and offers Resume, Send as new task, or Discard all.
Subtasks#
Select New subtask in the Task options (⋯) menu to split work off a task. Subtasks hang on a lane under their parent instead of cluttering the list. The assistant can also turn a long agent message into subtasks; see Writing faster in chat.
When an agent is stopped#
An agent with no work for about 10 minutes stops to free cluster resources. Its tasks are safe. When you open a task on a stopped agent, Nested says it stopped after a quiet period; select Start agent to continue.
Tasks that start without you#
Automations, schedules, webhooks, Slack, GitHub, formula steps, startup tasks, and other agents all create ordinary tasks. Their first message is labeled Automated message from the source. In the Archived tab, filter by kind: Chat, Scheduled, Hook, Automation, Formula, or Startup.
Example#
You ask an agent to upgrade a dependency. It finishes a turn and asks whether to also update the lockfile, so the task moves to Needs you. You answer “yes”, then add a second message while it works — it waits in the queue. When the agent reports success, you select Complete and the task moves to Archived.
Questions
- Why didn’t my task close when the agent finished?
- Nested leaves the task open after each turn so you can follow up in the same thread. Select Complete when you are done.
- What is the difference between Complete and Abort?
- Complete closes a task whose work is done. Abort stops the agent mid-turn and marks the task canceled.
- Can I send a message while the agent is working?
- Yes. It goes to Queued messages and sends after the current turn ends.