Memory reference

Bestie starts with local SQLite memory. Zep is planned as an optional advanced provider later, not the first memory layer.

Write policy

The model may propose durable memories through internal.remember_memory. Runtime config controls what happens next:

Policy	Behavior
allow	Store allowed non-secret memories directly.
ask	Queue allowed non-secret memories for owner approval. This is the default.
deny	Reject memory writes.

Eligible memory types include non-sensitive user facts, project context, durable decisions, communication preferences, and explicit preferences.

Sensitive personal details, relationship or family context, health context, financial details, and private identifiers should go to pending approval.

Never store passwords, tokens, payment details, secrets, or one-off venting unless explicitly requested.

Current storage

The SQLite store tracks:

• active memories
• pending memories
• persisted terminal and Telegram messages
• memory pause/resume state
• pending action approvals

Doctor verifies that the memory database can be created, opened, and migrated.

User controls

CLI controls include:

bestie memory status
bestie memory pause
bestie memory resume
bestie memory list
bestie memory search concise
bestie memory add communication_preference "User prefers concise replies."
bestie memory inspect 1
bestie memory edit 1 "Updated memory text."
bestie memory forget 1
bestie memory messages --limit 5 --role user
bestie memory messages search project --limit 5 --role assistant
bestie memory export
bestie memory clear --yes
bestie memory pending --limit 5
bestie memory pending search hanoi --limit 5
bestie memory pending inspect 1
bestie memory approve 1
bestie memory reject 1
bestie memory reject-all --yes

Terminal chat also supports /memory, /memory pause, /memory resume, and /pending.