1.9 Memory and the Workspace: Two Kinds of Continuity
That completes the four resource types. They decide what the agent can do. Two mechanisms decide what it remembers — one holds you, the other holds the piece of work.
What Memory Holds
Memory stores your user profile: your role, preferences, working habits, and any instruction you have given it to follow long term.
It is not a chat log. A chat log is a running record; Memory is a distilled, structured profile — the pattern, not the transcript.
The dividing line
A specific requirement for one task belongs in the prompt; a preference that keeps recurring belongs in Memory. One is temporary, the other long-lived.
Maintaining It
For updating the profile, checking the result, and comparing versions, see Memory and User Profile.
One sentence
Open 【Memory】 → 【Current Profile】 and enter an update at the bottom of the page:
The reverse works the same way:
Check the Current Profile
Read the updated content in 【Current Profile】. To correct outdated information or remove an item, enter a specific request at the bottom, submit it, and check the result.
Review Version Differences
Open 【Update History】 and select a version to compare the content before and after the update. To change a preference back, state the desired content at the bottom of 【Current Profile】, submit it, and check the profile again.
The Workspace: Remembering the Work
For creating a workspace, starting a task, and following up in the same conversation, see New Tasks and Conversations.
Beyond Memory there is a second layer of continuity: the workspace.
A workspace is a long-lived space for one business topic, holding its conversations, files, and outputs in one place. Select the workspace when you start a task, and later sessions can refer back to earlier conclusions and files.
| Comparison | Memory | Workspace |
|---|---|---|
| What it holds | Your preferences, habits, role | The files, conversations, and conclusions of this work |
| Scope | Across sessions and workspaces | Inside the workspace only |
| Question it answers | "Do it this way from now on" | "Where is the version we settled on" |
In one line: Memory remembers who you are; the workspace remembers what you are working on.
When Not to Create a Workspace
Without a selected workspace, the session is saved as a standalone conversation and does not appear as a workspace.
A one-off task does not need a workspace — creating one just leaves an empty shell. One test: will the next conversation need to refer back to this one's files and conclusions? If yes, create the workspace; if not, stay with a standalone conversation.
Summary
Memory remembers who you are; the workspace remembers what you are working on. Neither adds capability, but together they decide how much you repeat.
The next lesson closes Chapter 1 by matching task types to resources, inputs, and deliverables.
1.8.2 Base: Data the Agent Can Query and Write Back
Some content is not a document but data — queried repeatedly, written back to, calculated on. That belongs in Base.
1.10 Choose Resources and Deliverables for Your Task
Match resources to the task, then specify the source material, output format, and destination.