GitHub Copilot: GPT-5.3-Codex becomes base model for Business and Enterprise with 12-month LTS guarantee

On May 17, 2026, GitHub announced a significant change to the Copilot model portfolio: GPT-5.3-Codex replaces GPT-4.1 as the base model for Copilot Business and Enterprise tiers. The announcement comes with two key novelties — an LTS (long-term support) guarantee and a precise deprecation schedule for GPT-4.1.

What does an LTS model actually mean?

LTS is a new concept GitHub is introducing for the first time with GPT-5.3-Codex. The long-term support guarantee covers:

• 12 months of guaranteed availability — from February 5, 2026 (launch date) to February 4, 2027
• No surprise deprecations during the LTS period
• Enterprise security & safety reviews can be planned knowing the model won’t disappear during an audit cycle

The approach is borrowed from Linux distributions (Ubuntu LTS, RHEL) and Java versioning — model as infrastructure, not as an experiment. This is a significant structural shift: GitHub acknowledges that enterprise volatility is unacceptable for AI models that have become integral to development workflows.

Which plans does the change affect?

GitHub explicitly specifies the scope:

• Affected: Copilot Business, Copilot Enterprise
• Not affected: Copilot Pro, Copilot Pro+, Copilot Free

The distinction is not accidental — Business and Enterprise plans are tiers in which organizations have strict model approval processes, security reviews, and compliance frameworks. The LTS guarantee precisely targets that more complex procurement cycle.

Individual Copilot Pro users can continue using the latest models as they release, without LTS stability — but also without waiting for enterprise rollout cycles.

What happens to GPT-4.1?

GPT-4.1 has received a precise deprecation timeline:

• During the transition period — force-enabled at 0× multiplier (free), so existing workflows don’t break
• Deprecation: June 1, 2026 — responsible admins have ~2 weeks for migration

The approach is similar to what GitHub applied during the Grok Code Fast 1 deprecation on May 15, 2026 — formal timeline, clear recommendation, short transition window. The trend indicates continuous model portfolio refresh as standard operating procedure.

What does GPT-5.3-Codex bring technically?

GitHub cites a concrete performance metric as justification: “significantly higher code survival rates among enterprise customers.” “Code survival rate” is a metric measuring the percentage of generated code that remains in the final commit (as opposed to code the developer discards or significantly modifies).

A higher code survival rate signals:

• Better first suggestion — the model better anticipates what the developer needs
• Less friction — fewer iteration cycles
• Greater trust — developers don’t need to deeply review every suggestion

In enterprise contexts where developer time is costly, code review processes are formal, and regulatory compliance is critical, these metrics translate directly into ROI improvement.

Pricing implications

GPT-5.3-Codex uses a 1× premium request unit multiplier — meaning each request consumes one premium request unit. GPT-4.1 remains at 0× multiplier until deprecation (free).

Practical implications:

• Enterprise admins must update budget planning — from a free base it becomes a premium tier baseline
• Premium request quota is consumed faster — if an organization has a quota cap, it needs to be reassessed
• Cost optimization — consider redirecting high-volume low-complexity tasks to other available models through policies

Strategic implication

GitHub is consolidating the Copilot model portfolio through spring 2026:

• May 15, 2026 — Grok Code Fast 1 deprecation (replacements: GPT-5 mini, Claude Haiku 4.5)
• May 17, 2026 — GPT-5.3-Codex becomes LTS base for enterprise (GPT-4.1 deprecates June 1)

Pattern: GitHub actively curates the portfolio, not a neutral marketplace. Models that don’t demonstrate strong enterprise adoption + technical quality are rapidly deprecated; models that perform well receive LTS status.

For organizations: AI model selection becomes a continuous operational concern, not a one-time integration decision. Vendor lock-in mitigation through a multi-model strategy is a mandatory element of enterprise AI architecture.