Context & memory
Understand what agents use during a run and how saved knowledge carries decisions into later work.
Context is what an agent uses for the work in front of it. Memory is knowledge saved for future work. Keeping that distinction clear helps you decide where to put instructions, requirements and lessons.
What an agent uses
Section titled “What an agent uses”| Source | What it provides |
|---|---|
| Project context | The brief, repository instructions, stack, requirements and implementation plans |
| Chat history | Messages and observations from the current chat or cycle |
| Saved memory | Relevant conventions, decisions, preferences and lessons from your Workspace |
| Skills | Reusable instructions for particular tasks |
The cycle’s checklist carries the tasks and acceptance checks for its build agent.
Your standards reach agents through the project’s instructions, saved memories and activated skills. Put rules that belong with the code in the repository; save reusable decisions as memories.
What the project tabs show
Section titled “What the project tabs show”| Surface | What you can inspect |
|---|---|
| Context | Saved requirements, instructions and plans. Agency members also see learned knowledge and extraction status. |
| Memory availability | Which chat and run sources have recorded messages or observations, and which are unavailable |
| Task → Agent Runs | Individual run inputs, outputs and outcomes, with linked review evidence |
Inspect the chat history for the current discussion, Context for saved requirements and plans, and Memory for reusable knowledge.
How memory is reused
Section titled “How memory is reused”Agents retrieve memories relevant to the current task within your Workspace and the requested scope. Approved entries represent settled knowledge; tentative entries remain marked as unreviewed, and archived entries are excluded.
Agency members can curate this knowledge. Client project access does not grant access to private run history or learned agency knowledge.
Keep knowledge useful
Section titled “Keep knowledge useful”Review extracted candidates, approve useful decisions and archive outdated entries. If a memory is missing or not being used, check its scope, relevance and status. The Memories guide covers editing, search, extraction and troubleshooting, with API examples.