Kanban Board

The kanban board is your primary view of work in flight. Open the Tasks view from the navigation rail in the desktop app to see work flow through the lanes as agents pick it up.

Board Lanes

The board has five lanes representing task states:

Views

The Tasks view supports multiple modes — toggle between them from the header:

• Board — The classic swim-lane view
• List — A flat sortable list, useful for triage
• Table — A dense spreadsheet-style view with all task fields visible
• Graph — The dependency DAG, showing tasks as a graph with live status as agents pick them up

Adding Tasks

The easiest way to add tasks is through chat — describe what you want and the Product Manager agent will create well-structured tasks with sensible dependencies:

Add a new task for implementing the login page.

Break down user authentication into tasks.

You can also add tasks manually from the Tasks view toolbar.

Moving Tasks

Most of the time you don’t need to move tasks yourself — agents move them as they work. But you can drag a card between lanes any time you want to override (for example, manually moving something to Blocked while you investigate, or back to Todo to re-trigger work).

You can also ask in chat:

Mark task 5 as in-progress.

Move the login task back to todo.

Stopping Work

The Tasks view header has a Stop control. Stop aborts any tasks currently in flight and resets them back to Todo, so you can interrupt a run cleanly and re-trigger from a known state. (This replaces the older Pause control, which left running work untouched.)

Unblocking Tasks

A task lands in Blocked after repeated QA bounces. Blocked cards carry a Reset retries / clear QA bounces affordance — use it to clear the bounce count and requeue the card so the orchestrator picks it up again on a fresh pass.

Task Details

Click any task card to open the Task Detail dialog. From there you can:

• Read and edit the full task description
• See its dependencies and what’s downstream
• Inspect comments left by agents during execution
• View execution history
• Trigger a re-run

Task Dependencies

Tasks form a directed acyclic graph (DAG). The orchestrator picks up tasks once all their dependencies have moved to Done.

You can manage dependencies in chat:

Add a dependency so task 3 must complete before task 7.

Make the login task depend on the database setup.

Remove the dependency between tasks 2 and 5.

For the visual view, switch the Tasks view to Graph mode — it shows the dependency graph with live status:

Per-Project & Per-Subproject Runners

Each project — and each subproject within it — has a runner toggle. When the runner is on, the orchestrator schedules ready tasks; when it’s off, no new agent work starts but anything in flight finishes cleanly.

This lets you keep one project’s runner on overnight while pausing another, without affecting in-progress work.

Task Properties

Each task can have:

Subprojects

Within a project you can create subprojects — scoped slices of work (a feature, a sprint, a bugfix milestone) with their own kanban view. Each subproject has its own runner toggle and a chip in the board header for quick switching.

Workflow Example

Typical flow:

1. Describe a feature in chat — “Build user authentication with login, logout, and password reset”
2. The PM agent breaks it into tasks with dependencies
3. Open the Tasks view to review the breakdown
4. Adjust if needed (move tasks, add dependencies, edit descriptions)
5. Toggle the runner on
6. Watch tasks move through the lanes as agents do the work
7. Inspect anything blocked from the Blocked lane

Integrating with Jira

The board can sync bidirectionally with Jira:

• New Jira issues land in the Todo lane
• Status changes flow back to Jira when tasks move
• AI-powered DAG sync infers dependencies from Jira issue links

See Integrations for Jira setup.

Clearing Tasks

Use the Clear Board action in the Tasks view header to remove all tasks for the active project. This is useful when starting fresh.