Skip to content

refactor(ai-providers)!: remove the Cursor provider and Grok sign-in - #3369

Merged
datlechin merged 1 commit into
fix/settings-decode-per-fieldfrom
refactor/remove-cursor-grok
Oct 12, 2026
Merged

datlechin merged 1 commit into
fix/settings-decode-per-fieldfrom
refactor/remove-cursor-grok

Conversation

@datlechin

@datlechin datlechin commented Oct 12, 2026 •

Copy link
Copy Markdown
Member

Stacked on #3361.

Why

The Cursor provider could not call TablePro's tools, ran the Cursor CLI with --trust, and Cursor already reaches TablePro with full tools through the MCP server. Sign in with xAI went through a Grok CLI proxy with a loopback OAuth listener, an unofficial path that duplicated the ChatGPT sign-in code. xAI keeps working with an API key.

Change

  • Removed the Cursor provider: API and CLI transports, sign-in service, settings UI, strings and tests.
  • Removed Sign in with xAI: OAuth and PKCE client, loopback callback server, token store, Grok proxy transport, settings UI, strings and tests.
  • xAI is an API key provider on the Responses transport it already used for keys.
  • No migration. A saved Cursor provider is dropped on load by fix(settings): decode settings per field so one bad value keeps the rest #3361's per-row decode; an xAI provider without a key shows Not configured.

Verified

A decode test drops a stored Cursor row and keeps the rest; XAIRegistrationTests pins xAI to the Responses transport.

Not in this PR

@datlechin
datlechin force-pushed the refactor/remove-cursor-grok branch from bd777a8 to d2cc4c3 Compare October 12, 2026 12:33
@datlechin
datlechin removed this pull request from stack #3385 October 12, 2026 12:34
@datlechin
datlechin merged commit edfd16e into fix/settings-decode-per-field Oct 12, 2026
10 checks passed
@datlechin
datlechin deleted the refactor/remove-cursor-grok branch October 12, 2026 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant