Connect a Cursor Origin repository so the AI can reference your code and its structure — and so Delivery can open pull requests against it.
Origin is Cursor's code host for repositories and pull requests. The Origin Connection gives Hamster two things at once:
The Origin Connection is separate from the Cursor Connection, which hands deliveries to Cursor Agents. You can use either or both. Cursor Agents deliver GitHub repositories only, so they can't deliver a repository that lives on Origin.
Origin connects by installing the Hamster Origin App. One installation can include multiple repositories, and the Connection can see the repositories you granted access to during installation. The same installation can be used by multiple Hamster teams, and each team chooses its own repositories.
Each repository tracks one branch, which you choose when you connect it.
Once a repository is indexed, ask about it in Chat and Hamster answers from that code.
If installation fails, Hamster shows why. Whether you cancelled or it failed, start again from the Cursor Origin tile.
This recording predates the write-access list in Hamster's connect dialog and Origin's install window closing on its own.
You can also install the Hamster Origin App on Origin first, from Origin Apps (the Apps page in your codebase settings) or from the app's install link. Origin then sends you to Hamster:
If Hamster can't finish the connection, it adds no card, shows a message saying why, and leaves the app installed on Origin. See Troubleshooting.
For each repository you select, choose the branch to track — by default the repository's own default branch. Hamster indexes code from that branch.
Confirming the selection starts indexing each repository. Repositories you clear from the selection stop syncing and drop out of code search, without affecting the Connection itself. Hamster keeps what it already indexed, so selecting a repository again picks it back up. To stop indexing everything, clear every repository; the button then reads Stop indexing repositories.
Code updates normally appear after a push to the tracked branch. There are no per-repository webhooks to set up. Pushes to other branches, tag pushes, and branch deletions do not update the index. If you delete the tracked branch, its last indexed code remains searchable; choose another tracked branch to keep your code context current. If you delete a repository on Origin, Hamster stops indexing it and removes its indexed code.
If an update is delayed, Hamster checks again automatically. Check the connection's indexing status if changes aren't appearing.
The connected Origin card shows how many repositories are connected and a rollup of indexing state across them: Indexing, Embedding, Indexed, Index stale, or Sync failed. A failed sync surfaces the reason so you can act on it.
If Hamster can no longer use the installation, the card reads Reconnect to continue syncing. Click the card: the picker shows Cursor Origin authorization expired with a Reconnect Cursor Origin button. If you can't manage connections, the card reads Ask an admin or creator on this account to reconnect instead.
If the installation is suspended on Origin, the card reads Suspended in Cursor Origin. Hamster keeps your repositories selected and syncs them again once the installation is resumed.
Click the connected Origin card to reopen the repository picker. Only people who can manage connections can open the picker or see the × on the card.
The repositories the app can see are chosen on Origin, with Manage on the Hamster Origin App in Origin Apps. The repositories Hamster indexes are chosen in the picker. If you remove a repository from the app on Origin, Hamster stops indexing it and it drops out of code search.
To stop indexing a repository, clear it from the selection. To change which branch a repository tracks, reopen the picker and choose a different one.
Either way, Briefs, Tasks, and other data are kept, and Hamster doesn't delete the branches, pull requests, or comments it created on Origin. To connect again, start from the Cursor Origin tile.
Delivering a Brief with Hamster Cloud against a connected Origin repository pushes the delivery branch and opens a draft pull request. It stays a draft when the run finishes; mark it ready yourself when you want reviewers on it. If a pull request is already open for that branch, Hamster reuses it instead of opening a second one.
The pull request is opened by the Hamster Origin App, not by your Cursor account. Commits are authored as Hamster Agent.
The pull request is linked back to the Brief that produced it. In the Brief header, the pull request control shows Draft, Open, Merged, or Closed and links out to Origin.
You can also start the delivery from chat by asking Hamster to deliver the Brief to your Origin repository through Hamster Cloud.
Review reads that pull request's reviews, comments, and checks. Comments you post from Review are published by the Hamster Origin App, so there is no separate sign-in. On Origin the author is the app, not you; in Hamster your comments show Hamster (Cursor app) as the author. The toast says Comment posted to Cursor Origin.
Your Ready or Not yet vote stays in Hamster; Hamster doesn't post either vote to Origin. Hamster reads check runs but does not post them.
A push to a connected repository's tracked branch fires the Push to branch Routine trigger. Pull requests, comments, and reviews on Origin don't start routines.
From the Skills tab, click New skill and select Sync repo skills, then pick your Origin repository. Hamster reads each SKILL.md inside a subfolder of .agents/skills/, .claude/skills/, or skills/ (for example skills/my-skill/SKILL.md) from the last indexed snapshot and adds it to your Skills library.
Import from GitHub only takes public GitHub links, so it can't read an Origin repository.
Hamster reads repository contents for code context and needs write access to publish delivery branches and pull requests. For Review, it reads reviews, comments, and checks, and posts comments. These permissions also let an app do more, including merging pull requests, turning on auto-merge, re-requesting check runs, dismissing reviews, and posting review decisions. Hamster does none of these. The Hamster Origin App asks for:
Origin adds read access to repository metadata on every install and shows the exact permissions on its install screen. The permissions apply to every repository the app can access on Origin, not only the ones Hamster indexes. To limit them, give the app access only to the repositories you plan to use.
main or develop, not a feature branch.