It can modify everything, because while it's a single binary and that makes it easy for installation, there are things stored outside that binary. The memories, the skills, the config etc. But you can do everything from the UI and you don't need to bother, it will be all automatic.
To be honest, I was looking at a short name, something than "Rustacean" would get, had a domain name available, easy to pronounce. I didn't like rustclaw, I think having similar name doesn't mean much unless it's very related, like tinyclaw being a typescript simili I get it.
For the logo, I do think everyone went for the lobster meme for a connection to clawdbot. But in my case it's because I wanted to use a derivative of the Rust logo, a crab.
Heartbeat: is run on a regular interval (you choose) and can do something you define in the heartbeat prompt section of that settings.
Crons: is run when you want, you can ask to Moltis things like "do <whatever> every day at X" and it will automatically create a cron entry, you can disable later.
It's a different take and heavily inspired at first by OpenClaw, which is a great product and Peter the founder is an amazing human being. I'm adding features than I want, since I do Moltis for my own use but also try to add features than others will enjoy.
I think Rust makes a lot of sense security wise, it does add benefits like being a single binary and very easy to install. I also tried to make it easy to try with a 1-click deploy on the cloud.
I'm not sure this is convincing enough but I think you can only judge by yourself trying it out, and I'd love feedback.
author here, it works for a few friends. Would love to fix it for you, but you can also just use the github project: https://github.com/moltis-org/moltis
I've tried it all and the only real solution is a Linux VM without shared folders, which I'm fine with. The project I booted is used by other colleagues so I tried to make it "generic" and then yes, vagrant copies the file.
As you said (and others in comments) bidirectional syncing with docker-rsync, or using NFS, is one way to have files synchronising but it always ends up being a pain.
I did use cached and delegated but it's nowhere near close to the ideal solution: removing macOS of the equation. At least until Docker find a real fix for those performance issues, if anytime.