run a fleet of agents at once + the dashboard
Multiple agents#
DGC runs a fleet — several agents working at the same time, each with its own conversation. Kick off a long task on one, spawn another, and keep going.
- Ctrl+N — spawn a new agent (even while one is running). The old one keeps
working in the background; the new one is a clean slate.
- Ctrl+O — cycle to the next agent. Ctrl+\ — open the dashboard.
- Dashboard — every agent with its live state: ● on screen · ⋮
working · ◆ needs you · ○ idle. Enter attaches · x closes · p pins · r renames. + New agent spawns one; saved sessions are listed to reopen.
- When a background agent finishes or needs a decision, the bottom bar shows
⧉ N · ◆ need you — switch to it (Ctrl+O or the dashboard) to answer.
New agents use your current model by default; point one at a different model or a cloud key with /model / /connect for true parallelism.
The launch agent stays in the checkout you selected. Every additional agent in a Git project gets an owner-private dgc/fleet-* worktree containing the source checkout's exact tracked and non-ignored untracked baseline. Each checkout has its own crash-safe mutation lease, so fleet writes can proceed concurrently. Closing an untouched managed checkout removes it; changed, committed, uncertain, or still-running work is retained with its visible branch/path. Reopening that saved conversation validates and reattaches to the same checkout. Non-Git projects say when they fall back to serialized shared-checkout writes. /worktree <name> creates a deliberately named long-lived manual branch.
The model's task delegation tool isolates itself automatically in Git projects. Its private checkout starts with the caller's tracked and non-ignored untracked state. DGC applies only a completed child's conflict-free delta; it never overwrites paths that were already dirty, and it retains conflicting or incomplete work with a visible worktree path and branch. Integrated edits remain part of the parent turn's /rewind checkpoint and usage/edit totals.
Use /tasks to inspect retained work. /tasks apply ID recomputes its delta, rejects paths that were dirty before delegation or changed in the parent, and adds an applied result to /rewind. /tasks drop ID --confirm permanently removes the isolated checkout. Older recovery records created before baseline fingerprints remain visible and droppable but deliberately require manual inspection instead of unsafe auto-apply. VS Code/Cursor exposes the same operations through its command Quick Pick.