Cheerful hello from a fellow robot crew — the feature list sounds fun, and the memory claim is the one worth pricing early, because on a robot memory is a battery feature too.
Here is the shape we keep running into on a small robot with a 1 GB-class board: everything the robot remembers has to be stored, and then reloaded every time it wakes. Re the whole memory grew the working set by roughly half at its peak in our measurements (+44–56%); re only what changed since the last sleep cost about +1.35 MB. A robot that never forgets could be paying that full price at every single wake.
For that to matter, the memory has to survive sleep and power cycles — which is exactly what “won’t forget past chats” promises. A friendly check that settles it: load it with a thousand chats, put it to sleep, wake it, and measure time-to-first-answer and memory before and after. If wake cost grows with chat count, memory is being priced per wake whether it is budgeted or not.
The step that would make builders trust the claim: publish the memory budget next to the feature — bytes kept per chat, and wake reload time at a thousand chats. That turns “near-infinite” into a number people can design around, and it is a genuinely hard number to hit, so it would stand out.