中转codex cli的remote compact异常的BUG

[selang]

版本：0.5.8

使用 name = "OpenAI" 在会话的上下文快满的时候，会主动触发远程压缩。
一、转发请求加入了无效参数导致BUG
请求端点：/v1/responses/compact
错误详情:
{
"error": {
"message": "Unknown parameter: 'prompt_cache_key'.",
"type": "invalid_request_error",
"param": "prompt_cache_key",
"code": "unknown_parameter"
}
}
修复：针对/v1/responses/compact不注入prompt_cache_key
二、修复一后，返回的数据按SSE返回，但是codex cli 认为返回的数据非预期，报错。

修复：改为json返回

[github-actions]

Thank you for reporting this issue.

Analysis:
I have analyzed the codebase and identified the root causes of both bugs you described:

Bug 1: Invalid parameter

Root Cause:
In (line 57), the code checks if is an array to determine if it's a Codex request:

If true, it calls from which adds to the request body (line 282):

The problem is that requests also have an array in their body, so they incorrectly get added. When this request is forwarded to an OpenAI-compatible provider (like OpenAI), they reject this unknown parameter with:

Solution: The code should detect if the request is a request (accessible via ) and skip adding the for that specific endpoint.

Bug 2: SSE vs JSON response

Root Cause:
In (line 622), the code detects if the response is SSE by checking the content-type:

Additionally, in lines 1976-1983, it checks if the request body contains :

The issue is that responses are being returned as SSE (Server-Sent Events), but Codex CLI expects JSON format. The response handler doesn't have special logic to handle the compact endpoint differently.

Solution: The response handling should detect requests to and force JSON response format instead of treating it as a streaming response.

Relevant files:

• • Where is added (line 59-65)
• • The function that adds the parameter (line 282)
• • Where streaming/SSE is detected (line 622)
• • Session object with access (line 53)

---

Automated response from Claude AI

[github-actions]

Thank you for reporting this issue.

Analysis:
I have analyzed the codebase and identified the root causes of both bugs you described:

Bug 1: Invalid prompt_cache_key parameter

Root Cause:
In src/app/v1/_lib/proxy/session-guard.ts (line 57), the code checks if requestMessage.input is an array to determine if it is a Codex request:

const isCodexRequest = Array.isArray(requestMessage.input);

If true, it calls completeCodexSessionIdentifiers from src/app/v1/_lib/codex/session-completer.ts which adds prompt_cache_key to the request body (line 282):

if (missingBody) {
  args.requestBody.prompt_cache_key = sessionId;
  applied = true;
}

The problem is that /v1/responses/compact requests also have an input array in their body, so they incorrectly get prompt_cache_key added. When this request is forwarded to an OpenAI-compatible provider (like OpenAI), they reject this unknown parameter with:

Unknown parameter: 'prompt_cache_key'

Solution: The code should detect if the request is a /v1/responses/compact request (accessible via session.requestUrl.pathname) and skip adding the prompt_cache_key for that specific endpoint.

Bug 2: SSE vs JSON response

Root Cause:
In src/app/v1/_lib/proxy/forwarder.ts (line 622), the code detects if the response is SSE by checking the content-type:

const isSSE = contentType.includes("text/event-stream");

Additionally, in lines 1976-1983, it checks if the request body contains stream: true:

try {
  const parsed = JSON.parse(bodyString);
  isStreaming = parsed.stream === true;
} catch {
  isStreaming = false;
}

The issue is that /v1/responses/compact responses are being returned as SSE (Server-Sent Events), but Codex CLI expects JSON format. The response handler does not have special logic to handle the compact endpoint differently.

Solution: The response handling should detect requests to /v1/responses/compact and force JSON response format instead of treating it as a streaming response.

Relevant files:

• src/app/v1/_lib/proxy/session-guard.ts - Where prompt_cache_key is added (line 59-65)
• src/app/v1/_lib/codex/session-completer.ts - The function that adds the parameter (line 282)
• src/app/v1/_lib/proxy/forwarder.ts - Where streaming/SSE is detected (line 622)
• src/app/v1/_lib/proxy/session.ts - Session object with requestUrl access (line 53)

---

Automated response from Claude AI

[ding113]

感谢反馈。

第一个问题会在下一版本修复。

第二个问题的话，目前 CCH 并不会对响应体做转换。理论上是原样返回的。