Look for the decision a detail changes.
A food-ordering agent may know that someone avoids dairy. That matters when choosing a meal. Their favourite film probably does not. The difference is the decision the context helps the product make.
Before adding a remembered detail to an experience, ask where it belongs. Would it change a recommendation, remove a repeated question, or stop an unsuitable suggestion?
Use context without reciting it.
People rarely want a list of everything a product knows about them. A useful recommendation can demonstrate understanding quietly: a dairy-free lunch, available nearby, with a clear explanation when needed.
Make the connection visible when it helps someone judge the answer. Leave it in the background when repeating it would add noise.
Make correction part of the design.
Preferences change. A constraint might be temporary. A personal agent needs room for someone to say that an old detail no longer applies.
Design the next interaction around what matters now. Continuity should reduce the effort of using a product, not trap a person in an old version of themselves.
Thoughts on building personal agents into the products people already use.
More about why we’re building shardr