Cloud agents work on the web but desktop app reports Origin access denied

Support Bug Reports
, ,
1

I set up a new project in Cursor Origin and can work with it normally from the Cursor Mac app. Local Git operations, including pushing to the Origin remote, succeed.

The problem occurs only when I launch a Cloud agent for that project from the desktop app. The app reports:

[permission_denied] You do not have access to this repository on Origin. Contact your team admin if you believe this is a mistake.

Using the same Cursor account on cursor.com, Cloud agents run successfully against the same project, and the Cloud environment is configured and verified.

Expected behavior: launching a Cloud agent from the desktop app should work the same way as launching it from cursor.com.

Actual behavior: the desktop app returns permission_denied, while the website succeeds.

This looks like an authorization or account-context mismatch specific to the desktop app Cloud-agent launch path. Has anyone else encountered this, or is there a desktop authorization state that needs to be refreshed?

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

5

Where does the bug appear?

Cloud Agents & Automations — specifically launching a Cloud Agent from the Cursor Mac desktop app for a Cursor Origin repository.

Describe the bug

Cloud Agents launched from the Cursor Mac app fail with:

[permission_denied] You do not have access to this repository on Origin. Contact your team admin if you believe this is a mistake.

The same Cursor account can launch Cloud Agents successfully for the same project from the Cursor website. Local Git access is also working: the desktop project can fetch from and push to its Origin remote.

This appears to be an authorization or account-context mismatch in the desktop Cloud Agent launch path.

Steps to reproduce

  1. Create or open a project hosted on Cursor Origin.
    1. Open the project in the Cursor Mac app.
    1. Confirm that normal Git operations against the Origin remote work.
    1. Open the Agents window and select the project, branch, and Cloud execution.
    1. Send a simple prompt.
    1. Observe the permission_denied error.
    1. Open the same project using the same account on the Cursor website.
    1. Launch a Cloud Agent and observe that it works successfully.

Expected behavior

The desktop app should launch a Cloud Agent for the Origin repository just as the Cursor website does.

Actual behavior

The desktop app reports that the account lacks access to the Origin repository, while the website succeeds.

Operating system

macOS 26.5.2, Apple silicon

Version information

Cursor 3.17.21
Commit: 8f2a112cb2845a97b75fd932ea5c470579ca4060
Build date: 2026-08-25

Model

The failure occurs before model execution, so it does not appear to be model-specific.

Additional information

I verified the following after the initial failure:

  • Cursor is signed into the expected account.
    • git remote -v inside Cursor’s integrated terminal shows the correct Origin remote for fetch and push.
    • Local pushes to Origin succeed.
    • Reloading the Cursor Agents window clears the displayed error, but selecting Cloud and retrying produces the same permission failure.
    • The Cursor website continues to launch Cloud Agents successfully for the same project and account.
    • Request IDs and screenshots have been provided privately to Cursor Support.

Does this stop you from using Cursor?

No — local work and web Cloud Agents remain usable, but Cloud Agent launches from the desktop app are blocked.

9

Hey @Juan_Sanchez,

Good news: this isn’t anything on your end - your account and local Git access are both fine. Launching a Cloud Agent on an Origin repo takes a different path in the desktop app than on cursor.com, and that desktop path is where the permission_denied is coming from (which is also why reloading doesn’t clear it).

It’s not intended behavior and it’s an issue we’re tracking. For now, launching from cursor.com is the reliable path, as you’ve found. No need to send anything else over - I’ll follow up here when there’s an update.