Skip to content

[fork CI] fix(proxy): emit response.incomplete (39a714b3) - #2

Closed
RGB-loop wants to merge 14 commits into
mainfrom
fix/codex-response-incomplete-event
Closed

RGB-loop wants to merge 14 commits into
mainfrom
fix/codex-response-incomplete-event

Conversation

@RGB-loop

@RGB-loop RGB-loop commented Nov 5, 2026

Copy link
Copy Markdown
Owner

Fork-internal CI run for SaladDay#551 at 39a714b. Not for merge; will be closed after CI.

SaladDay and others added 14 commits October 22, 2026 18:37
…uery

fix(tui): align managed Codex OAuth quota with upstream
fix(codex): preserve provider authentication in forms
…ladDay#548)

* fix(presets): refresh provider model templates to current lineups

Mirror the desktop presets at farion1231/cc-switch e217bfc (2026-11-03) across
the bundled Claude, Codex, Gemini, Pi, OpenCode, OpenClaw and Hermes templates.

- Claude and Codex defaults move to claude-*-5-5, gpt-6.1-sol / gpt-6-luna,
  a 272000 OAuth context window, and gemini-3.8-flash.
- DeepSeek V4.1 Flash, GLM-5.3, MiniMax-M3.1-Flash and MiMo V2.6 model rows,
  with matching reasoning levels, modalities and context windows.
- Pi sponsor and gateway presets (OpenCode Go, Qiniu, OpenRouter) refreshed,
  including the Pi thinking maps and the 88API mirror.
- Pricing seeds for the new models plus the GPT-5.6 Sol promotional tier with
  repair guards for both old built-in generations.

* fix(presets): align upstream defaults and complete model pricing

---------

Co-authored-by: saladday <1203511142@qq.com>
… cache (SaladDay#527)

* fix(proxy): keep mid-conversation system messages in place for prefix cache

* style: rustfmt
…dDay#512)

Codex does not accept a `type` key on [mcp_servers.*] entries; it warns
about it and fails under --strict-config. Codex infers the transport from
`command`/`url`, and import_from_codex already infers `type` the same way
when it is absent, so the field can be dropped from generated TOML without
losing round-trip information.

Closes SaladDay#496
Converted Anthropic Messages and Chat Completions streams already set
response.status to "incomplete" (max_tokens, refusal, truncation,
finish_reason=length), but always sent the terminal event as
response.completed. Codex only reads incomplete_details from a
response.incomplete event, so these responses were treated as normal
completions.

Pick the terminal event name from the response status, and let the
usage parser, Codex OAuth SSE aggregation and Chat history recorder
accept response.incomplete so usage and history are not lost.

Fixes SaladDay#546

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RGB-loop

RGB-loop commented Nov 5, 2026

Copy link
Copy Markdown
Owner Author

Fork CI done (Rust CI 41984865485, Benchmark 41984865493 success @39a714b3).

@RGB-loop RGB-loop closed this Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants