Continue CLI behind corporate proxy: 404 and PostHog errors; VS Code extension works

[erigrus]

I am on Windows behind a corporate proxy. The Continue VS Code extension works fine with my Azure OpenAI setup and local MCP servers, but the CLI fails. When I run:

cn --config C:\Users\user\.continue\config.yaml --verbose -p "Test"

it returns {"status":"error","message":"404 Resource not found"}. In non-headless mode, the CLI also periodically logs PostHogFetchNetworkError. I expect the CLI to behave like the extension when using the same config. This appears to be proxy-related or a difference in how the CLI resolves endpoints or paths.

Questions

• Does cn use the exact same config schema and paths as the extension?
• How can I configure cn for proxies on Windows (HTTP_PROXY/HTTPS_PROXY/NO_PROXY)?
• How can I disable telemetry in cn?
• Is the 404 in headless mode a known issue with Azure provider configs?

[juan-3ds]

@erigrus There was some discussion on telemetry in the Discord forum https://discord.com/channels/1108621136150929458/1156679146932535376/1428463512103157800

[bdougie]

This is an area we need more information from corporate proxy users. The Continue IDE extensions after months of feedback. With the CLI being newer, we'd need some design partnership or community contribution to work through the limitations.

[dstanbai]

I have the same issue and NOT behind a corporate proxy, but am pointing to an azure.us endpoint. Extension works great, but I get a 404 on the CLI. The main guess is that the CLI has some different logic for the URL generation and the .us is throwing it somehow. Hope this helps

[erigrus]

We also use Azure (with .com endpoint). Maybe that is the main issue.

[mfmotta]

I have a similar issue: Azure provider returns 403 status code (no body) in CLI but works in VSCode Extension.

Interestingly, the Anthropic provider works fine in CLI. The key difference: my Azure config uses no API key (authentication is handled by our corporate gateway), while the working Anthropic config requires an API key.

Environment

• Continue CLI version: 1.5.25
• Continue VSCode Extension version: 1.2.11
• Node.js version: 22.20.0
• npm version: 10.9.3
• OS: Windows 11 Enterprise (Build 22631)
• Network: Corporate proxy with custom CA certificates

Configuration (Works in VSCode, Fails in CLI)

name: Azure GPT Test
version: 1.0.0
schema: v1
models:
  - name: Azure GPT-5.1
    model: gpt-5.1
    provider: azure
    apiBase: https://api-gateway.company.local/continue
    requestOptions:
      caBundlePath: C:/Users/username/.continue/certs/cacerts.pem
    capabilities:
      - tool_use
      - image_input
    env:
      apiVersion: 2024-04-01-preview
    defaultCompletionOptions:
      maxTokens: 128000
      contextLength: 400000

Steps to Reproduce

1. Save the above configuration to a YAML file
2. Run: cn --config config.yaml
3. Send any message
4. Result: Error: 403 status code (no body)

Key Observation

Anthropic provider works in CLI with the same network setup:

models:
  - name: Claude_Opus_4.5
    provider: anthropic
    model: claude-opus-4-5
    apiKey: <api-key>  # Note: API key required
    apiBase: https://my-resource.services.ai.azure.com/anthropic/v1
    requestOptions:
      proxy: http://corporate-proxy.local:80
      caBundlePath: /path/to/cacerts.pem

This confirms:

• Continue CLI works on our network
• Proxy and CA certificates are configured correctly
• Only the Azure provider (without API key) fails

Questions

1. Does the VSCode extension use Azure Account integration or different authentication that the CLI lacks?
2. Are there known differences in how the Azure provider is implemented between extension and CLI?
3. Is there debug logging to see what HTTP requests/headers the CLI sends?