Memory in Code
Understand task history, runtime context, local preferences, and linked Chat memory.
Four kinds of context
Code does not automatically put every task into Chat memory. The information available to a run depends on the current task, installed runtime, local settings, and any explicitly linked Chat project.
| Context | What it contains | How it is used |
|---|---|---|
| Task history | The local task transcript and run state | Reopen the task to inspect previous work and continue |
| Runtime context | The selected provider's conversation or session | Resumed when supported; switching providers does not transfer a complete native session |
| Project instructions | Repository guidance and the context selected for the task | Read by the runtime under the project's permissions |
| Linked Chat memory | Relevant account facts and conversation excerpts from an explicitly selected Chat project | Requested through supported recall tools while signed in; availability depends on the installed version and account service |
View diagram text
flowchart TD accTitle: Context available to a Code task accDescr: Local task history and project instructions feed the runtime. Optional Chat recall requires a selected project and a signed-in account. A[Local task history] --> D[Code task and selected runtime] B[Project instructions and selected files] --> D C[Explicitly linked Chat project] --> E[Optional read-only recall] E --> D D --> F[Local transcript and work results]
Continue work across runs
Continue in the existing task when earlier work matters. Name the files, decisions, and unfinished checks needed for the next step. If the provider session must be replaced, the retained transcript and any handoff context help recovery, but a reconstructed session may have less context than the original.
A resumed provider session, a visible task transcript, and a saved memory are different things. A fact mentioned in a Code conversation is not automatically a durable account memory. For repeatable repository guidance, use the project's instruction files and explicitly selected context.
Local personalization
Desktop Settings → Personalization has local profile and memory controls. The memory list is disabled by default and supports up to 20 active entries, with Add, edit, Disable, Enable, and Delete controls. Its Use memory in Chats switch applies to qualifying local general conversations. It does not enable automatic recall for every repository task or turn on account-backed Chat History Memory.
These local preferences stay on that installation. The separate Memory settings manage account and project facts for Chat. Provider-native memory features follow that provider's own configuration.
Link Chat context deliberately
Where linked recall is available, ask Code to show the available Chat projects and link the selected one to the current local project. For example: “Link this Code project to my Transit analysis Chat project, then look up the agreed reporting format.” A task without a local project can have its own link. The link is tied to the signed-in account and can be removed explicitly.
Recall reads relevant facts or source conversation excerpts; it does not upload the Code transcript or synchronize the repository. Delegated agents are restricted to the parent's linked project and cannot change the link or expand it themselves. Their own memory access setting can restrict recall further.
If the installed version or account service does not expose linked recall, provide the relevant context in the task. An unavailable service is not evidence that a memory does not exist. Mobile Remote uses the paired desktop's context; web Chat has no local Code runtime.