A connector reports as already connected and still refuses to work

SymptomGitHub shows as connected via Cursor, yet the Grok Bot connector demands a separate personal access token before it will do anything.

CauseGrok Bot's connector is distinct from the Cursor integration and does not inherit its authorisation.

DetectionThe task simply does not proceed. Reported independently by two hands-on testers eleven days apart.

FixComplete each Grok Bot connector's own auth explicitly rather than assuming an existing Cursor connection carries over. Related setup trap: a Slack trigger receives nothing until the connected app has been invited into the target channel.