> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/app-builder/tasks.md).

# Tasks

Tasks is a shared board between you and the Riff agent. When you ask the Riff agent to build something, it breaks the work into tasks here — so you can both track progress without re-reading long chat histories.

## What you see

A card headed **"Agent tasks"** with two controls at the top right:

* **Search** — filter tasks by title in real time
* **Show subtasks** toggle — reveals child tasks nested under parent tasks (off by default)

<div data-with-frame="true"><figure><img src="/files/4gUm5eBdmZgx6AQDrefM" alt=""><figcaption></figcaption></figure></div>

Tasks are grouped into four sections, from top to bottom:

<table><thead><tr><th width="192.3798828125">Section</th><th>What it contains</th></tr></thead><tbody><tr><td><strong>In Progress</strong></td><td>What the Riff agent is actively working on right now</td></tr><tr><td><strong>To Do</strong></td><td>Work that is queued but not yet started</td></tr><tr><td><strong>Done</strong></td><td>Completed tasks</td></tr><tr><td><strong>Cancelled</strong></td><td>Tasks that were dropped</td></tr></tbody></table>

Done and Cancelled only appear when tasks exist in those states.

## How it works

The Riff agent creates and updates tasks automatically as it works. When it starts on something it moves it to In Progress; when it finishes it moves it to Done. You can also create tasks manually or change their status.

## When to use it

* To check what the Riff agent is currently working on
* To see what is queued before you add more instructions
* To review completed work at a glance without scrolling back through chat
* To track parallel work across a longer build session


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.riff.ai/reference/app-builder/tasks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
