Deliver Briefs through your connected Cursor account, with Cursor handling the hosted environment and Hamster tracking the delivery.
Overview
The Cursor connection lets Hamster delegate Brief deliveries to Cursor Agents on your connected Cursor account.
Cursor owns repository access and cloud environment setup. Hamster sends the agreed work and context, tracks the run in the delivery thread, and links the result.
How It Works
Connect the Cursor account whose agents will handle deliveries.
Grant Cursor access to the repository. Cursor runs the agent in the cloud environment configured in Cursor. Cursor Agents delivers only to GitHub repositories. Use Hamster Cloud for repositories on GitLab or Cursor Origin.
In Hamster, open the chevron beside Deliver on the Brief and choose Cursor Agents. If no Cursor key is connected yet, Hamster asks you to connect one first. Delivery then starts using the Cursor model and pull-request setting from your delivery settings.
Follow progress and the final result from the Hamster delivery thread.
How to Connect
Create a user API key in your Cursor account at cursor.com/dashboard > API Keys. Cursor keys start with crsr_. A Cursor service-account key works too.
In Hamster, go to Settings > Connections and click the Cursor card.
Under Connect as, choose Yourself to keep the key private to you, or the team to share it with everyone. The team option appears if you can manage Connections.
Paste the key into API Key and click Connect. Hamster rejects a key that isn't in the crsr_ format.
Deliveries run on the Cursor plan behind the connected key, and pull requests open as that Cursor identity — so a personal key opens pull requests as you. If a team key is already saved, the dialog offers Replace team key instead.
Related
Cloud Agents — Hamster's own cloud agents are separate from Cursor Agents.
Cursor Origin — Connect repositories hosted on Cursor Origin; separate from Cursor Agents.
OpenAI Agents — The same delivery shape on your OpenAI account.