> But NanoClaw isn't just my personal project anymore. Thousands of people are using it. People are running production workloads on it. Businesses are building on it. There's a real community now.
as OpenClaw and now NanoClaw became "enterprise", now we need a new FemtoClaw to pick up the indie/boutique place
We need to go the other direction. GigaClaw eats $100,000/month in tokens and requires a Threadripper with 256GB of RAM on a gigabit connection just to handle the orchestration.
I'm sure whatever LLM FemtoClaw calls out to will also write a blurb about its growing adoption in production enterprise applications. This sentiment is probably very well represented in the training data.
That's old news. Now there's Plancklaw, renamed to ∅. It has no code base, no bugs, no security issues, infinitely scalable, and all the features of every other *claw.
All plugins run in one Docker container, but they're isolated from each other by different *nix users, so they can't read each other's files. That's much more lightweight, and you don't have to run one container per plugin.
Crucially, plugins can't read each other's secrets or modify each other's code. I even have a plugin configuration webpage that doesn't go through an LLM, so the LLM never sees your secrets if you don't want to.
That's the fun part! You spend all day hardening it... run it in docker in a vm on a separate machine. And then you hook it up to your gmail and give it unrestricted internet access :)
I’ve been building sandboxing for Claude code workloads. So I can let it run wild without breaking my computer. Originally I used docker, but I’m now in the process of jettisoning that, and switching to qemu.
For my use case I want ssh access and being able to use docker in docker. This allows for things like test containers and docker compose. You can get all of that working with docker. But you kind of have to fight docker the whole way.
NanoClaw might have different needs, and docker could work better for it, and I hope so for their sake. But I’m not optimistic.
I'm surprised that the developer experience around sandboxing on macOS is generally so bad. Seatbelt is in limbo and apple containers are just a pain to work with as some have highlighted in this thread
I can't believe the solution is creating uncompatibile branch and forcing users to use cladue for resolving merge conflits. Why not bake in the dual compatibility?
There is no special sauce, it's mass hysteria driven by fake adoption metrics and people who don't know anything about computers who let "agents" run free on theirs. It's the equivalent of showing a magician cut a women in a box in half to a 5 years old kid... Put them in the same category as the neckbeards getting a hard on every 3 weeks for the past 2 years when they get to see the new version of ThE PeLiCaN On A BiCyCle... I wonder how long the circus will keep on going, at least it's funny to witness from the outside
They're "always" running, so they can notify you out of the blue, without you having to initiate a conversation. It's really nice UX to get a message from my assistant saying "hey, it's time to leave for the gym, and don't forget the supermarket bag because you're picking up milk on the way back, as you've run out".
Dunno, my calendar reminds me "out of the blue", without me having to initiate a conversation, that it's time to leave for the gym, no "claw" or "ai" involved.
I always have my backpack with me, so if I need milk I can pick it up on the way back. And I am pretty sure that I have to notice if I need milk myself.
The tech sounds cool, but whenever I hear about actual applications, I don't see the point.
Hmm, Google Gemini has access to my Google Tasks and can set reminders. It's also asked me if I want it to check something at "tomorrow 9am", and when I said yes, it managed to do that.
Crons. A local daemon. System access as a user with the ability to listen to changes. Some idea of shared “memory” between sessions. Provider agnostic about AI. Multi-model.
I installed nanoclaw last night funny to see it here on HN.
It was easy to install it, and get it running. I could @Andy message it on whatsapp but after that it fell apart fast.
I asked it to login to Facebook and check my notifications, and it started saving credentials and random things in the repo as json files. And din't work. It was hard to even figure out what was happening and why it didn't work.
Then I tried messaging it again and it didn't respond to me.
These things are extremely brittle despite the enourmous amount of github stars. I think it's just normies starring things trying to get on the train unfortunately. The promise of an AI Jarvis is unrealized still.
> But NanoClaw isn't just my personal project anymore. Thousands of people are using it. People are running production workloads on it. Businesses are building on it. There's a real community now.
as OpenClaw and now NanoClaw became "enterprise", now we need a new FemtoClaw to pick up the indie/boutique place
We need to go the other direction. GigaClaw eats $100,000/month in tokens and requires a Threadripper with 256GB of RAM on a gigabit connection just to handle the orchestration.
I'm sure whatever LLM FemtoClaw calls out to will also write a blurb about its growing adoption in production enterprise applications. This sentiment is probably very well represented in the training data.
How is this "becoming enterprise"? If anything it now defaults to millions of Linux users being able to access it
Could also make the other part ‘smaller’ and use nail, hoof or dewclaw (https://en.wikipedia.org/wiki/Dewclaw)
How's 100 lines? :)
https://github.com/a-n-d-a-i/ULTRON/blob/main/src/index.ts
Well, there was Picoclaw, but I think it was renamed to Clawlet.
That's old news. Now there's Plancklaw, renamed to ∅. It has no code base, no bugs, no security issues, infinitely scalable, and all the features of every other *claw.
2 replies →
MicroClaw.. No fear of it becoming corporate LOL.
For my version of the AI assistant, I used a Docker container and Unix permissions:
https://github.com/skorokithakis/stavrobot
All plugins run in one Docker container, but they're isolated from each other by different *nix users, so they can't read each other's files. That's much more lightweight, and you don't have to run one container per plugin.
Crucially, plugins can't read each other's secrets or modify each other's code. I even have a plugin configuration webpage that doesn't go through an LLM, so the LLM never sees your secrets if you don't want to.
Putting these NanoClowns inside a container will not protect you from all kinds of safety hazards.
That's the fun part! You spend all day hardening it... run it in docker in a vm on a separate machine. And then you hook it up to your gmail and give it unrestricted internet access :)
Wearing a seatbelt will not protect you from all kinds of car accidents.
Yes. That's why you don't put a Clown behind the steering wheel.
2 replies →
Wearing a helmet will not protect you from all injuries caused by jumping off a cliff.
Point is, don't jump off a cliff.
2 replies →
I’ve been building sandboxing for Claude code workloads. So I can let it run wild without breaking my computer. Originally I used docker, but I’m now in the process of jettisoning that, and switching to qemu.
For my use case I want ssh access and being able to use docker in docker. This allows for things like test containers and docker compose. You can get all of that working with docker. But you kind of have to fight docker the whole way.
NanoClaw might have different needs, and docker could work better for it, and I hope so for their sake. But I’m not optimistic.
I'm surprised that the developer experience around sandboxing on macOS is generally so bad. Seatbelt is in limbo and apple containers are just a pain to work with as some have highlighted in this thread
I can't believe the solution is creating uncompatibile branch and forcing users to use cladue for resolving merge conflits. Why not bake in the dual compatibility?
you may slot in podman, but apple container is not very good atm.
Can someone explain the special sauce of the claws compared to just use claude.ai etc
There is no special sauce, it's mass hysteria driven by fake adoption metrics and people who don't know anything about computers who let "agents" run free on theirs. It's the equivalent of showing a magician cut a women in a box in half to a 5 years old kid... Put them in the same category as the neckbeards getting a hard on every 3 weeks for the past 2 years when they get to see the new version of ThE PeLiCaN On A BiCyCle... I wonder how long the circus will keep on going, at least it's funny to witness from the outside
They're "always" running, so they can notify you out of the blue, without you having to initiate a conversation. It's really nice UX to get a message from my assistant saying "hey, it's time to leave for the gym, and don't forget the supermarket bag because you're picking up milk on the way back, as you've run out".
Dunno, my calendar reminds me "out of the blue", without me having to initiate a conversation, that it's time to leave for the gym, no "claw" or "ai" involved.
I always have my backpack with me, so if I need milk I can pick it up on the way back. And I am pretty sure that I have to notice if I need milk myself.
The tech sounds cool, but whenever I hear about actual applications, I don't see the point.
3 replies →
Hmm, Google Gemini has access to my Google Tasks and can set reminders. It's also asked me if I want it to check something at "tomorrow 9am", and when I said yes, it managed to do that.
3 replies →
How would it know you've ran out of milk?
5 replies →
How do people afford this?
2 replies →
It can schedule stuff and run in a loop, so it's like claude combined with cron. Truly amazing technology.
Crons. A local daemon. System access as a user with the ability to listen to changes. Some idea of shared “memory” between sessions. Provider agnostic about AI. Multi-model.
It's for people that don't know how or don't want to be bothered with setting up a messenger integration and a scheduler.
There is no special sauce. They are claude or codex in a loop. The loop is facilitated by basic cron jobs. That's it.
Ai Agent as it has been for months, plus skills, plus a cron job to prompt it to do things every 20 minutes or 2 hours or however often you want.
they have a watchdog loop, it runs periodically
I installed nanoclaw last night funny to see it here on HN.
It was easy to install it, and get it running. I could @Andy message it on whatsapp but after that it fell apart fast.
I asked it to login to Facebook and check my notifications, and it started saving credentials and random things in the repo as json files. And din't work. It was hard to even figure out what was happening and why it didn't work.
Then I tried messaging it again and it didn't respond to me.
These things are extremely brittle despite the enourmous amount of github stars. I think it's just normies starring things trying to get on the train unfortunately. The promise of an AI Jarvis is unrealized still.
Sensible, this broadens our hosting options.
apple container is really buggy with networking
That’s not the fault of containers, I have significant Bluetooth and WiFi issues on my apple devices without running any containers.
So they're making it use OCI images? Cool. Hopefully there will be good support for Podman.
apple containers also run on OCI images: https://github.com/apple/container?tab=readme-ov-file#contai...
> The tool consumes and produces OCI-compatible container images...
Use containerd , Docker is cancer.