Summarizer

AI for System Administration

Experiences using AI to diagnose and fix Linux server issues, permission problems, and system configurations, with claims that AI can one-shot complex failure scenarios

← Back to Codex for almost everything

Long-time system administrators are finding that AI models are revolutionizing the terminal by translating cryptic commands and dense crash logs into simple, natural language requests. Users report that advanced LLMs can frequently "one-shot" complex failure scenarios—such as socket overruns, corrupted route tables, and tangled permission issues—that previously required hours of manual troubleshooting. By drastically reducing the friction of system configuration, this shift towards AI-mediated "computer use" promises to make powerful operating systems more accessible to casual users while significantly increasing the efficiency of technical experts.

7 comments tagged with this topic

View on HN · Topics
Lots of scepticism here, but I think this may really take off. After 25 years of heavy CLI use, lately I've found myself using codex (in terminal) for terminal tasks I've previously done by CLI commands. If someone manages to make a robust GUI version of this for normies, people will lap it up. People don't want to juggle applications, we want computers to do what we want/need them to do.
View on HN · Topics
I agree. As a long time linux user, coding assistants as interface to the OS has been a delight to discover. The cryptic totality of commands, parameters, config files, logs has been simplified into natural language: "Claude, I want to test monokai color scheme on my sway environment" and possibly hours of tweaking done in seconds. My setup has never been so customized, because there is no friction now. I love it and I predict this will increase, even if slightly, the real user base of linux desktops.
View on HN · Topics
Heavily agreed - LLMs are also really good at diagnosing crash logs, and sifting through what would otherwise be inscrutably large core dumps.
View on HN · Topics
> lately I've found myself using codex (in terminal) for terminal tasks I've previously done by CLI commands. This is the real "computer use". We will always need GUI-level interaction for proprietary apps and websites that aren't made available in machine-readable form, but everything else you do with a computer should just be mapped to simple CLI commands that are comparatively trivial for a text-based AI.
View on HN · Topics
It repaired an astonishing messed up permission issue on my mac
View on HN · Topics
I did some work on an agent that was supposed to demonstrate a learning pipeline. I figured having it fix broken linux servers with some contrived failures would make for a good example if it getting stuck, having to get some assistance to progress, and then having a better capability for handling that class of failure in the future. I couldn't come up with a single failure mode the agent with a gpt5.x model behind it couldn't one shot. I created socket overruns.. dangling file descriptors.. badly configured systemd units.. busted route tables.. "failed" volume mounts.. Had to start creating failures of internal services the models couldn't have been trained on and it was still hard to have scenarios it couldn't one shot.
View on HN · Topics
SSH to devboxes is the exact usecase for services like https://shellbox.dev : create a box using ssh... and ssh into it. Now web, no subs. Codex can create it's own boxes via ssh