Skip to main content
Cody CLI Docs

Network Configuration

If you're behind a corporate firewall, proxy, or have SSL inspection, you may need to configure Cody CLI to connect to AINative services.

Required Endpoints

Cody CLI needs outbound HTTPS access to:

  • api.ainative.studio — API gateway (LLM, auth, sessions)
  • ainative.studio — OAuth login and updates
  • registry.npmjs.org — Auto-updates (optional)

HTTP Proxy

Set standard proxy environment variables:

export HTTPS_PROXY=https://proxy.company.com:8080
export HTTP_PROXY=http://proxy.company.com:8080
export NO_PROXY=localhost,127.0.0.1

SSL / TLS Inspection

If your network performs SSL inspection, add your CA certificate:

export NODE_EXTRA_CA_CERTS=/path/to/corporate-ca.crt

Or disable strict SSL (not recommended for production):

export NODE_TLS_REJECT_UNAUTHORIZED=0

Custom Base URL

To route all API calls through your own gateway or proxy:

export ANTHROPIC_BASE_URL=https://your-gateway.company.com

Diagnostics

Run the built-in doctor to check connectivity:

cody /doctor

This checks DNS resolution, HTTPS connectivity, and auth status for all required endpoints.