[christso]

Summary

Copilot custom provider config now reuses AgentV's existing api_format public field instead of introducing a Copilot-specific wire_api YAML key. The resolver still maps api_format to Copilot's internal wireApi field and COPILOT_PROVIDER_WIRE_API env var at the provider boundary, so the user-facing config stays aligned with existing OpenAI-style target naming.

Config Example

targets:
  - name: copilot-openai
    provider: copilot-cli
    subprovider: openai
    base_url: ${{ OPENAI_ENDPOINT }}
    api_key: ${{ OPENAI_API_KEY }}
    api_format: responses

Tests

• bun run typecheck
• bun --filter @agentv/core test test/evaluation/providers/targets.test.ts test/evaluation/validation/targets-validator.test.ts — 70 pass, 0 fail
• bun run verify

Post-Deploy Monitoring & Validation

No additional production monitoring required; this is local eval target configuration parsing. Validate by running a Copilot target with flat api_format: responses and confirming the resolved Copilot provider still receives wireApi: responses / COPILOT_PROVIDER_WIRE_API=responses.

[cloudflare-workers-and-pages]

Deploying agentv with    Cloudflare Pages

Latest commit:	bdbf49e
Status:	✅  Deploy successful!
Preview URL:	https://2e4e3a29.agentv.pages.dev
Branch Preview URL:	https://fix-copilot-api-format-field.agentv.pages.dev

View logs