Replies: 1 comment
|
Yes. Current Headroom supports the The zero shown by v0.27.0 is not sufficient evidence that compression was disabled. Codex uses a long-lived Please upgrade to v0.29.0 or later, restart the proxy, and inspect {
"units_total": 12,
"units_modified": 9,
"tokens_saved": 4321
}If Evidence: PR #1680 documents that Codex WebSocket units were compressed while v0.27-era headline counters could remain frozen. The visibility fix shipped in v0.29.0. |

Yes. Current Headroom supports the
gpt-5.6-sol,gpt-5.6-terra, andgpt-5.6-lunamodel names on the Codex Responses/WebSocket path.The zero shown by v0.27.0 is not sufficient evidence that compression was disabled. Codex uses a long-lived
/v1/responsesWebSocket, and before v0.29.0 its live compression counters were not included in the main stats summary. Compression could therefore be occurring while the dashboard appeared unchanged.Please upgrade to v0.29.0 or later, restart the proxy, and inspect
summary.codex_wsin/stats:{ "units_total": 12, "units_modified": 9, "tokens_saved": 4321 }If
units_totaladvances buttokens_savedremains zero, the requests are reaching the Codex c…