Skip to content
DriftCaught
OpenAITool change

gpt-5.4

Tool change, announced 13 March 2026. Rerun the suite: If a feature sends images to gpt-5.4, run your image cases again after this date and keep both sets of outputs, because the id you call did not change.

What OpenAI says changed

OpenAI wrote that it updated its image encoder to fix a small bug with input_image inputs in gpt-5.4. OpenAI describes it as a bug fix and publishes no new model id alongside it.

OpenAI: API changelog

announced 2026-03-13 . verified 2026-09-22

This section restates the provider. It adds no judgement the provider did not make, and it contains no measurement of ours.

Entry

Provider
OpenAI
Models
gpt-5.4
Change type
Tool change
Announced
2026-03-13
Verified
2026-09-22

What this kind of change typically touches

No impact note on this entry. A note is published only where a cited practitioner source supports it, and for this change we have none. The entry stands on the provider's announcement alone.

What to do this week

Rerun the suite

If a feature sends images to gpt-5.4, run your image cases again after this date and keep both sets of outputs, because the id you call did not change.

If you are on a plan

A tracked provider update triggers a rerun of your suite within 2 business days of the announcement, and you get a written verdict. That is one of the six guarantees on every plan.

See plansRead EV-RERUN

Other OpenAI changes

OpenAINew version

gpt-6-astra

OpenAI released GPT-6 Astra, which it describes as its most capable model for end to end work, covering reasoning, coding, computer use and tools. It is available in the Responses API and the Chat Completions API.

Rerun the suiteAdd gpt-6-astra as a second model in your next scheduled suite run alongside the one you serve today, and read the differences before changing any default.

Source: OpenAI, OpenAI API changelog . verified 2026-09-22

OpenAITool change

slow_down, server_is_overloaded

OpenAI wrote that a rapid increase in traffic can now return a 429 error with the slow_down code, and that temporary overload can return a 503 error with the server_is_overloaded code.

Rerun the suiteCheck that your client and your eval harness treat these two codes as a signal to back off rather than as failures, then run a batch large enough to exercise that path.

Source: OpenAI, API changelog . verified 2026-09-22

OpenAIDeprecation

whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe, gpt-4o-transcribe-diarize

OpenAI announced on August 26, 2026 that whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe and gpt-4o-transcribe-diarize are scheduled to shut down on February 26, 2027. The recommended replacements are gpt-live-transcribe and gpt-transcribe.

Plan a migrationFind every call to one of the four ids, run a held out set of recordings through gpt-transcribe or gpt-live-transcribe, and keep both transcripts so the step after them can be compared before February 26, 2027.

Source: OpenAI, Deprecations . verified 2026-09-22

Questions

How do I know this is accurate?
The entry links to OpenAI's own page, and the date we read it is on this page. If the provider's page and this page disagree, the provider's page is right and we want to hear about it.
Does this mean my feature broke?
No. It means a thing your feature depends on changed. Whether anything about your output changed is a question only a rerun against your own dataset can answer, and that is what the recommended action is for.
Why is there no score or benchmark here?
Because we publish none. This site restates provider announcements and cites published practitioner guides. Any measurement we make belongs to the customer whose dataset produced it.

Sources

Change-log entries restate provider announcements with sources and dates. Impact notes cite public practitioner reports. The site publishes no measurements of its own on any model.

Related