Network

Corporate networks are covered: Kodine honors the standard proxy environment variables and can be taught to trust custom certificates.

---

Proxy

Standard proxy environment variables just work.

# HTTPS proxy (preferred)
export HTTPS_PROXY=https://proxy.example.com:8080

# HTTP proxy fallback when HTTPS isn't an option
export HTTP_PROXY=http://proxy.example.com:8080

# Always bypass the proxy for the local server
export NO_PROXY=localhost,127.0.0.1

Caution

Because the TUI talks to a local HTTP server, that traffic has to skip the proxy — otherwise you’ll create routing loops.

The server’s port and hostname are adjustable through CLI flags.

---

Authenticate

Proxies using basic authentication accept credentials straight in the URL.

export HTTPS_PROXY=http://username:[email protected]:8080

Caution

Don’t bake passwords into scripts — pull them from environment variables or a proper credential store.

NTLM, Kerberos, and other advanced schemes are best handled by placing an LLM Gateway in front that speaks your authentication method.

---

Custom certificates

Enterprises terminating HTTPS with their own CA can make Kodine trust that CA like so:

export NODE_EXTRA_CA_CERTS=/path/to/ca-cert.pem

The setting covers proxied traffic and direct API calls alike.