Manage multiple projects

One Delegator instance can hold tickets from several Git repositories. Each ticket retains its project, branch, worktree, and run history, while the inbox brings the work together.

Target a repository explicitly

By default, dg ticket uses the repository containing your current directory. Use --project when creating work elsewhere:

dg ticket "Add API health checks" \
  "Add the agreed health-check endpoint and tests." \
  --project /path/to/api

dg ticket "Document local preview" \
  "Document the existing development-server command in the README." \
  --project /path/to/website

The directories must be existing Git repositories with commits. You do not need to run a separate Delegator server for each repository.

Use one inbox or filter the history

dg
dg list
dg list --project /path/to/api

Use an explicit ticket ID to inspect a particular task. Commands such as dg show and dg accept also accept a project selector when you omit the ID, selecting that project’s first READY ticket:

dg show --project /path/to/api

Set capacity for your working style

For two open tickets across the instance, but at most one per project:

dg config set runs 2
dg config set max_runs_per_project 1
dg config

Both RUNNING and READY tickets count. These settings can allow work in two repositories at once while keeping each repository’s next ticket waiting until its previous change is reviewed.

max_runs_per_project is one instance setting applied to every project, not a different value stored for each repository. A value of 0 removes that additional restriction; the overall runs limit still applies.

Choose limits with shared resources in mind. Separate worktrees can still compete for a database, port, cache, or external service.

Pause the whole queue

dg pause

Pausing stops new runs from starting across the instance; current runs will finish. Resume when ready:

dg start

Separate instances

For completely separate queue state and configuration, the global --data-dir option selects another instance using an absolute directory. Use the same option consistently for commands intended for that instance.

This can be useful if you’d like to chain delegators together. For example, one instance can be focused on development work and another instance focused on updating documentation from accepted eng work. You can setup a background process to monitor the development delegator instance and create tickets automatically in the documentation instance.

Reference: dg ticket, dg list, dg config set.