The Model Drop That Landed

GPT-5.4 across Amplifier, zero user config

The usual scramble

A major model drop normally means an emergency scramble — in Amplifier, GPT-5.4 already landed

A new model like GPT-5.4 normally forces a rush to update every provider, routing matrix, and doc by hand. In Amplifier that work is already merged and shipped as the default.

Not a plan — a rollout that shipped. Here's the evidence.

On 2026-03-06 a coordinated wave shipped — 725 verified tests passing, zero failures

A single rollout day landed GPT-5.4 across the ecosystem in 9 merged PRs spanning 6 repos, backed by test counts that sum to 725 with no reported failures.

So where did all that change actually go? Six repos.

6
Amplifier repos touched
9
Merged PRs in the rollout
725
Per-PR verified tests passing
0
Failures reported

Provider code, routing, defaults, and docs — all moved at once

The rollout spanned six named repos, so a single model change touched every layer that has to agree on which model to run.

First, provider-openai had to get the model's behavior right.

A new ModelCapabilities architecture fixed the context window and added reasoning levels

provider-openai's PR #27 corrected the context window from a hardcoded 400K to GPT-5.4's real 272K and added xhigh and none reasoning-effort levels — not just the name, the behavior.

But getting a model right this way is fragile.

400K→272K
Context window corrected
xhigh / none
New reasoning-effort levels
233
Tests passing (provider-openai)

A reasoning-capable model with default effort None can silently lose reasoning tokens

When default_reasoning_effort is None, the include=[reasoning.encrypted_content] param is still required — miss it and reasoning tokens vanish silently. A regression fix (#28) caught it the next day.

Discipline like this is why the next drop can be made easy.

# PR #28 — merged 2026-03-07 fix: prevent silent reasoning token loss for GPT-5.4 # +1 regression test 233 tests passing (was 232)

A version-aware glob makes the resolver auto-pick the highest model — no matrix edit needed

The OpenAI matrices switched to a gpt-[0-9].[0-9] glob whose version-aware sort picks the highest available version automatically, so the next model drop needs no routing-matrix edit.

Then GPT-5.5 landed and put the design to the test.

# routing/openai.yaml model: "gpt-[0-9].[0-9]" # resolver's version-aware sort # picks the highest version # automatically

When GPT-5.5 landed it was a near-mechanical swap — 248 routing-hook tests passed, no changes needed

The glob proved itself on the very next bump: commit #17 lifted the mid- and heavy-tier OpenAI models to gpt-5.5 with 248 routing-hook tests passing and no changes needed.

So what does this mean for you as a user?

248
Routing-hook tests passing on the gpt-5.5 bump
0
Test changes needed

Pull latest and get the right model at the right reasoning level — no config, and each drop gets easier

GPT-5.4 is the default across the ecosystem — foundation's provider bundles all set default_model: gpt-5.4 and the matrices resolve OpenAI roles automatically. Copilot stays pinned by design, since its provider has no list_models fallback.

SHIPPED / DEFAULT · zero user config
1057
foundation tests passing today (1 skipped)
270
hooks-routing tests passing today
0
User config changes required
Sources

Sources & Research Methodology

Data as of: Rollout PRs merged 2026-03-06 through 2026-03-08; follow-on bumps 2026-04-24 and 2026-05-13.

Feature status: SHIPPED / DEFAULT — GPT-5.4 is the default OpenAI model across the Amplifier ecosystem; no user config change required.

Research performed (against microsoft/* repos under /home/ramparte/dev/ANext, independently re-verified in a fresh session):

Gaps / corrections: 725 is the sum of per-PR verified test counts (233 + 317 + 132 + 28 + 15); a prior "775" figure did not reconstruct and is not used. Repo count is 6 distinct repos (a prior "7" could not be verified). PR #230 is docs-only with no test count.

Primary contributors: Brian Krabach (foundation #118, routing-matrix #1, gpt-5.5 bump #17); Mowri Mohan (routing-matrix #4, copilot.yaml); Salil Das (routing-matrix #23, version-aware glob); Amplifier agent co-author on generated rollout commits.

More Amplifier Stories