FOSS Weekly #26.33: Mint Kernel, PDF Editing, VLC Drama, Omarchy Quattro and More Linux Stuff

Linux Mint is getting automatic old kernel cleanup in the next release, a feature Fedora has handled through DNF's installonly_limit for years. And I did not even know that Mint doesn't do it.

The Document Foundation has put up a write-up (part 1 for now) of how the Austrian Military migrated 16,000 PCs from Microsoft Office to LibreOffice. The part worth noting is that ~8,000 users installed it on their own before it was mandated. Now that's a pleasant surprise.

CachyOS released their August update, and the two things that stand out are Shelly v3 and the Server Edition groundwork. Running a cutting edge distro on a server? Old school sysadmins will shiver at that thought.

Apparently, VLC takes around 30 seconds to play an MP3 on Windows. But don't blame VLC when it is Microsoft's fault.

Proxmox VE now officially runs on ARM64, with the same codebase, release cycle, and support window as the x86-64 build. NVIDIA Grace and Vera systems are fully validated, and other UEFI-based ARMv9-A hardware gets best-effort support.

An open source project called Xodus is working through the hardest parts of bringing Xbox Game Pass to Linux. They have already figured out Xbox authentication and game downloads.

KGamma is getting a Wayland replacement that works with Night Color, supports independent per-monitor values, and applies settings on the first frame.

Illinois signed the Children's Online Social Media Safety Act, which requires device makers and OS providers to collect a child's age bracket at setup and expose it via an API for apps to query.

Omarchy Linux is going all in one with AI with its version 4.0 releasing this week.

There are a few more AI-related stories that we covered this week. But I am not going to include all of them here. They get covered in the Local AI Weekly newsletter, and you can also read them if you follow the feed. I'll try to keep the AI buzz to the necessary minimum in FOSS Weekly.

🤝 This edition of FOSS Weekly is supported by TuxCare.

Rebooting after a kernel update is frustrating and results in downtime. Critical infrastructure should not suffer from reboots. TuxCare allows you to patch Linux kernels live. Works with more than 60 distros.

Explore TuxCare

🧠 What We’re Thinking About

I had a good chat with Bianca Lewis, OpenSearch's executive director, talking about how OpenSearch has spent the past few years trying to shed the "Elasticsearch fork" label.

🧮 Linux Tips, Tutorials, and Learnings

A beginner's guide to installing software from source on Linux. It covers clone, configure, make, where to install things so cleanup isn't painful, and how to fix the missing compiler errors you'll almost definitely hit the first time.

A decade of hopping through Mint, Ubuntu, Kali, Arch, AntiX, and EndeavourOS, and the conclusion is that it was never really about the distro.

Six backup tools for different kinds of Linux users. The highlights include Déjà Dup for GNOME desktop with zero setup, Kopia if you want an open source GUI, Restic and BorgBackup for terminal-native control.

If you regularly deal with PDF, try a tool like PDF Arranger that allows you to split, merge, rearrange PDF docs.

In the same regards, in the situation where you have to convert multiple images into a PDF, use LibreOffice or gscan2pdf. I do this when I have to upload IDs and documents to a government portal.

👷 AI, Homelab and Hardware Corner

This corner may still have some local AI stuff for now. A practical setup guide for running Hermes agent on a Raspberry Pi as an always-on backend while controlling it from a laptop using Hermes Desktop's remote gateway feature.

🎓 Linux Foundation certification offer

Linux is turning 35 this month. The Linux Foundation, the official organization behind the Linux kernel project, has a catalog of industry-oriented training and certifications.

And they are offering 35% off on all of it, including the instructor-led classes that contain very technical topics like performance tuning. Popular certifications like LFCS and CKDA

Explore Linux Foundation Offer

✨ Apps and Projects Highlights

Censor is a PDF document redaction tool. When you want to hide part of information from a PDF, you can use this tool.

📽️ Videos for You

Enjoy customizing GNOME desktops with extensions. Take a look at some of the good ones in action in this video.

Subscribe to It's FOSS YouTube Channel

Desktop Linux is mostly neglected by the industry but loved by the community. For the past 14 years, It's FOSS has been helping people use Linux on their personal computers. And we are now facing the existential threat from AI models stealing our content.

If you like what we do and would love to support our work, please become It's FOSS Plus member. It costs $49 a year (less than the cost of a McDonald's burger a month), and you get an ad-free reading experience with the satisfaction of helping the desktop Linux community. And there are also free Linux ebooks.

Join It's FOSS Plus

💡 Quick Handy Tip

Ubuntu's Tiling Assistant has an experimental layout editor, which allows you to create tiles and assign windows to those tiles. First open the Extensions app and go into the settings for "Tiling Assistant."

Here, click on the "i" button and go into "Advanced..." and enable "Advanced/Experimental Settings." Now, inside the new "Layouts" page, you will find multiple layout entries without keybinds assigned.

Click on the "Disabled" box and enter a keybind, and use the downward arrow nearby to fine-tune the layout.

Once these are set, whenever you press any one of those shortcuts, any open windows can be opened in that layout for you. You can read how it works in the official documentation.

Local AI Weekly will start from first week of August. If you are interested in learning about open source AI, please subscribe to our upcoming Local AI Weekly newsletter.

Subscribe to Local AI Weekly

🎋 Fun in the FOSSverse

Our Scrambled Linux Editors crossword will test your grasp of Linux editors.

Those pesky clankers sure do know how to trick us. 🤖

🗓️ Tech Trivia: On August 5, 1858, Cyrus West Field succeeded on his fifth try at laying a telegraph cable across the Atlantic. Queen Victoria and President Buchanan traded congratulatory messages soon after. Though the celebration was short-lived, as the cable died within a month.

🧑‍🤝‍🧑 From the Community: Pro FOSSer Xander is asking other FOSSers what they like about Linux; do you have anything to add?

from It's FOSS https://ift.tt/cKBXutz
via IFTTT

Omarchy Bets Its Future on AI Agents While the Linux World Stays Cautious

The world of open source is split when it comes to AI, while a big project like Linux is seeing its leader warming up to it, telling those who object on the mailing list that Linux "is not one of those anti-AI projects."

Projects like Rust, GCC, and Codeberg are going the other way, banning AI from writing meaningful chunks of their code, though none of them draw that line in quite the same place.

Omarchy doesn't care about any of that. Its upcoming release, Quattro (4.0), is skipping the debate over whether AI should write code and is building AI agents into the desktop itself.

As a refresher, the project calls itself a "Beautiful, Modern & Opinionated Linux," and the opinionated part shows up in how the distro configures itself with minimal input from the user during installation.

Its creator, David Heinemeier Hansson (DHH), has now decided that AI agents belong in the defaults too, saying that this is how they will "truly democratize Linux," and predicting that Linux adoption among developers is going to explode.

Enter, Quattro

While Omarchy 4.0 is still in the beta stage, DHH is calling it their biggest release yet.

He is teasing all kinds of new agent-facing features, such as a crash watcher that briefs your AI agent the moment something breaks, a dedicated agents usage widget, and nine different agents to pick from.

The crash watcher is the one DHH teased on X first. Let's say a process crashes. Omarchy catches it off the systemd-coredump journal and pops up a toast. Click it, and your default agent gets briefed on the whole thing through a diagnose-crash skill built to make sense of the backtrace.

Don't worry, it still asks you for confirmation before reporting anything upstream, and it checks for duplicates too.

Quattro also lets you pick a default coding agent under Setup > Defaults > Agent, giving you nine options that include the likes of Claude, Codex, Gemini, Grok, and Copilot.

None of them come pre-selected either. During first boot, a notification nudges you to pick your default agent, and if you skip it, the agentic features stay disabled.

I briefly took a Gemini-powered AI agent for a run.

When I configured Gemini using an API key, I asked the agent what it could do for me, and it said that it could help with Linux configuration and window manager setup through Omarchy.

It also brought up crash diagnosis using the same diagnose-crash skill from earlier, on top of the usual code reading, writing, and command execution any coding agent handles.

There's even a model-usage widget that tracks usage against weekly limits, though it is only available for Claude Code, Codex, Pi, Oh My Pi, and OpenCode sessions.

And, if you go looking through the contributors list for the project, you will see that Claude has contributed a fair bit, further cementing where Omarchy as a project is headed.

Not everyone will be happy

It's been really cool to see the development of Omarchy, but unfortunately, I will not be updating to v4

Omarchy allowed me to take the leap of faith from MacOS to Linux and point me in the right direction

But now I've come to the point where I just need a terminal, a browser,… https://t.co/IZRYE5uifP

— IroncladDev (@IroncladDev) August 12, 2026

Depending on where you stand on AI, this is where people start picking sides. One of them, a developer who goes by the name IroncladDev, has decided they won't be updating to 4.0.

He says that Omarchy is what got him off macOS and onto Linux in the first place, but that's not enough to keep him around for Quattro. His issue is that he isn't interested in any of the "AI/Agentic additions." He just wants a terminal, a browser, and working USB ports, nothing more.

That kind of pushback was inevitable. Move a distro this hard, this fast, and you lose the people who signed up for something simpler. Baking agents into the OS is a bigger ask than a new theme, and DHH made that call for everyone whether they wanted it or not.

Closing thoughts

I believe that DHH is making a well-timed call before the rest of the ecosystem catches up. Omarchy went with Hyprland back when tiling window managers were a niche pick. Betting Quattro on AI agents looks like the same instinct that's paid off before.

While many open source projects are left arguing whether using AI and providing AI-focused features is a good call, Omarchy looks to be on track to become something we can call an "AI Linux distro."

from It's FOSS https://ift.tt/FQ81DYm
via IFTTT

VLC is Wrongly Blamed for Microsoft Defender's Clumsiness

It all started with a tweet by video game designer Jonathan Blow. Blow is the developer behind games like Braid and The Witness.

He mentioned that he had stopped using VLC on Windows because it took about 33 seconds to start playing a simple MP3, and he had switched to Microsoft Media Player instead.

Finally switched *away* from VLC *to* Microsoft Media Player, because VLC now takes 33 seconds to start playing an mp3 after clicking on it.

A large sector of open source software is in a truly embarrassing place now... pic.twitter.com/237aLdx2fG

— Jonathan Blow (@Jonathan_Blow) August 12, 2026

And he also shamed open source software, framing it as a sign that large part of open-source software is in bad shape.

A large sector of open source software is in a truly embarrassing place now...

This quickly turned into a heated discussion, with people joining from both sides.

VLC's official Twitter account clarified that this delay was not a core VLC regression but a side effect of a Windows 11 / Microsoft Defender update that quarantined VLC’s plugin cache. Their suggested solution is reinstalling VLC or regenerating that cache.

Jonathan argued that it is the developer's responsibility to fix. He cited his own experience of fixing an issue caused by AMD in his game Braid.

Linux user jumps in with solid evidence

A Linux user who goes by the X account @VoxelPrismatic jumped in with concrete evidence that it is not a core VLC issue but a Windows issue.

In this tweet, the user shared a recording of what seems like a Linux distro running KDE. Recording clearly showed VLC started playing an MP3 file in 1-2 seconds.

sounds like a windows issue ngl pic.twitter.com/9Icp2Sf58M

— PRIZ ;] (@VoxelPrismatic) August 12, 2026

But some people were still not satisfied because VLC being slow to open MP3 files on Windows is a real issue but they kept on blaming it on VLC.

The solution to the problem

VLC suggests the following fixes

• Regenerate the plugin cache (e.g. launch with vlc --reset-plugins-cache, or clear VLC’s cache under the user profile and relaunch)
• Reinstall VLC from the official build

However, a better suggestion came from a few users who noted that excluding vlc.exe in Microsoft Defender solves this problem. And I like this one better because it seems to address the problem where it originates, Microsoft Defender. And if the cache builds up, VLC may be slowed down again (I think).

The same was vouched by several people. So this sure looks like the workaround worth trying.

Asking the right question

Among all this, someone asked the real question; how come VLC not working for a single person becomes "a large sector of open source software" being an embarrassing place?

Blame Defender, not VLC

I understand the frustration. Waiting half a minute to play an MP3 should not be acceptable on a modern system, even if it is on Windows.

It is also okay to blame it on VLC when you don't know the real backstory and are unaware of the root cause.

But giving it a “open source is broken” narrative is highly far fetched.

I haven't tested it myself. Not going to jump into Windows just for this, but from what I see, the onus of fixing it lies on the Microsoft side. And from what I know about Microsoft, they won't do a thing.

What's your take on this episode? Share it in the comments.

from It's FOSS https://ift.tt/m0LxNP2
via IFTTT

SimpleX Chat Wants Its 400K+ Users to Become Investors Too

The world is in a messed-up state where surveillance and eroding people's rights are rewarded, and those who oppose are labeled unpatriotic, anti-national, radicals, criminal sympathizers, and what not.

Yet, that doesn't stop people from investing time and money in securing their data by opting for open source mobile operating systems like GrapheneOS and taking steps to improve their privacy in the online world.

One of those steps is to go for a private messaging app that doesn't give out your data to feed some AI or a governmental agency that asks for your data nicely. SimpleX Chat is one such option, a messaging network that doesn't ask for phone numbers, emails, or user accounts.

I tried it out myself back in 2024, and it left a strong impression. The team behind it has kept building since, and now it wants its users to also have a stake in where the project goes next.

Looking for investors

The founder of SimpleX Chat, Evgeny Poberezkin, reached out to us recently, saying that they were looking to give users "the opportunity to get a stake in SimpleX Chat and benefit from its growth."

That stake comes through a SAFE, short for Simple Agreement for Future Equity, live now on Wefunder.

The first $450,000 invested gets an Early Bird SAFE with a $40 million valuation cap. Once that fills up, later investors get a separate SAFE instead, this one at a $45 million cap.

There's a wrinkle though. Your money doesn't go straight into a SAFE with SimpleX Chat itself. It goes into an SPV, which is the entity that actually holds the SAFE, and your signature ends up on the SPV's own Subscription Agreement instead.

So this comes up as one version for early money, another for everyone who invests after.

The campaign's friends-first soft launch closes August 15, and as of August 11, it had already raised 50% of its target offering amount.

The company behind the app isn't quite what it used to be either. SimpleX Chat Ltd, the UK entity that built the app, is now a wholly owned subsidiary of a new US company, SimpleX Chat, Inc.

Keep that in mind if you consider where a firm is based out of before investing in it.

If the campaign only clears its $50,000 minimum target, the money would go toward covering general operating expenses, just enough to keep things running a while longer.

Hitting the full $1,235,000 target would mean they could hire additional team members, build out a browser-based messaging stack, provide tools for publishers, and work on a framework for interactive widgets.

The company also expects server hosting costs to fall as more independent operators take over network infrastructure, while planning to break even using revenue from public names, business services, and what it calls Community Credits.

That is a model for getting large channels to pay for the servers they use.

Before you go ahead and invest, do understand that this comes with the usual risks of backing a company this early.

There's no guarantee of a return, and what you invest isn't something you can sell easily if you change your mind. The company's own filing goes further, stating it doesn't expect to have enough cash to keep running for the next 12 months without more funding.

A similar occurence

We already had an instance of a messaging app asking its community for help earlier this year, where Session nearly shut down after it ran out of funding, needing $1 million to keep going.

By June, the foundation confirmed development had resumed, backed by two to three developers instead of the dozen-plus it once employed.

SimpleX Chat's own filing admits it doesn't have enough cash to keep going for the next 12 months without more funding either. Raising money through equity now, rather than an emergency donation drive, gives it a strong start.

from It's FOSS https://ift.tt/NAzblx7
via IFTTT

These Open Source Devs Are Reverse-Engineering Xbox Game Pass for Linux

Xbox Game Pass has never really worked on Linux beyond laggy cloud streaming, but an open source project called Xodus is trying to change that.

Earlier this week, replying to a thread on Reddit, Paweł Lidwin (imLinguin), project lead of Xodus, confirmed that the hardest parts of running those games on Linux, Xbox authentication, and game downloads are already working.

The project is attempting to reverse engineer Xbox's entire authentication, licensing, and delivery pipeline well enough to run Xbox on PC and Game Pass titles on Linux.

What's Xodus?

Xodus describes itself as "the great gaming migration to Linux," while cautioning people that it is not endorsed by Microsoft and using it comes with risks. You see, modern Xbox PC games run on Microsoft's Game Development Kit, or GDK, and ship as encrypted⁣ MSIXVC packages.

Getting a game running on Linux means handling both.

The project's GitHub page currently houses a handful of repositories that include the main xodus client written in Rust, a forked ntfs library for reading MSIXVC, and xgameruntime, an open source implementation of xgameruntime.dll built for use in Wine.

A companion repo, xgameruntime-docs, documents how that same DLL works internally.

There's also forked copies of Wine and Proton, maintained by the Xodus team, featuring custom tweaks, and xal-rs, an Xbox authentication library forked from OpenXbox.

Keep in mind that there are no binaries available for you to play around with just yet; there's still a lot of work to be done.

So yeah, a First Look at Xodus is still months away. 😆

The devs are surprised

Thanks to that Reddit reply, the project has gotten a wave of press coverage, and it has caught the developers off guard. "Quite unexpected," wrote Paweł on the project's Discord server after Digital Foundry picked it up.

Though the original coverage seems to have been from VideoCardz.com, many of the outlets out there have got a detail wrong. Describing Xodus as a project from the Heroic Games Launcher team is not right, as Paweł is the only Xodus contributor who has also worked on Heroic, not the whole team.

Another contributor, BellezaEmporium, who has been busy tracking this surprise wave of coverage, points out that one of the articles has been quite salty in talking about Xodus, while Olivia (olivi-r) shared some important developmental updates.

She says that:

Progress has been fairly rapid the last few days on the xgameruntime side, XTaskQueue is nearly implemented with a few modes and quirks to sort out.

Currently fixing XUser as it seems the signature generation is a bit messed up 😬

Still need to actually load tickets from xodus into XUser as well, I've been hardcoding mine for the testing, not sure if we're going with the stdio proxy or ipc implemented directly in wine yet.

What now?

If Xodus pulls this off, it closes one of the last major gaps between Linux and Windows gaming. Game libraries on Steam, GOG, and Epic Games already run well through Proton and Heroic, but Xbox PC and Game Pass titles have been locked to Windows or laggy cloud streaming until now.

And, if you ask me, this is the right time for Xbox to make Xodus' job easier by lending a hand, similar to say how Valve has handled the development of Proton while supporting Wine and DXVK upstream. This way, the whole ecosystem benefits, not just Steam.

If Xbox decides to help the project, then they do have many avenues to pursue…

from It's FOSS https://ift.tt/pbQKLA0
via IFTTT

Local AI Weekly #1: It's Happening

Welcome to the first issue of Local AI Weekly. A lot of It's FOSS readers have been curious about local AI but didn't want it mixed into FOSS Weekly. So here we are. A separate space for people who want to explore AI but the open source ones.

I'll be sharing experiments from my own hardware, open model news, tools worth your attention, and will keep an eye on the AI related news worth knowing. Let's get into it.

🧪 Experiment: Hermes on a Raspberry Pi

Hermes is the buzz of the AI town so I decided to give it a try. But I chose a rather unusual setup. I have the Hermes backend running on a Raspberry Pi and connecting to it via Hermes Desktop on my main machine. So the agent actually runs Pi, and I interact from my computer.

Hermes Desktop also has a voice conversation feature, most AI tools have it these days. Voice AI is shaping up to be the next big thing. Ubuntu 26.10 is already preparing native voice AI support and local tools like Vocalinux are already in development.

Seems like we're not far from AI-based desktop companions you can actually talk to. Think email briefings, task reporting, agent control. Those things are already here, even if in early stages.

🔍 Discover AI tools

Here is a new open source markdown-based knowledge base built for you and your AI agents. It is local-first, git-backed, and ships with a native MCP server, so commercial or local AI agents can read and write your notes directly.

Worth a look if you're building a personal wiki or a shared second brain your coding agents can use across sessions. Still in early stages of development, so expect bugs here and there. I am currently using Tolaria for my personal KB, and this one is my on my weekend activity list.

Another interesting open source AI tool I came across recently is Cleat. It basically runs Claude Code inside a Docker sandbox with one command, so an autonomous agent session can't touch your host system. It shares your Claude auth, edits project files, installs packages, and runs any command inside the container, but stays blocked from your SSH keys, other projects, and the rest of your machine unless you opt in.

The project is fairly new, and I don't see activities on its GitHub repo in the last three weeks. Hope it is not on the road to become an abandonware.

📡 Open Model News

The open model space has had a busy few weeks.

Kimi K3 landed on July 16 from Moonshot AI. It's a 2.8-trillion-parameter Mixture-of-Experts model with a 1M token context window, released under a "Modified MIT license". It's the largest open-weight model ever released, and early benchmarks are putting it within reach of frontier closed models. Running it locally requires serious hardware, but smaller distillations should be here soon.

Around the same time, Inkling was released by Thinking Machines Lab, the startup founded by former OpenAI CTO Mira Murati. It's a 975-billion-parameter multimodal model released under Apache 2.0. The Apache 2.0 choice is significant because it means free commercial use without the usage restrictions that come with some other open licenses, like the modified MIT.

Both are too large to run on most home hardware right now. But these releases matter because quantized versions and smaller distillations typically follow within weeks. Worth keeping an eye on Ollama's model library, even though Ollama is likely offering them on their cloud plan.

🗂 AI Jargon: Quantization

You might have come across the word quantization. It is the process of reducing the 'numerical precision' of a model's weights to make it smaller (and faster). A full-precision model stores each value as a 32-bit or 16-bit float. A quantized model stores them at 8-bit, 4-bit, or even lowre. The model gets smaller so it uses less RAM, and runs faster but that comes at the cost of quality.

Take a look at the tags of any model at Ollama... llama3.1 for example. You'll see names like instruct-q2_K, text-q3_K_S, fp16 etc. Those are quantized. The file size is smaller, an indication that it will need less RAM.

⚡ Quick Tip

When downloading models via Ollama, you can specify the quantization level directly. Instead of ollama pull llama3, try ollama pull llama3:8b-instruct-q4_K_M to get a specific quantized variant. Check the available tags on ollama.com/library for whichever model you're pulling. Just add /tags/ at the end of it.

And we continue...

I'll be honest. The local AI scene is more fragmented than the Linux distro landscape. And not all of us have the same needs. If you're a DevOps person, you might have no interest in AI image restoration tools. If you're a developer, graphics workflows probably don't apply to you.

So I'm going to share my own experiments and exploration. Some of it will be useful to you, some won't. That's fine. You'll likely learn new things and that's the goal.

See you in two week.

from It's FOSS https://ift.tt/WRiYc34
via IFTTT

Run Hermes on Raspberry Pi, Control It from Your Laptop

My agent harnessing journey started with Nanoclaw. Which is super simple to setup and use. It works for a few simpler tasks through Telegram.

But I wanted something to work on my main computer. Out of all claw like agents, I find Hermes the most suited.

So I installed Hermes on a Raspberry Pi running on Pironman 5 Pro Max. And I installed Hermes desktop on my Asus Zenbook laptop, my primary system.

The advantage is that the Raspberry Pi remains the always-on Hermes machine. I can close Hermes Desktop or shut down the laptop without needing Hermes itself to run on the laptop (for scheduled tasks). Also, Hermes agents won't have unrestricted access to my system. A safer approach, in my opinion. At least, that's the idea I am going with.

The basic architecture is:

Laptop
└── Hermes Desktop
        │
        │ Remote Gateway
        ▼
Raspberry Pi
└── hermes serve
    ├── Agents
    ├── Jobs
    ├── Memory
    └── Tools

Let me show you how you can use the Hermes agent via the remote gateway feature.

Step 1: Start the Hermes Gateway on the Raspberry Pi

🚧

I presume that you have already have Hermes agent installed on Raspberry Pi or any other remote system you can reach from your other system.

Open a terminal on the Raspberry Pi or SSH into it.

You need to add the following in the ~/.hermes/.env file of hermes:

HERMES_DASHBOARD_BASIC_AUTH_USERNAME=admin
HERMES_DASHBOARD_BASIC_AUTH_PASSWORD=YOUR_STRONG_PASSWORD
HERMES_DASHBOARD_BASIC_AUTH_SECRET=YOUR_RANDOM_SECRET

The 'random secret' can be generated with.

openssl rand -base64 32

These credentials will be used from the Hermes desktop. Now start Hermes's backend with:

hermes serve --host 0.0.0.0 --port 9119

You may see a message like this:

Headless backend (hermes serve): web UI disabled — use `hermes dashboard` for the browser UI.

This is normal. hermes serve does not provide a browser interface. It starts the backend that Hermes Desktop connects to.

Keep this process running while testing the connection.

Step 2: Verify that Hermes is listening

Open another terminal tab to access the Raspberry Pi, and run:

ss -ltnp | grep 9119

You should see something containing:

0.0.0.0:9119

This means Hermes is listening for connections on port 9119.

Step 3: Install Hermes Desktop on the pc

Hermes provides an official script for installing the Hermes Desktop:

curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash

During installation, Hermes may ask to choose a terminal backend:

Select terminal backend:

Local
Docker
Modal
SSH
Daytona
...
Keep current (local)

For this setup, you can leave this as:

Keep current (local)

The Terminal Backend setting is separate from the Remote Gateway setting. The gateway is what connects Hermes Desktop to Hermes running on your Raspberry Pi.

I also left out the model selection. Whatever the remote Hermes server uses will be used here, too.

Step 4: Use remote gateway on Hermes

Start Hermes Desktop from the terminal:

hermes desktop

That's the way it runs for the moment. Ironical to run a desktop GUI app from the terminal.

Anyways, inside Hermes Desktop, click on the settings and go to gateway and find the remote gateway option:

In the Remote URL field, enter the address of the device running the Hermes backend with the port 9119:

http://<IP of Pi>:9119

Then save/apply the setting and reconnect.

Hermes Desktop should now connect to the Hermes backend running on your Raspberry Pi.

Hermes Desktop becomes the interface for interacting with the Hermes instance on the Raspberry Pi.

Step 5: Make the gateway permanent

If things are working fine so far, it is time to make things permanent. Because keeping this running on the remote Hermes server is not a wise move.

hermes serve --host 0.0.0.0 --port 9119

Because if I close that terminal or reboot the Raspberry Pi, the gateway will stop.

For an always-on Raspberry Pi setup, running hermes serve as a systemd service works better.

No need to SSH into the Pi and manually launch Hermes every time. It will be automatically start thanks to the systemd service.

Get the Hermes executable path with:

which hermes

And then create the systemd service:

sudo nano /etc/systemd/system/hermes-server.service

Here's the file I used. You should replace the EnnvironmentFile and ExecStart values as per your setup.

[Unit]
Description=Hermes Agent Backend
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=pi
EnvironmentFile=/home/pi/.hermes/.env
ExecStart=/home/pi/.local/bin/hermes serve --host 0.0.0.0 --port 9119
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Once you have saved the service file, run it in this fashion:

sudo systemctl daemon-reload
sudo systemctl enable --now hermes-server

Check the status of the newly created systemd service:

systemctl status hermes-server

Conclusion

I am yet to fully utilize Hermes on desktop with the remote gateway method. Portability could be an issue if I move out of my home network, but even in that case, there are ways to SSH into Raspberry Pi from outside network.

I'll be sharing more of my local AI exploration and experiences. Do subscribe to Local AI Weekly newsletter for that.

from It's FOSS https://ift.tt/gpXdYxA
via IFTTT