feat(providers): Grok/xAI provider, Responses compat, and reasoning.effort mapping#252
Open
24baigei wants to merge 4 commits into
Open
feat(providers): Grok/xAI provider, Responses compat, and reasoning.effort mapping#25224baigei wants to merge 4 commits into
24baigei wants to merge 4 commits into
Conversation
Force openai-responses when Base URL is api.x.ai, strip OpenAI-only payload fields, request encrypted reasoning and search sources via include, and surface x_search / custom_tool_call hosted search events.
…ng effort Introduce ProviderId xai with Settings/WebUI tabs, official brand icon, and fixed openai-responses routing. Keep and map UI thinking levels to reasoning.effort for api.x.ai, import grokbuild providers from CC-Switch, and extend model fetch, native search, and tests for the new provider type.
24baigei
force-pushed
the
feat/xai-responses-compat
branch
from
July 23, 2026 19:20
a1b2de0 to
905b5a8
Compare
24baigei
changed the title
Fix lint failures in GUI and Gateway WebUI CI caused by unformatted sources (line endings / style) introduced with the xai provider work.
…xpectations Grok/xAI first-class provider defaults add xai: high; update WebUI settings tests to match GUI normalization expectations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
api.x.aiResponses compatibility for Codex/OpenAI-compatible providers, plus a first-class Grok (xai) provider type in desktop GUI and WebUI.openai-responsesfor xAI (formalxaitype or directapi.x.aibase URL), strip OpenAI-only request fields, keep/map UI thinking levels toreasoning.effort(minimal?low, etc.), and requestincludefor encrypted reasoning + hosted search sources.x_search_call,x_keyword_search/x_semantic_search,response.x_search_call.*).grokbuildproviders into LiveAgentxai, use the official Grok/xAI brand icon, and extend model list fetch / native search / gateway provider typing.Test plan
ccs_imports_grokbuild_*/ccs_maps_grokbuild_app_type_to_xaipnpm exec tsc --noEmit(agent-gui)liveagent.exe)minimal? payloadreasoning.effort: "low"grok-4.5, switch low/medium/high and confirm behavior / debug payloadgrokbuildrows under Grok