Skip to main content
Memory works best when it captures stable context you want Babbily to reuse across chats. Use this guide to decide what belongs in memory and how to phrase it.

​
Good memory examples

​
Keep this in the current chat

Some details are useful once but should not become long-term memory. Examples:
  • A one-time deadline.
  • A temporary draft direction.
  • A single customer’s private details.
  • A file-specific instruction.
  • A preference that only applies to this project phase.

​
Do not save sensitive information

Do not ask Babbily to remember:
  • Passwords.
  • Verification codes.
  • API keys.
  • Private keys.
  • Payment card numbers.
  • Government identifiers.
  • Raw connected-app credentials.
  • Confidential details you are not allowed to use in Babbily.
Memory is designed for useful context, not secrets. Keep sensitive information out of chat and memory.

​
Update memory when context changes

When a preference or project changes, say so directly.
You can also open Settings > Memory to review your Memory Profile and remove eligible memory citations.

​
Ask Babbily what it remembers

Use Settings > Memory for the most complete view. You can also ask in chat:
If something is outdated, ask Babbily to forget it:

​
Memory quality checklist

Before saving something, ask:
  • Will this still be true in future chats?
  • Would this improve many replies, not just one?
  • Is it safe to reuse?
  • Is it phrased clearly?
  • Would I be comfortable seeing it in Settings > Memory?

Memory

Learn how to review, update, and remove memory.

Data controls FAQ

Review privacy controls for memory, sharing, connectors, and Library items.