Connect Cursor IDE to enable Cloud Agents that can run Tasks directly in your codebase.
The Cursor Connection is different from other Connections. While GitHub, Linear, Slack, and Notion give the AI read access to data for context, the Cursor Connection enables a different capability: Cloud Agents that can perform coding Tasks inside your development environment.
When Cursor is connected, Hamster can delegate coding work to an agent running in your Cursor IDE — writing code, applying changes, and working through Tasks while you focus on other things.
This is an advanced feature that operates on your local development environment. It requires an active Cursor installation with an active session.
The Cursor Connection is distinct from the read-only context Connections. It allows the agent to take action, not just retrieve information.
The Connection is ready once saved. Unlike OAuth Connections, there is no redirect to an external site.
If the Connection fails after being saved (e.g., due to key expiration or Cursor account changes), the Connection will show a Reconnect required badge on your Connections page. Click the Connection and re-enter your API key to restore access.
Your Cursor API key is available in the Cursor settings. The expected format is key_ followed by alphanumeric characters (e.g. key_abc123xyz).
To find it:
Cursor is a single-connection service per workspace. You can have one active Cursor Connection per workspace. Once connected, the Cursor card no longer appears in the Add Connections grid. To change the connected Cursor account, remove the existing Connection first and then add a new one.