Network

HTTP/HTTPS proxy configuration for OpenCorvus.

OpenCorvus stores explicit proxy settings under the single network.proxy config entry. The Overlay Network panel edits this same field and its Test Proxy button sends one request through the edited proxy draft, reporting the HTTP status code and elapsed time.

Config

{
  "network": {
    "proxy": {
      "url": "http://127.0.0.1:7890",
      "username": "optional",
      "password": "optional",
      "llmProvider": true,
      "webResearch": true,
    },
  },
}

Field	Purpose
`url`	HTTP(S) proxy URL. Supports `http://` and `https://`; credentials must stay in `username` / `password`.
`username` / `password`	Optional proxy authentication fields. `password` requires `username`.
`llmProvider`	Routes model provider HTTP requests through the proxy.
`webResearch`	Routes websearch and webfetch requests through the proxy.

The proxy test uses the edited form values directly, so you can test before saving. It does not retry through a direct connection when the proxy fails.

Environment Variables

OpenCorvus still reads standard proxy environment variables for runtime paths that are outside network.proxy.

Variable	Purpose
`HTTP_PROXY` / `http_proxy`	Proxy for HTTP traffic
`HTTPS_PROXY` / `https_proxy`	Proxy for HTTPS traffic
`NO_PROXY` / `no_proxy`	Comma-separated host patterns to bypass

TLS / Custom CA

For self-signed corporate certificates, use Bun’s standard NODE_EXTRA_CA_CERTS or the OS trust store:

export SSL_CERT_FILE=/etc/ssl/certs/corp-ca.pem
opencorvus serve