Route Mistral API key autodetection through this.fetch

[devYRPauli]

Description

Mistral.autodetectApiKeyType() calls the global fetch directly:

const mistralResp = await fetch("https://api.mistral.ai/v1/models", {

That bypasses fetchwithRequestOptions, so this one request ignores the user's configured proxy, caBundlePath, verifySsl and custom headers. Every other request in this provider goes through this.fetch, which BaseLLM wires to fetchwithRequestOptions with this.requestOptions (core/llm/index.ts). The inherited call sites in OpenAI.ts all use this.fetch(...) already.

The call is reachable in the common case: the constructor invokes it whenever apiBase is not set explicitly, in order to decide between the codestral and mistral endpoints. Its rejection is swallowed by an empty .catch((err: any) => {}), so behind an intercepting corporate proxy or with a custom CA the request fails silently, no error surfaces, and the provider is left with an incorrectly autodetected apiBase.

This is a one line change to use this.fetch, which is already available on the class and has the same (url, init) => Promise<Response> signature. Only .status is read from the response, so there is no typing change.

This is a sibling of #12993 and #12999, which fixed the same class of bypass elsewhere in the codebase.

Checklist

• I've read the contributing guide
• The relevant docs, if any, have been updated or created
• The relevant tests, if any, have been updated or created

Tests

No new tests. The change swaps one call onto the same fetch wrapper every sibling method already uses, and the behaviour it restores (honouring requestOptions) needs a proxy or custom CA to observe, which the existing suite does not set up.

I ran a typecheck over core before and after the change: 115 pre-existing errors both times, none in Mistral.ts. The pre-existing errors are unrelated module resolution failures for unbuilt @continuedev/* workspace packages.

[chatgpt-codex-connector]

💡 Codex Review

continue/core/core.ts

Line 1136 in 13791dc

on("models/fetch", async (msg) => {

Restore enterprise license key handler

This new registration replaced the removed on("mdm/setLicenseKey", ...) handler, but the extension entry points still call that message (extensions/vscode/src/commands.ts:708 and extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/license/AddLicenseKey.kt:30). In those IDEs, entering an enterprise license key now has no core handler, so VS Code treats the result as invalid and IntelliJ gets a failed/no-content response instead of validating and saving the key.

---

continue/packages/config-yaml/src/registryClient.ts

Lines 26 to 27 in 13791dc

	case "slug":
	throw new Error("Slug-based package resolution is not supported");

Keep slug package resolution working

Rejecting every uriType: "slug" breaks the existing local unroll paths that still pass slug packages here, including --config owner/package when unauthenticated (extensions/cli/src/configLoader.ts:467-470) and local configs with uses: blocks. Those documented configurations now fail with Slug-based package resolution is not supported instead of fetching/unrolling the referenced package.

---

continue/core/llm/llms/Mistral.ts

Line 20 in 13791dc

const mistralResp = await this.fetch("https://api.mistral.ai/v1/models", {

Let Mistral autodetection rebuild the Codestral adapter

Using this.fetch here makes the 401 probe for a Codestral-only key throw before mistralResp.status can be inspected (BaseLLM.fetch throws on non-OK responses). The constructor then swallows the rejection, so the .then block at Mistral.ts:45-56 never rebuilds openaiAdapter after switching apiBase to the Codestral endpoint; default Codestral users with no explicit apiBase keep the adapter created by super() for api.mistral.ai and their requests fail with the wrong endpoint.

---

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

Lines 69 to 71 in 13791dc

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

Do not prefix internal docs redirects with /docs

For an internal redirect like /cli/overview -> /cli/quickstart, this sends the browser to /docs/cli/quickstart, but the new docs app serves pages at the root and even resolveHref strips /docs for internal links (docs-site/lib/resolveHref.ts:7-10). On the standalone docs site this lands on a non-generated route, and on GitHub Pages it also drops the /continue base 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".