#9816: core-memories: ingest chat into Flash + capture assistant replies
stale
### What
- Ingest inbound user messages into CoreMemories Flash (best-effort).
- Ingest assistant outputs (tool/block/final/abort payloads) as `assistant_reply` entries.
- Add `@openclaw/core-memories` as a workspace dependency so runtime imports work in dev.
### Why
CoreMemories is meant to be the 0–48h source of truth for recent conversation. This wires real chat traffic into the Flash store so retrieval/session-continuation can work.
### Notes
- Best-effort only: ingestion is non-blocking and wrapped in try/catch so it cannot break message handling.
- This PR does **not** change MEMORY.md behavior; it only records recent raw chat.
### Testing
- Manual: run fork gateway, send messages, confirm `.openclaw/memory/hot/flash/current.json` grows with `conversation` + `assistant_reply` entries.
- Lint: `pnpm lint src/auto-reply/reply/dispatch-from-config.ts`
<!-- greptile_comment -->
<h2>Greptile Overview</h2>
<h3>Greptile Summary</h3>
This PR wires CoreMemories “Flash” ingestion into the reply dispatcher, recording inbound message text as `conversation` entries and recording assistant abort/tool/block/final text as `assistant_reply` entries (best-effort, non-blocking). It also adds `@openclaw/core-memories` as a workspace dependency to make dev runtime imports resolve.
The main integration point is `src/auto-reply/reply/dispatch-from-config.ts`, where message dispatch now triggers background writes to CoreMemories alongside existing routing/TTS behavior.
<h3>Confidence Score: 2/5</h3>
- This PR has a couple of merge-blocking runtime/packaging issues despite being best-effort.
- Score reflects a likely install break from adding a `workspace:*` dependency to root `dependencies`, plus unbounded background ingestion work during block streaming that can hurt performance under load.
- package.json, src/auto-reply/reply/dispatch-from-config.ts
<!-- greptile_other_comments_section -->
**Context used:**
- Context from `dashboard` - CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8))
- Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=0d0c8278-ef8e-4d6c-ab21-f5527e322f13))
<!-- /greptile_comment -->
Most Similar PRs
#13775: Lucas/enable corememories
by Itslouisbaby · 2026-02-11
82.9%
#9818: coremem-tools: add coremem_recent/coremem_find agent tools
by Itslouisbaby · 2026-02-05
76.5%
#7480: feat: Add CoreMemories hierarchical memory system
by Itslouisbaby · 2026-02-02
75.7%
#8713: feat: gateway memory monitor, install linger, docs and failover
by quratus · 2026-02-04
74.9%
#6060: feat(onboarding): add Memory Optimization step to onboarding wizard
by GodsBoy · 2026-02-01
74.8%
#19341: Mind Memory Fork
by juliopx · 2026-02-17
74.1%
#8795: feat(memory): add Redis-backed long-term memory plugin
by tf-gmail · 2026-02-04
73.8%
#8919: Pr/memory flush improvements
by shortbus · 2026-02-04
73.5%
#3401: fix(memory-lancedb): improve autoCapture with turn-by-turn processing
by mike-nott · 2026-01-28
72.5%
#8900: fix: improve default memory flush prompts with urgency and specifics
by joetomasone · 2026-02-04
72.3%