Work Management

A project maps to a folder on your filesystem, typically a git repository. Each project has:

Tickets represent work items displayed on the Kanban board. Each ticket has:

Each ticket can have multiple executions (also called "attempts"). This allows you to:

• Try the same task with different CLIs (Claude vs Codex vs Cursor)
• Test different models within the same CLI
• Run in different git branches for isolated experimentation
• Compare token usage and results across attempts

Each execution tracks its status, token usage (input, output, cached, reasoning), and timestamps.

Ticket Statuses

Ticket Types

The document type is for organizing non-code tickets such as research notes, specs, or planning documents.

Priorities

Tickets support parent/child relationships, replacing the earlier flat subtask model. This lets you break down large tasks into smaller, independently executable pieces.

• Any ticket can be a parent with child tickets underneath
• Children are visible inside parent cards on the Kanban board
• Browse child tickets and ancestry from the inspector breadcrumb
• Each child ticket has its own executions, status, and priority

Filter the Kanban board to focus on specific tickets:

• Filter by ticket type (bug, feature, document, generic)
• Filter by CLI engine (Claude, Codex, Cursor)
• Quick type filter: double-click a type badge to focus on that type

You can move a ticket from one project to another. All associated data moves with it:

How to move: Open a ticket in the inspector, then use the project dropdown to select a different project.