I never understood memory solutions for coding agents.

You have the whole session history right there. One recall skill and some JSON parsing gets you grep over perfect memory. Why would you ever use more tools to spend more tokens to construct a imperfect memory next to your session history?

I just don't get it.

▲

ceejayoz 2 hours ago | parent | next [-]

> You have the whole session history right there.

But that's one session. Isn't memory for… the next session?

	▲	unlikelytomato 40 minutes ago \| parent [-]
		the code seems to fill this need, for me

▲

dboreham an hour ago | parent | prev [-]

It's just an optimization. You might not pay it to re-read everything. So it sticks some stuff in a notebook that it always reads. Like inspector Poirot.