Comment by fragmede
12 hours ago
How do I get it to fix my Bluetooth if I do that? If you've been AI-pilled, 2026 is the year of Linux desktop because instead of dicking around with config files, I can just tell AI to fix python.
12 hours ago
How do I get it to fix my Bluetooth if I do that? If you've been AI-pilled, 2026 is the year of Linux desktop because instead of dicking around with config files, I can just tell AI to fix python.
> How do I get it to fix my Bluetooth if I do that?
Manual tool calls. I ask AI to give me all the necessary reconnaissance commands, then I run them myself on the host and paste the output on the terminal with the SSH connection into the guest virtual machine where the harness is running. The AI then either figures it out and gives me the answer or runs additional tool calls by me. Repeat until annoying task is done, interrupt if anything suspicious shows up at any point.
Or just give it shell and it dies it all by itself
If you want to be security conscious don’t give it access to your system directly. Ask it to guide you through the information gathering part of the problem solving process and use your brain and judgment if it actually needs the information/data it’s attempting to access.
If you can’t make that judgement call because of lack of knowledge/familiarity it’s okay - spawn a new fresh chat, get up to speed on the topic first and then resume.
That way you accomplish three things: you learn something new, you fix your problem and you don’t let a Trojan do whatever the hell it wants to your box which among other thing contains all the browser sessions and cookies :)
pi.dev, local model, (RAG-ed) copy of archwiki. You are more able than you believe. Already now, no permission needed.
How is Hermes different in that regard?
Also note, that RAG and even vector search are more paths of the early days that didn't prove too valuable. Just let your agent search it directly and optionally create an index as a default entrypoint for common topics.
Fair points. Agreed.
They're talking about letting the agent access the bluetooth stuff, not about where to get information/knowledge from.
Literally the same security risk.
Bluetooth is the one thing I had problems in the past on GNU/Linux, Windows, macOS, Android and iOS. Linux is the only mentioned platform where you could technically give Codex root and let it fix it :)
I guess OpenBSD is the only OS where I never had any problem with Bluetooth audio.
Recently I had some crashes on my system and claude correctly diagnosed it to a broken SATA cable on my hard drive. That was really practical
I haven't had bluetooth issues in years, but I did have an agent reverse engineer a smartphone app that was required for programming some BT headphones. Now I can push my desired runtime settings automatically to the headphones when they connect to my computer
So, yes, I would say agents are pretty good at working with Bluetooth on Linux
My bluetooth jusy works actually. By the way I use arch
Use NixOS, only give your model access to the config in a git repo, zero access to the actual host machine.
That is also what I do now (both with NixOs and Guix Os), both for personal computers and for servers.
- I inspect the agent's changes, and only apply them - at once - if they are OK. So I have no half applied bad changes to my system, and I can catch critical mistakes before they are applied.
- I can roll back the changes by just doing a `git revert` and reapplying
- The agent cannot read secrets or unrelated data, just config.
- The agent gets the full configuration of all systems at once, without having to maintain parallel documentation (which can get out of sync) or rediscover each time from scratch (access my running systems, for example with `ssh root@server`).
- It's harder for the agent to miss some aspect of the configuration, because it's all in my dotfiles. If it's not there, it's nowhere
I just use a local model; its too dumb to hack into NSA just to fix my bluetooth.