Skip to content

[awf] Copilot engine: intermittent 400 'model not supported' for claude-opus-4.6 due to catalog inconsistency #4020

Description

@lpcox

Problem

~20-25% of runs targeting claude-opus-4.6 fail within ~4 seconds with 400 The requested model is not supported. The same workflow succeeds minutes later, indicating an upstream Copilot model-catalogue inconsistency rather than a configuration bug.

Context

Upstream report: github/gh-aw#35075

The model catalogue varies between runs (30 vs 39 models observed). The Copilot harness logs attempt 1: model not supported — not retrying.

Root Cause

The Copilot CLI's model-validation step checks the catalogue fetched at startup. When the upstream entitlement service returns a reduced catalogue (transient inconsistency), valid models like claude-opus-4.6 appear unsupported. The harness currently does not retry on 400 model not supported.

Proposed Solution

  1. In the Copilot harness retry logic, treat 400 model not supported as a transient error and retry up to 3 times with exponential backoff before reporting failure.
  2. Alternatively, add a --skip-model-validation flag to bypass pre-flight catalogue checks and let the API respond directly.
  3. Log the full model list at debug level when this error occurs to aid diagnosis.

Generated by Firewall Issue Dispatcher · sonnet46 1.2M ·

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions