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 :)
NanoClaw moved from Apple Containers to Docker
81–90 of 146 posts
Re: NanoClaw moved from Apple Containers to Docker
#82Earlier quoted context omitted.
What about heartbeats, cron etc? Seems like a major part of the 'claw' appeal is that it can work autonomously, monitor your email inbox for stuff and take action automatically...
I hear a lot about people doing this but it really seems like it is prompt injection as a service. eventually the things that can happen when you give the world write access to an unattended LLM that can access both your browser and password reset mechanism will happen. or someone will just make it email lewd pics to people’s bosses for the lols
I would never use it on my MacBook or any machine but I understand why technical people would want to experiment with something dangerous like that. It’s novel, exciting, and might inspire some real practical products in the future (not just highly experimental alpha software).
Re: NanoClaw moved from Apple Containers to Docker
#83You don't need to use OpenClaw, NanoClaw or any of these new variants. You can literally use Codex, Claude Code, Gemini, OpenCode for the same thing. The only thing that it is missing from all of them is the communication channels because none of them come with native communication tools like OpenClaw. But this is not such a big deal. I made an open-source lightweight daemon in Go that fills that gap. All it does is…
This is basically just telling people to learn to code
Which IMO they should anyway if they are doing advanced automation
Re: NanoClaw moved from Apple Containers to Docker
#84Can 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 B…
This is a classic early internet style snarky comment you used to find all over forums
Re: NanoClaw moved from Apple Containers to Docker
#85You don't need to use OpenClaw, NanoClaw or any of these new variants. You can literally use Codex, Claude Code, Gemini, OpenCode for the same thing. The only thing that it is missing from all of them is the communication channels because none of them come with native communication tools like OpenClaw. But this is not such a big deal. I made an open-source lightweight daemon in Go that fills that gap. All it does is…
This is basically just telling people to learn to code Which IMO they should anyway if they are doing advanced automation
No coding is required. You can literally ask your agent to install and configure it. It is only 2 small binaries and no external dependencies. It cannot be any easier than that.
Re: NanoClaw moved from Apple Containers to Docker
#86Earlier quoted context omitted.
You're just not providing any good examples of what I cant already do with current automation tools.
My wife constantly asks me about adding books to her Kindle. I use Anna’s archive for this, but the process can be very annoying. I have to go to the site, search for the content. Filter by epub and English. Then download the content. Then send it to her Kindle email. My openclaw now searches for the relevant content upon her request, sends the URL to a Stacks docker instance, monitors the Stacks instance for when th…
But it's so easy to just download from libgen and send as an attachment to a Kindle email...
Re: NanoClaw moved from Apple Containers to Docker
#87You don't need to use OpenClaw, NanoClaw or any of these new variants. You can literally use Codex, Claude Code, Gemini, OpenCode for the same thing. The only thing that it is missing from all of them is the communication channels because none of them come with native communication tools like OpenClaw. But this is not such a big deal. I made an open-source lightweight daemon in Go that fills that gap. All it does is…
Seriously, for anyone that knows how to code it’s super easy to setup your own thing. I set up an cloudflare email worker that just forwards emails to my server and Claude can send me emails back. It’s super nice because email already has all the functionality for threads and nice formatting.
Since I control the server and all the code it’s very simple to setup up schedules or new tools.
Re: NanoClaw moved from Apple Containers to Docker
#88Putting these NanoClowns inside a container will not protect you from all kinds of safety hazards.
I’m not sure what docker is helping with that an unprivileged Linux user account doesn’t already do. The scary stuff with claws is unrelated to process isolation.
Re: NanoClaw moved from Apple Containers to Docker
#89Lol production use case for apple containers on what cloud
Re: NanoClaw moved from Apple Containers to Docker
#90TBH I'm not sure why there is a whole debacle around security with openclaw (obviously you should run it in a sandbox) and if it makes sense for these bots to tackle sandboxing themselves. Now I have to trust their sanboxing vibe code? If not, then I have to run them in another sandbox and deal with nested virtualization.