v6.11.2

Fixed

warm was broken for every user on 6.11.0 and 6.11.1.

The warm ping sent its request body with no content-type header. fetch defaults a string body to text/plain;charset=UTF-8, and the backend refused it:

Warm request failed: HTTP 400: {"detail":"Unsupported content type"}

Only warm was affected. Normal chat traffic goes through the proxy path, which wraps OpenCode's own request object and already carries a JSON content type — warmAccountWindow is the single place that builds headers from scratch and sends a body.

Verified live: same body, same account, only the header differing.

content-type	Result
text/plain;charset=UTF-8	400 {"detail":"Unsupported content type"}
application/json	200 OK

It reproduced on a Pro account fully entitled to gpt-5.5, which rules out plan and entitlement as factors. The 6.11.1 fix targeted the retired gpt-5.4 entry point — a real improvement, but not the cause; the old code discarded the upstream error body, so the failure only ever surfaced as a bare HTTP 400.

A warm 400 that is not an entitlement error is now also reported as itself rather than as a model problem.

Thanks to @Grelo4ka for reporting and for pushing back after the first attempt.

npm install -g oc-codex-multi-auth@6.11.2
rm -rf ~/.cache/opencode/packages/oc-codex-multi-auth*

Full Changelog: v6.11.1...v6.11.2