Problem Statement
PR branch copilot/add-models-section-to-awf-config added a top-level models key to awf-config.json introducing 7 model aliases. The AWF firewall (v0.25.38) performs strict schema validation at agent startup and hard-fails with:
Error loading --config: Invalid AWF config at /home/runner/work/_temp/gh-aw/awf-config.json:
- config.models is not supported
This prevents the agent from starting entirely — 0 turns, 0 tokens, $0 cost per affected run. The failure cascades to every workflow triggered by the PR.
Affected Workflows and Run IDs
All 10 runs failed at the same startup validation step. Individual failure tracking: #30241, #30244, #30242, #30231, #30300, #30299, #30298, #30296, #30272.
Probable Root Cause
The AWF config schema (v0.25.38) does not include a models field. The PR added this field to support model aliasing, but the firewall schema validation rejects unknown top-level keys. The PR was likely created ahead of schema support being shipped.
Proposed Remediation
Option A (immediate): Revert or remove the models field from awf-config.json in the copilot/add-models-section-to-awf-config PR branch until schema support is added to AWF.
Option B (preferred long-term): Add config.models support to the AWF firewall schema validation before or alongside the PR merge. This should be the approach if the models aliasing feature is ready to ship.
Success Criteria
Parent report: see linked parent issue.
Generated by [aw] Failure Investigator (6h) · ● 950.6K · ◷
Closing as fixed (2026-05-09 failure investigation)
This issue is now fixed. The AWF schema has been updated so the models aliases are now correctly placed under apiProxy.models (no longer rejected as a top-level config.models).
Evidence: awf-config.json from a recent run on firewall v0.25.42 shows models correctly nested under apiProxy.models:
{
"apiProxy": {
"enabled": true,
"models": {
"auto": ["large"],
"sonnet": ["copilot/*sonnet*", "anthropic/*sonnet*"],
...
}
}
}No config.models is not supported error appears in any agent-stdio log from the past 6h window. Recent runs that consume the schema (e.g. §25605079586 Smoke Gemini on PR #31224) load awf-config.json cleanly — the agent starts and progresses past schema validation.
Reopen if any future run shows Error loading --config: ... config.models is not supported.
Generated by [aw] Failure Investigator (6h) · ● 24.7M · ◷
Problem Statement
PR branch
copilot/add-models-section-to-awf-configadded a top-levelmodelskey toawf-config.jsonintroducing 7 model aliases. The AWF firewall (v0.25.38) performs strict schema validation at agent startup and hard-fails with:This prevents the agent from starting entirely — 0 turns, 0 tokens, $0 cost per affected run. The failure cascades to every workflow triggered by the PR.
Affected Workflows and Run IDs
All 10 runs failed at the same startup validation step. Individual failure tracking: #30241, #30244, #30242, #30231, #30300, #30299, #30298, #30296, #30272.
Probable Root Cause
The AWF config schema (
v0.25.38) does not include amodelsfield. The PR added this field to support model aliasing, but the firewall schema validation rejects unknown top-level keys. The PR was likely created ahead of schema support being shipped.Proposed Remediation
Option A (immediate): Revert or remove the
modelsfield fromawf-config.jsonin thecopilot/add-models-section-to-awf-configPR branch until schema support is added to AWF.Option B (preferred long-term): Add
config.modelssupport to the AWF firewall schema validation before or alongside the PR merge. This should be the approach if themodelsaliasing feature is ready to ship.Success Criteria
copilot/add-models-section-to-awf-configPR passes withoutconfig.models is not supportederrorsParent report: see linked parent issue.
Closing as fixed (2026-05-09 failure investigation)
This issue is now fixed. The AWF schema has been updated so the
modelsaliases are now correctly placed underapiProxy.models(no longer rejected as a top-levelconfig.models).Evidence:
awf-config.jsonfrom a recent run on firewallv0.25.42showsmodelscorrectly nested underapiProxy.models:{ "apiProxy": { "enabled": true, "models": { "auto": ["large"], "sonnet": ["copilot/*sonnet*", "anthropic/*sonnet*"], ... } } }No
config.models is not supportederror appears in any agent-stdio log from the past 6h window. Recent runs that consume the schema (e.g. §25605079586 Smoke Gemini on PR #31224) loadawf-config.jsoncleanly — the agent starts and progresses past schema validation.Reopen if any future run shows
Error loading --config: ... config.models is not supported.