FirstbeamKeep project context useful
Store durable decisions without filling every conversation with old notes.
Record decisions that outlive a task
Project memory is for stable facts, decisions and known pitfalls. Record why a choice was made, where the implementation lives and how it was checked. A short note with links is easier to maintain than copying an entire conversation.
Keep project and personal scope clear
Use project notes for shared implementation knowledge. Use reusable skills for instructions you want to apply repeatedly. A conversation attachment provides temporary context; it should not become a permanent rule unless the decision is deliberate.
Maintain, do not accumulate
Update an existing note when a decision changes. Mark obsolete behavior clearly and link to the replacement. Before a new task, read the project instructions and the relevant notes, rather than asking the agent to infer history from unrelated messages.
Save evidence with the decision
Include checks that passed and anything not measured. A smaller JavaScript bundle, for example, does not establish lower native RAM usage. Keeping this distinction in the note prevents future work from treating an assumption as a verified result.
An example durable note
A useful note can say: the Settings page saves preferences locally; the capability scope filter only changes the displayed inventory; the actual team editor is shared with Agent Mode. Link the files and verification record. That is actionable context for the next agent without preserving every intermediate thought from the old conversation.
Keep secrets outside project notes
Describe which provider or credential setting is used without storing the key itself. A shared note can identify an endpoint, model and error category, but should not contain access tokens or private transcripts. Revisit notes after a release so later work sees the shipped state rather than an outdated plan.