Remember the correction too
Personal context needs dates, scope and a way to fix it.
Retrospective field note for 2026-02-02, reconstructed on 16 November 2026. The archive date is not a claim of publication at the time.
“Keep this brief” can mean this answer. It does not necessarily mean every conversation for the rest of the year.
Memory gets irritating when it turns a passing instruction into a permanent personality trait. The assistant remembers the words and loses the situation around them. Then the user has to spend time correcting a preference they never intended to create.
Keep the source and scope attached. A project deadline expires. A draft gets replaced. A decision can be reversed. When the remembered detail affects the answer, make the assumption easy to spot and correct without sending someone into a settings maze.
The audience matters too. Something shared while planning privately does not automatically belong in a public article. Being able to retrieve a detail is separate from having permission to publish it.
Personalisation should reduce repeated explanation. If it produces unwanted callbacks, stale assumptions or little demonstrations of how much the system knows, it has added another thing to manage. Remember the correction as carefully as the original detail.
Google published its January Gemini Drop on 30 January. Source.