Grokbot and GitHub

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Something else — Grok Bot / Grok iOS app GitHub connector

Describe the Bug

The GitHub connector in the Grok iOS app fails to load even though my GitHub account is shown as Connected.

The following error appears:

Error — Failed to load connector

“Couldn’t start sign-in: Streamable HTTP error: Error POSTing to endpoint: bad request: Authorization header is badly formatted”

The account section still shows my default GitHub account as Connected.

Pressing Retry does not resolve the problem.

Steps to Reproduce

  1. Open the Grok app on iPhone.
  2. Open the GitHub connector.
  3. Attempt to load/use the connected GitHub account.
  4. The connector fails to initialize.
  5. The error reports that the Authorization header is badly formatted.
  6. Press Retry.
  7. The same error persists.

Expected Behavior

The connected GitHub account should authenticate successfully and the GitHub connector should load normally, allowing Grok to access the GitHub functionality exposed through the connector.

Screenshots / Screen Recordings

Screenshot attached showing:

  • GitHub connector
  • GitHub account listed as Connected
  • Failed to load connector
  • “Authorization header is badly formatted” error
  • Retry button

Operating System

The issue occurs in the Grok iOS app, not Cursor IDE.

Device: iPhone 16 Pro Max

iOS Version: 26.6

Version Information

Grok iOS app version: **1.4.0 (6495)

Cursor IDE/CLI version: N/A

For AI issues: which model did you use?

N/A — this appears to be a Grok GitHub connector authentication issue, not a model-generation issue.

Request ID

N/A / not available

Additional Information

The GitHub account is displayed by Grok as Connected, but the connector cannot initialize.

The specific server-side/client authentication error is:

“Streamable HTTP error: Error POSTing to endpoint: bad request: Authorization header is badly formatted”

This suggests the connection exists but the authorization credentials/header being sent when the connector initializes may be malformed or incorrectly constructed.

Retrying does not resolve the issue.

Does this stop you from using Cursor?

No — Cursor itself works.

The problem is specifically with the GitHub connector inside the Grok iOS app.

IMG_5926
IMG_59261320×2868 258 KB

IMG_5918
IMG_59181320×2868 168 KB

2

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)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something 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!

  1. …
  2. …
  3. …

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!

10

Hi @cyclopsmustache Thanks for the post, and sorry for the hassle here. The GitHub connector showing Connected while returning this authorization error matches an issue we’re already tracking. Nothing here points to a configuration problem on your side.

As a workaround, please try resetting the saved GitHub account:

  1. Open the GitHub connector.
  2. Press and hold the default account row.
  3. Select Remove.
  4. Start the GitHub connection again and complete sign-in.

If Remove is unavailable or the same error returns afterward, let me know what you see. I’ll update this thread when there is more to share.

11

Heard.

I try to hit remove and get the first screenshot and then it reverts to the second.

Thank you!

IMG_5928
IMG_59281320×2868 215 KB

IMG_5929
IMG_59291320×2868 188 KB

12

Any luck resolving this? I’m having the same issue!

13

Thanks for trying that and for sharing the screenshots. They confirm that the saved default account cannot be removed from the app, so the reset steps I suggested will not work in this state.

We’re still tracking this issue. I don’t have another reliable workaround to suggest right now, and reinstalling or retrying is not expected to clear the saved connection.

@Johnny_Morris, if you’re seeing the same Authorization header is badly formatted message while the account shows Connected, this is the same issue. If your message differs, please share a screenshot along with your device and Grok Bot version.

I’ll update this thread when there is something actionable to share.

14

Thanks, yes, it is the same issue

15

The GitHub connector shows Connected in Grok, but it cannot access private repositories.

I installed the Grok by xAI GitHub App on my organization with read/write access to all repositories. I disconnected and reconnected the connector multiple times, including a full reinstall of the app. Private repos still return 404. The authenticated-user endpoint returns 401. Public repos are visible.

This looks like a stale or mis-scoped token that is not refreshed on reconnect. It matches the GitHub connector issue tracked in this thread around August 31.

Please investigate token refresh and repo-scope grant for the GitHub connector.

That’s the second place. Paste that into the thread.