Background Agent not creating PR

Bug Reports
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

We’re encountering an issue where Background Agents on Slack integreation, that are not creating a Pull Request to Github.

This was working fine a week or so ago, and stop working.

Steps to Reproduce

On Slack comment define a task description.
In a thread ask @cursor to tackle it.

Cursor agent seems activated, but after a while when is marked as solved it does not come with a PR created, but instead just answer what it would have done.

Example answer:
“I’ve started by reviewing the task to…” with the following actions possible “Open in Cursor” & “Open in Web”.

vs.

“I implemented …” with the following actions possible “View PR”, “Open in Cursor” & “Open in Web”

Expected Behavior

We would expect the background agent to create the PR with the solution, like it did before.

Screenshots / Screen Recordings

Screenshot 2025-10-13 at 17.16.45.png
Screenshot 2025-10-13 at 17.16.45.png1820×838 87 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.11 but we’re using Slack so no version to specify.

For AI issues: which model did you use?

claude-4.5-sonnet

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report. This looks related to Background Agent issues we’re tracking.

Could you share:

  • A Request ID from one of the failed agent runs (from the Slack thread or agent logs)
  • Confirmation that your GitHub integration is still connected: Settings → Integrations

Please also try disconnecting and reconnecting the Slack and GitHub integrations to see if that resolves it.

If that doesn’t help, I’ll pass this to the team for a deeper investigation.

3

Hello @deanrie

Thanks for getting back to us.

  • Example of one request not working as expected: bc-0b5c4d8c-585c-4765-80d5-bc9ec414a9ac
  • We can confirm the integration is present in the settings and also as we have it connected before when it was working as expected.

Thanks in advance!

4

Another example that didn’t create a PR: bc-1cf07c00-179b-4bce-b9b1-743fa2bbad3b

6

Thanks for the info, that’s very helpful.