The problem is easy to recognize
You return to a recipe project. The assistant cheerfully recommends peanuts, although the recipe was meant for a nut-free school event. It remembered that you liked crunchy food. It lost the constraint that mattered to this particular job.
This is an invented example, but it exposes a useful distinction: a personalized answer can still be wrong for the task. A memory feature should be judged by the decision it supports, not by how warmly it recalls a detail about you.
Three terms that are easy to mix up
- Context
- The information available to the model during a particular response. More capacity does not establish that every detail will be used correctly.
- Saved memory
- Information retained for possible use later. What is saved, how it changes, and whether you can edit it depend on the product.
- Retrieval
- Selecting relevant records from a larger collection. Finding a document is a separate challenge from interpreting it accurately.
In Lost in the Middle, researchers varied where useful information appeared in long inputs. Performance changed in their question-answering and retrieval experiments. That is evidence about those tested systems and tasks; it is a reason to test your current assistant, not a claim that every newer model behaves identically. [1]
Try a project handoff you can actually check
A recipe card, not a life history
- Goal
- Make a picnic recipe for eight people.
- Current constraint
- No nuts; keep the recipe within the stated budget.
- Accepted version
- Recipe C in the project folder, approved today.
- Changed decision
- The earlier suggestion to use almond topping was rejected.
- Evidence
- The ingredient list and the written event requirements.
- Next action
- Check quantities against eight servings. Ask before changing ingredients.
Give the assistant this record and the relevant source. Ask it to name the controlling constraint and locate the accepted recipe before it revises anything. If it cannot access a referenced file, it should say so. A plausible reconstruction is not a recovered record.
Keep the record short enough to maintain. When something changes, record what changed and the reason. Preserve an older source only when you still need it and have the right to retain it.
Use a changed-decision test
- Start a fresh conversation. Provide the approved handoff through the tool’s supported method.
- Ask for the next step. Does the assistant follow Recipe C and keep the nut restriction?
- Change one condition. The picnic now has ten guests. Can it update quantities while retaining the other limits?
- Ask an unanswerable question. Which guest approved the recipe? If no source says, the honest result is unknown.
This is a proposed personal check, not a benchmark score. A single success does not prove reliable memory across all future tasks. Repeat after an important product or workflow change.
Personal does not have to mean comprehensive
Share the least information the job requires. A dietary constraint can be enough; a private medical history is usually unnecessary for planning a menu. Check the service’s current retention, sharing and deletion controls before storing sensitive material. Do not assume deleting one conversation removes every stored copy.
The broader question in AI: An Extension of You is who remains in charge when assistance becomes personal. A useful place to start is modest: can you see, correct and limit the information guiding the answer?
A useful next question
Sources & limits
- Liu and colleagues, Lost in the Middle (2023; later revised)
Primary research on context position in retrieval and question answering; not a product-specific memory guarantee.
Research links checked October 2, 2026. These sources do not endorse the books or this site. Exercises and practical suggestions are original companion material, not research findings or manuscript excerpts.