Elon Musk’s SpaceX acquired AI code editor Cursor on August 24, 2026, instantly cutting developers off from OpenAI’s flagship models inside the platform they had built their workflows around.
Within hours of the deal closing, the integration layer that powered Cursor’s autocomplete, chat, and inline-refactor features reportedly flipped from OpenAI’s API to xAI’s Grok endpoints.
Code completion requests that previously routed to GPT-4o now reportedly flow exclusively to Grok-2 and Grok-3, according to industry reports.
Developers who relied on Cursor as their primary AI pair-programmer woke up to broken pipelines, dead API keys, and a model picker that no longer listed the vendor that built the category.

Spacex-cursor Openai: The Acquisition and Immediate Lockout
The SpaceX-Cursor OpenAI’s model access change landed without a grace period. Reports indicated that Cursor’s status page showed OpenAI endpoints returning errors from the morning of August 25.
Enterprise customers running on the $40-per-month Enterprise tier reportedly lost their third-party API key configurations on the spot, with the Bring-Your-Own-Key toggle reportedly disabled in the same release.
Michael Truell, Cursor’s co-founder and CEO, posted a short statement on X acknowledging the migration. He reportedly framed the Grok switch as a strategic alignment with SpaceX’s broader AI roadmap, and reportedly pointed to forthcoming pricing changes for the Enterprise tier.
Sam Altman and the Industry Reaction
OpenAI CEO Sam Altman responded publicly on X on August 25, reportedly calling the sudden API revocation a reminder that model access is a contract, not a guarantee.
He reportedly did not announce a workaround for displaced Cursor users, but reportedly indicated that OpenAI’s direct API keys remained accessible, meaning developers can reportedly still reach GPT-4o through the OpenAI dashboard, VS Code extensions, or competing tools like Windsurf and Zed.
The reaction across developer forums was reportedly sharp. Threads on r/MachineLearning and Hacker News reportedly logged hundreds of complaints within six hours, with several long-time Cursor users reportedly announcing switches to Claude Code and Aider.
Reports indicated that the migration forced some teams to rebuild CI scripts overnight, because their agentic test-runner relied on Cursor’s OpenAI-backed function-calling behavior.
What Enterprise Developers Are Losing
For the $40-a-month tier, the disruption goes deeper than a model swap. Cursor’s OpenAI integration reportedly supported structured outputs, JSON-mode completions, and a fine-tuned retrieval pipeline that enterprise teams had wired into production codebases.
Grok-2 and Grok-3 reportedly do not yet match GPT-4o’s reliability on these specific tasks, and early benchmarks reportedly circulating on X suggest a regression on structured-output accuracy.
Independent of whether those numbers hold up under scrutiny, the practical question for paying customers is whether SpaceX will refund the prorated remainder of their August subscriptions. As of press time, Cursor’s support team has not issued a public policy.
What Comes Next for Cursor Users
Developers who want GPT-4o back have three reportedly realistic paths. They can reportedly cancel Cursor and move to the OpenAI first-party Codex CLI, switch to Anthropic’s Claude Code for similar agentic workflows, or reportedly wait for SpaceX to restore OpenAI endpoints as a paid add-on.
Truell’s statement reportedly hinted at the third option, but gave no timeline. The SpaceX-Cursor OpenAI’s lockout is the first large-scale test of how much leverage an acquirer has over a developer’s model stack, and the answer so far is: nearly total. More on SpaceX-Cursor OpenAI’s as the story develops.
FAQ
Why did Cursor stop supporting OpenAI models? SpaceX acquired Cursor on August 24, 2026, and reportedly redirected all default completions to xAI’s Grok models within hours of closing the deal.
Did Sam Altman respond to the lockout? Yes. He posted on X on August 25, 2026, reportedly calling the move a reminder that model access is a contract rather than a guarantee.
Can enterprise users still bring their own OpenAI key? Reportedly not. The Bring-Your-Own-Key toggle was reportedly disabled in the same release that flipped defaults to Grok.
What are the best alternatives to Cursor for OpenAI users? OpenAI’s Codex CLI, Anthropic’s Claude Code, and the open-source Aider project all reportedly retain direct GPT-4o access.
Will Cursor refund affected Enterprise tier subscribers? Cursor’s support team has not published a refund policy as of August 29, 2026.
Originally reported by The Indian Express.
Related Articles
Was this article helpful?
Your feedback directly improves future articles on this site.





