Start your first run

Start a run from New run, the command palette, Slack or an issue label, then follow it from plan to pull request.

On this page

A run is one piece of work going through a factory’s workflow: usually plan, approve, build, test, review and merge. You can start a run in four ways. They all create the same kind of run, and you follow it the same way.

Before you start, connect GitHub and pick a factory. If you don’t have a factory yet, use a template from Explore; the Ship features template is a good first one.

Start a run from New run

  1. Press C anywhere in the app, or select the + button at the top of the sidebar. The New run dialog opens.
  2. Describe the work in a sentence or two, or paste an issue link. For example: “Add a retry with backoff to the payout webhook handler.” Linking an issue gives the agent its full description and comments.
  3. Pick the Factory that should do the work. The factory’s default workflow is used unless you choose another one.
  4. Check the estimate and the cap that will apply. The dialog shows a cost and time range based on earlier runs of that workflow.
  5. Select Start run. The run opens and the agent starts reading your repo.

Other ways to start a run

  • Command palette. Press ⌘ K (Ctrl K on Windows and Linux), type “New run” and press ↵.
  • Slack. In any channel where Duun is installed, type /build followed by what you want done. Duun replies in a thread with a link to the run.
  • Issue label. If a factory has an Issue label trigger, adding that label (for example ready) to a Linear, GitHub or Jira issue starts a run for it. Nothing else to click.

Manual starts from New run, ⌘K and Slack work whenever the workflow’s Manual trigger is on.

Follow the run

The run page shows the conversation with the agent on the left and tabs on the right: Plan, Changes, Terminal, Preview and Checks. The header shows what the run has spent and what caps it.

Most runs stop once or twice to ask you something. Those asks also appear in your Inbox:

  1. Approve the plan. The agent explains what it will change. See Approve a plan.
  2. Allow a command it isn’t allowed to run on its own. See Allow a command.
  3. Review pull request. Checks are green and the PR is ready. See Review and merge.

If something goes wrong

  • The Start button is disabled. Your balance or a budget can’t cover the low end of the estimate. The dialog names the limit and links to fix it.
  • Nothing happens after adding a label. Check that the factory isn’t paused and that the label matches the trigger exactly.
  • The agent seems stuck. Read An agent seems stuck.

Prefer the terminal? Developers can start runs with duun run; see the Quickstart.

    Type to search the docs, help center and blog.