Memory and project context

Use the right place for knowledge

Session history records the conversation. Project instructions record conventions you want the agent to follow. Memory helps retain useful project context across work. These serve different purposes and can all become outdated.

Use checked-in project documentation for facts that your team needs to review and maintain. Do not rely on memory alone for a requirement that must be followed exactly.

Inspect project context

The Graph entry in the sidebar opens the project knowledge view available in the desktop app. Use it to explore the context associated with your work. Ask the agent to identify the files or decisions behind an important statement rather than treating remembered information as authoritative.

Correct an outdated assumption

State the correction clearly and ask the agent to reread the current source:

The API endpoint changed in the latest version.
Read the current configuration and update the plan to match it.
Explain which earlier assumption was incorrect.

For durable guidance, update the relevant project document as well. Summarize important decisions at the end of a session so that you can intentionally carry them into the next task.

Know the boundaries

Avoid storing credentials or personal records as memory. A local memory feature does not mean every model or connected tool runs locally. Check your provider and plugin choices before supplying sensitive project context.

Cross-device continuity and a supported phone workflow are still upcoming. Do not use memory as a backup or assume that opening another device restores all of your local work.