Git parts of Cursor background/cloud agent is not working reliable

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Hello, most of the times when I run a Cursor cloud/background agent it does not create and push the branch to Github. And I have a very hard time debugging it as it seems like the git parts of the cloud agent workflow is not visible for us. So the only reliable thing I can do is to prompt and force the LLM to push the branch to origin through prompting in the chat (even if it is not suppose to do that according to your system prompt). Sometimes, very randomly it works, but most time it doesn’t. This is currently a huge blocker for me at the moment.

Here are a couple of request ID’s for debugging:

  • bc-630886b1-92d7-4a04-90b0-5dacb7e8170e
  • bc-4e3effb8-2b93-48c2-bedd-ce463ef2c979
  • bc-4b013904-0436-4dd0-ace6-121e55bbc55f

Br Alex

Steps to Reproduce

Not sure how to reproduce it for others. I have a 80% chance to reproduce it by creating a new agent background task.

Expected Behavior

The background agent should use git to push the branch to origin successfully.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 23.3.0

For AI issues: which model did you use?

GPT 5.2 / Opus 4.5

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, thanks for the report. This is a known issue with Cloud Agent, and the team is already aware and working on a fix.

A few quick questions for the engineers:

  1. Is the repo public or private?
  2. Can you check your GitHub integration status at https://cursor.com/dashboard? Is everything connected correctly?
  3. Do you have permission to push directly to this repo (without PR review)?

For now, the workaround is what you mentioned: explicitly ask the agent to push the changes in the prompt. Not ideal, but it works.

I’ll pass your request IDs to the team so they can investigate further.

4

I understand, please keep me posted.

  1. Private
  2. Status looks good.
  3. Yes, as long as it is not to the master branch which is protected.

Br Alex

1 Like