Thanks for the response.
Unfortunately, executing a test run is still not working.
Pulling up the failed run in the history shows me this:
I’m not sure what else to do as our GHE github is definitely integrated and functional, bugbot and cloud agents have been working fine for us since January.
@mmmeff, can you check that there is actually a GHE App registered under the Integrations tab of your dashboard?
If so, please try registering a new application and removing the old one.
Removed the old “Cursor” app and added the new “Cursor Enterprise” one. However, I’m still getting the same error when attempting to test run my automations.
I’m helping @mmmeff on this- @Colin if it is any help debugging, we have limited Cursor Enterprise to only be able to access select repositories, rather than access all repositories (this is a requirement for our environment).
Update here - it seems as though detaching and re-creating the cursor app has entirely broken our ability to spawn cloud agents 
Splitting this off into its own thread, as I think it will be easier to handle here.
@mmmeff Can you make sure that after recreating the Cursor app, you have made sure that the GitHub app actually gets installed on your organization within GHE?
once u do u still need click manage GHE > view it on Github → and explicitly install the Cursor App
@Colin
Yes, this step is completed. The app is configured both for the organization as well as my own personal account on our GHES deployment
Thanks @mmmeff !
I can see that you’ve successfully spun up cloud agents since this post:
Has that been addressed?
You (and your team) will need to reconnect to GitHub on https://cursor.com/dashboard/integrations (the very first option you see, switching from github.com to your GHE instance)
If cloud agents are working again for your team, can you try both a team-owned automation and a user-owned one against a GHE repo and see if the behavior differs between them?
Yeah, I was able to get cloud agents running again, but I had to remove our cloud environment setup before it would let me boot one up.
I attempted re-creating the environment setup but as soon as I reintroduce one, the agents are no longer able to start again.
Both private and team-owned automations still do not work and exhibit the same issue.
I think there’s something very wrong with how cursor is authenticating with our GHES deployment.
Even executing agents and telling them to assign PRs to certain individuals gets them trapped in a death spiral where it cannot find the correct credentials to interface with our github instance.
Seeing errors like:
pull request create failed: GraphQL: Resource not accessible by integration (createPullRequest)
Even though the app clearly is configured with read/write perms when I look in the app settings in github 
Hey Matt,
How are things looking now? Have you been able to make some progress?
