Capture what happened, compress it, put the relevant part back at the start of the next run. Three verbs and one boundary, which is the whole shape of the problem this addresses.
Capturing everything is cheap and injecting is mechanical. Deciding what survives the boundary is where a memory tool is actually judged.
The description names seven agent products and then says more. A memory layer that belongs to no single vendor is the only kind worth carrying between them.
No storage format, no compression ratio, no token budget, no retention window. The trending description names none of it.
Concept mock, not affiliated with the project. The three verbs and the seven host names are quoted from the repository's own GitHub Trending description on 27 August 2026. The panel is labelled shape only: the two session boxes carry no transcript, no size, and no example, because the project publishes none there.