Origin Cloud Agent 403 repository_access_denied after Create Repo

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cloud Agents lost git write to an Origin repo after promoting agent-temp → Create Repo. UI browse still works as owner; agent push returns 403.

Repo: adam-caton/Lapaz-regional-hospital
Agent: bc-e1cbfaa0-a6a6-48b7-a1cf-7ab486bf2c94 (Grok-Lapaz-Master)
Remote: https://origin.cursor.com/git/adam-caton/Lapaz-regional-hospital.git

Error:

fatal: unable to access '...Lapaz-regional-hospital.git/': The requested URL returned error: 403
{"error":"You do not have access to adam-caton/Lapaz-regional-hospital on Origin. Contact your team admin if you believe this is a mistake.","reason":"repository_access_denied"}

Empty commit stayed local: branch cursor/write-probe-2c94 @ 5c2463cdcfb4f0608840a4c2d8831df3824ff379. Did not use GitHub.

Contrast: sibling Origin repo adam-caton/cah-policy-detect still accepts pushes from its existing Cloud Agent after the same Create Repo flow.

Also: fresh Cloud Agent launches mis-route toward GitHub for this Origin-only repo (“not accessible to connected GitHub account”).

Ask: restore Cloud Agent Origin git write for post–Create Repo standalone Origin repos; stop requiring GitHub for Origin-only repos.

Happy to share more ids/screenshots. — Adam Caton

Steps to Reproduce

  1. Use the Origin-only repository adam-caton/Lapaz-regional-hospital and promote agent-temp → Create Repo.
  2. From the existing Cloud Agent (bc-e1cbfaa0-a6a6-48b7-a1cf-7ab486bf2c94), attempt a git push to the Origin remote.
  3. The push returns HTTP 403 with reason repository_access_denied, while UI browsing still works as owner.

Expected Behavior

Cloud Agent should retain Origin git write access after Create Repo, and fresh launches for Origin-only repositories should use Origin rather than requiring GitHub.

Operating System

Other

Version Information

Cloud Agent / Origin repository; Cursor version not available.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

9

Hey @Adam_Caton, thanks for the report!

When you used Create Repo, the draft repository your agent was working in was renamed in place to adam-caton/Lapaz-regional-hospital. The agent itself keeps a credential tied to the original address, so it keeps working as long as it pushes through that address.

Right after you created the repo, the agent switched its git remote to the new address (origin.cursor.com/git/adam-caton/Lapaz-regional-hospital.git), and from that point, every fetch and push returned the 403 you saw. Your account and the repository are fine, which is why browsing on the web still works, and your other repo still pushes because that agent never changed its remote.

To unblock the Grok-Lapaz-Master agent, ask it to run:

git remote set-url origin https://origin.cursor.com/git/adam-caton/tmp-1f9b8a6382536b43.git

and push again. That address keeps working after Create Repo and the commits land in Lapaz-regional-hospital. Alternatively, start a fresh Cloud Agent on the repo from https://cursor.com/agents, which gets a credential for the new name.