feat: add provider-scoped environment overrides#5807
Merged
Conversation
vegarsti
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds provider-scoped environment overrides for Pi. API key credentials in
auth.jsoncan now include anenvobject, and stream options supportenvdirectly. These values take precedence over process environment variables for provider configuration, API key lookup, headers, Cloudflare URL placeholders, Azure OpenAI settings, Google Vertex project/location and credentials path, Amazon Bedrock settings, cache retention (PI_CACHE_RETENTION), and proxy configuration (HTTP_PROXY,HTTPS_PROXY).In order to facilitate this, I also cleaned up code slightly along the way. This centralizes provider env lookup in
pi-ai, including the existing Bun sandbox/proc/self/environfallback for direct library consumers that do not go through the Pi coding-agent Bun entrypoint. There were some cases where we skipped over that logic which looked unintentional.Fixes #5728