I don’t seem to have cursor following along on the GitHub PRs and fixing check failures. I see the checks fail on the right pane, but I have to ask the agent to fix them.
And then when I do, it rarely finds all of them.
This looks like from the documentation that it should work. I checked permissions and it has the read and write checks permissions.
Any ideas? Is this supposed to work?
Hey, quick nuance: the Automatically fix CI failures feature is designed to work only for PRs created by Cloud Agent. For PRs you create yourself or via any other workflow, it won’t trigger, which explains what you’re seeing.
To get autofix on your own PRs, you can set up a custom Automation with the trigger Checks completed (on failure). The setup guide is in the Automations docs: Automations | Cursor Docs. The agent will run on every failed check and try to fix it.
Just to confirm: are the PRs where you expect autofix created by Cloud Agent, or are you pushing them yourself? If Cloud Agent creates them and it still doesn’t fire, let me know, there’s a separate known issue for that case.
About the agent rarely finding all of them: a more detailed prompt helps when you run it manually, explicitly say fix all failing checks, run them locally to verify. Another option is to run a separate task for each failed check.
Related feature request to expand the scope: Automations should monitor Github CI after creating a PR. Feel free to chime in there too.
>If Cloud Agent creates them and it still doesn’t fire, let me know, there’s a separate known issue for that case.
That is the case - these are all created by the cloud agent, not by me directly.
For prompting it to fix the failing checks, last time I used:
“please fix the lint errors that are failing on the PR checks” (same prompt I’ve used with claude)
For “Another option is to run a separate task for each failed check.” - how would I do that, just @cursor mesage it inside of a github PR?
Thanks and I really appreciste your response!!
Also I don’t see an “Automations” page on my cursor settings, either on the web or in the IDE. I’m on nightly for beta releases, so am not sure why it’s not showing up. I’m on a Pro $60 plan, is there some other plan I need for this? Teams?
Turns out its not a setting, its’ on the agents page at (https://cursor.com/agents) but not dashboard page (and not settings where the Feature report mentioned it would be) - posting this so hopefully it helps someone else.
Also note that this seems like a “spin up a new thread to respond”, vs. respond with the same context from the previous conversation the way that claude handles it (which I think provides more context and is possibly better)
Thanks for the info. Replying point by point:
Cloud Agent PRs, autofix isn’t triggering. This is a known bug on our side and we can reproduce it. Even when the PR is created by Cloud Agent and the Automatically fix CI failures toggle is enabled, check failure events don’t always get picked up. The issue is reported. I can’t share an ETA for a fix yet. I’ll post an update in the thread as soon as I have one.
Where Automations are. You’re right, the page lives at https://cursor.com/agents under the Automations tab, not in Settings or in the Dashboard. It’s available on Pro, you don’t need a separate Teams plan. Docs are here: Automations | Cursor Docs. I’ll flag the mismatch with the feature report to the docs team. Thanks for calling it out.
One task per failed check. The simplest way is to leave an @cursor comment directly in the PR with a specific instruction for each check, for example one comment for lint and another for tests. Each @cursor comment starts an independent run, so they can run in parallel and each one has a narrow context. This is usually more reliable than one general prompt like fix all failing checks.
About starting a new thread instead of continuing context. This is currently by design. Each Automation or each @cursor comment starts an isolated run with a clean context. There are upsides to this since it avoids mixing old attempts, but I get your point and I’ll pass it on as feedback to the team.
Let me know if anything else comes up with Cloud Agent PRs.