# ACCT: Asymmetric Cross-LLM Context Transfer

Source: [arXiv](https://arxiv.org/abs/2610.42116v1)  
Feed7 permalink: https://feed7.dev/p/2610-42116v1-086agqc  
Published: 2026-10-30T17:50:49.000Z  
Trust: Needs Review (needs_review)

## Why Included

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.

## Source Summary

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**.

## Practical Implication

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.

## Agent-Ready Context

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.

## Connected Context

Feed7 judgment across 974 accumulated Signals:

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.

- [Context Engineering in 2026 — Louis-François Bouchard, Omar Solano & Samridhi Vaid, Towards AI](https://feed7.dev/p/context-engineering-in-2026-louis-francois-bouchard-omar-solano-samridhi-1dnlyr0) — The full-history result favors keeping cached context when it is cheap; ACCT could reduce the cache cost of that choice when switching model sizes within a family.
- [Better prompt caching for GPT-6](https://feed7.dev/p/better-prompt-caching-for-gpt-6-0mbpmnp) — Both target the cost of repeated context through cache reuse, but ACCT transfers KV state between same-family models while this candidate focuses on improving prompt-cache behavior.
- [ReToken: One Token to Improve Vision-Language Models for Visual Retrieval](https://feed7.dev/p/2607-28627v1-0pc8021) — Both operate on cached representations to avoid treating every context token equally; ReToken selects visual evidence for retrieval, while ACCT transfers sparse KV states across model sizes.
- [CliffCompaction: Cost-Efficient Compaction for Long-Horizon Coding Agents](https://feed7.dev/p/2609-26779v1-1nezvu9) — ACCT may reduce the need to compact context when moving between same-family model sizes; CliffCompaction instead bounds context by dropping or truncating source material.

## Context Map

- Layer: context
- Domains: research
- Topics: context-engineering, context-caching

## Uncertainty

- 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.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.