Skip to main content
Configure one HTTP CONNECT, SOCKS4, or SOCKS5 proxy for outbound sandbox connections with the proxy= argument to Sandbox.create(). Proxy protocols are mutually exclusive. See Proxies for routing behavior, security considerations, and limits.
Outbound proxies are local-only. Cloud sandbox creation rejects this setting.

Typical flow

Sandbox.create()

OutboundProxy

Frozen proxy configuration passed through Sandbox.create(proxy=...). HTTP CONNECT sends the policy-checked destination IP and port through the proxy. Destination DNS resolution remains in microsandbox. HTTP CONNECT supports TCP only and optional HTTP Basic authentication; UDP is unsupported. The SOCKS4 user_id must contain 1–255 bytes and no null byte. It identifies the caller; it is not a password.

credentials()

Return a SOCKS5 or HTTP CONNECT proxy with username/password authentication. Pass SecretSource.env("SOCKS5_PASSWORD") or SecretSource.env("HTTP_CONNECT_PASSWORD") as password. Calling this method on a SOCKS4 proxy raises ValueError. HTTP CONNECT accepts an empty username for token-only authentication. A non-empty username must not contain : or control characters. The host environment variable is read once each time the sandbox starts. Changing it affects the next start, not a sandbox that is already running. config_json and the database contain the source reference but never the resolved password. For SOCKS5, the username and resolved password must each contain 1–255 bytes.

SecretSource

env()

Create a host environment-variable reference for a SOCKS5 or HTTP CONNECT password. Import SecretSource from microsandbox.