Automatic memory curation

After every chat turn the agent loop runs a lightweight curator pass that asks the LLM whether the recent conversation contains durable, reusable facts (user preferences, names, settings explicitly flagged with phrases like “remember that”, “keep in mind”, etc.). When the curator decides yes, it persists at most three short entries to the per-agent memory store via the internal hiveloom_memory_write tool. Transient task details, tool payloads, and secrets are explicitly excluded.

Defaults

• The curator runs whenever a turn count is a multiple of 8 (so it isn’t invoked on every reply), or unconditionally on turns that contain an explicit “remember” phrasing.
• Each write is capped at 120 chars for the key and 1000 chars for the value; oversized writes are dropped with a warning.
• A failure in the curator is logged and never breaks the user-facing turn.

Tune the cadence

# /etc/systemd/system/hiveloom.service.d/40-memory-curation.conf
[Service]
Environment=HIVELOOM_MEMORY_CURATION_INTERVAL_TURNS=8

Set to 0 to disable the periodic pass and only act on explicit “remember” requests.

Inspect what was saved

Via the memory MCP tool, or directly against the tenant database:

sqlite3 /var/lib/hiveloom/tenants/<tenant-id>/store.db \
  "SELECT scope, key, value FROM memory_entries WHERE archived = 0"