Introduction
What darting.dev is, how work moves through projects and threads, and where to start.
darting.dev is a workspace for building software with coding agents. You can run several pieces of work at once: each thread has its own conversation, branch, and isolated sandbox, while the project's Knowledgebase keeps useful context close.
The core idea
Describe the result you want in a thread. Its lead agent can inspect the code, plan the work, delegate parts to other agents, build, and check the outcome. You can follow the transcript, inspect the changes, ask for visual proof, and use Ship it when the work is ready to publish.
You ──▶ Lead agent ──▶ sub-agents
├─ explorer (reads the code)
├─ coder (builds and tests)
└─ UI driver (checks the app on screen)
Your project's Coordinator is the place to ask about that project's work or have it start and follow threads; it has no code sandbox of its own. The Overseer does the same across the projects you can access. Neither writes the code itself: work runs in threads. After work is merged, you can put a supported app online at its permanent darting.app link through hosting. See The Coordinator & the Overseer.
What you see
The sidebar groups projects by team. Open one for its Coordinator, its Threads, a Shipped history, and its Knowledge; Settings opens project settings. Inside a thread, the thread list sits in a column beside the transcript and composer, and a side panel with Overview, Extras, and Chat tabs holds the app, the changes, and team chat. Take the workspace tour for the full map.
Where to start
- Create or import a project with Projects & setup.
- Follow Workflow from the first request through Ship it.
- Learn how Threads & branches and isolated sandboxes let work run in parallel.