Give the agent a continuing project notebook
Set up a continuing notebook that helps the person and their existing coding agent recover what matters about a project. Build it extremely well. They should be able to return after a break and continue with the understanding they developed together. Follow the shared launch.
Choose a project already underway. Start by finding its existing guidance, decisions, notes, and saved work. Improve that organization where needed, keeping each important fact with the source that should own it.
Preserve what would otherwise need explaining again
Recover the project's purpose, the people it serves, consequential choices, useful observations, and questions still open. Preserve why a decision was made when that reasoning will help later work.
For example, a booking app may keep full lesson material so the tutor can use its exercises and teaching notes during a session. That reason helps a future agent understand the design. The current date of an appointment belongs in the application record, where the notebook can direct the agent to find it.
Use readable Markdown and ordinary supporting files that the person can inspect and keep. Retain authorship and relevant dates so an observation, a proposal, and an agreed decision remain distinguishable. Preserve original notes and valuable historical reasoning when the team's understanding changes.
Make the useful context easy to recover
Provide a concise entry into the notebook with references to the sources needed for the project. Keep current orientation easy to find and older investigations available when their questions become relevant again.
Connect the notebook to the agent's normal project guidance or supported memory mechanism. Preserve useful existing instructions. A subsequent session should know where to look and be able to retrieve deeper context according to the work at hand.
Let the agent add understanding after consequential discoveries: a constraint learned from actual use, an assumption overturned, or a choice that changes the project's direction. Match the note to what a future session would benefit from knowing.
Keep the current explanation aligned with its owning sources. When a decision changes, make the new position apparent and preserve enough of the earlier reasoning to understand the change. Link to actual application state and source files where they already answer the question.
Include thinking that happens away from the desk
Connect agent-readable phone notes when the person uses them. A photograph of an awkward workflow, a dictated idea, or an observation made during a visit can become material for the next conversation.
Keep captured observations distinguishable from commissioned work. Let the person discuss an idea, decide what it means for the project, and preserve the resulting understanding in the appropriate place.
Make corrections comfortable from either side of the collaboration. The person can say that a note misrepresents their intent, and the agent can revise it while preserving the useful surrounding context. Keep the collection recoverable through the shared launch's ownership guidance.
Resume a real piece of work
Deliver the notebook, discovery guidance, and any chosen connection to existing notes. End one session with a meaningful decision preserved, then use a later session to recover the project and continue an actual task.
Judge whether the agent can explain the relevant purpose, find current facts, and recognize what remains unresolved. Correct a gap revealed by that use. The notebook should save explanation while leaving room for the person to change their mind.
Teach the difference between keeping records and retaining useful understanding. Good continuity helps the next conversation start from what has already been learned, with the original work still available to inspect.