Loading page…
Cursor’s appeal is a single coding interface for several model providers. OpenAI’s proposal would remove one of those direct connections, with the migration path still undefined.
Listen to this story
OpenAI is seeking to terminate Cursor’s direct model connection on November 12, though the year, covered models, and any replacement account or API route remain unspecified. The proposal follows SpaceX’s completed acquisition of Cursor, which adds access to SpaceX’s GPU fleet and strengthens Cursor’s ability to develop first-party models.
The cutoff is proposed, not final; its practical impact depends on negotiated commercial terms and any alternative access path.
Cursor’s developers may retain the editor and other providers but could lose an established route to OpenAI models.
SpaceX’s GPU access could lower Cursor’s model-training costs and support expansion of its first-party model lineup.
OpenAI has proposed ending Cursor’s direct access to its models on November 12. If finalized, the change would remove a supplier connection from an AI coding editor that lets developers use models from multiple providers in one interface, following SpaceX’s August acquisition of Cursor.
Cursor’s design puts several model suppliers behind one coding workspace. That setup lets a developer retain the same editor, repository context and configured workflows while selecting a model. OpenAI’s proposal concerns Cursor’s direct connection to OpenAI models, not the editor’s general ability to carry models from other providers.
The operational consequence is clear even as the terms are not: developers could lose an established route to OpenAI models without leaving Cursor. OpenAI has not identified the models covered or said whether customers could continue through another connection, such as an account or API-key route.
Cursor said SpaceX would provide access to its GPU fleet, allowing the company to train stronger models at lower operating costs. Cursor has added first-party models alongside third-party options, while SpaceX has a financial interest in models developed with SpaceXAI. The deal therefore gives Cursor more resources for its own model work as OpenAI proposes withdrawing a direct supplier relationship.
OpenAI has not attributed the proposal to competition with Codex. But Codex is already generally available across cloud, terminal, IDE and Slack workflows, and its SDK lets organizations embed the coding agent in internal tools. Those are separate OpenAI routes for developers and engineering teams that use its coding products.
Cursor entered the sale with sizable company-reported operating figures. In November 2025, it said it had passed $1 billion in annualized revenue, served millions of developers and employed more than 300 people. Cursor also reported a $2.3 billion Series D at a $29.3 billion post-money valuation; Axios later reported that the all-stock SpaceX transaction valued Cursor at $60 billion.
November 12 remains a proposed cutoff, rather than a completed disconnection. Its practical effect will depend on the final commercial terms and the access path, if any, offered to Cursor users.
Editorial analysis
The immediate issue is not whether Cursor can continue offering AI coding help. It is whether an editor built around provider choice can preserve that choice after its owner commits compute to Cursor’s own model work. OpenAI has not tied the proposal to Codex competition, so that motive should not be assumed. The next concrete signal is whether the companies set out an access route for existing users before November 12, or let direct OpenAI access disappear from Cursor’s menu.
Loading discussion...
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.