<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>smol machines blog</title>
    <link>https://smolmachines.com/blog</link>
    <atom:link href="https://smolmachines.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Where the smol machines team shares what we learn building it, and how we think about computers, AI agents and the infrastructure they run on.</description>
    <language>en</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Running agent evals on a laptop, one VM per trial</title>
      <link>https://smolmachines.com/blog/agent-evals-on-a-laptop</link>
      <guid isPermaLink="true">https://smolmachines.com/blog/agent-evals-on-a-laptop</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <category>Engineering</category>
      <description>Harbor, the harness behind Terminal-Bench 2.0, can run every trial in its own VM embedded in Harbor's process. We measured it against Apple's container tool on one MacBook: 1.3 seconds per trial against 21.</description>
    </item>
    <item>
      <title>Giving AI an undo button</title>
      <link>https://smolmachines.com/blog/undo-button-for-ai</link>
      <guid isPermaLink="true">https://smolmachines.com/blog/undo-button-for-ai</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
      <category>Engineering</category>
      <description>AI agents work on real computers, and computers have no undo. smol machines checkpoints an agent's whole machine, so you can undo a bad step, go back to any earlier point, or branch to try several paths at once.</description>
    </item>
    <item>
      <title>GPU access by API remoting: how a driverless microVM runs CUDA, and how it compares</title>
      <link>https://smolmachines.com/blog/gpu-over-vsock</link>
      <guid isPermaLink="true">https://smolmachines.com/blog/gpu-over-vsock</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Engineering</category>
      <description>A smolvm guest runs CUDA workloads without a passed-through GPU or an NVIDIA driver: it carries drop-in shim libraries that forward CUDA calls over vsock to a host that owns the GPU. How API remoting works, and how it compares to passthrough, vGPU, and container device injection.</description>
    </item>
    <item>
      <title>Running a real Kubernetes cluster inside one microVM</title>
      <link>https://smolmachines.com/blog/kubernetes-in-a-microvm</link>
      <guid isPermaLink="true">https://smolmachines.com/blog/kubernetes-in-a-microvm</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Engineering</category>
      <description>The newest release runs k3d inside a single machine. Kubernetes wants its own kernel, cgroup hierarchy, container runtime, and a specific set of device nodes. Here is why a microVM can host it where a container cannot, and the /dev/kmsg node the kubelet refused to start without.</description>
    </item>
  </channel>
</rss>
