Sign InGet Started

Cursor

Connect Cursor IDE to enable background agents that can run tasks directly in your codebase.

Overview

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: background 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.

What It Enables

  • Background coding tasks — Agents can work on implementation tasks in your codebase
  • Code changes — The agent can write new files, modify existing ones, and apply diffs

The Cursor connection is distinct from the read-only context connections. It allows the agent to take action, not just retrieve information.

How to Connect

  1. Go to Settings > Connections and click the Cursor card.
  2. In the dialog, enter your Cursor API Key.
  3. Click Connect.

The connection is ready once saved. Unlike OAuth connections, there is no redirect to an external site.

Getting Your Cursor API Key

Your Cursor API key is available in the Cursor settings.

To find it:

  1. Open Cursor.
  2. Go to Cursor Settings.
  3. Copy your API key from the account or API section.

One Connection Per Workspace

Cursor is a single-connection service. 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.

Tips

  • Background agents work best on well-defined, scoped tasks. Providing clear task descriptions and context produces better results than open-ended requests.
  • The agent operates in your local Cursor environment. Make sure Cursor is running and your project is open when you want the agent to work.
  • Review changes made by the agent before committing them. Background agents can make mistakes, particularly on complex or ambiguous tasks.
  • Connecting GitHub alongside Cursor helps the agent understand your repository structure and code conventions before making changes.

Related