Core concepts
Project memory
Save confirmed project conventions and constraints for future conversations.
Project memory keeps useful facts available across conversations in the same project. Use it for a stable build constraint, a confirmed hardware issue, or a decision future work should respect.
Keep temporary observations and unfinished task notes in the current conversation or a hardware case.
State the reason and relevant files so the fact remains useful later. Saving and updating memory follow your approval settings. Review the proposed change when prompted; Skip all approvals or an existing Allow always grant can let it proceed without another prompt.
Memory can describe a pattern, preference, decision, or issue. You do not need to format the entry yourself.
Ask Embedder to update an existing entry when a fact changes rather than keeping contradictory versions.
The project supports up to 50 entries, including five pins. Keep pins for constraints that matter across tasks. Unpinned entries remain searchable.
Use Act mode for deletion. Removing an entry follows the same approval settings as saving it. Ask Embedder to list the remaining entries to check the result. Clearing a conversation does not remove project memory.
Use EMBEDDER.md for the project’s shared instructions and exact commands; use memory for confirmed knowledge you want Embedder to recall.
Last modified on September 12, 2026