Hello, Lemmy enjoyers. I’ve been working on LunarWing, a FOSS agentic software framework written in Rust that’s designed from the ground up to be fully self-hosted. No cloud dependencies, no SaaS, no phoning home. It runs entirely on your own infrastructure. LunarWing has a heavy prioritization of local models which route over a local routing gateway (Tensorzero)
The core ideas I want to highlight here for brevity:
- AI agents connecting to private, secure communication channels like DarkIRC (an encrypted p2p overlay network) or self-hosted XMPP with OMEMO.
- Genuine value for secret preservation. The only other project that takes this seriously at all is NearAI’s Ironclaw.
- a genuine unique take on AI agents, what they are, and what defines them
- REAL GENUINE SYSTEMS LEVEL ENGINEERING to make everything stable and robust!
It has built-in secret management with specialized credential handling for Postgres and LibSQL backends, and a WASM plugin system so you can extend agents with your own tools without touching the core.
Additional things you may be interested in:
- Works (with tools) with any local model inference on consumer GPUs (I can run an entire multi-tenant instance on another machine on my LAN with 3 actual tenants with their own scheduled routines all on a PNY RTX 4090 with llama-server, routed over tensorzero without the need of a proxy or functional tool calling middleware)
- Uses docker by default now for the multi-tenant admin setup harness, but podman support is being tested and should be included within the next release or two
- AGPL-3.0 licensed, no CLA, lunarpunk ethos
I’ve also been working on some new incredible self healing capabilities that I’m gradually rolling out over the next few releases.
Multiple Disclaimers Here: It’s a hard fork of NearAI’s IronClaw with significant divergence since < IronClaw 0.1.23. I started this Febuary initially designing custom tools and channels in Rust for Ironclaw itself and kept a local branch that I’ve been making a myriad of changes ever since, long before deciding to hard fork and make this an official project). I’ve been running it on my own homelab for months as my daily driver and across multiple testing environments. I reference “We” in the documents but I’ve been working on this all by myself, sharing it to a few close friends and family, and hoping that more people discover the project and begin to contribute. I am especially interested in those with more Rust experience than I have who can help provide polish, modernization, and suggestions on which libraries I can completely throw away now that I’ve stripped much of the proprietary channels and extensions from the core project. I believe LunarWing is unique in multiple ways that other projects cannot match. I’ve not shared the project across other communities yet. I figured the fediverse would be a good place to start.
Website: https://lunarwing.org/ Source: https://github.com/LunarWingOrg/lunarwing IRC: #lunarwing on irc.libera.chat (port 6697, TLS)
Happy to answer any questions about the architecture or setup. I’ll periodically check back on lemmy this week. I would especially be interested in discussion of my plans further down the line to improve LunarWing, including the new features and changes I would like to make. I am open to suggestions as well. I have a small roadmap document in the docs section of the repo as to what I want to add for the foreseeable future. you can take a look at that too if you want. I’ve also been trying to keep up with the documentation of known bugs as well as the fixes for each.
PS: I’ve recently written a short blog post about the importance of local models and tooling here:
https://blog.lunarwing.org/2026/06/14/the-dark-forest/
I will periodically create new blog posts detailing the direction I would like to take LunarWing at https://blog.lunarwing.org/
The next blog post will be about my proposed self healing architecture I was explaining earlier (it’s something quite unique to LunarWing)
What’s the security model and permission system like? Can I run this as my regular user, or can this nuke my projects directory or pull random code from the internet and execute it like most of the other agents?
filesystem access is something you can choose to give it, but the security model by default doesnt allow this. you can enable certain flags within the database that could allow local filesystem access to use tools specifically designed for that but that is not anything the agent can do by itself. This is an example of a “developer tool” and its not something I use at all outside of a single tenant instance on a raspberry pi 5. Sandbox and worker containers are preferred. The agent’s memories, routines, settings exist within a database, not on a file system. a basic internal shell can be “emulated”, but for advanced tasks, that’s what the sandbox or external workers are for. That being said, feel free to use the mt admin script to automatically create users anyway for multi agent setups. it takes care of linger, adding the user to a docker group, and so on. Permission system is incredibly robust AND customizable. The default permissions are generally sane though: Tool calls need explicit approval by default and approval prompts pause other agent activity in the agent loop in the conversation thread. Up to you if you want to pass “always approve” to specific tools