GPT-5.4 across Amplifier, zero user config
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.
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.
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.
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.
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.
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.
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?
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.
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):
gh search prs --owner microsoft "gpt-5.4" --merged --created 2026-03-06..2026-03-09 | grep amplifier — confirmed 6 repos, 9 PRsgh pr view 27 --repo microsoft/amplifier-module-provider-openai / gh pr view 28 … — ModelCapabilities (232 tests, 400K→272K) and reasoning-token regression fix (233 tests)gh pr view 1 --repo microsoft/amplifier-bundle-routing-matrix — all 5 OpenAI matrices (317 tests); gh pr view 14 …/provider-azure-openai (28 tests); gh pr view 23 …/provider-github-copilot (132 tests); gh pr view 230 …/amplifier (docs-only)cd amplifier-bundle-routing-matrix && git show 54a90ba (copilot.yaml TODOs → gpt-5.4); git show 6c631d1 (gpt-[0-9].[0-9] glob); git show 86f0608 (gpt-5.5 bump, 248 passed)cd amplifier-foundation && git show 4f6ef3d --stat; grep -n default_model providers/openai-gpt*.yaml; .venv/bin/pytest tests/test_gpt54_provider_updates.py -q (15 passed)hooks-routing pytest -q (270 passed); amplifier-foundation pytest -q (1057 passed, 1 skipped)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.