# Background Agent doesn't push new commits **URL:** \ **Category:** Bug Reports\ **Tags:** github, cloud-agents\ **Created:** [February 18, 2026, 4:54am UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158 "2026-02-18T04:54:18Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [February 18, 2026, 4:54am UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/1 "2026-02-18T04:54:18Z")
### Where does the bug appear (feature/product)? Background Agent (GitHub, Slack, Web, Linear) ### Describe the Bug Long Running Prompts via Github do not trigger new commits. As you can see on the screenshot, there are no commits in between my message and cursor’s response. ### Steps to Reproduce Start a long running agent via the web dashboard. Then follow up with a github comment on the PR to update something ### Screenshots / Screen Recordings ![Screenshot 2026-02-18 055137.png](https://us1.discourse-cdn.com/cursor1/original/3X/1/a/1a18c16ebf1accff95deb4afe37cd96f94d585e2.png) ### Operating System Windows 10/11 ### Version Information No version. ### For AI issues: which model did you use? Codex 5.3 High ### For AI issues: add Request ID with privacy disabled bc-5e384971-cf53-452a-9efb-24fb051eb19b ### Does this stop you from using Cursor Sometimes - I can sometimes use Cursor ---
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [February 18, 2026, 5:30am UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/3 "2026-02-18T05:30:18Z")
Here is a second one where no commits were pushed: bc-c7ca4ca6-351f-407f-9c2f-64131824a667 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/5/1/514ac9b28126558a2e6382837f67dfe48de26739.png) UPDATE: and even with a second prompt: ![image](https://us1.discourse-cdn.com/cursor1/original/3X/4/9/4986ef2acfb0fab4694e4b09a4a7e4500acc6a2c.png) ---
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [February 19, 2026, 7:04am UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/5 "2026-02-19T07:04:40Z")
Any news about this? @deanrie ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [February 21, 2026, 12:21pm UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/6 "2026-02-21T12:21:06Z")
Hey @gillesheinesch! I took a look at those Request IDs. Both hit a known issue where the PR body generation step was timing out (exceeding a 60-second deadline). This is the step that runs after the agent finishes processing your follow-up. The error rate was relatively high this week, but decreased significantly yesterday. Could you let me know if you’re still seeing this with new runs? If so, happy to dig in further with fresh request IDs. ---
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [February 22, 2026, 6:31am UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/8 "2026-02-22T06:31:23Z")
Hello @Colin , Thanks for the explanations. Unfortunately I still have the same issue. Here is the ID: bc-718706f8-55a1-413c-bc41-e90edad2124b ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [February 24, 2026, 9:44am UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/9 "2026-02-24T09:44:05Z")
Sent you a PM – it looks like there’s a commit on this ID! ---
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [February 24, 2026, 3:23pm UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/10 "2026-02-24T15:23:49Z")
Hello @colin, Sorry for that. Here is the correct ID: bc-50127fb2-5d27-4ce2-971e-9134b1b39606 ---
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [March 1, 2026, 1:21pm UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/11 "2026-03-01T13:21:13Z")
Hello, I found one more where the changes are not committed: bc-d190829d-bd14-497f-8fa5-670b25fe8758 ---
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [March 1, 2026, 7:00pm UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/12 "2026-03-01T19:00:39Z")
Here two more: - bc-cbfda7de-f8a3-408f-962b-6f3179861be0 - bc-82f2c459-fed5-4de6-90ee-9fe4fbe96d63 ---
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [March 6, 2026, 4:15pm UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/13 "2026-03-06T16:15:43Z")
Hello any news about this one? I’m wasting prompts to always ask cursor to not forget to push the commits. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [March 9, 2026, 2:35pm UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/14 "2026-03-09T14:35:06Z")
Hey @gillesheinesch! Sorry for the delay! I looked into both of those runs. The background agent is instructed via its system prompt to commit and push, but it looks like you have a rule in your `.cursor/rules/` that says “Do not commit anything on your own” which is overriding the push behavior. The agent sees conflicting instructions and follows your rule. If you remove or update that rule, the agent should commit and push as expected. You could also add a rule specifically telling the agent to always push after completing work. ---
**Author:** ![gillesheinesch](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gillesheinesch](https://forum.cursor.com/u/gillesheinesch)\ **Post date:** [March 10, 2026, 6:29am UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/15 "2026-03-10T06:29:50Z")
Hello, interesting to know. I didn’t know that the background agent takes the same rules. Thanks ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [April 1, 2026, 6:30am UTC](https://forum.cursor.com/t/background-agent-doesnt-push-new-commits/152158/16 "2026-04-01T06:30:17Z")
Closed on April 1, 2026, 6:30am UTC This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.