Save and recall project memory.
Project memory is a record of useful facts and decisions that later agent sessions can retrieve from the site.
Save decisions, not every detail
Good memory explains a convention or constraint: which field stores a subtitle, why a template is shared, or which parts of a page must remain unchanged.
Ask the agent to save a concise fact after you have confirmed it. Avoid long transcripts, outdated assumptions, and information that is already easy to inspect directly.
Recall the record before new work
At the start of a later session, ask the agent to review relevant project memory and summarize the constraints for the task. Check that the summary still matches the project.
Saving memory does not guarantee that every model will interpret it correctly. Specific instructions and a short, current record are easier to use than a large collection of unreviewed notes.
Treat memory as maintained project information
Update a fact when the underlying decision changes. Remove obsolete entries instead of leaving contradictory instructions for a later session.
Do not store passwords, API secrets, payment information, or other credentials. Connected clients can receive recalled information, so save only what belongs in their working context.
A useful example
“Service pages use the shared service template. The subtitle comes from the service_subtitle field. Update the page content without changing that template.”
That note explains a relationship and a limit. It helps the next session make a more informed change without pretending to replace a review of the actual site.
Explore Avius Pro