I have a couple ESP32 with a very small OLED display, I'm now thinking I could make an "intelligent" version of the Tamagotchi with this. Do you HN crowd have other cool ideas?
This is a great example of how silly this whole thing is. There’s next to nothing to these claws. Turns out that if you give an llm the ability to call APIs they will.
I think you can use C++ on esp32, that would make the code more readable
"LLM backends: Anthropic, OpenAI, OpenRouter."<p>And here I was hoping that this was local inference :)
Sure. Why purchase a H200 if you can go with an ESP32 ^^
Blowing more than 800kb on essentially an http api wrapper is actually kinda bad. The original Doom binary was 700kb and had vastly more complexity. This is in C after all, so by stripping out nonessential stuff and using the right compiler options, I'd expect something like this to come in under 100kb.
Doom had the benefit of an OS that included a lot of low-level bits like a net stack. This doesn’t! That 800kB includes everything it would need from an OS too.
yeah i sandbagged the size to start (small enough to fit on the c3, 888 picked for good luck & prosperity), so i can now reduce it as an exercise etc
haha well I got something ridiculous coming soon for zclaw that will <i>kinda</i> work on board.. will require the S3 variant tho, needs a little more memory. Training it later today.
right, 888 kB would be impossible for local inference<p>however, it is really not that impressive for just a client
Genuinely curious - did you use a coding agent for most of this or does this level if performance take hand written code?
Relevant: <a href="https://github.com/sipeed/picoclaw" rel="nofollow">https://github.com/sipeed/picoclaw</a>
Is there a heartbeat alternative? I feel like this is the magic behind OpenClaw and what gives it the "self-driven" feel.
This is absolutely glorious. We used to talk about "smart devices" and IoT… I would be so curious to see what would happen if these connected devices had a bit more agency and communicative power. It's easy to imagine the downsides, and I don't want my email to be managed from an ESP23 device, but what else could this unlock?
Serious question: why? What are the use cases and workflows?
The various *claws are just a pipe between LLM APIs and a bunch of other API/CLIs. Like you can have it listen via telegram or Whatsapp for a prompt you send. Like to generate some email or social post, which it sends to the LLM API. Get back a tool call that claw then makes to hit your email or social API. You could have it regularly poll for new emails or posts, generate a reply via some prompt, and send the reply.<p>The reason people were buying a separate Mac minis just to do open claw was 1) security, as it was all vibe coded, so needs to be sandboxed 2) relay iMessage and maybe 3) local inference but pretty slowly. If you don't need to relay iMessage, a raspberry pi could host it on its own device. So if all you need is the pipe, an ESP32 works.
I don't fully get it either. At least agents build stuff, claws just run around pretending to be alive?
for fun!
I don't really need any assistance...