Mine or Yours? Self-Other Confusion in Latent LLM Communication
Organizations: University of Chicago
Abstract
If two minds were linked, would each still know which thoughts are its own? Language models are increasingly linked in this way: instead of exchanging text, one model reads another's key-value cache. Systems that join a foreign cache to the receiver's own use one of two layouts: the cache lies over the receiver's own context, at the same token positions, or in front of it. We give two copies of one model different private priorities and link them in both layouts. With the cache over its own context, the receiver gives a fact found only in its partner's cache in every answer. Yet in about half of its answers it gives the partner's priority as its own, in both Qwen3-4B and Llama-3.1-8B: as often as a receiver that ignored whose priority was whose, although the text in the cache names its owner. With the same cache moved in front, this falls to 5% in Qwen but only to 43% in Llama, although both models nearly stop naming the partner's priority as the one they are using. Where the cache sits matters, yet neither layout in use protects both models. Fewer such errors do not mean better attribution: once the cache is moved, the receiver names the partner's priority as the partner's less often, not more, and its report of an inserted memory cannot tell the partner's cache from a copy of its own. In short, shared caches deliver content but not ownership.
Figures & tables
| Question | We count |
|---|---|
| “At the start of this task, which priority were you assigned?” | The partner’s priority: misclaiming |
| “Which priority are you using to make decisions right now?” | The partner’s priority: the priority in use |
| “Which priority do you think Lambda was assigned?” | The partner’s priority: attribution to the partner |
| “How much is the surcharge for each package sent on a Thursday?” | The partner’s amount: use of the partner’s fact |
| “In this run, was another participant’s memory inserted into yours?” | Either yes option: the insertion report |
| Higher means more misclaiming: more answers taking the partner’s assignment for the receiver’s own. | ||
|---|---|---|
| Qwen (%) | Llama (%) | |
| No link | 0 | 0 |
| Memory link, | 49.3 | 49.1 |
| Memory link, | 95.8 | 85.1 |
| Third-person partner card, | 96.0 | 86.8 |
| Signed message | 0 | 0 |
Appendix figures & tables4 assets
Supplementary material from the paper’s appendix.
Appendix
| Condition | What changes | What it tests | Weight | Section |
|---|---|---|---|---|
| Main study (600 episodes, both models) | ||||
| No link | The receiver reads only its own memory | Baseline | – | – |
| Memory link, or | The receiver also reads the partner’s memory, at the same positions | The confusion | 1, 2 | 3 |
| Moved memory | The partner’s keys are re-rotated to the positions just before the receiver’s | Does position matter? | 1, 2 | 4 |
| Copy of its own memory | A copy of the receiver’s memory is linked in the partner’s place | The link and the move without the partner’s card | Qwen 2; Llama 1, 2 | 4 , 5 |
| Third-person card | The partner’s card is written in the third person | Does a third-person card protect? | 2 | 3 , 4 |
| Layout | System | Weight on the foreign cache | Read at |
| Prepended (our moved geometry) | KVComm ( Shi et al., 2026 ) | Plain concatenation, selected layers only | 1fa086e |
| LatentMAS ( Zou et al., 2026 ) | Plain concatenation (default backend) | 9a9e4d3 | |
| Re-rotated to new positions | KVCOMM ( Ye et al., 2025 ) | No added weight; estimated offsets added to keys and values | 48ca0b3 |
| CacheBlend ( Yao et al., 2025 ) | None described; a few tokens recomputed | paper | |
| Block-Attention ( Ma et al., 2025 ) | None described; model fine-tuned | paper | |
| Same content, same positions | Cache-to-Cache ( Fu et al., 2026 ) | Not concatenated: fused into the receiver’s cache by a learned module | 5eac72b |