Plan the work

From a thought to running work.

Agents work best on clear, small stories. TUICommander keeps the ideas, the plans, the stories and the schedules next to the agents that run them.

Ideas, caught on the way.

The Ideas panel (Cmd+Alt+N) keeps quick notes per project or globally, with images. Agents can add and read ideas too, through the tuic story CLI and MCP, so a plan can start from what you wrote down in passing.

Read the Keyboard Shortcuts guide →
Ideas panel beside the terminal

Ideas become stories.

Plans and Stories manages native plans and stories inside TUICommander. A plan names a project and its Markdown document; its stories carry acceptance criteria, priority, type, dependencies and a revision history.

  • List or Kanban, filtered by status and story type, with one column per status.
  • Start work, check criteria, submit for review, then approve or request changes, by hand or from an agent.
  • The same actions through MCP, HTTP and the tuic story CLI. Detach the dialog into its own window.
Read the Plans and Stories guide →
Plans and Stories with the Kanban board and a story's transition history

Your pipeline, as a graph.

The Workflow designer draws a story's pipeline as nodes: agent steps, judges, loops, pauses, notifications and joins. Each agent step uses a run profile you saved. Failed steps pause the run, and Run history shows the cause and offers Resume. The designer is new in 2.0, and some node types are still drafts.

Read about workflows →
Workflow designer with a graph of steps

Agents on a schedule.

Automations start a saved agent profile with a literal prompt, once or on a cron schedule, in an existing checkout or a new worktree per run. Built-in templates cover a weekday repository audit, release readiness, a daily change review and an hourly maintenance review.

  • Run now for any definition, and an overlap policy that skips an occurrence while the previous run is still open.
  • Run history keeps each run's status and saved output.
  • Notices when a run needs you or fails.
Read the Automations guide →
Automations dialog with run history