Turn a ready Brief into a pull request on GitHub or Cursor Origin, or a merge request on GitLab — from a conversation, or directly from the Brief workspace — without leaving Hamster.
A Brief is only valuable when it ships. Once your Plan is in place and your team is aligned, the next step is getting the code into a pull request or merge request. Hamster handles the dispatch, tracks the agent's work live, and links the Result back into the thread where you were already working.
When your Brief's Plan is ready and still has tasks to deliver, a Deliver button appears at the foot of the plan thread in chat. Click it to start delivery with the method from your delivery settings. Hamster checks that everything is ready, starts delivery against the selected repository, and the Delivery thread opens in chat.
Alternatively, tell Hamster directly in conversation:
The delivery thread opens and updates in real time as Hamster works.
Open the Brief and select Deliver from the action bar. Hamster picks the repository and branch for you and uses the method, model, and automation from your delivery settings, so there is nothing to confirm.
Both paths run the same pre-flight checks and use the same Delivery agent. The output — a pull request, merge request, or branch — is identical regardless of how you triggered it.
The chevron beside Deliver opens a menu of every method this workspace offers:
The first time anyone on your team clicks Deliver, Hamster asks how to deliver: pick one of the three method cards and click Continue. To automate the whole run, choose Automate with Hamster Cloud, leave Auto Approve the Technical Spec and Auto Deliver the Plan on (they're on by default), and click Deliver My Brief. Hamster resolves the Technical Spec, generates the Plan, and starts delivery from its Tasks without stopping for your review. If you aren't an owner or admin, Continue saves your pick as your own delivery settings instead. Once anyone on the team finishes the dialog, it doesn't show again.
Owners and admins can change the team's method, model, and automation later in Settings > Delivery. Any automation step you leave off pauses for your review.
To deliver differently yourself, turn on Override team defaults in Personal settings > Delivery. Your deliveries then stop following later team changes until you turn it off.
Hamster checks four things before dispatching:
| Check | What it means |
|---|---|
| Plan has tasks | Hamster Cloud generates a missing plan first. Cursor Cloud asks you to generate one before delivering. |
| Repo connected | Hamster can find a connected GitHub, GitLab, or Cursor Origin repository for the brief. |
| Spec ready | The technical spec meets your team's approval requirements. |
| No job in flight | A Delivery for this Brief isn't already running |
If any check fails, Hamster explains what's missing. Follow the prompt — regenerate a Plan if it has no tasks, connect a repository from Connections, review the spec, or wait for the current Delivery to finish — then try again.
When Auto Approve the Technical Spec is off and the Technical Spec still has unanswered questions or its investigation is still running, Deliver opens a Spec approval needed dialog instead of starting. Approve this time answers the open questions with the Technical Spec's recommended options and continues the Delivery. Review spec opens the Technical Spec so you can answer them yourself.
A Delivery thread opens as soon as the job is dispatched. The agent's work streams in live:
You can leave the Delivery thread and come back. The transcript persists as a permanent record of what was built and why.
If the Plan includes Person or Tool Tasks, the Delivery pauses at each one and resumes once it's done. See Task Assignment.
Send a message in the Delivery thread while the delivery is running to give Hamster a new instruction. Your message waits while the current turn finishes, then enters the coding session at a safe boundary, and the same delivery continues without restarting.
Pending messages appear above the composer until Hamster receives them, then move into the transcript. After delivery ends, the composer shows that the delivery is no longer running.
While a Hamster Cloud Delivery is running, a status line above the composer shows what it's doing, and Stop ends the current run; send a message to resume it. Once nothing is running, Archive replaces Stop. Archiving permanently deletes the delivery's saved working state, so it can't be resumed, but the transcript stays readable.
When the agent finishes, the final step in the Delivery thread shows the Result:
No need to switch to the code host to find what was shipped — the link is right there in the thread.
On the Plan tab, the Deliver button shows delivery progress while the agent works and disappears once delivery completes. After a failed run it stays, so you can deliver again. Once a pull request or merge request exists, the control in the brief header shows its state — "Draft #42," "Open #42," "Merged #42" — with a link out to it. The brief status moves to Shipping while the delivery runs and to Delivered when it succeeds. If the delivery fails or is cancelled, the status goes back to what it was.
If the agent hits an error, the Delivery thread shows the failure inline. The card reads Delivery Failed; click it to open the thread and inspect what happened. Common causes:
Fix the underlying issue and re-deliver from the Brief workspace or chat.