Pausing a run puts it on hold without throwing away the work so far — handy when you want to step away, take a closer look, or stop the spend for a while without ending the attempt. This page covers pausing a run and picking it back up. Pausing isn’t the same as cancelling; to end a run for good, see Cancel a running task.
When you can pause
The Pause button appears on the run detail page, and only while the run is Developing — the step where it’s writing code. During other steps (planning, testing, reviewing) and while a run waits on you at a gate, the button isn’t shown. Open the run detail page for a run that’s actively developing and you’ll find Pause in the action bar near the top.
Pause the run
Select Pause. The pause is cooperative: the run finishes the step it’s on rather than stopping mid-change, so nothing is left half-done. While it wraps up, the button reads Pausing…. Once it reaches a safe stopping point, the run settles into the Paused state.
While a run is paused:
- Spend stops. Nothing is charged while it sits paused.
- Your place is kept. The run holds everything it’s done so far, on the same branch.
- The project stays busy. A paused run still holds the project’s one-run-at-a-time slot, so other tasks keep waiting their turn. If you need the project free for other work, cancel the task instead of pausing it — see The task queue.
Resume the run
You can resume from either of two places:
- The run detail page. The paused run shows a Run paused card with a Resume button. Selecting it opens a Resume run? confirmation, which notes that resuming continues the work and draws on your balance again. Confirm with Resume.
- The task detail page. A Resume button (▶) sits in the action bar. Selecting it resumes the run directly, without a confirmation step.
Either way, the run picks up from the step after the one where it paused — it doesn’t repeat work already done, and it continues on the same branch. From there it carries on through the pipeline as usual.
Pause is one of several ways a run waits
A run can also pause itself for other reasons — waiting on a gate, a plan approval, a question, or payment. Those are different states, each with its own control, and they’re not something you trigger; Paused is the hold you start yourself. For the whole set and what each one waits on, see Run states and the Run states reference.