lunarwingorg

joined 2 weeks ago
[–] lunarwingorg@lemmy.world 1 points 2 days ago* (last edited 2 days ago)

claude opus 4.8 doesnt even come close in terms of understanding how systems actually work or bothering to actually read existing code beyond the most cursory glance. the united states empire is truly over, as are these "premium" "flagship" closed weight Western models. Every so called mainstream "benchmark" publication is a bold faced lie where each company pays off the creators of each major benchmark publisher to tip the scales in their favor. Even when playing dirty, however, openai and anthropic still can't win.

[–] lunarwingorg@lemmy.world 1 points 3 days ago

it has anything to do with my external calibration stuff so no

[–] lunarwingorg@lemmy.world 1 points 3 days ago* (last edited 3 days ago)

I've actually been really trying to work on documentation lately, as well as get a lot of the old outdated docs removed/archived. I am still not 100% done but I've made a lot of progress with that, especially in this past week. Feel free to take another look at the in repo documentation for now. I'll also need to further update the main website at some point... there's at least two broken links and I'd like to add at least one additional page later.

 

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 heavily prioritizes models which route over a local routing gateway (Tensorzero)

The core ideas I want to highlight here for brevity:

  1. AI agents connecting to private, secure communication channels like DarkIRC (an encrypted p2p overlay network), self-hosted XMPP with OMEMO, and other various freedom respecting communication channels. Tools, channels, extensions, and bridges which connect to proprietary platforms, especially hosted by companies with nefarious intentions are intentionally unsupported as part of the main repository to ensure user freedom (You can read more about this on the project's README.md)

  2. Genuine value for secret preservation. The only other project that takes this seriously at all is NearAI's Ironclaw.

  3. a genuine unique take on AI agents, what they are, and what defines them

  4. REAL GENUINE SYSTEMS LEVEL ENGINEERING to make everything stable and robust!

For more information on my philosophy, you may read the MANIFESTO.md file in the repo.

More information about LunarWing:

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 rootless podman by default for worker containers and database

  • AGPL-3.0 licensed, no CLA, lunarpunk ethos. Will always be open and free. We support freedom.

  • Actual self healing capability that nothing else has, created by a professional systems engineer (Newest blog post is about this)

Multiple Disclaimers Here: It's a hard fork of NearAI's IronClaw with significant divergence since < IronClaw 0.23.0. This explains why certain things in the repository do not necessarily fit in with the stated philosophy. I've been gradually yanking out the egregious bits over time (Slack, Discord, Google extensions), little by little, to ensure stability. I will continue proceeding with this operation across each new release. I started this project in Febuary. I was 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 into an official project, for multiple reasons). 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 recently 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 many of the proprietary channels and extensions from the core project. I believe LunarWing is unique in multiple ways that other projects simply cannot match on a technical level (or straight up refuse to). Instead of spending time developing features that every other project does, I'm focusing on what really matters, while paying attention to what some other projects do correctly or seem the most useful and interesting. I focus on aspects of agentic software that most LunarWing rivals have not spent nearly enough time on. You could say I am fairly opinionated in the decisions that I make. I am hoping to find like-minded indiviuals who can also share some of these opinions on what an "AI agent" should be. This is my third lemmy post on LunarWing.

Website: https://lunarwing.org/ Source: https://github.com/LunarWingOrg/lunarwing Community Discussion: 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 personally recently written a very short blog post about the importance of local models and tooling here:

https://blog.lunarwing.org/2026/06/14/the-dark-forest/

It only briefly touches on my philosophy for LunarWing near the end, but the point is made.

I will periodically create new blog posts at https://blog.lunarwing.org/ to discuss the direction of the project, my philosophical thoughts, and more news related to LunarWing.

I appreciate the traction I have made across the other lemmy communities I've posted this too. I have browsed the locallama subreddit previously in the past and figured some of you may be interested in this.

Thank you for reading.

[–] lunarwingorg@lemmy.world 1 points 1 week ago

You are right. People do not care about agorism. But, Tailscale is not something that should be recommended. There are actual real self-hosted options like Netbird and Nebula.

[–] lunarwingorg@lemmy.world 2 points 1 week ago (2 children)

just the nature of them being quite old models without proper tool calling functionality. What actually DID help was setting up middleware and custom python servers/clients with proper json mapping to enable the proper tools to be selected. so, literally zero model tuning required in the end.

[–] lunarwingorg@lemmy.world 2 points 1 week ago (4 children)

unfortunately, i did not notice much of a difference with model tuning. it took a pretty decent chunk of time. For my most powerful pc, which is what I run most models (the lower end machines with worse gpus run embedded text models) I got a fairly powerful machine with a single 4090. I have had better luck just downloading differently tuned variants of the same model from others

[–] lunarwingorg@lemmy.world 1 points 1 week ago (6 children)

lora, yes. mostly custom scripts downloaded off of hugging face to automatically handle a lot of complicated stuff I'm not totally sure of how it actually works under the hood to be honest

[–] lunarwingorg@lemmy.world 2 points 1 week ago

you can try to ask the agent to talk like a pirate for example

[–] lunarwingorg@lemmy.world 2 points 1 week ago (2 children)

hermes has some built in agent orchestration layer which seems cool on paper. never tried it. other small nice things that are unique to hermes which other agents really don't have, which I have actually tried, include: switchable agent personalities, pretty decent thread suspension mechanism, decent webhook subscriptions, and human delay mode. The biggest thing, at least in my opinion, is certainly: Self-improving skills with patching - with an entire slew of caveats... In my opinion, this is useful but I strongly recommend using a manual review process. Otherwise, the agent has the potential to "teach itself wrong". Human review.

[–] lunarwingorg@lemmy.world 2 points 1 week ago

working on it this very evening. rootless podman support for each database and each external worker container. My openrc implementation is already working! implementing a systemd service implementation with timers instead of fcron as well as was planned. you want quadlets? quadlets will be supported too! and all of it will integrate with the new healthcheck and self-repair system

[–] lunarwingorg@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

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

[–] lunarwingorg@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

Yep, I got harnesses for the actual multi-tenant setup that support pre-seeded values and memory workspace data as well as testing harnesses to automate a lot of the developer testing. Additionally, I'm writing a chaos harness as well for chaos engineering tests in order to test the new self-healing feature

 

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:

  1. AI agents connecting to private, secure communication channels like DarkIRC (an encrypted p2p overlay network) or self-hosted XMPP with OMEMO.
  2. Genuine value for secret preservation. The only other project that takes this seriously at all is NearAI's Ironclaw.
  3. a genuine unique take on AI agents, what they are, and what defines them
  4. 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)

view more: next ›