Cursor Origin

Connect a Cursor Origin repository so the AI can reference your code and its structure — and so Delivery can open pull requests against it.

Overview

Cursor Origin is Cursor's code host for repositories and pull requests. The Cursor Origin Connection gives Hamster two things at once:

  • Read access for the AI. Once connected, the AI can answer questions about the codebase, reference file structure and content when generating Briefs, and ground its suggestions in the repository you're actually working on.
  • A delivery target. When you deliver a Brief with Hamster Cloud against a connected Cursor Origin repository, Hamster pushes a delivery branch and opens a pull request on it.

The Cursor Origin Connection is separate from the Cursor Connection, which hands deliveries to Cursor Cloud Agents. You can use either or both. Cursor CLI runs inside a Hamster Cloud sandbox. Cursor Cloud cannot deliver a repository that lives on Cursor Origin.

One Hamster Origin App installation can include multiple repositories. The Cursor Origin Connection can see the repositories you granted access to during installation.

What It Syncs

  • Files and content — The contents of files in the repository at the branch you select, indexed for AI search and context.
  • Repository structure — Directory layout and file organization.
  • Code symbols — Functions, classes, and other named symbols indexed for AI search and context.

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.

How to Connect

  1. Go to Knowledge > Connections in your workspace and click the Cursor Origin tile. You need permission to manage connections.
  2. Review the access requested by the Hamster Origin App, then click Install Origin App. That opens Cursor Origin's app installation page. Hamster reads repositories, commits, and pull requests from the installation. It also reads file contents on the branches you select and the changes it links back to Briefs and Plans. The app also needs write access to push delivery branches, open pull requests, and publish comments from Review.
  3. On that page, install the Hamster Origin App and choose which repositories it can access.
  4. Hamster opens the repository picker on the Connections page in your original tab.
  5. Select repositories — Choose which repositories to index:
    • Hamster Free plan — You can index 1 repository across GitHub, GitLab, and Cursor Origin.
    • Paid Hamster plan — The picker lets you index up to 100 repositories per connection.
    • On Hamster's free plan, selecting more than one repository offers you an upgrade before you can confirm.

If installation is cancelled or fails, start again from the Cursor Origin tile.

Repository Selection and Branches

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 their indexed content is removed, without affecting the Connection itself.

Keeping the Index Fresh

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 an update is delayed, Hamster checks again automatically. Check the connection's indexing status if changes aren't appearing.

Connection Health

The connected Cursor 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 it and choose Reconnect Cursor Origin, or start again from the Cursor Origin tile.

Managing the Connection

Click the connected Cursor Origin card to reopen the repository picker. Changing the repository selection requires permission to manage connections. There is no Manage on Origin link on the card. The repositories the app can see are chosen on Origin; the repositories Hamster indexes are chosen in the picker.

To stop indexing a repository, clear it from the selection. The picker keeps at least one repository selected, so you can't clear the last one. To change which branch a repository tracks, reopen the picker and choose a different one.

Who Can Push

If delivery is blocked, follow the error shown in Hamster. Depending on the error, the repository owner may need to upgrade their Cursor plan, change the Privacy Mode Legacy setting, or enable Origin before you retry.

Read-only mirrors cannot accept delivery changes. Use a writable repository or ask the owner to resolve the mirror restriction, then retry.

Delivery and Pull Requests

Delivering a Brief with Hamster Cloud against a connected Cursor 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.

Cursor Cloud cannot deliver that repository. Its repository list only includes GitHub repositories the connected Cursor account can reach.

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 Cursor Origin repository.

Review on a Pull Request

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, Review shows you posting as Hamster (Cursor app). The toast says Comment posted to Cursor Origin.

Your Ready or Not yet vote stays in Hamster. Cursor Origin does not support posting either vote as a review decision. Hamster reads check runs but does not post them.

Starting Routines

A push to a connected repository's tracked branch fires the Push to branch Routine trigger. Pull requests, comments, and reviews on Cursor Origin don't start routines.

Importing Skills

From the Skills tab, click New skill and select Sync repo skills, then pick your Cursor Origin repository. Hamster reads the SKILL.md files in its .agents/skills/, .claude/skills/, or skills/ folder from the last indexed snapshot and adds them to your Skills library.

Import from GitHub only takes public GitHub links, so it can't read a Cursor Origin repository.

Tips

  • Track the branch you develop on — usually main or develop, not a feature branch.
  • You can connect GitHub, GitLab, and Cursor Origin side by side. They are separate Connections with separate repository selections.
  • Connecting a repository indexes it, it does not run it. Indexing reads and references the code for context; running code is Delivery's job, not the Connection's.
  • Pair Cursor Origin with Linear or Jira so the issue and the code that addresses it are both in reach when you ask.
  • Resolve access issues before retrying. Follow the error shown in Hamster and ask the repository owner to confirm that the repository accepts writes.