Skip to content
Code Dev Home

Continuity / Code Dev Home

Make it easy to come back.

A good session note helps you resume a task without repeating the entire investigation. Write down the decisions that changed the work, the evidence supporting them, and the next unresolved action. Keep a copy in a location appropriate for your project.

Record decisions with their reasons

"Use the existing parser" is less helpful than explaining which behavior it already handles and where it lives. Include the files inspected, the checks performed, and the assumptions that remain. Keep the note short enough to read before opening a new session; a raw conversation transcript usually hides the useful decisions.

Refresh the note when you return

Check whether the repository state has changed since the note was written. A teammate may have changed the same area, or your local edits may have moved forward. Ask the assistant to verify the relevant references before continuing. Do not assume that a new session retains old context or that remembered details are still accurate.

A session closing note

Adapt to your project
Task: The behavior we are changing.
State: Current branch and relevant local edits.
Decisions: What we chose and why.
Evidence: Files inspected and checks performed.
Unresolved: Questions or failed checks.
Next action: One concrete step on return.
Should a session note contain credentials?

No. Refer to the documented credential location or setup procedure. A note should explain how to resume work without carrying secrets into prompts or tracked files.