On November 17, OpenAI released a breaking change that stopped caching the instructions field on GPT-6.2, which is where LiteLLM puts your system prompt when it forwards /v1/chat/completions and /v1/messages requests to OpenAI. Requests still worked, but GPT-6.2 users paid full price for their system prompt on every call. We are proactively shipping a fix and backporting it to 5 release lines.
Action items
- Upgrade to the version for your release line, or any later version. No config changes are needed.
| Release line | Upgrade to |
|---|---|
| 1.108 LTS | v1.108.13 or later |
| 1.111 RC | v1.111.0rc3 or later |
| 1.110 stable | v1.110.2 or later |
| 1.109 stable | v1.109.3 or later |
| 1.106 stable | v1.106.12 or later |
Am I affected?
You were affected if you sent GPT-6.2 traffic through LiteLLM in one of these ways.
/v1/chat/completionsto a GPT-6.2 deployment that uses the Responses API, such as theopenai/responses/prefix,chatgpt/or Bedrock Mantle GPT-6.2/v1/messagesto GPT-6.2, for example from Claude Code or another Anthropic-format client
Root cause
The Responses API accepts a system prompt in two places, the top-level instructions field or a message at the start of input. Up to GPT-6.1 both were cached the same way, so LiteLLM used instructions.
On November 17, OpenAI updated its docs to say that starting with GPT-6.2, instructions are billed at the uncached rate on every request, even when they are identical, and that reusable prompts should go in a developer message at the start of input instead. Nothing failed on our side, so none of our error alerts fired, and a customer reported the missing cache hits on November 18.
Our fixes
- LiteLLM now sends the system prompt as a
developermessage at the start ofinputon GPT-6.2, where OpenAI caches it. See PR #52599, backported to every release line in the table above. - Our bot that watches provider changelogs now flags changes to what gets cached, so we catch the next change like this before you do.


