CLI LLM Tools Made Linux Fun Again For Me

By | May 16, 2026

I Discovered Linux When I Was in High School

It took me twenty years to make Linux my daily driver. Not because I did not want to. Because every time I tried, something stopped me. A missing driver, a configuration file I could not decode, a game I wanted to play, some piece of software my livelihood depended on that only ran on Windows. I would install, struggle, reach the limit of my patience, and reformat back to safety. Then a year or two would pass and I would try again, convinced that this time the ecosystem would be ready. It never was.

Until this year.


The Weekend Install Loop

I discovered Linux when I was in high school. Slackware, Red Hat, and SuSE. I did not understand what I was doing, but I understood that it mattered. There was something about the idea of an operating system you could configure yourself, piece together yourself, break yourself.

I stayed over at a friend’s house and brought my computer with me. The whole thing. Tower, monitor, keyboard, mouse. We would install Linux in different flavors all weekend, splitting our attention across two machines, leaving one working so we could use dial-up to find documentation that barely existed. We did not know how to exit vi. We could not get things working. But we had books, we had time, and for reasons I still cannot fully articulate, we would just reinstall Linux over and over. Different distros. Failing to configure X. Celebrating when we could switch between virtual terminals and X Windows and Enlightenment.

XBill and some bubble-popping game were it for entertainment. I played a couple of MUDs that an upperclassman showed me in Speech class. He was super cool in my eyes. He played Master of Puppets in that class too. But I could never stay on Linux for any length of time. Everything I did was on Microsoft Windows. I would install Linux out of curiosity over the years, never sticking with it. There was always one thing or another I needed Windows for.

The Decade of Near Misses

When I started working on computers, my first job was on a Macintosh. Now that was an alien system compared to anything else I had used. MS-DOS, Windows 95, Windows 98. I skipped Windows ME thankfully, and then Windows 2000. When I learned about virtual machines in one of my first real jobs, I installed Linux again and Solaris this time as well. I have never met Solaris in the wild. Each time, Linux lasted a few days, maybe a week at most, before I reformatted back to Windows.

I did not understand what a man page was. I had secondhand books. I would go back to Windows, where a vibrant pirate ecosystem supported all manner of exploration. I learned how to use all the tools my employers would eventually pay for.

Years went by and I got another taste of Unix when macOS switched to a Unix foundation. I never understood the architecture, but I really liked using it inside my MacBook. I got so used to it that when I went back to Windows, I missed it. Mac still had most of my software and enough to work, but not everything. I stuck to Windows. I continued to install Linux as an idle curiosity, but always in a virtual machine. Safe. Isolated. Temporary.

The cycle decayed with each pass. Each install was a little less exciting, a little more resigned. I could get things running faster, but I also knew exactly how far I could go before hitting the wall. I stopped believing there was anything on the other side of that wall worth the climb.

What Changed

This year I decided to try again. Not in a VM. Not as a dual-boot I would never use. As my main operating system on a laptop.

I thought there would have been more changes, but the landscape is nearly the same. More package managers, more software, more drivers, and the same old configuration headaches. The kinds of things that used to stop me dead were still there: audio devices that would not route properly, touch screens that needed specific kernel parameters, backlight controls buried in sysfs, GPU configurations that fell apart after an update.

What changed is that I had local LLMs and CLI agents that could help me configure my machine. Everything that would normally have stumped me, taken hours, or led me to give up again was now something I could work through in minutes. Opencode became my wingbot. I would hit a problem, describe it in plain language, get a precise fix or a debugging strategy, apply it, and move on. The wall I had hit for two decades was not a knowledge wall; it was a feedback loop wall. I had no way to close the gap between what I wanted and what I knew how to ask. Now I do.

I still reinstalled three or four times. Some of it was my own impatience. Some of it was genuinely broken configurations I could have avoided with better planning. But I have been full-time Linux on my personal laptop for nearly four months now. It has everything I need. I had it help harden security by turning off services I did not know were running. Audio issues, touch screen problems, keyboard backlight settings, GPU configurations. None of them were obstacles. They were just tasks with solutions I could now reach.

Fun, Finally

Here is the part I did not expect: it became fun.

Not the grim satisfaction of finally beating a configuration into submission after six hours of digging through forums. Actual fun. The kind of fun I had in high school installing Slackware on a Saturday morning, before the failures stacked high enough to drain the enjoyment out of it. The difference is that now the fun does not stop when something breaks. Something breaks, I describe it to Opencode, it gives me a diagnosis and a fix, I apply it, and I am back to whatever I was doing before the fun was interrupted. The interruption is measured in minutes instead of weekends.

That changed everything. Linux stopped being a project I was perpetually failing at and became a system I actually used. I installed things because I wanted to try them, not because I needed to justify the install time. I configured services because I was curious, not because I was troubleshooting. I started looking forward to tinkering with the machine instead of dreading the next thing that would go wrong.

Usefulness followed naturally. Once I stopped fighting the OS, I could put it to work. I set up a local AI stack. I automated backups. I learned actual system administration because I wanted to, not because I was forced to. The grey beard competence I had spent two decades wanting to earn stopped being an aspirational target and became a side effect of having fun with the machine every day.

I did not need to become a Linux expert. I just needed the friction low enough that I would stay long enough to discover that Linux was useful on its own terms, not just as something to conquer.

The Part That Was Always There

The previous struggles probably helped, but they are not what made this stick. What made this stick is that everything actually works now. Not mostly works. Not good enough if I squint. Everything. Audio routing across Bluetooth and HDMI. The touch screen. The keyboard backlight. GPU switching. Sleep and wake. Printing. Scanning. Every peripheral, every service, every configuration detail that used to be a separate crisis.

I did not achieve this through accumulated wisdom. I achieved it by describing problems to Opencode in plain English and having it produce working configuration files, debug logs I could understand, and fixes I could apply without fully understanding the underlying subsystem. It turned every broken thing into a conversation instead of a research project.

The wall I hit for two decades was never really about Linux being hard. It was about the latency between wanting something fixed and being able to fix it. That latency was the real problem. With the AI tools, that latency collapsed to near zero. I would hit a snag, describe what I saw, get a solution, apply it, and move on within minutes. That speed changed the emotional calculus entirely. Linux went from something I endured to something I enjoyed.

I still reinstalled three or four times this year. Some of it was impatience. Some of it was genuinely broken configurations I could have avoided. But I have been full-time on my personal laptop for nearly four months now, and I am not planning my next reformat. I am not waiting for the other shoe to drop. There is no other shoe. The machine works. All of it.

The thing that kept me coming back all those years was not masochism. It was the sense that Linux was serious business in a way Windows never was. Grey beard programming. System administration. The kind of professional competence I did not have but wanted to earn. Even when I could not get it working, I knew the capability was there, behind a wall of arcane knowledge I did not possess. The wall is lower now because I have a guide. But the guide did not just help me over the wall. It showed me that on the other side, everything was already there, working, waiting.

I am just using the computer. For the first time, that is enough.


LLM Disclosure: This post was written with AI assistance for drafting and feedback.

Category: AI

Leave a Reply

Your email address will not be published. Required fields are marked *

Comment moderation is enabled. Your comment may take some time to appear.

This site uses Akismet to reduce spam. Learn how your comment data is processed.