Background Agents not working - github access required (but already has access)

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

GitHub access required
Connection failed. If the problem persists, please check your internet connection or VPN
Unauthorized request.

I click “set up” and click through to confirm that for my github account and the appropriate organization, all permits cursor access.

Request ID:
Unauthorized request.

Steps to Reproduce

attempt to launch a background agent

Expected Behavior

background agent runs

Screenshots / Screen Recordings


This part is weird - I obv have a git repo in this project, in the root of the project, so right there.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.27 (user setup)
VSCode Version: 1.99.3
Commit: d750e54bba5cffada6d7b3d18e5688ba5e944ad0
Date: 2025-09-17T20:21:17.042Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

gpt-5-high max

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey folks, can I get some eyes on this one? still cannot use background agents - what other info can I supply?

I’m having the same issue as well lately, but only in the last week or so… Eventually the background agent will start for me though.

I have this issue as well.

This has a significant negative impact, as I can’t have any background agents running now.

I don’t think I changed anything in my settings.

@deanrie any chance you could look at this please?

Hey, the team’s already on it.

1 Like

Hi @deanrie , any update on this please?

The team is working on a fix, and an update should be released soon.

1 Like

@deanrie can you please share any workarounds?

Or can you share what causes the issue, so I can figure out a workaround?

Obviously many users have this functionality working.

So there’s something about my setup that is causing the bug.

If I can figure out what it is then I can get this working until the Cursor team releases a fix.

Hi @deanrie , have you had a chance to look at this?

Hi @deanrie , have you had a chance to look at this?