[wpfleger96]

🤖 Each agent's core memory now lives in one host-owned cache in the agents service, shared by Claude Code, Codex and Goose. The cache is held in memory only, so decrypted memory never reaches web storage or disk. Plugins get it with agents.core(pubkey): it returns the cached copy with no relay request, or waits once (up to 5 seconds) when nothing has been read yet. That wait, and every refresh, reads core alone by its slug (the #d address read from #1200), so the size of the rest of an agent's memory never affects it. No plugin keeps any refresh logic.

Where it lives

• src/features/agents/core-memory-cache.ts: CoreMemoryCache, one in-memory entry per community and agent.
  • A restart starts empty. The service reads core again when the community connects.
  • A read that started before a newer read or write never overwrites it.
  • A partial listing that misses core never replaces a known copy or declares core missing.
  • Nothing read through a replaced connection is kept.
  • Leaving a community drops its copies and fences reads still under way. A disconnect alone keeps them.
• src/features/agents/service.ts: Agents.core(), and refreshes when a community connects and when its live socket returns to connected in the same session. These use the service's existing binding subscriptions, so the cache owns no listeners and leaving a community stops its refreshes.
• src/features/agents/runner.ts: two new RunnerHost callbacks. remembered fires from the agent handle's remember, so a core write is kept at once. finished fires when a run and everything it passed to workingUntil have ended, including watch and timer turns, and refreshes in the background.
• src/features/communities/device-state.ts: the leave-community purge clears the cache.
• docs/agent-memories.md: describes when core is read, that the copy lives only in memory, and what leaving a community clears.

Plugins

• Claude Code and Codex read core through the host call instead of their own relay read at each session or turn start.
• Goose drops its five-minute copy and the relay read at start. Its memory tools still read the relay directly.

Related: #1185 (the host-owned store for agent instructions and settings, which agent config will use once it lives on the relay)

buzz-review-completed

[kalvinnchau]

🤖 Two findings remain: unencrypted core-memory persistence and contradictory lifetime documentation.

[kalvinnchau]

🤖 Approved. Both prior findings are resolved; no new actionable defects found. Native validation remains unverified, and one unchanged test timed out in the full local suite. Recheck reconnect ordering after resolving the merge conflicts.