Agent Upstart

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

Playbooks · Teams tasks

Kilo's November 12 cutoff: what actually ends

Written November 9, 2026

OpenAI's proposed Nov 12 cutoff ends Cursor's model supply — future models withheld, personal API keys limited to local Chat/Agent. What ends, and what doesn't.

The date is a proposal, not a settled fact

Read this first, because most coverage gets it wrong: November 12, 2026 is a proposed date. OpenAI's own announcement, published August 28, says it notified SpaceX that it intends to wind down the contract providing OpenAI models to Cursor, "with a proposed shutoff date of November 12, 2026." OpenAI's help article says the same thing in plainer terms: "We have proposed a transition period of November 12, 2026. During that period, we would continue providing Cursor access to the OpenAI models it uses today. Cursor may choose to end access sooner. We will share the official termination date as soon as it is confirmed between both companies." As of November 9, neither OpenAI nor Cursor has confirmed November 12 as the final date. Kilo's own offer page phrases it the same way: access is "currently scheduled to end November 12, 2026, per public reporting; terms may change." This page is about the mechanics of what OpenAI proposed, not a prediction that the date holds.

What OpenAI proposed

The trigger was the acquisition: SpaceX bought Cursor's parent company, Anysphere, and the deal closed August 14, 2026. Two weeks later OpenAI invoked the change-of-control window in its custom agreement with Cursor, saying it cannot be confident SpaceX will use its technology within its terms of service, based on its experience with Elon Musk's companies violating contracts. The announcement says OpenAI held the cancellation to the latest date the contract allows, to maximize the time developers keep access — and that it will not provide future models to Cursor in the meantime. Its upcoming model Astra is named in the announcement as one that will not be supplied. Cursor CEO Michael Truell replied the same night that OpenAI models account for about 5% of Cursor's user traffic, and that the companies were talking to resolve it.

What ends, if the proposal goes through as written: Cursor's direct supply of OpenAI models through its own model picker, and any future OpenAI model reaching Cursor through that contract. What does not end: Cursor itself, which keeps its Anthropic, Google, and Grok models and its own Composer models, and the workarounds below.

What a personal API key still does after November 12

OpenAI's help article lays out three routes for continuing to use OpenAI models inside Cursor, and the first has a hard limit that matters more than the date. A personal OpenAI API key works only for local Chat and Agent features in the Cursor desktop app, billed through your own OpenAI API account. It does not apply to Cursor Tab and autocomplete, Auto model selection and routing, Cloud or Background Agents, Automations, the Cursor CLI, or Cursor's API and SDK. Those features use models supplied or routed by Cursor, and your key cannot reach them. A ChatGPT subscription does not include API usage, so the key route is billed separately from any subscription.

The other two routes: the Codex IDE extension, which runs the Codex agent directly inside Cursor as a separate extension, signed in with a ChatGPT subscription or an API key, and does not depend on OpenAI models being available through Cursor's own model picker; and an AI gateway provider, connecting Cursor to OpenAI models through an account with a compatible provider such as Amazon Bedrock or Azure, or another OpenAI-compatible gateway such as OpenRouter or Vercel AI Gateway. The help article warns that gateway compatibility varies and some model-specific controls may not be available through a custom base URL — and that the guidance is directional, because Cursor may change the functionality and availability of these features over time.

What to do before November 12

  1. Move shared work off OpenAI models in Cursor now. Switch the model selection to Claude, Gemini, or Grok for anything a team or a deadline depends on. The 5% figure is Cursor-wide; your team's share could be all of it.
  2. Test the bring-your-own-key path on local Chat and Agent only. Create an OpenAI API key with billing configured, add it in Cursor Settings under Models, and confirm it works in a local Chat or Agent session. Do not plan around it for Tab, Auto, cloud agents, automations, or the CLI — the help article excludes all of those.
  3. Test the Codex extension if you need Codex inside Cursor. It is a separate agent experience with its own panel, and it does not change the model used by Cursor Chat, Agent, Tab, Auto, or cloud agents. Know which surface you are actually using before you depend on it.
  4. Do not wait for the date to be confirmed. Cursor may end access sooner than November 12, and the official termination date does not exist yet. A migration done this week works under either outcome; a migration planned for November 11 does not.

The Kilo offer, kept separate

None of the above is the Kilo offer. Kilo, an independent coding platform, offers Kilo Enterprise free for the rest of a Cursor enterprise contract, up to one year, with one Kilo Enterprise seat for each Cursor seat. Applications close November 30, 2026, and the offer requires a signed attestation of an active paid Cursor enterprise contract plus a redacted proof document showing only customer name, tier, seat count, and contract end date. AI usage is separate, no credits are included, and the offer is discretionary — submission is a request, not automatic approval. The offer does not reimburse or cancel a Cursor contract.

Verdict

No verdict on the date itself — it is a proposal, and this page gives the mechanics to prepare for either way it lands. What is settled is the shape of the fallback: a personal API key covers local Chat and Agent only, the Codex extension is a separate surface, and anything routed by Cursor needs a different model. Prepare on that shape, not on the calendar.

What can go wrong

Limits

Related playbooks

Sources

Back to: Small-team playbooks hub · Also: Kilo Enterprise free for Cursor teams · Move Cursor work before the OpenAI shutoff · Agent change deadlines: retirements and shutdowns