Agent memory has a basic identity problem
memory often focuses on how well the system can find stored information. A more basic problem comes first: knowing when different records belong to the same person. One person may appear as an anonymous browser ID, a logged-in user ID, and a ID.
If the treats those as separate people, context saved in one session will not carry over to the next session or another device. Builders need to decide whether memory should be keyed to the logged-in user ID, a hash, or handled by the main app before matters.
Key points
- needs a reliable way to know which records belong to the same person.
- Anonymous browser IDs, logged-in user IDs, and IDs can split one person into multiple identities.
- Bad identity handling can stop context from carrying across or devices.
- Builders must choose whether to key memory on a user ID, a hash, or the main app’s identity system.