Repository navigation
Conversation
Routing an agent through a company AI gateway needed two things paude could not do: set arbitrary env vars (ANTHROPIC_BASE_URL, model overrides, feature flags) in the agent container, and have the proxy inject the provider API key for a host other than the provider's own domains. --env KEY=VALUE (or bare KEY to copy the host value) sets agent env vars. Provider credentials and paude-managed proxy/CA/PAUDE_* vars are rejected, since --env values are visible via inspect. --credential-domain PROVIDER=HOST[:PORT] writes a paude-proxy routing file to the session auth volume and points the proxy at it via PAUDE_PROXY_CREDENTIALS_CONFIG. The proxy replaces its built-in table with a custom file, so paude writes a copy of the pinned defaults with the custom route first. The host is always allowlisted, and a non-443 port is added to allowed endpoints. Both settings are stored in labels and the upgrade/backup manifests, so they survive start, proxy recreation, allowed-domains/endpoints updates and upgrade. create.py option types and dry-run moved to their own modules to keep it under the file-size limit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
1 participant
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.
Routing an agent through a company AI gateway needed two things paude could not do: set arbitrary env vars (ANTHROPIC_BASE_URL, model overrides, feature flags) in the agent container, and have the proxy inject the provider API key for a host other than the provider's own domains.
--env KEY=VALUE (or bare KEY to copy the host value) sets agent env vars. Provider credentials and paude-managed proxy/CA/PAUDE_* vars are rejected, since --env values are visible via inspect.
--credential-domain PROVIDER=HOST[:PORT] writes a paude-proxy routing file to the session auth volume and points the proxy at it via PAUDE_PROXY_CREDENTIALS_CONFIG. The proxy replaces its built-in table with a custom file, so paude writes a copy of the pinned defaults with the custom route first. The host is always allowlisted, and a non-443 port is added to allowed endpoints.
Both settings are stored in labels and the upgrade/backup manifests, so they survive start, proxy recreation, allowed-domains/endpoints updates and upgrade. create.py option types and dry-run moved to their own modules to keep it under the file-size limit.