Kimi K3 State Loss After Compaction: A Deep Dive into API Payloads
Few_Sort8392 · reddit · 2026-07-30
Developers have found that Kimi K3 may hallucinate and re-plan completed tasks after triggering context compaction. Inspecting the API payload reveals that the model loses its internal state during the transition.
The root cause is that K3 expects the full assistant message back (including content, reasoningcontent, and toolcalls). If an upstream gateway like ZenMux drops the reasoning history, it leads to unstable outputs. Developers are advised against switching to K3 midway through an existing session.
More from coding & agent
- Managing Agent State with HTML Boards; Bun Allegedly Rewritten in Rust with Claude — Vjeux · 2026-07-31
- deepagents v0.7 Released: Major Boost in Configurability & Context Efficiency — hwchase17 · 2026-07-31
- GitHub Discussion: Building Agent Skills & New MCP Release — marlene_zw · 2026-07-31
- Devin Showcases New 'Engineer': 10 PRs Merged in First Week — DevinAI · 2026-07-31
- An Engineering Trick to Adapt ML Agents for the Real World — gandamu_ml · 2026-07-31
- Dev releases new MCP servers for Teams and Azure DevOps — jgbright-5000 · 2026-07-31