Reflect fails on Bedrock Kimi K3: model rejects the temperature field
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start with hindsight_api/engine/reflect/agent.py to trace where the reflect temperature is set, then read engine/providers/litellm_llm.py to see how the provider passes it through. Compare with how reasoning models that reject temperature are handled. Done when reflect works with the Bedrock Kimi K3 model while temperature is unset or dropped.
Written by the indexing model from the issue text.
Description
What happens: every reflect on bedrock/us.moonshotai.kimi-k3 fails on main with:
BedrockException - {"message":"This model doesn't support the temperature field. Remove temperature and try again."}
How to see it: run run_reflect_agent with LLMProvider(provider="bedrock", model="bedrock/us.moonshotai.kimi-k3") (found during the smoke run for #6671; 2/2 runs failed on main, before that PR).
Expected: reflect works, with temperature left unset for this model, the way reasoning models that refuse a temperature already are.
Where: reflect sends temperature=get_config().llm_temperature_reflect (hindsight_api/engine/reflect/agent.py), and the LiteLLM provider passes it through (engine/providers/litellm_llm.py). The model probably needs to be known as one that refuses temperature, or LiteLLM's drop_params used for it.
- Dominant language
- Python
- Stars
- 45.2k
- Forks
- 5.9k
- Avg merge
- 5h 45m
- Merged PRs (30d)
- 355
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vectorize-io/hindsight
-
Hermes plugin: switch to stop mirroring built-in memory writes into the bank (mirror_builtin_memory)Openintegration:hermes
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vectorize-io/hindsight#6725 ·
Maintainers usually reply within 1 day
-
bug core
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vectorize-io/hindsight#6719 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vectorize-io/hindsight#6690 ·
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vectorize-io/hindsight#6662 ·
Maintainers usually reply within 1 day
-
integration:hermes
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vectorize-io/hindsight#6658 · 1 comment ·
Maintainers usually reply within 1 day
All issues in vectorize-io/hindsight
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
abetlen/llama-cpp-python#2424 ·
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
jqueryscript/awesome-claude-code#1009 ·
-
tests
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day