AI 開發工具
OpenAI Plans to Stop Supplying Models to Cursor on November 12, Requiring Existing Agent Routing to Be Revalidated
OpenAI has initiated contract termination procedures following SpaceX’s acquisition of Cursor and says it will not provide Cursor with future models. Cursor’s current documentation on routing, enterprise allowlists, and bring-your-own API keys does not yet explain exactly how these features will behave after termination, so engineering teams should not treat model replacement as a seamless switch.
OpenAI announced on August 28 that it had notified SpaceX of its intention to terminate its contract to provide models to Cursor, with a proposed end date of November 12, 2026. Future OpenAI models will also not be made available through Cursor. OpenAI linked the decision to the change in control of Cursor and risks related to its terms of service. For users, however, the immediate consequence is that the model supply chain integrated into the editor, cloud agents, and automatic routing will change.
Cursor’s current documentation shows that, in addition to its own Grok 4.5 and Composer, the platform offers models from OpenAI, Anthropic, Google, and others. Its smart routing system currently includes GPT-5.5 in the candidate pool and warns that routing quality may decline or features may stop working if administrators block some recommended models. GPT-5.6 Sol is recommended for complex, multi-step tasks. The impact therefore extends beyond the removal of a single option from the model menu: workflows that depend on fixed model IDs, reasoning effort, context length, tool-calling formats, or routing quality may all experience behavioral drift.
Enterprise teams should first inventory rules pinned to OpenAI models, evaluation baselines, agent prompts, and cost budgets, then compare alternative models using real codebase tasks rather than relying solely on general-purpose benchmarks. Cursor’s documentation still lists bring-your-own API key support, but neither OpenAI nor Cursor has confirmed whether BYOK will fully preserve capabilities such as agents, subagents, caching, and zero data retention after November 12. They have also not explained how existing conversations will be migrated. The end date remains a “proposed” arrangement; the next key signals will be Cursor’s formal migration announcement and any updates to its model catalog or Router composition.