Both SDKs honour HTTPS_PROXY. Nothing else in your agent code changes.
The Aarmos CLI is not publicly distributed. Commands here are reference examples, not instructions you can run today.
1 · Environment
eval "$(aarmos env)" # authenticated HTTPS_PROXY + HTTP_PROXY
export OPENAI_API_KEY=sk-…
export ANTHROPIC_API_KEY=sk-ant-…2 · Policy
[[allow]]
verb = "communicate"
host = "api.openai.com"
ceiling.per_minute = 60
[[allow]]
verb = "communicate"
host = "api.anthropic.com"
ceiling.per_minute = 603 · Run
aarmos run -- node agent.mjsNotes
- Streaming responses (SSE) are proxied without buffering.
- The proxy matches hostnames and does not decrypt HTTPS, so it cannot read or cap token counts in requests.
- Model-side tool use inside an encrypted API call is not visible to the proxy; govern tools at the adapter or tool boundary.
See all providers → recipes index.