Error_github_no_user_credentials

I am on the Ultra plan. Account email: [email protected].

Important clarification: the local agent in Cursor works fine. Only the cloud / background agent fails. When I start Background Composer from a snapshot, the flow errors out immediately.

Request ID: 56f06251-cebd-4514-b2dc-f621a5a5895f

Full error payload:

{“error”:“ERROR_GITHUB_NO_USER_CREDENTIALS”,“details”:{“title”:“Failed to get service account access token”,“detail”:“Failed to get service account access token for any user.”,“additionalInfo”:{},“buttons”:[],“planChoices”:[],“analyticsMetadata”:{“actionRequired”:“login”}},“isExpected”:true}

Additional message: Failed to get service account access token for any user.

ConnectError: [unauthenticated]

The stack trace in the app points to:

  • startBackgroundComposerFromSnapshot
  • _createAgentReal

Environment:

  • OS: Windows

Integrations (Settings):

  • GitLab: connected (e.g. as Baburin_Dmitriy)
  • GitHub: not connected (shows “Connect”)

I use GitLab for my repositories. The error code mentions GITHUB.

I have tried signing out and back into Cursor. Local agent behavior is unchanged (still OK); cloud agent still fails with the same error.

Please investigate using the Request ID above and advise what I should configure, or fix on your side if this is unintended.

Thank you,
Dmitriy

Text Error:

Request ID: 56f06251-cebd-4514-b2dc-f621a5a5895f

{“error”:“ERROR_GITHUB_NO_USER_CREDENTIALS”,“details”:{“title”:“Failed to get service account access token”,“detail”:“Failed to get service account access token for any user.”,“additionalInfo”:{},“buttons”:[],“planChoices”:[],“analyticsMetadata”:{“actionRequired”:“login”}},“isExpected”:true}

Failed to get service account access token for any user.

Error

ConnectError: [unauthenticated] Error

at t (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%B8%D0%B9%20%D0%91%D0%B0%D0%B1%D1%83%D1%80%D0%B8%D0%BD/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:66454)

at async Object.startBackgroundComposerFromSnapshot (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%B8%D0%B9%20%D0%91%D0%B0%D0%B1%D1%83%D1%80%D0%B8%D0%BD/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29268:4386)

at async bEm._createAgentReal (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%B8%D0%B9%20%D0%91%D0%B0%D0%B1%D1%83%D1%80%D0%B8%D0%BD/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45404:48209)

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!