Pi: "Error: Unknown provider \"azure-openai-responses\""
Error: Unknown provider "azure-openai-responses". Use --list-models to see available providers/models.Tool: Pi coding agent (pi). Versions: Affected: 1.0.3 and later; last version without this error: 1.0.2; we reproduced it on 1.0.2, 1.0.3, 1.1.0. Exit code 1.
Cause: Pi 1.0.3 (released 2026-10-05T08:38:23Z) renamed the provider azure-openai-responses to azure, so passing the legacy provider name fails validation.
Fix: Replace azure-openai-responses with azure in CLI commands and configuration files.
# CLI invocation: pass --provider azure instead of --provider azure-openai-responses
pi --provider azure --model gpt-4o -p "test"
# In auth.json: rename the "azure-openai-responses" provider key to "azure"
# In models.json: rename "azure-openai-responses" under "providers" to "azure"
# In .pi/settings.json: update defaultProvider and model patterns to use "azure"Pi 1.0.3 renamed the provider to support Azure Foundry Chat Completions deployments alongside the Responses API under a single provider ID. Existing AZURE_OPENAI_* environment variables (AZURE_OPENAI_API_KEY, AZURE_OPENAI_BASE_URL, AZURE_OPENAI_RESOURCE_NAME) remain unchanged.
How did we reproduce the Pi coding agent error?
A fresh Debian 13 VM from bin/sandbox-run on pc (x86_64, Node.js 24, root, online, no credentials for any service), destroyed after the run. Run on . Failing command: pi --provider azure-openai-responses --model gpt-4o -p "test".
Before: provider accepted, proceeds past resolution to credential check (Pi coding agent 1.0.2):
$ pi --provider azure-openai-responses --model gpt-4o -p "test"
No API key found for azure-openai-responses.
Use /login to log into a provider via OAuth or API key. See:
/opt/pi-1.0.2/lib/node_modules/@earendil-works/pi-coding-agent/docs/providers.md
/opt/pi-1.0.2/lib/node_modules/@earendil-works/pi-coding-agent/docs/models.md
# exit 1After: rejected by provider validation (Pi coding agent 1.0.3):
$ pi --provider azure-openai-responses --model gpt-4o -p "test"
Error: Unknown provider "azure-openai-responses". Use --list-models to see available providers/models.
# exit 1Same in the latest release (Pi coding agent 1.1.0):
$ pi --provider azure-openai-responses --model gpt-4o -p "test"
Error: Unknown provider "azure-openai-responses". Use --list-models to see available providers/models.
# exit 1Fix verified: passing azure succeeds through provider resolution (Pi coding agent 1.1.0):
$ pi --provider azure --model gpt-4o -p "test"
No API key found for azure.
Use /login to log into a provider via OAuth or API key. See:
/opt/pi-1.1.0/lib/node_modules/@earendil-works/pi-coding-agent/docs/providers.md
/opt/pi-1.1.0/lib/node_modules/@earendil-works/pi-coding-agent/docs/models.md
# exit 1Why does Pi coding agent print this error?
Pull request #9714 (merged 2026-10-05T07:46:49Z) shipped in Pi 1.0.3 (released 2026-10-05T08:38:23Z) and renamed the Azure provider from azure-openai-responses to azure to support Azure Foundry Chat Completions deployments (such as azure/deepseek-v4-pro) alongside Responses API models under a unified provider ID. (earendil-works/pi PR #9714)
Related Pi coding agent fixes and pages
Error: --tools: tool names cannot be mixed with +name or -name entries(Pi coding agent 1.1.0 and later)- Pi coding agent tool page: Passing legacy --provider azure-openai-responses fails with unknown provider error
- All fix pages
Sources
- feat(ai): support Azure Foundry Chat Completions deployments (PR #9714) (read 2026-10-10)
- Pi 1.0.3 release notes (read 2026-10-10)
- Pi 1.0.2 release notes (read 2026-10-10)
- Pi Azure provider source (v1.0.2) (read 2026-10-10)
- Pi 1.1.0 release notes (read 2026-10-10)
- Issue #10501: docs: providers.md Azure OpenAI section does not name the new azure provider id (read 2026-10-10)
- Pi coding agent providers documentation (v1.1.0) (read 2026-10-10)
- Pi model resolver source (v1.1.0) (read 2026-10-10)
Last verified: 2026-10-10.