The Night Shift: Overnight Tech News with Jennifer Hudsen • 2:00 a.m. EDT edition • Cutoff 2:17 a.m. EDT August 29 / 06:17 UTC
OpenAI Proposes a November 12 Cutoff for Its Models in Cursor After the SpaceX Deal
Status at cutoff: OpenAI says it notified SpaceX that it intends to wind down the contract that supplies OpenAI models through Cursor, with a proposed shutoff date of November 12, 2026. [1] Cursor CEO Michael Truell says the companies are talking and that OpenAI models represent about 5% of Cursor user traffic. [3] The date is not yet final, current access has not ended, and Cursor may stop access sooner. [4]
What happened
OpenAI published a company statement Friday saying it had formally notified SpaceX of its intention to end the agreement under which OpenAI models are available inside Cursor. The company proposed November 12 as the cutoff and said that was the maximum notice its contract allows. OpenAI also said it would not provide future models to Cursor during the wind-down. [1]
The contractual trigger, according to OpenAI, was Cursor’s change of control after its acquisition by SpaceX. OpenAI says its agreement gives it a limited cancellation window after such a change. It framed the decision as a terms-of-service and safety-at-scale judgment, alleging prior contractual violations by Musk-controlled companies. Those allegations are OpenAI’s stated rationale; this article does not independently adjudicate the companies’ past disputes. [1]
Reuters independently reported the planned termination at 10:01 p.m. EDT and said SpaceX did not immediately respond to its request for comment outside regular business hours. Reuters also reported that Truell said Cursor and OpenAI were speaking to resolve the issue. [2]
Truell’s own response adds a useful scale marker: he says OpenAI models currently serve about 5% of Cursor user traffic. That is a company-provided traffic share, not an independently audited user count, revenue share or measure of business impact. It suggests the platform is not wholly dependent on OpenAI, but it does not tell an individual developer whether a critical team workflow is part of that 5%. [3]
Why it matters
The immediate issue is narrower than the Musk–Altman rivalry: a model provider has announced an exit from a widely used coding environment, and developers have a proposed transition date. Teams that explicitly select OpenAI models in Cursor should treat November 12 as a planning deadline, not as a guarantee that every feature, plan or account will behave unchanged until that day.
OpenAI’s support page says it would continue providing Cursor access to the OpenAI models used today during the transition period, while warning that Cursor may choose to end access sooner. It promises to publish the official termination date after the companies confirm it. The same page describes possible continuation paths, including bringing an organization’s own OpenAI API key, using the Codex IDE extension, or connecting through a compatible gateway. Availability, billing, feature coverage and enterprise policy can differ across those routes. [4]
Cursor’s current documentation shows that its model catalog is broader than one provider: it lists Cursor models alongside models from OpenAI, Anthropic and Google, with access depending on plan and other controls. [5] That gives many users an in-product fallback, but “another model is visible in the picker” is not the same as “the workflow is equivalent.” Models can differ in context handling, tool behavior, output quality, cost, data routing, retention terms and administrator approval.
Who is affected
- Individual Cursor users who select OpenAI models: current access remains available during the proposed transition, but users should identify which chats, agents and automations rely on those models. [4]
- Teams with pinned model names: scripts, onboarding guides, project rules and internal playbooks may fail or silently change behavior if a model disappears or a default shifts.
- Enterprise administrators: alternative providers, personal API keys and gateways may be restricted by organization policy. A technically possible fallback is not automatically an approved one.
- Developers using Cursor without OpenAI: there is no evidence in the cited announcements that the entire Cursor editor is shutting down. Truell’s 5% traffic figure also indicates most reported traffic uses something else, though the metric is company-reported. [3]
What readers should do
- Practical guidance—inventory real dependencies. Check Cursor’s model selector, team defaults, agent presets, project documentation and any automation that names an OpenAI model. Record what is business-critical without copying secrets or proprietary prompts into a new system.
- Practical guidance—run one representative fallback test now. Choose a normal task—such as a code review, test repair or small refactor—and run it with an approved alternative. Compare correctness, latency, tool use and cost. A tested fallback is more useful than a list of available models.
- Practical guidance—keep changes reversible. Put model names behind one configuration value where practical, use version control, and avoid rewriting every workflow around a replacement before the final date and product behavior are confirmed.
- Practical guidance—ask the policy questions before adding credentials. OpenAI lists bring-your-own-key and gateway options, but do not paste an API key into a tool until your organization approves the provider, billing account, retention terms and route through which code context will travel. [4]
- Practical guidance—watch the primary pages. OpenAI says the termination date is still being confirmed, while Cursor says discussions are ongoing. [4] [3] Recheck both companies before making an irreversible migration decision.
Upside, cautions and unknowns
Upside: The proposed date provides weeks rather than hours of notice, and OpenAI has documented possible continuation routes. [4] Cursor already supports multiple model families. [5] Practical analysis: that gives teams time to test alternatives rather than switch during an outage.
Caution: OpenAI’s allegations about previous contract violations are claims made by an interested party in a business dispute. Reuters reported no immediate SpaceX response, and Cursor says talks continue. The 5% figure comes from Cursor’s CEO and is not independently audited. [2] [3]
Unknown: the final cutoff date; whether an agreement changes the plan; which OpenAI models and Cursor features will remain available through the last day; whether Cursor ends access earlier; and how pricing, enterprise controls or support will work for every continuation path.
Evidence snapshot
| Claim surface | What is established | What remains unsettled |
|---|---|---|
| OpenAI contract | OpenAI says it gave notice and proposed November 12, while withholding future models. [1] | The official termination date and whether talks change the plan. |
| Cursor response | Truell says talks are ongoing and OpenAI models serve about 5% of user traffic. [3] | Independent audit of that metric and per-plan impact. |
| Developer options | OpenAI documents BYOK, Codex extension and compatible-gateway routes; Cursor lists multiple provider families. [4] [5] | Feature parity, price, approval and data-governance fit for each team. |
Frequently asked questions
Did OpenAI models stop working in Cursor tonight?
No. OpenAI describes a transition period with a proposed November 12 cutoff and says current models would remain available during that period; it also warns Cursor could end access sooner. [4]
Is November 12 final?
No. OpenAI repeatedly calls it proposed and says the official date will be shared once confirmed between the companies. [4]
Is Cursor losing every AI model?
No such claim appears in the cited sources. Cursor’s current documentation lists several provider families and its own model pool. The announced contract concerns OpenAI-provided models. [5]
Should I move everything immediately?
Practical guidance: not blindly. Inventory dependencies, test an approved fallback and keep configuration reversible while the companies continue talking. [3] Urgency should match the importance of the affected workflow, not the drama of the corporate dispute.
Can I just add my own OpenAI API key?
OpenAI lists that as one option for certain Cursor features, but billing, plan support, enterprise controls and data-routing requirements still apply. Follow your organization’s credential and vendor policy before enabling it. [4]
Sources
- OpenAI: “Our decision on Cursor following its acquisition by SpaceX,” August 28, 2026
- Reuters: “OpenAI to end agreement with SpaceX’s AI coding tool Cursor,” August 29, 2026, 2:01 a.m. UTC
- Michael Truell: Cursor response, August 29, 2026, 2:52 a.m. UTC
- OpenAI Help Center: “Using OpenAI models in Cursor,” checked August 29, 2026
- Cursor Docs: “Available models,” checked August 29, 2026
Reporting cutoff: 2:17 a.m. EDT on August 29, 2026 (06:17 UTC). This is a disclosed near-window fallback: the official OpenAI announcement entered the Google News technology feed at 9:46 p.m. EDT and Reuters published at 10:01 p.m. EDT—before the strict 11:30 p.m. desk boundary but within the permitted six-hour fallback. This is one subject checked against The IT Guys’ prior 36 hours and earlier Night Shift coverage. Featured image: original Jennifer Hudsen newsroom concept art, not an official product screenshot.