Finding / heypi

2026-10-13-heypi-relevant-shared-memory-is-eligible-for-recall-across-conversations-by-default

Relevant shared memory is eligible for recall across conversations by default. This corrects the older memory-off claim. Memory is enabled by default. Relevant shared records are eligible for recall across conversations with the same adapter ID; they are not all injected into every turn. Recall considers user records before conversation and shared records, selects for relevance, limits records/characters and escapes text before labelling it untrusted reference context. Separate adapter IDs retain a storage boundary. These measures do not establish immunity to prompt injection.

Channel: preview-or-beta heypi 0.3.0-beta.2; legacy 0.1.3 still documents memory off. Half: both. Date: 2026-07-21 (historical beta.0 default); re-verified for the 2026-10-13 profile.

Operator consequence: Use memory: false when this cross-conversation recall surface is unwanted; separate adapters when their state must stay apart. Include memory files in retention and review. The name-based approval configuration can target the memory tool as a source inference, but no integration test of that policy was run. Do not describe bounded relevant recall as universal injection or as only a prompt label.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-heypi-relevant-shared-memory-is-eligible-for-recall-across-conversations-by-default

Profile citations

  • heypi / claim / memory-on-with-relevant-shared-recall
  • heypi / posture / capability
  • heypi / posture / governance

Source links

Primary links, including exact changelog lines when available.