[codex] fix xAI OAuth test and reasoning effort

[nguyenxvotanminh3]

Summary

• add an OAuth connection test probe for xAI accounts
• normalize xAI reasoning efforts so max/xhigh are sent upstream as high
• add regression coverage for xAI reasoning effort normalization

Root cause

After the provider update, xAI rejects unsupported reasoning effort values such as max with HTTP 400. The xAI translator only accepted xAI-native values and could still leave unsupported aliases on the outgoing request path. OAuth xAI connections also had no dashboard test config, so provider tests reported Provider test not supported.

Validation

• node --import tsx/esm --test tests/unit/xai-translators.test.ts
• npm run typecheck:core
• npx eslint src/lib/providers/xai/thinking.ts src/lib/providers/xai/translators/openai-chat.ts src/app/api/providers/[id]/test/route.ts tests/unit/xai-translators.test.ts
• pre-push hook: npm run check:any-budget:t11, npm run check:tracked-artifacts

[gemini-code-assist]

Code Review

This pull request introduces a helper function normalizeXaiReasoningEffort to map unnormalized reasoning effort values (like 'max' or 'xhigh') to 'high' for xAI, applying it in applyThinking and chatRequestToXaiResponses, and adds an xAI test probe to the OAuth test configuration. The reviewer recommends normalizing the effort field inside req.reasoning to avoid HTTP 400 errors, updating the xAI OAuth test probe to use the native xAI reasoning format instead of reasoning_effort, and adding a unit test to cover the normalization of req.reasoning.effort.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

If the incoming request contains an OpenAI Responses-style reasoning object with an unnormalized effort value (such as "max" or "xhigh"), it is currently passed through verbatim to out.reasoning without normalization. This will cause the upstream xAI API to reject the request with an HTTP 400 error. We should normalize the effort field inside req.reasoning if it is present.

Suggested change

	if (req.reasoning) out.reasoning = req.reasoning;
	if (req.reasoning && typeof req.reasoning === "object") {
	const reasoning = req.reasoning as Record<string, unknown>;
	const effort = normalizeXaiReasoningEffort(reasoning.effort);
	out.reasoning = effort ? { ...reasoning, effort } : reasoning;
	}

[gemini-code-assist]

The direct OAuth test probe bypasses the translator and is sent directly to the upstream xAI API. Since the native xAI API expects the reasoning object (e.g., reasoning: { effort: "high" }) rather than the OpenAI-specific reasoning_effort parameter at the root level, sending reasoning_effort directly may result in an HTTP 400 Bad Request. We should use the native xAI format here.

Suggested change

	reasoning_effort: "high",
	reasoning: { effort: "high" },

[gemini-code-assist]

To ensure the new normalization logic for req.reasoning is fully covered and to prevent future regressions, we should add a unit test case validating that chatRequestToXaiResponses correctly normalizes the effort field inside req.reasoning.

test("chatRequestToXaiResponses: normalizes max reasoning_effort for xAI", () => {
  const req = { model: "grok-4.3", messages: [], reasoning_effort: "max" };
  const out = chatRequestToXaiResponses(req);
  assert.deepStrictEqual(out.reasoning, { effort: "high" });
});

test("chatRequestToXaiResponses: normalizes reasoning.effort for xAI", () => {
  const req = { model: "grok-4.3", messages: [], reasoning: { effort: "max", summary: "auto" } };
  const out = chatRequestToXaiResponses(req);
  assert.deepStrictEqual(out.reasoning, { effort: "high", summary: "auto" });
});

References

1. Always include tests when changing production code (Rule 9 of the Repository Style Guide). ^(link)

[diegosouzapw]

Merged into release/v3.8.39. Verified on the merge result — the xAI translator suite is 46/46 green, and normalizeXaiReasoningEffort correctly downgrades max/xhigh to the xAI-supported high. The CI reds were base-stale and cleared on the release tip. Thanks for the well-tested fix and welcome! 🎉