Turn a ready Brief into a GitHub pull request — 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 PR. 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 has a Plan and a connected GitHub repo, a Deliver button appears at the foot of the completed plan thread in chat. Click it to start delivery with your workspace's delivery method. For Hamster Cloud, that opens the delivery dialog: pick your target repo (or set up a repository if needed), and dispatch. Hamster checks that everything is ready, dispatches the job to your connected GitHub repo, 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. Pick the target repo and branch from your connected GitHub accounts, choose a delivery model, confirm, and dispatch. Hamster remembers your last pick for the next delivery.
Both paths run the same pre-flight checks and use the same Delivery agent. The output — a PR or branch — is identical regardless of how you triggered it.
The chevron beside Deliver opens a menu of every method this workspace offers:
Hamster checks four things before dispatching:
| Check | What it means |
|---|---|
| Plan exists | The Brief has a generated, accepted Plan with at least one Task |
| Repo connected | A GitHub repo is connected to your account |
| Push access confirmed | Hamster can push to that repo |
| No job in flight | A Delivery for this Brief isn't already running |
If any check fails, Hamster explains what's missing. Fix it — generate a Plan, connect a GitHub repo in Settings, or wait for the current Delivery to finish — then try again.
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.
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 in the queued-messages dock until Hamster receives them, then move into the transcript. After delivery ends, the composer shows that the delivery is no longer running.
When the agent finishes, the final step in the Delivery thread shows the Result:
No need to switch to GitHub 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, then drops away once the run finishes. Once a PR exists, the PR control in the brief header shows its state — "Draft #42," "Merged #42" — with a link to the pull request on GitHub. 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 "View Delivery" link on the Delivery card stays active so you can inspect what happened. Common causes:
Fix the underlying issue and re-deliver from the Brief workspace or chat.