Overview

With Cursor in Plane, you hand a coding task to the Cursor Cloud Agent directly from the work item. Mention @cursor on any work item or assign it directly, describe what you want, and Cursor will read the work item context, work against your connected GitHub repository, and open a pull request linked back to the work item.

It fits naturally into the way your work already moves through Plane. The work item is the brief, the comment thread is the conversation with the agent, and the resulting pull request shows up on the work item the moment it's ready for review.

Features

• Trigger from any work item
  Mention @cursor on a comment, or assign it directly to launch a Cursor Cloud Agent session for that work item.

• Automatic work item context
  The work item's title, description, and identifier are passed to Cursor so it understands what to build.

• PRs linked back to Plane
  Cursor prefixes the pull request title with the work item identifier (e.g. [ENG-124]) so Plane's GitHub integration automatically links the PR to the work item.

• Multi-repository projects
  Map one or many GitHub repositories to a Plane project. When multiple are mapped, select the target inline with [repo=owner/name].

• Conversational follow-ups
  Reply in the same thread to send follow-up instructions to the running Cursor session, no need to start over.

• Live progress in the conversation
  Intermediate updates appear as collapsible thinking indicators; the final summary and PR link are posted as replies.

• Shared or per-user authentication
  Run with a single workspace API key (PRs open under the Cursor GitHub App), or switch to per-user mode where each member connects their own Cursor account and PRs open under their personal GitHub account.

• Branch override
  Pin a default branch per project–repository mapping when Cursor should start from somewhere other than the repository's default branch.

Configure

1. Install the Cursor app from the Plane marketplace. This creates the workspace connection between Plane and Cursor.

2. Choose an authentication mode.

   • Shared: one workspace-level Cursor API key, PRs open under the Cursor GitHub App.

   • Per-user: each member connects their personal Cursor account; PRs open under their GitHub account and usage tracks to their personal Cursor plan.

3. Add the API key. In shared mode, paste the workspace key on the Cursor settings page. In per-user mode, each member adds their own key from Profile → Connections.

4. Map projects to repositories. For every project that should use Cursor, pick one or more GitHub repositories from the list (fetched directly from Cursor). Optionally pin a default branch per mapping.

5. Mention @cursor on any work item in a configured project. If the project is mapped to more than one repository, include [repo=owner/name] in your message to pick the target.

Prerequisites: A Cursor account with Cloud Agents access, a Cursor API key, and at least one GitHub repository already connected to your Cursor account.

👉 For step-by-step instructions, see the Cursor Integration Guide.