Skip to content

004-docs-network.md

Latest commit

 

History

History
63 lines (44 loc) · 1.7 KB

004-docs-network.md

File metadata and controls

63 lines (44 loc) · 1.7 KB
Raw
title Network
url https://opencode.ai/docs/network/
source crawler
fetched_at 2026-02-14 12:04:41 -0300
rendered_js false
word_count 88
summary This document explains how to configure proxy settings and custom CA certificates for OpenCode in enterprise network environments. It covers environment variables, authentication, and trust configurations for secure connections.
tags
proxy-configuration
environment-variables
custom-certificates
enterprise-networking
authentication
network-security
category configuration

OpenCode supports standard proxy environment variables and custom certificates for enterprise network environments.

Proxy

OpenCode respects standard proxy environment variables.


# HTTPS proxy (recommended)
export HTTPS_PROXY=https://proxy.example.com:8080
# HTTP proxy (if HTTPS not available)
export HTTP_PROXY=http://proxy.example.com:8080
# Bypass proxy for local server (required)
export NO_PROXY=localhost,127.0.0.1

You can configure the server’s port and hostname using CLI flags.

Authenticate

If your proxy requires basic authentication, include credentials in the URL.


export HTTPS_PROXY=http://username:password@proxy.example.com:8080

For proxies requiring advanced authentication like NTLM or Kerberos, consider using an LLM Gateway that supports your authentication method.

Custom certificates

If your enterprise uses custom CAs for HTTPS connections, configure OpenCode to trust them.


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

This works for both proxy connections and direct API access.