This sounds interesting but I have no idea what use case this could have other than a robot that can communicate with an LLM but it appears it's more than that. Isn't it slow to run scripts rather than have a preprogrammed hardware with tight loops written in C? I'm genuinely confused, please don't take it as a criticism. What kind of projects have you done or what do you have in mind or envisage in the future? Autonomous robots? Cheers
As a robot it literally can program itself; it becomes its own firmware engineer, and can adapt its own code.
As an assistant, it remembers everything, up to the limit of its 2TB sdcard, both facts and vectors, but can still reach out to say Google sheets.
As a plaything , it's a tamagotchi on steroids with it own character that responds to voice.
---
Lets say you had an unknown EV motor on a CAN bus. You want to make it run, but you don’t now the right protocols, or the right codes. An LLM does, or can work it out. You ask the device, as you would ask an experienced firmware engineer, play with this motor until you make it work. So the LLM does, and when it has the code working, it creates a skill that runs the motor when a pedal on CAN bus is pressed. No more firmware engineer.
Or lets say you want to build a wearable that runs on batteries for a long time, so need a mW class processor that can store all your context, and goes with you everywhere, the pendant, the clasp, the buckle. You speak to it with your earbuds, it only knows wake words but streams your audio to the LLM. Its not just a chat bot. It is the agent that stores your whole digital life .
Or maybe, because it’s a $2 part, it’s whimsical, like a tamagotchi or a bag charm. Take care of me and I respond, but I help you too. ‘You tell stuff to me you don’t want to tell Google or Apple, or even your best friend’.
---
The key is this is not a chat bot, it’s an embodied OpenClaw class agent, take it where you will, on whatever LLM you will. And it’s so cheap, you can tie it to your service and give it away.
As for speed, ask yourself, how does numpy work? The answer to that is exactly why pycoClaw works. Its 20K LOC fast path is in C , but it’s exposed to the Agent as Python, because it has to be. It has to be run time modifiable, because thats what an agent needs, because an agent is ‘just’ a while loop with a REPL. The key is what the LLM populates the REPL with.
The LLM is the tokens in, tokens out intelligence, but it turns out the Agent or Harness is where the power really lies.
This project looks super cool. I love having the idea of having openclaw on a low powered device. I am working on something and should have it out next week. It was designed to run on a raspberry pi and would be a great companion to your project. I will post back when it is live and would love for you to take a look.
This sounds interesting but I have no idea what use case this could have other than a robot that can communicate with an LLM but it appears it's more than that. Isn't it slow to run scripts rather than have a preprogrammed hardware with tight loops written in C? I'm genuinely confused, please don't take it as a criticism. What kind of projects have you done or what do you have in mind or envisage in the future? Autonomous robots? Cheers
As a robot it literally can program itself; it becomes its own firmware engineer, and can adapt its own code.
As an assistant, it remembers everything, up to the limit of its 2TB sdcard, both facts and vectors, but can still reach out to say Google sheets.
As a plaything , it's a tamagotchi on steroids with it own character that responds to voice.
---
Lets say you had an unknown EV motor on a CAN bus. You want to make it run, but you don’t now the right protocols, or the right codes. An LLM does, or can work it out. You ask the device, as you would ask an experienced firmware engineer, play with this motor until you make it work. So the LLM does, and when it has the code working, it creates a skill that runs the motor when a pedal on CAN bus is pressed. No more firmware engineer.
Or lets say you want to build a wearable that runs on batteries for a long time, so need a mW class processor that can store all your context, and goes with you everywhere, the pendant, the clasp, the buckle. You speak to it with your earbuds, it only knows wake words but streams your audio to the LLM. Its not just a chat bot. It is the agent that stores your whole digital life .
Or maybe, because it’s a $2 part, it’s whimsical, like a tamagotchi or a bag charm. Take care of me and I respond, but I help you too. ‘You tell stuff to me you don’t want to tell Google or Apple, or even your best friend’.
---
The key is this is not a chat bot, it’s an embodied OpenClaw class agent, take it where you will, on whatever LLM you will. And it’s so cheap, you can tie it to your service and give it away.
As for speed, ask yourself, how does numpy work? The answer to that is exactly why pycoClaw works. Its 20K LOC fast path is in C , but it’s exposed to the Agent as Python, because it has to be. It has to be run time modifiable, because thats what an agent needs, because an agent is ‘just’ a while loop with a REPL. The key is what the LLM populates the REPL with.
The LLM is the tokens in, tokens out intelligence, but it turns out the Agent or Harness is where the power really lies.
pycoClaw is the LLM harness for hardware.
This project looks super cool. I love having the idea of having openclaw on a low powered device. I am working on something and should have it out next week. It was designed to run on a raspberry pi and would be a great companion to your project. I will post back when it is live and would love for you to take a look.
Hope its a cool local LLM.
Also will soon have this running on RP2350 soon, so stay tuned for that!
picoClaw has a built in provider router to that heartbeats etc can go local to save tokens and $$$
eg
etc