How does model switching affect KV Cache?
Yes. During normal consecutive tool calls in the same turn, HiRoute reuses the routing decision and prefers the current model within the selected group, preserving reuse of the growing prefix. A new user message triggers reassessment; a switch may lose the old cache on the first request, while later calls can reuse the new cache.
After compaction or a history rebuild, some cache entries already need rebuilding, so reassessment at that boundary may incur a smaller additional loss. HiRoute preserves continuous execution to reduce unnecessary cache overhead. Whole-task costs include rebuilding, routing decisions, and retries; the article below explains the effects and Astra × Qwen calculations.
Read the cache and cost analysis: Astra × Qwen 3.8 Flash →
What execution history can a decision model see?
HiRoute supplies simplified Agent-turn history: user input, accepted output, tool names, and coarse outcomes. HiRoute binds internal task categories, groups, and execution identities itself. Trimming, eviction, or restart may leave history incomplete; completeness of the assessed stage is tracked separately. Missing or partial assessments are not zero scores.