Show HN: Moltis – AI assistant with memory, tools, and self-extending skills (moltis.org)
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.
32 comments
[ 2.4 ms ] story [ 57.0 ms ] threadOne pain point I have with openclaw is compaction. It uses so many tokens that compaction happens often - but I'd say it's not great at keeping the thread. I think this could be a nice little benefit you offer folks if you can get higher quality continuity.
- Cybersecurity (you can't expect a non-technical person to read a skill)
- Token usage (without a flat fee subscription it'll become expensive very fast)
I understand that security is a hard problem to solve but having a single binary + containers should definitely help! I'll definitely keep an eye on this.
ps. One can use mistral’s API through liteLLM.
Though, I am looking forward to the next generation of AI agents that aren't named after a lobster
You seem to have a good sense of what you want to do, and a manageable queue of bugs and PR's, but this projects has so many dimensions/large feature surface, you/one could get lost chasing everything or dealing with feedback and help. Any guidance? Just fix bugs we bump into?
I've really been enjoying it. Heavily added onto my fork already. Not at all because it wasn't good already, exactly because it is so it's worth building on top of!
I tried fixing bugs in some alternatives but there were just so many and it felt like a losing battle.
I'll definitely be submitting some (more) PRs in the future. I've pushed one upstream so far for review, but I have a lot more ready to submit later on.
Again, thank you so much for making this! Stellar work!
What are some actually useful use cases and how would I install them? This seems like the missing piece.
Very cool build though, will try it out
I see that not all models available in my Github subscription are available (all models should be visible).
Further, is it possible to use openrouter with the current implementation? I couldn't figure it out by reading the documentation alone.
Thank you!
how are you handling the trust boundary for self-created skills? thats usually where things get tricky.
also curious about the memory architecture. file-based memory (like markdown files the agent reads/writes) has been surprisingly effective in my experience compared to fancy vector DB approaches. simpler to debug, easier for the agent to reason about, and way less infrastructure overhead. whats your approach?
At least in the Claude model, there's nothing a skill can do that the model couldn't already do? Isn't it still the same tool calls underneath, with the same permissions?
Think of skills as plugins providing AGENTS.md snippets and a subdirectory of executables, as if those were part of the workspace to begin with.