Slack and desktop Getting Started still show Connect/Link after Slack is already linked

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

After a successful Slack ↔ Cursor account link, the integration itself works, but two onboarding surfaces never update and still look disconnected.

What is actually linked:

  • The Cursor website shows “Account Linked — Your Slack account has been linked to your Cursor account”
  • Slack @Cursor settings returns model/repo/branch and shows an Unlink Slack Account button
  • Dashboard → Integrations shows Slack as Manage (same connected state as GitHub), with GitHub connected as jonmc12 / Epistemic-Me and default repo Epistemic-Me/Clarity-API

What still looks broken:

  1. Cursor desktop app sidebar Getting Started stays at 2/3 and still shows a Connect Slack button
  2. Slack Cursor app History welcome thread still says “To get started, sign in with Cursor” with a green Link Account button

This makes a completed link look like a failed one, so users keep re-running OAuth.

Steps to Reproduce

  1. Install/connect the Cursor Slack app and complete the Link Account OAuth flow (from Slack or from Cursor dashboard Integrations).
  2. Confirm the Cursor website shows the Account Linked success dialog.
  3. In Slack, send @Cursor settings. Confirm it returns settings and an Unlink Slack Account button.
  4. Open Dashboard → Integrations and confirm Slack is Manage (connected).
  5. Look at the Cursor desktop app Agents sidebar Getting Started card — it remains 2/3 with Connect Slack.
  6. Open the original Cursor Slack welcome/history thread — it still shows Link Account.
  7. Repeat Link Account several times. The stale onboarding UI does not catch up.

Expected Behavior

After a successful per-user Slack link:

  • Cursor desktop Getting Started should mark Slack as connected (complete the 2/3 step / dismiss Connect Slack).
  • The Slack welcome/history onboarding message should not keep presenting Link Account as if the user were unlinked.
  • Linked state should be consistent across dashboard, Slack bot, and the desktop onboarding checklist.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.15.19
VSCode Version: 1.128.0
Commit: de07bee81cefe43461ebf4f40c3d2d78d15052a0
Date: 2026-08-11T05:22:54.627Z
Build: stable

For AI issues: which model did you use?

N/A — this is an onboarding/UI state bug, not a model-output issue.

For AI issues: add Request ID with privacy disabled

N/A — no agent Request ID. This is stale Slack/desktop onboarding UI after a successful OAuth link.

Additional Information

Plan: Cursor Pro (team account, Jonathan McCoy).

Related reports (titles only):

  • Stuck on cloud environment setup (3/4) — Getting Started checklist won’t finish
  • Slack Integration Spamming intro message
  • Slack Bot linking issues

Screenshots (2 due to new-user media/link limits):

  1. Slack History welcome thread still showing Link Account
  2. Cursor desktop sidebar Getting Started 2/3 + Connect Slack

Also observed: website Account Linked success, dashboard Integrations with Slack as Manage, and Slack @Cursor settings showing Unlink Slack Account.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report and screenshots. I can see both the Slack History thread with the Link Account button and the desktop Getting Started card stuck at 2/3 on Connect Slack.

Good news, the link is active and working. The fact that the dashboard shows Slack as Manage, and that @Cursor settings in Slack returns your settings plus an Unlink button confirms the connection is successful. The two places that look not connected are just a stuck onboarding UI state, not the real link status.

What you can do right now:

  • Desktop Getting Started card: restart the Cursor app. After the restart, the card should refresh and Slack should show as connected. This is a known issue we’re tracking, the card doesn’t always refresh if the link is completed outside the app.
  • The old Slack welcome message with the Link Account button: you can safely ignore it. It’s posted once and doesn’t reflect the current status, so you don’t need to click OAuth again.

So no extra OAuth is needed, it’s already linked. Let me know if the desktop card is still stuck at 2/3 after restarting, and we’ll dig deeper.