Describe the bug

I want to add Azure OpenAI as a provider to Goose. I have a specific API key that should be used to access Azure OpenAI but also use the Azure CLI locally for unrelated tasks. Goose doesn't even ask for an API key and apparently just tries to use the Azure CLI.

This causes issues because the user signed into Azure CLI does not have permissions to call Azure OpenAI.

Note: It does work when setting AZURE_OPENAI_API_KEY as an environment variable, but this would mean the secret isn't stored inside keychain.

Expected behavior

Goose should allow me to choose if I want to configure AZURE_OPENAI_API_KEY or use the Azure CLI authentication.

Screenshots

Please provide following information:

• OS & Arch: macOS Sequoia 15.4.1 (24E263)
• Interface: goose CLI (installed via homebrew)
• Version: 1.0.24
• Provider & Model: Azure OpenAI