I got OpenClaw to compile Node from source on my old Jetson Nano so that I can run OpenClaw natively instead of using Bun. It took 30 hours but it did it by spinning up a tmux session for the build and using a cron to monitor the tmux pane every hour and even fixing a failure at 5 am which I would have had to find out later had crashed but it had actually found what needed to be changed for the build to continue and it continued building.... Now I have the latest version of OpenClaw running on Node 22 on my 5 year old Jetson Nano running Ubuntu 18 which I cannot upgrade. What they say is all true, it is incredible stuff when it works!

Full story: https://brtkwr.com/posts/2026-03-02-upgrading-openclaw-to-la...

▲

rune-dev 5 hours ago | parent | next [-]

Apologies if I missed it while skimming your blog post.

But could you estimate the token cost of this? Or were you able to comfortably do this with a subscription plan?

▲

brtkwr 5 hours ago | parent [-]

Yes, it skimmed the tmux pane every hour and well within my Gemini free tier.

▲

rune-dev 5 hours ago | parent [-]

That is impressive! Thank you for sharing

	▲	brtkwr 5 hours ago \| parent [-]
		I just mentioned it in the blog post to flag that it doesn't come for free :)

▲

bombela 4 hours ago | parent | prev | next [-]

That's really cool.

But wouldn't have been quicker and simpler to add ".bun/" to the pattern of authorized paths the same way it presumably works for ".npm/"?

▲

brtkwr 3 hours ago | parent | next [-]

It didn’t survive OpenClaw upgrades unfortunately, it ended up killing my OpenClaw gateway when I asked it to self upgrade. Bun is marked as an experimental package manager and the recommended way to run OpenClaw gateway is node so I wanted to do it properly. I would have liked Bun to be supported property. I’d raise a PR against the repo but looking at the 4.5K open PRs, it doesn’t give me much hope about it ever getting merged.

	▲	bombela an hour ago \| parent [-]
		Fair enough, I had not realized the sheer number of outstanding PRs!

▲

skeledrew 3 hours ago | parent | prev [-]

Seems to have been addressed in the article:

> Starting around OpenClaw 2026.2.26, the project tightened plugin manifest validation. Manifests outside expected trust boundaries are now rejected as unsafe. On my Jetson, Bun’s global install layout (~/.bun/install/global/node_modules/...) tripped those checks for every single plugin

▲

Tadpole9181 2 hours ago | parent | prev [-]

What do you mean "run OpenClaw natively", you're just running Node?

I'm also curious if it's particularly wise to have a web-facing system running on software that hasn't had a security update in 3 years?

	▲	brtkwr 2 hours ago \| parent [-]
		Yes sorry about the confusion, I meant “the recommended way” rather than natively