Fix Grok iOS GitHub connector “Authorization header is badly formatted”

On the Grok iOS app, the GitHub connector can show your account as Connected and still fail to load with:

Failed to load connector — Couldn't start sign-in: Streamable HTTP error: Error POSTing to endpoint: bad request: Authorization header is badly formatted

Cursor staff (Kevin Neilson / kevinn) confirmed this matches a tracked product bug. Your GitHub OAuth settings are fine; Retry alone does not clear it.

This page is the iOS / Grok Bot phone connector failure. Connecting GitHub on grok.com/connectors for web chat is a different surface — see Connect GitHub so Grok can search repos, issues, and PRs.

What staff asked people to try

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

When Remove will not stick

Reporters who follow those steps see Remove flash and then the account return to Connected, still failing with the same Authorization header error. Staff reviewed screenshots and said:

1. The saved default account cannot be removed from the app in this state, so the reset steps do not work.
2. Reinstalling or retrying is not expected to clear the saved connection.
3. Anyone seeing the same Authorization header is badly formatted message while the account shows Connected is on the same issue.

There was no other reliable user workaround published as of the Sep 4, 2026 staff update. Staff said they will update the forum thread when something actionable lands.

Practical options while it is tracked

1. Use GitHub from grok.com connectors or desktop Grok Bot plugins if those still authenticate for your account.
2. Keep the forum thread bookmarked for the staff fix note.
3. When you report a duplicate, include device, iOS version, Grok / Grok Bot app version, and a screenshot of Connected + the Authorization header error.

Pitfalls

• Connected ≠ working. The broken state still paints the account as Connected.
• Rotating GitHub passwords or regenerating PATs will not clear this iOS header bug. Staff said configuration on your side is not the cause.
• Catalog GitHub on consumer Grok and GitHub login for Cursor IDE Cloud Agents are separate flows from this iOS connector init error.