Use memory and recap to continue work

Keep context for the right purpose#

Use Memory for durable facts, Recap for a session summary, and Daily Briefing for recent activity.

Inspect existing context#

Choose @Memory and confirm project or global scope. In Settings → Personalization, inspect memory controls and open memory management to review saved items.

Do not save credentials or temporary tokens. Repeated procedures belong in a Skill. Memory does not guarantee every historical detail appears on every turn.

Save a fact and recap a task#

1. Verify a useful convention in a demo project.
2. Send the request below and inspect its saved content and scope.
3. After a small task, use @Recap or /recap.

Remember for this project: use synthetic accounts for invitation tests.
Save this as project context, not a global rule for all projects.
Show the saved content and its scope.

Ask the recap to include results, evidence, checks performed, unresolved questions, and the next action.

Check what the next task will use#

Success means the fact has the right scope and the recap separates completed from unverified work. Correct or archive stale memories rather than merely adding a contradictory item.

Open Daily Briefing from the sidebar and check included projects and generation settings. Follow an item back to its session, then recheck current files and services.

Troubleshoot missing or stale context#

• Missing or incorrectly scoped memory: check saved state, scope, and memory controls.
• Incomplete recap: identify the relevant message or file and request a correction.
• Missing briefing project: check included projects and generation period.
• Summary contradicts files: recheck the evidence; do not overwrite files to match an old summary.

Continue the work#

Take the recap back to projects and sessions. See Skills for reusable procedures and settings and data for information boundaries.