I assume running tool calls in a sandbox (like you do it in mom) helps to protect against such holes? (One should probably still add the node flag…)

This! And tbh, it feels best when it’s my own code that I deleted. Deleting obsolete code means that things got better, that I got better.

For me it’s not OpenClaw itself that hyped me, but seeing what’s possible in regard do extremely accessible automation.

For month I resisted looking into agents and didn't even want to understand them because I felt the concept is just crazy and dangerous, where the benefit can't possibly higher then the risk. Well...I changed my mind thanks to @openclaw and now I'm sitting here and trying to understand how pi.dev works and how to make things at least a little bit securer.

Cool, I'll check out "mom" in the next days, should be enough to get some inspiration even if it's vibe slop.

Reading your posts about the quality of openclaw for the last few days and from the limited amount of code I've seen so far, I agree on most of what you say. My take is: Wait a few weeks and an alternative will emerge that can do most of the stuff Clawd can, while not being fully vibe coded. I wonder @badlogicgames, do you know of any such project that is already in the works? Any tips on which route to go if wanted to figure out how to build my own custom built single purpose agents based on pi?

Nope. I assume you mean dboxed.io? I’m currently not sure if I should continue this project tbh. Working on it since a year and not a single user yet and there is no end in sight regarding the amount of work needed.

100% agree and always thought the same. At the same time, never realised that I might be doing the same and having that exact blind spot actually :D

Look into @netbird as an alternative. They got their first A round this year, so there’s no guarantee that they don’t go the same route. But looking at them they look like their heart is at the right place.

Oh sheeze, the agents fever got me. A friend has just shown me @openclaw. A lot of my scepticism regarding agents has just been blown away today. Time to try it out.

mining could have been done anonymously, so no one would have actually known its an inside operation. In the end profit and (minimal) risk is the driving factor. the issue is that if someone else builds hardware that is 100x more efficient, you're out of business very fast even if you own 50% of the network (no matter if AI or mining). the risk here is just to high for a company like Nvidia that build general purpose hardware. I know that Nvidia (Jensen) publicly argues that CUDA and the ecosystem is the killer feature that will make them stay at the top. But an ASIC that can run some of the most important models at 100x efficiency changes quite some dynamics, and "being general purpose" becomes a less important factor :)

Not sure about that tbh. Nvidia, could have done the same when the crypto boom was at its highest point, running their own mining operations and avoid selling hardware. If they would have done this, specialised mining hardware (ASICs) would have killed them in an instant. Same applies to the ASIC producers as well, any competitor being able to build a more efficient machine would kill the own mining business, so they were forced to sell hardware. I predict that Nvidia will become less important in the future actually. Specialised hardware will come at the market that will be able to run the most important models but with much much much better energy efficiency. Nvidia betting on their own AI operations would be a guaranteed and fast death in the end, so selling like crazy now is the best thing they can do.

Beyond Compare is a classic and never disappointed me. Looks like the early 2000s but it does the job very well.

I fear the day where "pretty good source data" gets completely replaced with "pretty good AI generated source data" because everyone stopped programming (or any other science/art) by themself. But until then, lets enjoy the ride :)

This feature also allows to pass open namespace descriptors between processes. Useful if you want to pass a privileged namespace into a sandboxed child process, e.g. to allow some level of control over the host system inside an otherwise sandboxed container.

I assume Open Source communities always start with single individuals. Happy to see the first people show up on Github and contribute via detailed bug reports and feedback 🙏

Just released v0.8.0 of Dboxed, allowing you to use Git as the source of box definitions. So you can now write down the box spec inside a file called "dboxed-specs.yaml" and Dboxed will create the actual boxes and volumes from them. Proper docs will follow tomorrow. I'm also at the point now where I should start thinking about development and release processes. For example, releases should now start having changelogs and migration infos/guides.

And while we re-consider it, can we also find a way to reliably run CI jobs locally, without the need to push to Git? I'd like to get away from push-and-pray workflows, pleeeeaaase 🙏