OpenAI said on August 28, 2026 that it intends to stop providing OpenAI models through Cursor on November 12, 2026. The proposed cutoff follows Cursor’s August 14 announcement that its acquisition by SpaceX had closed.
This is a planned provider change, not a current outage. OpenAI says developers can retain access during the notice period, but it does not plan to provide future models to Cursor. Cursor has not published a product migration notice on its blog as of August 29, so teams should avoid guessing which models, compatibility layers or account options will replace affected workflows.
What OpenAI announced
- Proposed end date: November 12, 2026 for OpenAI models supplied under the Cursor contract.
- Reason given: OpenAI linked its decision to Cursor’s change of control and concerns about enforcing its terms at scale.
- Transition window: OpenAI says it selected the latest cancellation date allowed by the contract to preserve access for developers as long as possible.
- Future models: OpenAI explicitly said it would not provide future models to Cursor under this arrangement.
Cursor’s acquisition post says the company expects to use SpaceX compute to build stronger, lower-cost models and points to Grok 4.6 as an early example. That provides direction, but it is not yet a detailed migration contract for existing OpenAI-backed Cursor workflows.
Why this matters for QA engineers
The OpenAI Cursor model exit could change generated code, tool selection, latency, context handling and test recommendations even when prompts and repositories stay the same. A replacement model passing a few happy-path tasks is not enough evidence of equivalent behavior.
- Inventory dependencies: record which Cursor modes, automations, rules and team workflows explicitly or implicitly select an OpenAI model.
- Freeze a baseline: save representative prompts, repository commits, model identifiers, settings, outputs, tool traces, latency and token or cost data.
- Build a migration matrix: compare candidate models on compile success, deterministic tests, seeded defects, security checks, diff size and unsupported-tool behavior.
- Test the boundaries: repeat approval, secret-access, network, file-scope and destructive-action tests; provider changes can alter when an agent asks, blocks or proceeds.
- Separate editor from API risk: OpenAI’s notice concerns models provided through Cursor. Do not assume it changes a team’s separate OpenAI API or Codex contracts.
A practical migration test
Select 10 to 20 real but sanitized QA tasks: generate a boundary test, diagnose a flaky failure, repair a seeded defect, explain a risky diff and refuse an out-of-scope action. Run each task on the current model and every approved alternative against the same commit and configuration.
Require deterministic CI to judge correctness. Track not only pass rate but also false fixes, unnecessary edits, skipped tests, approval behavior and reproducibility. Keep the existing route available until the replacement meets explicit acceptance thresholds, and schedule a final comparison close enough to the cutoff to catch product changes.
Bottom line
OpenAI’s announcement gives Cursor users a dated migration risk rather than an immediate service failure. QA teams can use the notice period well: identify model-coupled workflows now, preserve evidence, validate alternatives with real defects and wait for concrete Cursor guidance before making assumptions about the final replacement path.
Sources
- OpenAI: Our decision on Cursor following its acquisition by SpaceX — August 28, 2026
- Cursor: Cursor is now a part of SpaceX — August 14, 2026