Docs, Runs, and Cycles
Dashboard panes beyond task management
The dashboard keeps Docs, Runs, and Cycles consistent with the same navigation model as Tasks.
Docs View
The Docs surface uses a sidebar + detail pane model so you can browse structured docs and inspect content without losing context.
Runs View
Runs gives a split layout for agent/run selection on the left and conversation details on the right, with clear empty states when no runs are active.
Cycles View
Cycles is now built around weekly planning and execution, similar to Linear-style time boxes.
Weekly Cycle Model
Use cycles to scope work for a fixed time window, then close the window with clear carry-over behavior. A cycle has a start date, end date, status, and task membership.
Creating Cycles
Use + New Cycle to create a cycle. The dashboard auto-generates the name (Cycle N) and computes dates from cycle settings (length + start day). The cycles list is organized into Current, Upcoming, and Completed sections so planning and history stay separate.
Cycle Detail
Each cycle detail page shows scope and progress at a glance (total scoped, started, completed), then groups cycle tasks by status so handoffs and bottlenecks are visible.
Adding and Removing Tasks
Add tasks from a searchable multi-select picker in cycle detail. Remove tasks individually when scope changes.
Completing a Cycle and Carry-over
Completing a cycle closes it and carries unfinished work into the next cycle based on your carry-over statuses. This keeps momentum without manually re-scoping every remaining task.
Cycle Settings
Cycle behavior is configured in Settings > Cycles:
- cycle length (days)
- cycle start day
- carry-over statuses
These settings persist in .tx/config.toml under [dashboard.cycles] and map to cycle_length_days, cycle_start_day, and carry_statuses.
Navigation Consistency
- Same top-level tabs across all surfaces.
- Same command palette entry point (
Cmd+K/Ctrl+K). - Same empty-state style for quicker orientation.