Feature request: GitHub Projects (v2) read/write for Cursor agents, including user-owned boards

Ideas Feature Requests
, ,
1

Feature request for product/service

Cloud Agent (GitHub, Slack, Linear,…)

Describe the request

Summary

Cursor’s GitHub App gives cloud agents, Projects, Bugbot and Automations access to repositories, but there is no way for them to read or update GitHub Projects (v2) boards. Please add Projects support so agents can keep a project board in sync with the work they do.

Use cases

  • Auto-create a board per new project. When I start a new Cursor Project for a client site (for example a “Site Launch” project with ~9 parallel threads), I want a matching GitHub Project created from a template, linked to the repo, with one item per task.
  • Update status as agents work. When a thread opens a draft PR, the linked item should go to “In review”. When it’s blocked (for example a missing secret), it should go to “Blocked” with a note. Today every status change is manual or needs a separate bot running on my PC with my personal gh login.
  • One task board across tools. I run a single board (a user-owned Project v2) where every task has one owner and one status. Cursor agents are the main source of work, but they can’t see it or write to it.

What we found

  1. Cursor’s GitHub App has no Projects permissions, and there’s no native Projects integration in Cursor.
  2. A custom GitHub App doesn’t help. I created one with Projects permissions, but Cursor cloud agents on github.com always use Cursor’s app or my personal login, not a custom app.
  3. GitHub limitation: GitHub Apps and fine-grained PATs cannot access user-owned Projects v2 at all. Only a classic token or OAuth with the project scope can. Org-owned Projects do allow app access.
  4. Built-in Project workflows (item added, PR merged, closed) only cover a small part of this. They can’t create boards or set custom statuses.

Request

  1. Add Projects (read/write) to Cursor’s GitHub App, so agents can create and update org-owned boards.
  2. Support user-owned boards through the user’s own GitHub authorization with the project scope (opt-in), since GitHub doesn’t let any app reach them.
  3. Ideally, a native integration: link a Cursor Project to a GitHub Project, create items for threads, and update status and PR links automatically.

Environment

  • github.com (not GHES), personal account, all repos installed on the Cursor GitHub App
  • Using Cursor cloud agents and Cursor Projects