fix(fetch): honor proxy and verifySsl on the node fetch path

[devYRPauli]

Problem

proxy, verifySsl, and caBundlePath set in config.yml were ignored by the remote config-sync / index-cache client. core/continueServer/stubs/client.ts used the global fetch() directly for its requests, so unlike the LLM request path (which already routes through fetchwithRequestOptions), these node fetches never applied the configured request options.

Fix

Route the ContinueServerClient requests (getConfig, getFromIndexCache, sendFeedback) through fetchwithRequestOptions, and thread config.requestOptions in from the single call site in core/indexing/CodebaseIndexer.ts. The new constructor parameter is optional, so existing callers are unaffected.

Test

Added packages/fetch/src/fetch.test.ts asserting the agent is an HttpsProxyAgent pointed at requestOptions.proxy, that rejectUnauthorized is false when verifySsl: false, and both together. The packages/fetch suite passes (100 tests).

Fixes #12956.

[chatgpt-codex-connector]

💡 Codex Review

continue/docs-site/app/[[...slug]]/page.tsx

Lines 69 to 71 in 42a1879

	const target = redirectTo.startsWith("http")
	? redirectTo
	: `/docs${redirectTo}`;

Avoid prefixing standalone docs redirects with /docs

For any internal redirect from docs.json (for example /cli/overview -> /cli/quickstart), this sends the browser to /docs/cli/quickstart. The standalone docs app already strips /docs for normal links via resolveHref, and generateStaticParams creates pages like /cli/quickstart, not /docs/cli/quickstart, so these redirect pages land on a non-existent route/404 on the docs subdomain. Use the same href resolution as the rest of the docs shell or redirect directly to redirectTo.

---

continue/core/core.ts

Lines 1138 to 1142 in 42a1879

	return await fetchModels(
	msg.data.provider,
	msg.data.apiKey,
	msg.data.apiBase,
	);

Thread requestOptions into dynamic model fetches

When the Add Model UI calls this new models/fetch handler, only provider/API key/API base are passed through, so the implementations in core/llm/fetchModels.ts use native fetch or an LLM created without requestOptions. In environments that require config.requestOptions.proxy, caBundlePath, or verifySsl: false, dynamic model loading for OpenRouter/Anthropic/Gemini/Ollama fails even though normal LLM requests honor those settings. Load the current config here and pass its request options into the fetch path.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".