dev-remember

Persist engineering decisions across sessions by writing structured notes that capture why a decision matters, its context, and a file or link reference. This ensures context survives beyond the current conversation for future engineering work.

Save agent memory by storing structured notes in the correct agent memory folder when a specific engineering agent owns the context. This preserves decisions and confirmed patterns for long-running development work without losing them on restart.

Store engineering notes in a workspace research remember file when no single agent owns the context. This shared workspace memory approach ensures confirmed patterns and gotchas remain accessible across the entire project.

Workspace memory and engineering notes should follow a structured format containing a title, why it matters, context, and a reference. This consistent structure keeps decision logs searchable and actionable for future sessions.

Context persistence does not require full long-term memory for every note. You can save quick decision notes that future sessions will need, reducing repeated mistakes without turning every gotcha into a permanent memory record.