Headful Experience

Dashboard UX for tasks, docs, runs, and cycles

The dashboard gives you a visual, keyboard-first layer on top of tx primitives. This section documents the current headful UX and the workflows it unlocks.

Treat the dashboard as the visual layer over the same primitives. It becomes most useful once your task, spec, and observability workflows are already in place. Watchdog remains a separate, optional operations layer.

What Changed Recently

• Cmd+K / Ctrl+K command palette is available everywhere in the dashboard.
• Task and sub-task workflows support faster bulk selection and action flows.
• Tasks now support a list/kanban view toggle in the main toolbar.
• List view now uses 8 explicit status filters with counts (no 3-bucket status model).
• Kanban now renders 8 status columns with drag-and-drop updates and a collapsed Done column.
• Weekly cycles now support create/manage/complete workflows with automatic carry-over behavior.
• Settings is now tabbed (General, Labels, Cycles), including default task view and cycle configuration.
• The status label human_needs_to_review is now needs_review.
• Task detail layout is tighter, with a stronger split between content and properties.
• Docs, Runs, and Cycles views have clearer empty states and panel behavior.

Explore the Headful Docs

• Tasks and sub-tasks
• Filters and settings
• Command palette (Cmd+K)
• Docs, runs, and cycles views

Headful + Headless

The UI is intentionally a layer over the same primitives:

• Work queue and status transitions map to tx ready, tx done, and status updates.
• Task relationships and bulk operations map to dependency and hierarchy primitives.
• Keyboard actions mirror command-line intent for fast operator workflows.

Suggested Path

1. Tasks and sub-tasks
2. Filters and settings
3. Command palette
4. Docs, runs, and cycles

Next Step

If you later need detached supervision, rollback, and recovery playbooks, use the Watchdog Runbook.