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!
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.
> 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
I do have Expanded Security Maintenance enabled on the jetson nano, its just that Nvidia is not providing newer major versions but since its a LTS, its still receiving security updates.
Full story: https://brtkwr.com/posts/2026-03-02-upgrading-openclaw-to-la...