# Tasks

Plan the work on a board backed by your project's Beads issues.

**Tasks** shows the issues of a [Beads](https://github.com/gastownhall/beads) workspace in your project. Bud doesn't have its own task storage; the built-in adapter reads and writes through the `bd` CLI, and [another adapter](/docs/app/guides/storage) can supply tasks from a different tracker.

## Requirements

- `bd` 1.3.1 or newer on your `PATH`
- An initialized workspace (`bd init`) in the project

Without them there's no **Tasks** screen at all, and no task links or **New task** anywhere; `bud doctor` says what's missing. Bud never initializes a workspace for you.

## The board

Tasks sit in status columns, or in a list. With the [factory](/docs/app/guides/factory) on, the columns are its steps: Open, In progress, Needs approval, Ready to merge and Merged, with Closed folded away. Without it, the board shows open and started work, with done work folded away.

Each card shows the task's title, its agent's run, the person who created it and when, its epic and how many messages its discussion has. The top bar holds a search, a person filter (everyone, **Mine** or one person), an epic filter once there are epics, the board or list switch and **New task**. On a phone or tablet, the search opens from its button and the filters share one menu.

You move a card by hand only to Open or to Closed. Every other step belongs to whoever does the work: in factory mode, the factory moves the task as its agent works.

**Sync** pulls and pushes through the Beads remote, and shows only when the workspace has one.

The board stays current on its own. Changes made with the `bd` CLI, by an agent or in another tab appear within a few seconds, and an open task page picks them up too. Your browser keeps the last board it saw, so reopening **Tasks** shows it at once while Bud reads the latest.

## Task pages

Open a task to read it on its own page, at `/tasks/<id>`. The breadcrumb shows its epic, and **Back** returns to the board where you left it.

The page leads with the title and description, which you edit in place, then a line with the task's status, the person who created it and when. Below come its epic, the tasks linked to it, the agent's run when the factory is on, the discussion, and its activity, folded away until you open it. The menu beside the title closes or reopens the task, or deletes it after asking.

**New task** asks only for a title and a description. Bud records who created each task on the server: your Git author locally, the person who signed in on a hosted Bud. Nothing the browser sends can change it.

Changes show right away, on the board too. Every change still checks that the task hasn't changed since you opened it; if Beads refuses one, Bud undoes it and tells you why. Bud never retries a change on its own.

Beads keeps more than this screen shows, such as priority, type, assignee and labels. To show them, see [Task designs](/docs/app/guides/task-designs).