fix(llm): allow disabling prompt cache key - #2562
Open
lihailong00 wants to merge 1 commit into
Open
Conversation
This was referenced Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
prompt_cache_keyboolean setting tokimiprovider configurationprompt_cache_keyrequest field when the setting isfalseThird-party Kimi-compatible endpoints such as NVIDIA NIM can use:
Reproduction and verification
A local OpenAI-compatible HTTP endpoint reproduces the reported behavior: before the fix it returns HTTP 400 when the request contains
prompt_cache_key. With the new setting disabled, the real request JSON completely omits the field. A second HTTP regression verifies that the default managed Kimi path still sends the session ID.uv run pytest tests/core/test_config.py tests/core/test_create_llm.py -q— 53 passedgit diff --check— passedCloses #2534