ACCT: Asymmetric Cross-LLM Context Transfer
ACCT transfers selected KV cache states between differently sized models in the same family, so a target can reuse context computation. The paper reports faster prefill conversion and similar or better task performance with a smaller cache.
ACCT converts a source model’s KV cache into sparse states a target model in the same family can use directly. Its Cartographer selects relevant tokens, Allocator distributes a shared KV budget, and Compiler produces the target states. The paper reports matching or better performance with **75% less KV cache**, and **6.5–21.2×** faster conversion than target prefill at about **19K tokens**.
For agent workflows that reuse long context across model sizes, this suggests a way to avoid repeating prefill when switching models. The approach depends on transferring cache state between models in the same family, rather than treating context as portable across arbitrary models.
ACCT converts a source model’s KV cache into sparse states a target model in the same family can use directly. Its Cartographer selects relevant tokens, Allocator distributes a shared KV budget, and Compiler produces the target states. The paper reports matching or better performance with **75% less KV cache**, and **6.5–21.2×** faster conversion than target prefill at about **19K tokens**. For agent workflows that reuse long context across model sizes, this suggests a way to avoid repeating prefill when switching models. The approach depends on transferring cache state between models in the same family, rather than treating context as portable across arbitrary models. The results cover **five general-capability benchmarks** and **six context-dependent tasks**. The material does not specify implementation availability or how the method performs in production systems.
ACCT adds a model-side option to reuse long context across sizes within one model family: it transfers KV state directly, with reported cache and conversion savings. This complements approaches that retain or retrieve context at the harness level, but its family constraint and benchmark scope leave broader production portability unestablished.