Persistent "Repository not accessible to the installation" + "Resource not accessible by integration" errors on GitHub PR fetch/create despite multiple app reinstalls (organization repo)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I’m experiencing ongoing GitHub integration issues with Cloud Agents / Background Agents / Automations when interacting with pull requests in an organization repository. Even after uninstalling and reinstalling the Cursor GitHub App multiple times (with explicit repo inclusion or “All repositories”, plus full relevant permissions), reconnecting in Cursor settings/dashboard, and verifying org third-party access, the problems continue.
Exact errors observed (from various runs):

Failed to fetch PR #[redacted] from GitHub: Repository not accessible to the installation: [redacted org/repo path]
GraphQL: Resource not accessible by integration (repository.pullRequest.statusCheckRollup.nodes.0.commit…) [truncated]
Related/earlier errors: pull request create failed: GraphQL: Resource not accessible by integration (createPullRequest)
Similar 403/401 failures when attempting PR comments, status checks, or other write/read operations on PRs/issues.

Steps already tried (repeatedly):

Uninstalled Cursor GitHub App from the organization/repo → reinstalled fresh via GitHub Apps - Cursor · GitHub, selecting the org and ensuring the target repo is included (or “All repositories”).
Confirmed permissions in GitHub → Installed GitHub Apps → Cursor: Contents (Read & Write), Pull Requests (Read & Write), Commit statuses (Read), Checks (Read), Issues (Read & Write), Metadata (Read-only), and others as needed.
Reconnected GitHub in Cursor app settings and at https://cursor.com/dashboard?tab=integrations.

Steps to Reproduce

Create an automation that triggers from a PR comment and hit “test run”

Expected Behavior

we get an error and it won’t run
Failed to fetch PR #1589 from GitHub: Failed to create installation access token for installation 70682934

Operating System

MacOS

Version Information

Cursor automations - web

Does this stop you from using Cursor

Yes - Cursor is unusable

2 Likes
3

Hey, this is a known issue. The installation token the agent gets in the sandbox doesn’t include the right scopes for pull request and issue actions, even when the GitHub App permissions are set up correctly. Your error, “Failed to create installation access token for installation 70682934”, is caused by the same thing.

A few other users have reported the same problem:

The team knows about it and is tracking it. No ETA yet, but your report helps with prioritization.

Workaround for now: after the agent finishes, you should get a link to create the PR manually. The branch and commits will already be there, so you just need to open the PR yourself. Not ideal, but it works until this is fixed.

Let me know if you have any questions.

5

Having the same issue.

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.