Workflow

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 a git repo. The New Project dialog offers three ways in, all producing the same workspace:

• Git URL — paste any HTTPS or SSH URL. Private repos authenticate with a token you provide.
• Local folder — the browser's File System Access API detects your remote and reads .env for secrets.
• Empty repo — starts from a bare git init in the sandbox, no clone needed.

The sandbox clones the repo, installs dependencies, and boots the dev server while you watch the output stream live.

2. Start a chat thread

Each project keeps an active chat thread. The lead agent in that thread is persistent — every message you send creates a new execution attempt, but the agent and its history carry across turns.

3. Pick a mode

Switch modes per turn to control what the agent can do:

See Plan & Agent modes for details.

4. Let the swarm work

In Agent mode, the lead agent writes files, runs commands, and can dispatch sub-agents and automations. Heavy work — builds, test suites, Playwright runs — happens inside isolated sandboxes, not on your machine.

5. Review

The Code tab shows branch-aware diffs. The Git tab shows an SVG branch graph where you can click any commit to see its diff. While agents work, a live terminal, dev-server logs, and a streamed desktop are always in view.

6. Commit Thread

When you're happy, Commit Thread integrates the work:

• With feature branches on, it merges into a generated branch and opens a pull request with an LLM-drafted title and body.
• With feature branches off, it merges straight into the default branch.

That's the whole loop. Repeat it across as many threads as you like — they run in parallel.