NanoClaw

“I'm thankful to things like nanoclaw and then Hermes for exposing me to the core ideas.”

“after multiple cases of NanoClaw "forgetting" to do it or accidentally running multiple times”

“I've given my openclaw/nanoclaw a personality whose sole job is to tend to my server and enjoy it”

“The great things about NanoClaw is that its actually Claude running in an Apple Container on my Mac.”

“need something to pay with paperclip, gastown, nanoclaw and the next 100k stars FOMO hype”

“It's freed up my home life to spend more time with my children and my Mrs.”

“nanoclaw has a lot fewer capabilities than openclaw, with the expectation that you'll essentially build your own features on top of it”

“that assumption isn't safe, remember that the only thing namespaces away is that which supports namespaces”

“It's a mess in terms of code/filesystem organization, but it's nice to be able to text somebody”

“I love how NanoClaw is aggregating the effort of making personal assistants more secure.”

“nanoclaw is a slightly more secure version - containerized filesystem basically - and very popular”

“What these 'channels' do is essentially why I was running a nanoclaw at work”

“dockerized by default, a fraction of the amount of lines of code so you can actually peer review the code”

“I simply can't bring myself to give Israeli software like this access to any of my systems.”

“It knows my goals, keeps me on track, does meal planning for me”

“a couple novel design decisions are going to prove to be widely adopted and revolutionary”

“it worked fine until the next day some update decided to revert the power management settings”

“it should be small enough to understand, modify and extend itself”

“So the skills model means that you only "generate code" that _you_ specifically ask for.”

“I tried NanoClaw and love the skill (and container by default) model.”

“nanoclaw requires agents to code extensions on the fly to get to feature parity with openclaw”

“It is designed as a sort of framework that gives a solid foundation for you to build your own custom version.”

“I don't see how self-modifying code that uses a RNG to generate changes is going to be better for security than a proper plugin system.”

“Now my partner (and i) have a chat-interface to independently manage movies”

“It's novel, exciting, and might inspire some real practical products in the future”

“I find some things useful about my nanoclaw setup - convenience and easy scheduling of LLM related tasks”

“It can schedule stuff and run in a loop, so it's like claude combined with cron.”

“the solution is creating uncompatibile branch and forcing users to use cladue for resolving merge conflits”

“Karpathy's point about NanoClaw's ~4000 lines being auditable is a solid trust argument”

“We're already running two of them in production (PR reviews and ticket triaging)”

“get daily briefings on sales pipeline status, get reminders on tasks, give it updates after calls”

“I wanna say for something which is 100% a security product I prefer explicit versus implicit / magically”

“I run this instead of openclaw, mostly because Claude Code itself is sufficient as a harness.”

“This isn’t production code but a reference or starting point they can use to build functional custom software”

“Nanoclaw is excellent. Natively uses Apple containers and easy to use with oauth Claude code subscription.”

“It's really smart to run something like this in a sandbox, especially in the current beta/experimentation phase.”

“def appreciate this more compact approach; everything is an experiment rn.”

“The scheduled tasks seem like the major functional difference. Pretty cool.”

“I can fork it as a starting point or just give it to Claude for inspiration”

“The smell of LLM from the docs of any project puts me off even when I like the idea of the project itself”