fix: remove wall-clock timeout from streaming SSE to prevent thinking chain cutoff

The 60s --max-time timeout was killing curl mid-stream during long
reasoning/thinking outputs (30-120+ seconds). Streaming requests now
rely on header timeout + AbortSignal for protection instead.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

CHANGELOG.md

@@ -6,6 +6,10 @@
 
 ## [Unreleased]
 
+### Fixed
+
+- 流式 SSE 请求不再设置 `--max-time` 墙钟超时，修复思考链（reasoning/thinking）在 60 秒处中断的问题；连接保护由 header 超时 + AbortSignal 提供，非流式请求（models、usage）超时不受影响
+
 ### Added
 
 - 代理池功能：支持为不同账号配置不同的上游代理，实现 IP 多样化和风险隔离

src/proxy/codex-api.ts

@@ -247,11 +247,10 @@ export class CodexApi {
     );
     headers["Accept"] = "text/event-stream";
 
-    const timeout = config.api.timeout_seconds;
-
+    // No wall-clock timeout for streaming SSE — header timeout + AbortSignal provide protection
     let transportRes;
     try {
-      transportRes = await transport.post(url, headers, JSON.stringify(request), signal, timeout, this.proxyUrl);
+      transportRes = await transport.post(url, headers, JSON.stringify(request), signal, undefined, this.proxyUrl);
     } catch (err) {
       const msg = err instanceof Error ? err.message : String(err);
       throw new CodexApiError(0, msg);