Ship it & pull requests
Publish a thread with Ship it, follow pull-request checks and fixes in chat, and decide when green changes merge.
Ship it is the publish action for a thread, not a way to save a checkpoint. Work is committed to the thread's own branch at the end of each turn; you can inspect or rewind it before publishing. When a GitHub, GitLab, or Bitbucket repository is connected, Ship it brings the branch up to date, pushes the work, opens a pull request, and follows that PR through checks and merge. One thread ships one PR. After it lands, new work belongs in a fork or follow-up thread.
The status pill and the card
Above the message box, the ship control is a status pill that names where the thread stands: Ready to ship, Agent working, PR open, Merged, or Live. Click it for a popover with the next action and three settings: Open PR as a draft, Review these changes (a second AI checks the agent's work before merge, on the model you pick), and Merge this PR automatically. The settings stay editable while a ship is queued.
Once a turn has changed files, a Ready to ship card also appears at the end of the transcript with the change size and three actions: Ship it, Try it yourself to open the app in your browser, and Show me to have the agent prove it works. The card and the pill describe the same ship; once you click Ship, the card gives way to the ship's progress in the conversation. Still working? Ship when done queues the action until the agent and queued messages finish. A draft PR must be marked ready before it can proceed. If your project tracks a separate production release, the control may say Save rather than promising that a PR merge immediately deploys it.
Knowledgebase entries, project rules, and plan updates written by the thread can stay pending alongside its code. Ship it carries them with the thread; they take effect when its PR merges, so project memory doesn't describe code that hasn't landed yet. Staged knowledge never ships on its own: without a merge, it does not land. Collections & history explains the pending state.
Follow the PR in chat
The transcript folds shipping into one collapsible row whose header shows the live status ("Writing the pull request…", "CI running — 2 of 5 checks done", "Ready to merge") with links to the PR and the changed files. Expand it for the milestones: Shipping started, CI ran, Ready to merge, Merged PR #n, and Landed on main — and, for a tracked deployment, production going live. The thread's status stays visible even when the agent is no longer typing.
A long wait says how long it has lasted: the status line ends with a running time ("In GitHub's merge queue · 12m 5s"), and hovering it shows the exact start. The timer appears for the merge queue, running CI, checks darting runs itself, a merged thread waiting for the next release, and a deploy darting watches on another host. When a merged thread reads Completed. Will be deployed in the next release, a Deploy now link under that line opens the project's Ship page.
On a red CI run, the agent receives the failed job names and log output in a fix-only turn. It makes a narrow correction, verifies it locally, and the turn-end commit is pushed to the open PR so the git host runs checks again. Fix-only means no unrelated refactors, feature changes, or weakening tests to make a check pass. A failure that calls for a larger design decision is handed back to you rather than guessed through. Environmental problems such as a runner or third-party outage are investigated as such rather than disguised as code changes. You can use Fix CI on a failed PR when the automatic work has stopped.
Ship it → sync branch → open PR → CI → ready to merge
↳ red → fix-only turn → push → CI again
Merge only when you choose
Green checks make the PR ready; they do not force it into main. Turn on Merge this PR automatically if you want it to land once checks and review allow it, or merge when you are ready. If a review asks for changes, a fix turn starts on the thread. Armed PRs go through the merge queue, where overlapping changes wait their turn. If the default branch moved, the platform merges it into the thread branch before publishing or merging; conflicts are resolved as a turn of that thread rather than dropped. See update from main.
Review conversations
A thread can also work the review itself: ask it to read the PR's inline review conversations, reply to each one, and resolve the ones it addressed. With Answer review comments on (Project settings → Pull requests), a trusted teammate's comments are picked up on their own — the thread replies and resolves as part of the fix turn; when it is off, a thread still does it when you ask.
Projects without a repository
In a project without a repository, the first thread's work is saved without a click: when the agent finishes a reply that changed code, darting creates the project's repository and pushes the thread's branch to it. That automatic save never ships — nothing lands on main, the thread stays open for more work, and main receives it only when you press Ship it.
Pressing Ship it (or Save) yourself before that has happened creates the repository and ships in one step. If your account is set to ship new repositories to GitHub and access is missing, Connect GitHub appears first; completing that connection creates the GitHub repository and saves the thread's branch there. Then Ship it opens the PR. When that PR merges, the thread closes with its published outcome. By default, a new repository is instead stored by darting: Ship it creates the repository and lands the thread on main as one commit, without a PR. Darting runs the project's recorded check command in a clean sandbox before landing; a failed check returns to the thread for a fix. You can later move that repository to GitHub from project settings for the PR workflow. See Git hosts & authentication.