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