Workflow
The end-to-end loop, from creating a project to merging a pull request.
Every project follows the same loop. Once you've seen it once, the rest of the docs just fill in detail.
1. Create a project
A project is your workspace. The New Project flow offers several ways in:
- Git URL — paste any HTTPS or SSH URL. Private repos authenticate through the darting GitHub App on GitHub, or a token for GitHub, GitLab, or Bitbucket.
- Start fresh — choose Darting, GitHub, or GitLab as the repository store. The repository is created on the first save.
The sandbox clones the repo (when you have one), installs dependencies, and boots the dev server while you watch the output stream live.
2. Start a chat thread
Each project keeps chat threads. The lead agent in a thread is persistent — every message you send creates a new execution attempt, but the agent and its history carry across turns. The project's Shipped view shows merged work, and its Knowledgebase shows filed plans beside the systems they concern.
3. Describe the outcome
Tell the lead agent what you want. It self-assesses complexity:
| Path | What happens |
|---|---|
| Direct | Simple asks get implemented immediately |
| Brief plan | Moderate work gets a short approach, then code |
| Living plan | Complex work becomes a versioned plan you Build when ready |
See How the lead agent works for details.
4. Let the swarm work
The lead agent writes files, runs commands, and can dispatch sub-agents. Heavy work — builds, test suites, Playwright runs — happens inside isolated sandboxes, not on your machine.
5. Review
The Changes view shows branch-aware diffs. While agents work, you can open a live terminal, dev-server logs, or the streamed desktop from the side panel's Extras → Try it section. Implementation tasks often return video proof of the feature working.
6. Open a PR and merge
When you're happy, open a pull request with a drafted title and body. The orchestrator tracks CI, pushes fixes if checks fail, and marks the PR ready when they pass. Arm auto-merge when you want green checks to land without you — nothing merges until you opt in.
That's the whole loop. Repeat it across as many threads as you like — each runs in its own sandbox, so they never collide. The merge queue groups open PRs by file overlap so unrelated work can land in parallel.