Memory and knowledge

Neo can use durable memory for stable preferences, decisions, ongoing projects, and other context that improves future assistance. Structured knowledge can preserve organized notes, source summaries, entities, and analyses.

Availability and controls vary by product surface.

What belongs in memory

Good candidates are facts that are stable, useful across future conversations, and safe to retain:

• your preferred name, tone, and output formats;
• durable project decisions and definitions;
• recurring workflow preferences;
• important relationships between concepts or entities;
• conclusions worth revisiting.

What does not belong

Do not store passwords, API keys, authentication codes, private financial credentials, recovery phrases, or other secrets. Avoid retaining short-lived details that will become misleading, or sensitive information that is not necessary for future work.

Ask explicitly

Use clear requests:

• “Remember that executive updates should be under 200 words.”
• “What do you remember about this project?”
• “Correct the project launch date to 14 October.”
• “Forget my previous formatting preference.”
• “Do not retain the information in this conversation.”

Neo should distinguish what was actually saved from what appeared only in the conversation.

Memory versus source material

Memory is helpful context, not always the authoritative source. For dates, policies, financial figures, or changing project status, identify a maintained file or system as the source of truth.

Knowledge quality

Durable knowledge should retain provenance when it matters: where a claim came from, when it was recorded, and whether it is confirmed or inferred. Review or refresh knowledge after important changes.

Review regularly

Ask Neo to summarize remembered project facts before a major decision. Correct stale items and remove context that is no longer useful. If accuracy or privacy matters, do not assume memory is complete—ask and verify.