fabienpenso

Yes. The UI allows you to add repositories (OpenClaw is one listed), and you can enable/disable any of them.

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.

It is already MIT license.

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.

Moltis can do all that yes, unless I missed something. And it's way easier to setup.

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.

There is actually a reason, the Rust logo is a crab named Ferris: https://rustacean.net

Let me confirm, I just tried on digitalocean and I have a similar issue, the last version I published might have issue. Fixing as of now.

oh so those are issues from the provider itself, you get to choose between model the provider advertise for you, meaning:

- you can have models you can not actually use (that gpt-5.3 response) - you can have model non-listed.

Those are all coming from the provider with your API_KEY.

You should not be limited, which provider do you use?

author here.

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

Hey HN. I'm Fabien, principal engineer, 25 years shipping production systems (Ruby, Swift, now Rust). I built Moltis because I wanted an AI assistant I could run myself, trust end to end, and make extensible in the Rust way using traits and the type system. It shares some ideas with OpenClaw (same memory approach, Pi-inspired self-extension) but is Rust-native from the ground up. The agent can create its own skills at runtime.

Moltis is one Rust binary, 150k lines, ~60MB, web UI included. No Node, no Python, no runtime deps. Multi-provider LLM routing (OpenAI, local GGUF/MLX, Hugging Face), sandboxed execution (Docker/Podman/Apple Containers), hybrid vector + full-text memory, MCP tool servers with auto-restart, and multi-channel (web, Telegram, API) with shared context. MIT licensed. No telemetry phoning home, but full observability built in (OpenTelemetry, Prometheus).

I've included 1-click deploys on DigitalOcean and Fly.io, but since a Docker image is provided you can easily run it on your own servers as well. I've written before about owning your content (https://pen.so/2020/11/07/own-your-content/) and owning your email (https://pen.so/2020/12/10/own-your-email/). Same logic here: if something touches your files, credentials, and daily workflow, you should be able to inspect it, audit it, and fork it if the project changes direction.

It's alpha. I use it daily and I'm shipping because it's useful, not because it's done.

Longer architecture deep-dive: https://pen.so/2026/02/12/moltis-a-personal-ai-assistant-bui...

Happy to discuss the Rust architecture, security model, or local LLM setup. Would love feedback.

These is one of the option but I felt like it was a bit early to use.

Not really, there are been numerous tries but nothing these days. You can use less memory hungry libraries like hanami instead of Rails, for example.

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.

I just tried on the repo links in the post, had hopes when I read your comment. But it makes no difference...

I use ssh and vim so it works for me, but agreed it doesn't work for everyone.

author here. M1 was running arm images, but as far as I know Docker Desktop on M1 use Qemu which is super slow anyway.

My solution for such is parallels beta (m1 supported), and arm Debian Linux.

Bigger font, straight to the point and no fuss. Contrary to you, I love its (non) design.

Same here, but still I used gmail too long.

Just filter all those mail into a unsubscribe folder instead of marking them as read.

Also filter all emails with unsubscribe in their body to that folder. Works like a charm.