-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Description
goose configure (azure openai provider) with 1.23.0 fails on model fetch with "Request failed: Resource not found (404): Resource not found" using the same values that work in goose configure 1.22.2.
💡 Before filing, please check common issues:
https://block.github.io/goose/docs/troubleshooting
📦 To help us debug faster, attach your diagnostics zip if possible.
👉 How to capture it: https://block.github.io/goose/docs/troubleshooting/diagnostics-and-reporting/
A clear and concise description of what the bug is.
To Reproduce
goose configure with 1.22.2 for azure openai provider with api key works if you set this env var to use the api key:
AZURE_OPENAI_API_KEY=
however, attempting the same goose configure with a clean 1.23.0 install fails at the end with "Request failed: Resource not found (404): Resource not found".
the configure doesn't finish and the CLI does not work.
simply manually adding these lines to config.yaml fixes the problem, so it's just the goose configure model fetch that fails.
GOOSE_PROVIDER: azure_openai
GOOSE_MODEL: gpt-5.2
Please provide the following information
- OS & Arch: Ubuntu 24.04.1 LTS (via WSL2)
- Interface: CLI
- Version: v1.23.0
- Extensions enabled: N/A
- Provider & Model: Azure OpenAI gpt-4o, Azure OpenAI gpt-5.2
Additional context
Add any other context about the problem here.