Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

OpenAI's Cursor cutoff day came and went

Written November 12, 2026

November 12 was the proposed shutoff for OpenAI models in Cursor. It is still only proposed — GPT-5.6 is still listed. What to do now.

Where things stand

As of the morning of November 12, nothing has been shut off. OpenAI's help page still uses the same wording it has carried since the announcement: OpenAI is planning to wind down its contract providing OpenAI models to Cursor, it has proposed a transition period of November 12, 2026, and during that period it would continue providing Cursor access to the OpenAI models it uses today. The page adds that Cursor may choose to end access sooner, and that OpenAI will share the official termination date as soon as it is confirmed between both companies. No confirmed date has been shared.

Cursor's side matches. Cursor's models documentation still lists GPT-5.6 Luna, GPT-5.6 Sol, and GPT-5.6 Terra, each at 272k default context and 1M maximum. No GPT-6 family model appears in the list, which fits the wind-down either way: the models Cursor has are the GPT-5.6 family, and newer OpenAI models are not arriving in Cursor under these terms.

The migration guide linked below was written for the proposed date. This page is the day-of update to it: the date arrived, the proposal is still a proposal, and the decision changes from “move before the deadline” to “keep the routes ready and keep working.”

The verdict

Do not emergency-migrate today. Nothing has been shut off, the models you use in Cursor are still listed, and a rushed move spends real work to escape a date that has not been confirmed. Keep the routes below ready, and move when a date is actually confirmed — or when Cursor ends access sooner, which OpenAI's page says it may.

The routes that stay ready

Where a key does not reach

Every route above covers local work in the Cursor desktop app. OpenAI's page is explicit that Cursor does not support bring-your-own-key in Tab, Auto, Cloud or Background Agents, Automations, the Cursor CLI, or Cursor's API and SDK. Those features use models supplied or routed by Cursor and cannot use your API key or gateway credentials. Work that lives on those surfaces needs a replacement model from Cursor's own supply, tested on your real tasks, not a key.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Move Cursor work before the OpenAI shutoff · Kilo's November 12 cutoff: what actually ends