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
- Connected steps are not a workflow: nobody designs the handoff — usehive · 2026-10-16
- Making Blender animations with Opus, Astra and Argon: how you prompt still matters — chongdashu · 2026-10-16
- Running PolyStrata + Cline coding agent on a $0-fancy laptop at ~90 tok/s — rpwoerk · 2026-10-16
- How do you attribute agent gains: model training or infrastructure? — jrxna · 2026-10-16
- Feed Claude your books, blogs and top engineers' code for claude.md — 'it now writes better code than me' — blaizedsouza · 2026-10-16
- Open-source /label plugin auto-names and colors Claude Code sessions in one step — hermanschutte · 2026-10-16