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

# Tasks

> Ask Empirical agents to add or update test coverage

A task is a work item for adding or updating test coverage. It keeps the original brief, status, and every agent session associated with the work in one place.

## Creating a task

**1. Navigate to Tasks**

Open **Tasks** in your project.

**2. Create a new task**

Click **New Task**.

**3. Describe the coverage**

Add a clear title and description. Turn on **Create as draft** to save it as a draft until it is ready.

**4. Track progress**

Open the task and select the **Sessions** tab. Start an agent session with **New Session**, and follow its progress there.

A clear task leads to a better test. Cover these four things:

* **What to test** — the feature or user flow
* **Steps** — the actions the user takes, in order
* **Expected outcome** — what a passing test looks like
* **Edge cases** — variations or special conditions to account for

To provide screenshots, videos, or other files, attach them to the prompt when you start a session from the task.

### Example Prompt

```
Test the checkout flow for a returning customer:
1. User logs in with existing credentials
2. Adds product to cart from the search results
3. Navigates to checkout
4. Selects saved payment method
5. Completes purchase
6. Verify order confirmation appears with correct order details
```

## Drafts and statuses

New tasks are **Open** by default. A **Draft** is a task that is not ready yet; changing it from Draft to Open starts an agent session.

Use the status selector on the task to move it between **Draft**, **Open**, **In Review**, **Resolved**, and **Closed**. Editing the title or description does not change existing session messages, so send important follow-up context in the relevant session as well.

Tasks created from [Linear](https://empirical.run/docs/integrations/linear.md) or [Jira](https://empirical.run/docs/integrations/jira.md) also link back to their source issue.

## Who a task is for

Every task belongs to the person who asked for it: you when you create it, the person who assigned or labelled the issue in Linear or Jira, or the person who asked an Empirical agent in Slack. People who don't have an Empirical account yet get one created from their email, and it is theirs when they sign up.


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