Skip to content
track

Dispatching Tasks

The normal loop starts in the CLI and finishes in the WebUI.

1. Capture a task from the CLI

Section titled “1. Capture a task from the CLI”

From any directory, put the project name or alias near the start of the note for the most reliable first-run capture:

Terminal window
track todoapp fix stale task status after a canceled run

or

Terminal window
track todoapp prio high fix stale task status after a canceled run

You can be rough. The local parser is there to turn your note into a structured task, as long as the project name or alias resolves to something you already registered.

2. Review the task in the WebUI

Section titled “2. Review the task in the WebUI”

Open the task drawer and do the light cleanup there:

  • tighten the description
  • adjust the priority
  • close or reopen the task if needed

3. Dispatch the task

Section titled “3. Dispatch the task”

When the task looks good, click Dispatch.

The usual status sequence is:

  • Preparing
  • Running
  • one of Succeeded, Blocked, Failed, or Canceled

If a run succeeds and opens a pull request, the task drawer shows the PR link directly.

4. Use the Runs page when you want history

Section titled “4. Use the Runs page when you want history”

The Runs page is the best place to watch active work or revisit older task runs. Use the task drawer for the current task, and the runs view when you want the bigger picture across projects.

When dispatch does not start immediately

Section titled “When dispatch does not start immediately”

The most common missing pieces are:

  • the remote agent was never configured from the CLI
  • the shell prelude was never saved in the WebUI, in which case track sends you to Settings to finish runner setup
  • the project metadata is incomplete