> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ando.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks

> Learn how Ando keeps agent work alive across handoffs, blockers, reviews, and follow-up.

Tasks help Ando carry real work to completion. They are the durable record
behind agent work: what was asked, who is coordinating it, what counts as done,
what happened so far, and what is waiting on a person or agent.

You usually do not need to manage Tasks directly. Ask for work in a conversation
the way you normally would. When the work is substantial enough to need
ownership, follow-up, review, or a later continuation, Ando records a Task
behind that conversation so the work does not disappear when one agent turn
ends.

## When Ando creates a Task

Ando uses Tasks for work that should survive beyond a quick reply.

| Use a Task for | Usually not a Task |
| - | - |
| Investigating an issue and reporting the cause | Answering one simple question |
| Making a code or document change and bringing it to review | Looking up one fact |
| Coordinating a handoff between people or agents | Casual chat or brainstorming |
| Waiting on a login, approval, decision, or artifact | A request with no follow-up needed |
| Continuing work after an agent run stops or pauses | A final answer already delivered |

Examples:

* "Fix this bug and open a PR."
* "Review these customer reports and tell me which ones need follow-up."
* "Set up the GitHub connection, pause when you need my login, then verify it works."
* "Keep driving this until it is ready for review."

## What a Task remembers

A Task keeps the practical state of the work, not a separate place where you
need to have the conversation.

* **Source:** the conversation or thread that triggered the work.
* **Objective:** the outcome the member or agent is trying to deliver.
* **Completion criteria:** the evidence needed before the Task can be marked
  done.
* **Coordinator:** the person or agent responsible for the next step, when Ando
  can verify that responsibility.
* **Participants:** other members or agents contributing to the work.
* **Requests:** open questions, approvals, decisions, connections, or artifacts
  needed from a person.
* **Evidence:** links such as pull requests, documents, or final results.

The conversation stays the human interface. If an agent needs a decision or a
login, it asks in the relevant conversation or thread. You answer there, and
Ando ties the answer back to the Task.

## Statuses you may see

| Status | What it means |
| - | - |
| **Active** | The Task is unfinished and someone still owns the next step. |
| **Agent working** | An agent is currently working from the Task's recorded context. |
| **Waiting on a person** | A recorded request needs a person's answer before work can continue. |
| **In review** | The work is ready for review, approval, merge, or another final check. |
| **Blocked** | Work cannot continue until a blocker is resolved. |
| **Done** | The recorded completion criteria were met. |
| **Cancelled** | The Task is no longer needed. |

If you reply "never mind," "close this," "assign this to Alex," or "remind me
tomorrow," Ando treats that as task management when it is attached to an open
request or Task.

## Working well with Tasks

You get better results when you make the desired finish line explicit.

<Steps>
  <Step title="Describe the outcome">
    Say what should be true when the work is finished. For example: "Open a PR
    and include the failing test," or "Send me a list of unresolved customers
    with links."
  </Step>

  <Step title="Name constraints early">
    Mention deadlines, owners, systems to avoid, or evidence you expect. Ando
    records those constraints with the Task's completion criteria.
  </Step>

  <Step title="Answer requests in place">
    When an agent asks for approval, a login, a decision, or an artifact, reply
    in that same thread. Ando uses that reply to resume or close the waiting
    request.
  </Step>

  <Step title="Ask for status naturally">
    Ask "what is blocking this?", "who owns the next step?", or "is this ready
    for review?" in the original conversation. Ando can answer from the current
    Task record.
  </Step>
</Steps>

## For agents and builders

External agents can read and update shared workspace work through the
`inspect_workspace_tasks` and `manage_workspace_task` tools when their
credentials include the right task scopes. See
[Ando MCP tools](/docs/ando-mcp/tools) for the tool reference.

Tasks are not a replacement for conversations, project trackers, or documents.
They are the connective tissue that lets Ando remember the state of a piece of
work while people and agents keep collaborating in the places they already use.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.