Which tool to choose
If you use a project space with files, you update the file and all the chats take it into account; some assistants, like Gemini connected to documents on Drive, see the change as soon as you save it. If you work without projects, your point of reference is a context document that you update by hand. In both cases the principle is the same: you change only the piece that has changed, you don't rewrite everything.
How it's done
- Keep a project context document or file, which serves as the up-to-date version of the situation.
- When something changes, edit only that point in the document, leaving the rest intact.
- To the AI communicate only the difference. The operational wording:
Update to the project context: this has changed → [describe what has changed]. Everything else remains valid as before. Realign and tell me what changes in the next steps.
- If the project files are connected (like a document on Drive), often just saving the change is enough for the AI to see it.
A concrete example
Marta was organizing a course with the AI's help, and halfway through the work the date slipped by two weeks. Instead of re-pasting the whole plan, she wrote only: "the date has changed, it's now the 20th instead of the 6th; everything else stays the same, realign the deadlines." The AI recalculated the preparation schedule without her touching the rest. She then corrected the date in her context document, so future conversations too would start from the right figure. Thirty seconds instead of re-explaining the entire course.
When it does NOT work (and how to fix it)
If the AI applies the change but forgets the rest
In a long chat, the old context may already have dropped out of the window, so the delta hooks onto nothing. The fix is to realign it on the updated document: paste the current version of the context, not just the change, so it starts again from a complete and coherent picture.
If the changes are too many
Many deltas one after another end up confusing more than updating. When the changes pile up, it's best to stop and make a clean summary of the updated context, instead of continuing to add corrections on top of corrections.
If you use a static file loaded into the project
A document loaded once doesn't update on its own: telling it out loud that it has changed isn't enough. You have to reload the updated version of the file, otherwise the AI keeps reading the old one.
A tip from someone who actually uses it
Keep the context document as the single always-up-to-date source, and communicate changes as a difference: what it was before, what it is now. This way of working spares you from rewriting everything at every change and, above all, reduces inconsistencies: when you re-explain an entire context from scratch, it's easy to forget a piece or contradict something you'd said before. The delta, anchored to an updated document, is safer as well as faster.
Frequently asked questions
Do I have to reload the files every time something changes?
It depends on the type: connected and synced files update when you edit them, while statically loaded ones must be reloaded in the new version. Knowing which of the two you use tells you whether just saving the change is enough or whether you have to reimport the document.
How many updates can it handle before getting confused?
A few targeted deltas it handles well; many, piled one on another, start to create confusion. The practical rule is: a few pointed updates are fine, but when there are many it's best to consolidate everything into a clean summary and start over from there.
How do I make it understand what has changed compared to before?
With a "difference" message: you state what has changed and specify that the rest remains valid. It's much more effective than re-pasting the whole context, because the AI knows exactly where to act instead of having to rebuild everything and guess what's new.
To update the AI, do I necessarily have to re-explain everything from scratch?
No, and it's precisely the waste to avoid. Rewriting the entire context at every change costs time and introduces risks: in redoing everything it's easy to skip a detail or contradict yourself. The delta — only what has changed, on a base that stays valid — is faster and safer. Re-explaining from scratch is needed only when the changes are so many that a new summary is best, not as a habit at every small edit.