[guerython]

This is a useful direction, especially for teams that mix Codex and Claude in the same repo.

One thing that matters in practice is memory lifecycle. Shared memory tends to drift unless entries have retention rules (TTL, dedupe, and merge policy) plus periodic compaction.

Are you planning a policy layer so users can control what persists as raw events versus summarized state?

[joeljoseph_]

Great point, and yes, that’s exactly where this is heading.

policy driven persistence and compaction is planned, and parts of the lifecycle are already live.