Git, diffs & Commit Thread

darting.dev is git-native. Everything an agent does lands as commits on a branch, so review and integration use tools you already trust.

Reviewing changes

The Code tab is branch-aware. Selecting a thread points the file tree and diff view at that thread's sandbox, so you always see the right version. Clicking a file in a write tool-call jumps straight to its diff.

The Git tab shows the branch graph. Click any commit to see its full diff grouped by file, with the message, timestamp, and a +/- summary.

View in your IDE

For deeper review, the View in IDE action fetches an agent's branch locally and opens it in your editor's native source-control panel:

git fetch origin agent-swarm/<id>
git checkout agent-swarm/<id>

Cursor and VS Code then show side-by-side diffs with accept/reject per file. No custom extension required.

Commit Thread

When the work is ready, Commit Thread integrates it. A dialog fetches an LLM-drafted title and body, lets you edit them, and confirms — then it merges the thread into a feature branch and opens a pull request. Integration is never silent: it always lands as a PR, so nothing reaches your default branch without passing through review and CI.

If the PR can't be created (a transient GitHub hiccup, say), the merge to the feature branch still lands and the dialog offers a one-click Retry PR.

After the PR opens

Opening a PR starts a feedback loop the orchestrator runs on its own: it tracks CI, hands the agent capped fix-only turns when checks fail, and marks the PR ready when they pass — arm auto-merge and green checks land it without you. Pull requests & the CI loop covers the whole loop and its guardrails.

Open PRs land through the merge queue, which groups them by the files they touch so unrelated work merges in parallel. And while a thread is in flight, update from main keeps it current as main moves — with conflicts resolved in the thread, not discarded.