CodexHub 0.1.8 Beta 3.3

CodexHub 0.1.8 Beta 3.3

Republished in place again on 2026-08-10. GitHub keeps the release's original published timestamp. The tag and all downloadable assets now include the Codex App Chat-history scope correction below. If you installed or downloaded Beta 3.3 before this notice, download it again and overwrite the existing installation.

This refresh

• Corrects the scope of the previous message-phase fix: Codex App requests targeting a Chat Completions provider no longer depend on a Collaboration V2 signal.
• Old Codex tasks can switch to Kimi K3 when assistant history contains the valid Responses-only phase: "final_answer" field.
• At the Codex App/Chat wire boundary, the Gateway removes only phase from the outgoing message item before Chat translation.
• Responses upstreams continue to receive message phase; ordinary non-Codex third-party Responses-to-Chat translation remains strict.
• Existing task files are not modified or cleaned on disk. No provider/model fallback was added.
• Telemetry records only the aggregate chat_message_phase_removed count and does not record message IDs, phases, content, reasoning summaries, encrypted content, or text.

Earlier Beta 3.3 fixes retained

• Responses reasoning history is adapted at the Collaboration V2 + Chat boundary without leaking private reasoning.
• Kimi Chat Completions responses, including legal empty-content and reasoning-extension frames, convert into standard Responses streams without leaking raw reasoning.
• Translation failures after a Responses SSE stream starts terminate with a standard response.failed event.
• Strictly valid stale plain-function history can be rendered as a read-only transcript when the current Collaboration V2 plan no longer owns it; malformed or ambiguous history remains fail-closed.
• Catalog entries that fall back from a missing output limit continue to expose max_output_tokens = context_window.
• For Codex App requests to Ollama Cloud, only fallback-derived wire values equal to or larger than the fallback context window are omitted; smaller explicit and authoritative limits are preserved.

Verification

• focused routing regressions on candidate and merged main: 4 passed, 2 subtests passed
• Python core: 2224 passed, 3 skipped, 484 subtests passed
• Python partitions: complete and disjoint (2373 = 2227 core + 146 synthetic collected)
• report-only quality scan: exit 0, parse_errors: 0
• Standards review: no findings
• Spec review: no findings
• isolated live Kimi K3 request from main commit d1308ce5, without a Collaboration V2 signal and with representative reasoning + phase history: HTTP 200, expected marker and response.completed, no response.failed, no phase error, no private reasoning leakage
• installed Gateway 127.0.0.1:9099 remained PID 31324 throughout verification and release work
• normal/debug updater signatures cryptographically verified; both manifests identify source revision d1308ce5bd0546993a68579b23102bafde24513a
• portable archive contains an exact hash match of the corrected Gateway source

Assets

• CodexHub_0.1.8-beta.3.3_x64-setup.exe — SHA-256 fea2df9119e356d8787b730450ca8fb02afe53d5d138614d9bc581bb256e2be0
• CodexHub_0.1.8-beta.3.3_debug_x64-setup.exe — SHA-256 df5314c3469fd8c3a808ee7539af1ee02c6d2ff5b9d3703b8fb0d77d25a4583f
• CodexHub_0.1.8-beta.3.3_portable_d1308ce5.zip — SHA-256 af35c827ca39b161c00778ea570563da91c85bf52887cd3e7a8c0f13ac0c99fa

The release tag points to main commit d1308ce5bd0546993a68579b23102bafde24513a.

Related pull requests: #384, #385, #386, #387, #388, #389, #390, #391. Follow-up to #377.