KVMem (arXiv 2609.04852, Mon 7 Sep digest) is a KV-context virtualization system for long-running agents: instead of compacting overflowed workspace history into summaries or re-retrieving it as text (losing fine-grained execution evidence and re-prefilling already-processed content), it preserves overflowed history as paged KV state across GPU memory, host memory and NVMe. Lightweight model-native attention-space indexes select relevant historical blocks, and a query-dependent execution view bounded by the model's native context window is materialized on demand. On long-context agent benchmarks spanning histories up to one million tokens — LongMemEval, MemoryAgentBench, AgentLongBench — KVMem generally achieves higher task utility and greater inference efficiency than compaction-based approaches, the de-facto standard for context overflow (paper reports a DeepSWE long-context test with Qwen3.8-27B).
KVMem virtualizes million-token agent workspaces on a consumer GPU
KVMem (arXiv 2609.04852, Mon 7 Sep digest) is a KV-context virtualization system for long-running agents: instead of compacting overflowed workspace history into summaries or re-retrieving it as text (losing fine-grained execution evidence and re-prefilling already-processed content), it preserves overflowed history as paged KV state across GPU memory, host memory and NVMe. Lightweight model-native attention-space indexes select relevant historical blocks, and a query-dependent execution view bounded by the model's native context window is materialized on demand. On long-context agent benchmarks spanning histories up to one million tokens — LongMemEval, MemoryAgentBench, AgentLongBench — KVMem generally achieves higher task utility and greater inference efficiency than compaction-based approaches, the de-facto standard for context overflow (paper reports a DeepSWE long-context test with Qwen3.8-27B).
Imported from the existing research archive. Migration preserves the recorded judgment and is not a fresh verification.
What this means for you
This attacks the biggest practical gap in long-running agents: compaction is lossy and re-retrieval is expensive, while the KV the model already computed is thrown away. Paging KV to host/NVMe with attention-space indexing is the memory-hierarchy move the agent-memory space has been missing, and it runs on a single consumer GPU. Teams building persistent workspaces (cloud agents, long coding sessions) get a design template that keeps full-fidelity history without paying unbounded context costs.
Public artifacts and validated results are different.
The recorded fact is the public work and its artifacts. Author-reported outcomes do not establish independent reproduction. Next checks include usable code, task conditions and third-party validation.
Evidence & related material
Technical details & scores
| Approach | paged KV state for overflowed workspace history across GPU memory / host memory / NVMe; model-native attention-space indexes select relevant blocks; query-dependent execution view bounded by native context window |
|---|---|
| Benchmarks | LongMemEval, MemoryAgentBench, AgentLongBench; histories up to 1M tokens; also DeepSWE long-context test with Qwen3.8-27B |
| Comparison | generally higher task utility and greater inference efficiency vs compaction-based approaches (the de-facto standard) |