Cloud Agent "Repository access denied" — works for one team member but not another (same org/repo)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Team plan ([email protected]). Cloud Agent PR Review automation fails with “Repository access denied” on PRs created by my GitHub account (adam-oneoff) in the oneoffworld org. The exact same automation succeeds on PRs created by a teammate (alexhatzo) in the same repo (oneoff-api).

(edit: no automations succeed anymore with cloud agent)

Bugbot works fine on the same repo and PRs — this is Cloud Agents only.

What I’ve verified:

  • Cursor GitHub App installed on oneoffworld org with “All repositories” access
  • GitHub App authorized for adam-oneoff on both personal and org accounts
  • Created a duplicate automation under my own Cursor account — same error
  • Tested with empty PR and PR with actual file changes — both fail
  • Bugbot reviews the same PRs successfully

Steps to Reproduce:

  1. Create PR in oneoffworld/oneoff-api from adam-oneoff GitHub account
  2. Cloud Agent automation triggers
  3. Fails with “Repository access denied — The automation could not authenticate with the repository”

Expected Behavior:
Cloud Agent should access the repo, same as Bugbot and same as when teammate creates PRs.

Info:

  • Cursor account: [email protected] (Team Plan)
  • GitHub org: oneoffworld
  • GitHub user: adam-oneoff
  • OS: macOS

Steps to Reproduce

  1. Create a Cloud Agent PR Review automation on the oneoffworld org
  2. Open a PR in oneoffworld/oneoff-api from the adam-oneoff GitHub account
  3. Automation triggers but fails with “Repository access denied”
  4. Same automation succeeds when teammate (alexhatzo) opens a PR in the same repo

Expected Behavior

Cloud Agent should authenticate and review the PR regardless of which team member created it. Bugbot can access the same repo/PRs fine.

Operating System

MacOS

Version Information

Cursor Web (as of 2026-03-17)

Additional Information

Cursor account: [email protected] (Team Plan)
GitHub org: oneoffworld
GitHub user: adam-oneoff
Teammate’s GitHub: alexhatzo (his PRs work, mine don’t)
Repo: oneoffworld/oneoff-api (private)
Bugbot works fine on same repo/PRs — Cloud Agents only.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Automations not triggering for organization repositories (works for personal repos)
4

Hey, thanks for the detailed report. It helps that you already listed what you checked.

Bugbot working while Cloud Agents don’t is expected. They use different auth paths. Bugbot goes directly through the GitHub App installation, while Cloud Agents use user-level OAuth. If something is off with linking your GitHub account to Cursor, Cloud Agents are the ones that break.

A few things to try:

  1. Go to https://cursor.com/dashboard?tab=integrations. What does it show for GitHub? Is adam-oneoff connected?

  2. Try disconnecting GitHub on the dashboard, then reconnect it.

  3. Also check Sign in to GitHub · GitHub. Find Cursor GitHub Extension and make sure the oneoffworld org is authorized. If you’re not sure, revoke it and authorize again.

  4. What scope is your automation set to, USER or TEAM? If it’s USER, try switching to TEAM. That uses a different auth path and might work around the issue.

  5. The most useful thing for debugging is the bcId or request ID from the failed run in the automation history. With that we can pinpoint exactly where auth is failing.

This is a known category of GitHub auth issues for Cloud Agents and the team is aware. Let me know what you find from the steps above, and if you can share the bcId we can dig deeper.