“888 KiB Assistant” but the assistant itself is a multi terabyte rental-only model stored in some mysterious data center.
There are many concerns and areas for improvement with open claw and other similar projects (continuous loop script with broad OS access that manages your agents and interfaces with a standard messaging app)<p>However, file size I have never seen on that list. I would rather offer for something that is even bigger in file size so it afford certain functionality like better security tighter permissions however it would do that.
I fail to understand why 888 KiB matters if it's just a wrapper around a cloud api.
A lot of the *claws emphasize binary size and lines of code. I think for better or worse people treat codebase size as a proxy for "how much of the project is unsupervised, unmaintainable, buggy AI slop?"
Have you seen OpenClaw's codebase? 680.000 LOC.<p>I care how big it is.
Because of resource-constrained environments, the primary deployment target seem to be microcontrollers. You can get ESP32 boards for pretty cheap.
Because it means you can run it on an ESP32 which is a low power microprocessor package.
Me: "GPIO 5 can be active for a maximum of 100ms, then it needs to cool down for at least 1s. Otherwise the MOSFET is fried."<p>Zclaw: "GPIO 5 is active now, however the server is not responding so I'm awaiting further instructions."
The domain crashed and burned or something, hopefully this link is correct:<p><a href="https://github.com/tnm/zclaw" rel="nofollow">https://github.com/tnm/zclaw</a>
Clicked on this expecting to see a crontab file.
1. why
There is the same divide starting to form that NFTs had back in the day. Tech bros instantly like if something has claw in the name, the rest of us will dismiss anything with that naming and philosophy as toxic slop culture. will be interesting to see how far this one will go.