Cursor GitHub App Does Not Have Issue View or Create Permissions

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

When I ask for it to read an issue, it says it can’t find it (GitHub reports 404 when you don’t have permissions to view an issue)

When I try to create an issue, I get a response like this:

gh issue create failed because the GitHub token in this environment does not have permission to open issues:

GraphQL: Resource not accessible by integration (createIssue)
So the issue was not created from here.

Why this is important:

A key workflow when using cloud agents is to ask the agent to fix a specific issue, or to ask the agent to create an issue so you can work on a problem later. As things stand now, neither of these can be achieved with Cursor when the repository is private.

A better fix would be to just let users configure the permissions themselves, since I can imagine the specific things that a user might want to let cursor do in a private repo might vary from project to project.

Steps to Reproduce

  1. Configure the GitHub integration
  2. Start a cloud agent session with a private repo
  3. Enter: Please create a GitHub issue titld “test” with content “test”. Or, “Please read and address GitHub issue #22

Expected Behavior

I can ask a Cursor cloud agent to create a GitHub issue for me, or ask it to read one, even on a private repository.

Operating System

Windows 10/11
MacOS
Linux

Version Information

Its the web interface. There is no version to report.

For AI issues: which model did you use?

This is not related to the model, but if you must know, I tested Composer 2 and Composer 2.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Brian_Heise!

Thanks for the feedback.

The cloud agent’s GitHub installation token does not include the issues scope. The GitHub App requests broad permissions at the app level (which users see in installation settings), but the token actually minted for the sandbox is scoped more narrowly.

We have an open issue here to figure out what to do (either add issues scope to background agent runner GitHub token or update docs to remove Issues from supported permissions. Have added your feedback to that ticket!

@Colin I want to clarify the issue. I am faced with the same issue on the team plan at work. I can’t read and write github issues in the github organization of the company. Meanwhile, I can read and write github issues of my personal github repositories in my personal Cursor Pro+ plan. What are differences?

Hey @yu-iskw

This behavior (not being able to view issues while using Cloud Agents) should be consistent across different plan types!

What does it look like when it’s working for you? Feel free to share a screenshot.

@Colin The screenshot below was run on my personal Pro+ plan. Though I don’t set extra secrets for the GitHub token, it was able to created the issue. I don’t do the same on the team plan at work.

Can you open up the Worked for 13s? That would show exactly how the agent did it.

With that said, I noticed your repo is open-source, which might also be making the difference here.