Sign InGet Started

Delivering Briefs

Turn a ready brief into a GitHub pull request — from a conversation, or directly from the brief workspace — without leaving Hamster.

The job delivery does

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.

Two ways to deliver

From chat

When your brief has a plan and a connected GitHub repo, you can trigger delivery directly in conversation. Tell Hamster what you want to ship:

  • "Ship this brief"
  • "Deliver to myorg/backend"
  • "Ship the authentication brief to the API repo"

Hamster checks that everything is ready, dispatches the job to your connected GitHub repo, and posts a delivery card in the conversation. You can keep working in chat — the delivery runs in the background and updates in real time.

From the brief workspace

Open the brief and select Deliver from the action bar. Pick the target repo from your connected GitHub accounts, confirm, and dispatch.

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.

Before Hamster can deliver

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.

Watching delivery happen

A delivery thread opens as soon as the job is dispatched. The agent's work streams in live:

  • Boot phases appear first — environment setup, context load
  • Each step the agent takes (reading files, writing code, running checks) appears as it completes
  • Tool calls and phase transitions render as distinct items so you can follow the agent's reasoning

You can leave the delivery thread and come back. The transcript persists as a permanent record of what was built and why.

After delivery completes

When the agent finishes, the final step in the delivery thread shows the result:

  • Pull request opened: #123 — clickable link straight to the GitHub PR
  • Branch pushed: feature/my-branch — clickable link to the GitHub compare page so you can review the diff immediately

No need to switch to GitHub to find what was shipped — the link is right there in the thread.

If delivery fails

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:

  • A test or lint check failed during the delivery run — review the agent's output for specifics
  • Push access changed — check that Hamster's GitHub connection is still active in Settings
  • A merge conflict or branch protection rule blocked the push — the thread will describe the blocker

Fix the underlying issue and re-deliver from the brief workspace or chat.

Related