Grok Bot GitHub plugin Authenticate: Github didn't provide a sign-in link

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else: Grok Bot (also reproduces in Cursor IDE — see Additional Information)

Describe the Bug

Official GitHub marketplace plugin (id 48677658) stays Needs auth. Clicking Authenticate shows toast: “Github didn’t provide a sign-in link”. No browser/OAuth window. MCP user-Github: needsAuth / authentication_required, tools listed as 47 but unusable until auth.

Steps to Reproduce

  1. Grok Bot desktop → Plugins → GitHub (installed).
  2. Account default shows Needs auth.
  3. Click Authenticate.
  4. Toast: Github didn’t provide a sign-in link. Still Needs auth.

Expected Behavior

Authenticate opens GitHub OAuth / provides a sign-in link and completes connection.

Screenshots / Screen Recordings

Operating System

darwin (macOS) arm64

Version Information

Grok Bot 0.44.0 stable (desktop)

Additional Information

  • Bot name: Bug/Feature Logger
  • Conversation ID: unknown — filing from this agent chat; desktop surface
  • Surface: Grok Bot desktop (primary). Also fails similarly in Cursor IDE 3.19.13 arm64 (dd066f332fcea7382764400fde902f61920648d0).
  • Plugin: GitHub marketplace 48677658
  • Related: Plugin MCP OAuth never reaches needsAuth — Authenticate button missing, browser never opens (different symptom — missing Authenticate / never needsAuth — opposite of this case where Needs auth shows and Authenticate is clicked)
  • Worked-around locally via custom github-local PAT MCP; marketplace plugin still broken
  • In-app SendFeedback also submitted for this report.

Does this stop you from using Grok Bot?

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

Hey @jsolly - this is a labeling issue, not a sign-in that’s actually failing. The GitHub plugin authenticates with the personal access token you enter under Setup Values (Edit Values), not a browser sign-in, so the badge shows Needs auth and the Authenticate button has no link to open (hence the toast). Your connector is already working — the 47 tools are loading with your token, so you can ignore that label (the custom PAT MCP you set up isn’t needed).

Quick confirm: in any bot, ask “Using the GitHub connector, which GitHub user am I signed in as?” - if it returns your username, you’re good.

This is an issue we’re tracking and I’ve added your report to it; I’ll follow up here when there’s an update. For the Cursor IDE, could you share the exact screen and status text you see there? That’s a different path, so I’d like to look at it separately.

Update (2026-09-08): After uninstall → retry Authenticate on the GitHub marketplace plugin, the toast changed.

  • Still Needs auth on account default
  • New toast: Couldn’t start sign-in for GitHub. Details: fetch failed
  • Prior toast on this thread was Github didn’t provide a sign-in link

Environment (confirmed):

Screenshot (Plugins → GitHub → Needs auth + fetch failed toast):

In-app SendFeedback also submitted for this update (cross-link).

@jsolly your GitHub connection is actually working, the screenshot shows all 47 tools loaded. The Authenticate button and “Needs auth” label don’t apply to this plugin, it signs in with the token under Setup Values, not a browser flow, so that button will always error (it just changed from “no sign-in link” to “fetch failed” after the reinstall). Uninstalling and retrying won’t change it.

To confirm, ask any bot: “Using the GitHub connector, which GitHub user am I signed in as?” If it returns your username, you’re good, ignore the label. This is a known labeling issue we’re tracking. If the Cursor IDE case behaves differently, share the exact status text there and I’ll look at it separately.