Background Agent - code change won't be push to origin after opening a github PR

Bug Reports
1

Describe the Bug

When working with Background Agents, once I ask it to open a PR, any following changes by the background agent won’t be pushed to origin and won’t be reflected in the PR.

My current workaround is to checkout the changes locally and continue from there.
(note that when I checkout locally, the latest changes by the background agent are not reflected in the local checkout - meaning, anything that does not show on origin (PR) is not checked out locally)

Steps to Reproduce

Configure the Github integration (on Github Enterprise).
Create a new background agent job that has made code changes.
Open a pull request from the background agent’s Cursor IDE interface.
Ask the agent to perform additional changes.

Expected Behavior

I expect that any additional changes done by the background agent, after opening a PR, would be automatically push to the PR.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.1
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:06:37.704Z (2 days ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Additional Information

I’m working with Github enterprise.

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

One thing that I noticed just now - one of my background agents does indeed push the changes to the PR when the agent finishes making changes, but 2 other background agents do not.

3

UPDATE:
It seems that the background agent completes the changes but silently fails to commit them.
In our case, we have pre-commit lint checks that may fail.
I noticed that when the agent completes it work, the changes are not committed and pushed to origin because the pre-commit failed, yet there is no indication for that.
Furthermore, in the source control panel, there are no apparent file changes until the “sync” icon is pressed, and then the staged changes suddenly appear.

So, bottom line, if pre-commit fails, the agent will silently fail and the user won’t get an indication for that.