News & Updates

OpenAI Cuts Cursor Loose After SpaceX Takeover. Anthropic Seizes the Moment With More Claude Capacity

OpenAI just told SpaceX it plans to stop supplying models to Cursor. The proposed cutoff lands on November 12, 2026. Developers who built workflows inside the AI-powered code editor now face a choice. Stick with what remains or shift heavily toward alternatives. Anthropic moved fast. Its co-founder promised extra compute for Claude inside Cursor and pointed to a long-standing partnership. The move turns a corporate breakup into an opening for one rival to capture more developer mindshare. The trigger was straightforward. SpaceX closed its $60 billion all-stock acquisition of Anysphere, Cursor's parent, earlier in August. OpenAI cited a change-of-control clause in its custom contract that gave it a narrow window to exit. Company executives said they could not trust that SpaceX would honor terms of service. Past dealings with Elon Musk's companies factored heavily into that judgment. "We are making this choice because we cannot be confident that SpaceX will use our technology within our terms of service, based on our experience with Elon Musk's companies violating contracts," OpenAI wrote. The post referenced Musk's acquisition of Twitter, which it said broke prior agreements, and Musk's testimony this year admitting xAI had violated similar rules. It also noted new accountability attached to its unreleased Astra model. Future versions would stay off limits for Cursor. Cursor's reaction stayed measured. Co-founder and CEO Michael Truell posted that OpenAI models represented only about 5% of user traffic. "We're sorry to see that OpenAI put out a note saying they plan to block Cursor users from accessing OpenAI models in three months. OpenAI models serve about 5% of Cursor user traffic, and we're speaking with the OpenAI team to resolve this," he wrote on X. The company has spent years positioning itself as model-agnostic. Users could tap GPT, Claude, Gemini or others depending on the task. But 5% still matters when that slice includes power users who rely on specific GPT behaviors for certain refactors or agent runs. And the timing stings. Cursor has grown into one of the most widely adopted AI coding tools among professional developers. Engineers at more than 60% of Fortune 500 companies reportedly use it. Many treat the editor like a daily driver. Losing direct baked-in access to one family of frontier models forces adjustments. Some will bring their own OpenAI API keys. Others will route through gateways. A few may simply migrate workloads to Claude. Anthropic's Swift Counter-Move Anthropic did not wait. Within hours Tom Brown, co-founder and chief compute officer, posted: "Cursor has been a trusted partner of Anthropic since Sonnet 3.5. We'll continue to increase compute to support Claude models in Cursor and are excited for what comes next with them at SpaceX." The statement landed like a direct response. It signaled not just continuity but expansion. Brown's team would add capacity to absorb any displaced traffic. That pledge carries weight. Digital Trends reported Anthropic is also raising weekly usage limits for Claude Code users. Standard limits for Pro, Max, Team and seat-based Enterprise plans get a permanent 25% bump starting September 14. Until then, the existing 50% temporary boost remains. The combination gives developers more room to run longer agent sessions or tackle bigger codebases without hitting caps as quickly. Claude models already dominate many Cursor workflows. Recent benchmarks show Sonnet and Opus variants excel at multi-file edits, repository-scale reasoning and clean code generation. Developers praise their ability to maintain context across large contexts. Now those strengths get amplified at the precise moment OpenAI steps back. The shift could accelerate. Cursor users who previously split time between providers may default to Claude for consistency and higher limits. Yet the episode reveals deeper tensions. AI labs increasingly treat their models as strategic assets rather than neutral commodities. Contracts come with strict usage rules. Competitive concerns surface when a customer gets acquired by a rival. Anthropic itself cut off access to other coding tools in the past when acquisition rumors swirled. The pattern repeats. Loyalty lasts only as long as business interests align. Musk dismissed the news. "I couldn't care less," he posted on X, adding pointed criticism of Sam Altman and OpenAI leadership. The remark fits a years-long public feud. Reuters detailed how the rivalry has played out in lawsuits, public accusations and now commercial retaliation. Reuters noted the $60 billion deal turned Cursor into part of a larger SpaceX AI organization. That integration apparently crossed a line for OpenAI. Developers watch these moves with a mix of frustration and pragmatism. Many already maintain multiple subscriptions. They bring their own keys where possible. They test models side by side. The Cursor situation forces a sharper evaluation. How much does direct integration matter versus raw capability and rate limits? For teams running heavy agentic workloads, capacity often decides. OpenAI's help center post outlines workarounds. Users can plug in personal API keys for supported chat and agent features, though some advanced Cursor capabilities like Tab, Cloud Agents or the CLI remain tied to provider-supplied models. The Codex IDE extension offers another path. Gateways provide a third. None fully replicate the pre-acquisition experience. And none guarantee access to future OpenAI releases inside Cursor. Anthropic's response looks calculated. It keeps a key customer. It gains potential volume. It burnishes its image as the more developer-friendly option in a moment of disruption. Whether the added compute scales without new bottlenecks remains to be seen. Demand for Claude in coding tasks has climbed steadily. Extra capacity helps, but frontier models still require massive resources. The next several weeks will test these promises. Cursor must guide users through the transition without losing momentum. Anthropic must deliver on higher limits and extra headroom. OpenAI must demonstrate that its workarounds satisfy the developer community it says it wants to support. And everyone watches to see whether this accelerates a broader fragmentation of the AI coding stack or simply pushes more traffic toward the current leader in that category. One thing looks clear already. In the contest for developer loyalty, raw model performance still matters. But so does reliability of access, predictable limits and willingness to scale alongside fast-growing tools. Anthropic just bet it can meet that test. The market will deliver the verdict.