Cursor Cloud Agents are failing to checkout to a big repo

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

:wave: Hey team, I’ve been trying again some Cursor Cloud Agents recently. They used to work for our frontend repo, but it looks like it’s not the case anymore.

They consistently fail during the Checking out repository… step, which leads me to believe that we are reaching the platform’s limit but this is not documented anywhere, nor in any forums and the error is not explicit (cf video attached)

Is there anything we could do to make this work ?

Steps to Reproduce

Try to run a cloud agent for a big repo

Expected Behavior

The agent starts and run the prompt

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77 (Universal)

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @valentinmelusson :waving_hand:

Can you grab me a request ID (the three dots in the upper right). Happy to look into it for you with that info. :slight_smile:

Hey @Colin, here is one request ID that failed : bc-967de217-7960-4aab-adc1-753d8858652c

Let me know if you need any more info (and thanks for taking a look :bow:)

Thanks!

The good news is that repo size shouldn’t be the issue here. Our own (very large) monorepo works great with cloud agents.

Looking at your logs, they match a pattern we’ve seen where the culprit was the .cursor/environment.json file for a given repo. Common issues include outdated repo URLs.

If nothing jumps out at you in your current environment.json, I’d recommend walking through the setup process again to regenerate it from scratch.

We know we need to surface .cursor/environment.json issues better (there’s a ticket for it), so if this turns out to be the problem, I’ll make sure to add your case to help prioritize the fix.

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