[Feature]: Adapt Codex namespace tools for xAI/Grok Responses

[Transparent0]

Feature area

Request forwarding / API compatibility

Problem

Problem

When Codex Desktop calls grok-4.5 through CliRelay xAI OAuth, it posts to /v1/responses with tools[].type = "namespace".

Grok Build rejects the request with HTTP 422:

Failed to deserialize the JSON body into the target type: unknown variant `namespace`

Claude Code works with the same xAI credentials because it uses the Anthropic Messages route instead. The failure reproduces across two xAI OAuth accounts, so it is not tied to a single account or model availability.

Proposed solution

Please add xAI-specific Responses compatibility for Codex namespace tools:

1. Flatten namespace child tools into qualified top-level function names before forwarding to Grok.
2. Restore the original namespace/name when converting Grok function calls back to Codex Responses output.
3. Keep the existing Codex/OpenAI GPT path unchanged.

This should be a provider-boundary adaptation rather than removing namespace tools globally.

Use case

Codex Desktop users who route Grok Build through CliRelay need normal coding tools and MCP/connectors. Without this compatibility, every Codex request containing a namespace tool is rejected before the model runs.

Are alternatives acceptable?

Yes, a simpler alternative is fine

Panel version

v0.4.11

Backend version

v0.4.11

Extra context

Upstream reference implementations:

• fix(xai): 保留 namespace 工具路由信息 router-for-me/CLIProxyAPI#4251
• fix(xai): flatten Codex Responses Lite additional tools router-for-me/CLIProxyAPI#4307

No credentials, tokens, cookies, or private request payloads are included in this report.

Safety check

• I have not included API keys, auth files, cookies, tokens, or other secrets.

[github-actions]

Thanks for the clear write-up. CliRelay is rejecting Codex Desktop /v1/responses traffic to xAI/Grok when tools include type: "namespace", and Grok returns 422 because it only accepts its own tool variants. Claude via Anthropic Messages is unaffected, and the OpenAI/Codex GPT path should stay as-is.

Direction: keep this as an xAI Responses boundary adapter only. On the way in, expand namespace child tools into qualified top-level function tools Grok accepts; on the way out, rewrite Grok function calls back to the original namespace/name shape Codex expects. Avoid global removal of namespace tools.

Reasonable scope split: (1) outbound request rewrite + validation, (2) inbound tool-call/output restore, (3) regression tests for Grok vs OpenAI Responses. The linked CLIProxyAPI PRs are useful references for naming and round-trip behavior.

Panel/backend v0.4.11 and the failure mode are enough to start from; no secrets needed.