Use records effectively
Help the team carry yesterday's work forward.
The team continues from records, so what you preserve determines what it can recall. An agent's working context may fade as a conversation grows. Recorded decisions and rules can be read again after a fresh start. For the concepts, see Shared memory.
What to record
| Record | Example |
|---|---|
| Decisions | Store the data in one file. |
| Rules | Do not delete existing files. |
| Completed and remaining work | List screen complete; entry screen still needed. |
| Lessons from failures | We rejected this approach because it was too slow. |
Do not put passwords, tokens, or API keys in records. Agents read these materials. Keep credentials separately and securely.
Make it a habit
- At the end of work Say, 'Record today's decisions and remaining work.'
- When changing direction Ask the team to record the change and the reason.
- Before a fresh start First ask, 'Read the records and summarize where we are.'
assets/support/guides-records.png · Recommended size: 1600×900
Using record lists and search to find recent work
Check the record room
People can view and edit records, too. See the basis for the team's work to reduce unsupported judgments. Find instructions in the Record room guide.
Reset and records
Reset clears an agent's working context, not the saved records. Record what matters, then have the agent read it after a reset to continue. Agent roomexplains the difference between Reset and Stop.
Checklist
- I recorded decisions and remaining work after each task.
- I kept passwords and tokens out of records.
- I asked the team to read records before restarting.
Next Work safelyis a good next read.