[Bug] 使用 codex 原生 compact 接口会报错

[hang333]

当使用 codex 原生的 compact 接口 v1/responses/compact 会报错

{
  "error": {
    "code": "unknown_parameter",
    "type": "invalid_request_error",
    "param": "stream",
    "message": "Unknown parameter: 'stream'."
  }
}

其原因应该是

claude-code-hub/src/app/v1/_lib/codex/utils/request-sanitizer.ts

Lines 227 to 230 in 12cd84a

	// Codex API 的默认行为
	if (output.stream === undefined) {
	output.stream = true; // Codex 默认流式
	}

在 stream 参数未定义的时候被强制设置成了 true 导致的

[github-actions]

Thank you for reporting this issue and for accurately identifying the root cause.

Analysis:

You are correct. The issue is in src/app/v1/_lib/codex/utils/request-sanitizer.ts (lines 226-230):

// 步骤 3: 确保必需字段
// Codex API 的默认行为
if (output.stream === undefined) {
  output.stream = true; // Codex 默认流式
}

The /v1/responses/compact endpoint is a non-streaming endpoint that does not support the stream parameter. However, the current sanitizer logic forcibly sets stream = true when the parameter is undefined, which causes the API to reject the request with an unknown_parameter error.

Code flow:

1. Request to /v1/responses/compact falls through to handleProxyRequest (since only /v1/responses is explicitly routed in src/app/v1/[...route]/route.ts:31)
2. Format detection via detectFormatByEndpoint() in src/app/v1/_lib/proxy/format-mapper.ts:65 only matches /v1/responses exactly (not /v1/responses/compact)
3. When the provider type is codex, the sanitizeCodexRequest() function is called (src/app/v1/_lib/proxy/forwarder.ts:1055)
4. The sanitizer always sets stream = true if undefined, which is incompatible with the compact endpoint

Affected files:

• src/app/v1/_lib/codex/utils/request-sanitizer.ts:228-230 - The problematic forced stream = true logic
• src/app/v1/_lib/proxy/format-mapper.ts:65 - Only matches exact /v1/responses path
• src/app/v1/[...route]/route.ts:31 - Only /v1/responses is explicitly routed

Potential fix considerations:

1. Modify the sanitizer to detect the compact endpoint and avoid setting stream
2. Or conditionally skip the stream parameter assignment when stream is explicitly absent/false in the original request for specific endpoints like /responses/compact

---

Automated response from Claude AI

[ding113]

@claude fix it

[ding113]

I've created a fix for this issue.

Pull Request: #369

Changes made:

• Removed the forced stream = true assignment in sanitizeCodexRequest() function
• Now the sanitizer preserves the original stream value (or keeps it undefined)
• The /v1/responses/compact endpoint will no longer receive the unsupported stream parameter

The fix is minimal and targeted - it only removes the problematic default while keeping all other sanitization logic intact.

---

Response from Claude AI