A Linux desktop built for working with AI agents. The claude, codex, opencode, openclaw and goose agents, Docker, Docker Sandboxes, QEMU with KVM and GPU runtimes are there on first boot, in a bootc image with atomic updates and automatic rollback. Zola 2026-11-04T00:00:00+00:00 https://agenticlinux.github.io/blog/atom.xml 2026-11-04T00:00:00+00:00 2026-11-04T00:00:00+00:00 Unknown https://agenticlinux.github.io/blog/apple-silicon-16k-variants/

<p>AgenticLinux now has variants for Apple Silicon Macs. On a Mac mini M1 that we switched to the KDE one, the kernel reports a 16 KiB page size, the Plasma login screen comes up, the Wi-Fi joins on its own, the GPU shows up in Vulkan as <code>Apple M1 (G13G B1)</code> on the Honeykrisp driver, and <code>claude</code>, <code>codex</code>, <code>openclaw</code> and <code>goose</code> start.</p> <p>This post covers what the <code>16k-</code> variants are, how they are built, how to switch to one, what went wrong on the way, and what we did not test.</p>

2026-11-04T00:00:00+00:00 2026-11-04T00:00:00+00:00 Unknown https://agenticlinux.github.io/blog/dgx-spark-support/

<p>AgenticLinux now runs on the NVIDIA DGX Spark. On a Spark running the KDE variant, <code>nvidia-smi</code> sees the GB10 GPU with the 580.196.07 driver, the Wi-Fi, NetworkManager and <code>sshd</code> come up on their own, and the agents run on a local Qwen 3.8 27B.</p> <p>This post covers the driver, the agents running on the Spark, how we installed AgenticLinux over the Spark’s stock Ubuntu, and what we did not test.</p>

2026-11-04T00:00:00+00:00 2026-11-04T00:00:00+00:00 Unknown https://agenticlinux.github.io/blog/introducing-agenticlinux/

<p>AgenticLinux is a Linux desktop built for working with AI agents. Everything is there on first boot: the <code>claude</code>, <code>codex</code>, <code>opencode</code>, <code>openclaw</code> and <code>goose</code> agents, a way to run them side by side, a way to watch their usage limits, and the container and GPU tooling they usually need.</p> <p>It is a <a rel="external" href="https://bootc-dev.github.io/bootc/">bootc</a> image. The whole OS ships as a container, so updates are atomic and rollback is one command.</p>

2026-11-04T00:00:00+00:00 2026-11-04T00:00:00+00:00 Unknown https://agenticlinux.github.io/blog/updates-that-roll-themselves-back-bootguard/

<p><code>bootc rollback</code> gets you back to the previous image, but only if you can still run it. An update that never reaches userspace, or reaches it and hangs, leaves you at a firmware prompt or an emergency shell instead.</p> <p>bootguard is the part of AgenticLinux that handles this. A newly applied deployment gets a limited number of boot attempts. If it does not come up healthy within them, the machine returns to the previous deployment by itself and remembers not to try that image again.</p>

2026-11-04T00:00:00+00:00 2026-11-04T00:00:00+00:00 Unknown https://agenticlinux.github.io/blog/why-tmp-is-not-a-tmpfs/

<p>The Fedora and CentOS Stream images AgenticLinux is built from use a tmpfs for <code>/tmp</code>, and AgenticLinux replaces it. <code>/tmp</code> is <code>/var/tmp</code> mounted over <code>/tmp</code>, so the two are one directory on the root filesystem, and RAM does not limit it.</p> <p>The reason is what happens when a build leaves gigabytes behind. This post covers the problem, the two small systemd pieces that fix it, and what you give up.</p>