Read the pull request your Brief delivered with a guided Tour, comment on the code, and approve or request changes without leaving Hamster.
Once Delivery opens a pull request or you link one by hand, the Review tab next to Plan becomes available. Until a pull request is linked, the tab is greyed out with the tooltip "No linked pull request".
The Review header shows the pull request title, +N −N line totals, a short AI overview, and a state pill linking to the code host. The rest of the tab is the Tour.
Review reads GitHub pull requests, GitLab merge requests, and Cursor Origin pull requests. On Cursor Origin, comments are published by the Hamster Origin App, so Origin shows that app as the author, and the toast reads Comment posted to Cursor Origin. Your Ready or Not yet vote stays in Hamster; neither is posted as a review decision to Cursor Origin.
Review works on any pull request linked to the Brief, not only one Hamster Cloud opened. To link one yourself, click + in the Brief header, choose Pull Request, paste the pull request URL, and click Link.
Click the pull request pill in the Brief header to see its state, number, and repository, with a link out to the pull request. To point the Brief at a different one, paste its URL there and click Replace. Unlink pull request removes the link.
If you can manage documents, you can also paste a pull request URL into the Brief's chat and ask Hamster to link it, or ask Hamster to unlink it. From the Hamster CLI, run hamster brief link-pr <brief> --pr-url <url> or hamster brief unlink-pr <brief>.
The Tour is a walkthrough Hamster writes for the pull request. It groups the changed files into named sections, each with a short summary and the real diffs inline. You can collapse or expand any file. On wider screens, a progress rail beside the Tour shows which section you're in and jumps to any section.
Hamster remembers which section and file you had open in this browser, so you can leave a long pull request and come back to the same place.
To rewrite one part of the Tour, hover a section title and click Regenerate section. Hamster builds the Tour after loading the pull request and the commits it compares.
Select code in a diff and click Comment, or click Comment on file in a file's header. Comments on a file appear under it, and you can Reply to a thread. After you comment, Hamster opens the Brief's chat to the thread the comment landed on.
Tick Send to Hamster on a comment to have Hamster act on it in a delivery. While a delivery is already running, the option reads Queue for Hamster and waits until that delivery finishes.
On GitHub and GitLab, Review writes as you, not as Hamster's app, so a comment or a decision needs your own sign-in to reach the code host.
If you have not signed in, a line at the top of Review reads "Comments and approvals stay in Hamster until you sign in." with a Sign in with GitHub button. If a previous sign-in has lapsed, it reads "GitHub sign-in expired. Reconnect to post comments and approvals as yourself." with Reconnect GitHub. GitLab merge requests show the same prompts with GitLab's name.
Hamster tells you which of the two happened each time you comment: "Comment posted to GitHub" when it reached GitHub, "Comment saved in Hamster. GitHub did not receive it." when it did not. A comment that failed to post shows "Couldn't post to GitHub" with a Try again beside it. A decision the code host rejects shows an error rather than appearing submitted.
When you sign in, Hamster posts your saved comments, plus any decision you made in this session.
On the Review tab, the Ready? vote in the Brief toolbar also decides the pull request review.
When GitHub or GitLab accepts your decision, the toast confirms it, for example "Pull request approved on GitHub". A decision kept only in Hamster has a local confirmation, for example "Approved in Hamster".
You can't approve a pull request you opened, including one your own delivery opened. You can still vote Not yet and describe what needs to change.