https://wjmaritz.dev/tags/agents/Recent content in Agents on Wilhelm MaritzHugo -- gohugo.ioenWed, 21 Oct 2026 00:00:00 +0000https://wjmaritz.dev/posts/deploy-ran-my-tests/Wed, 21 Oct 2026 00:00:00 +0000https://wjmaritz.dev/posts/deploy-ran-my-tests/<p>Over two days my desktop ran out of memory five times. Four of those times it took my whole terminal window, with herdr, the Hermes agent running in it, and everything else in that window. From where I sat, Hermes kept crashing. It wasn&rsquo;t Hermes.</p> <p>Every one followed the same command by a minute and a half to two minutes: a run of one test file in <a href="https://wjmaritz.dev/posts/railway-request-counter/">railway-bridge</a>, my exporter for Railway&rsquo;s metrics. I matched the agent&rsquo;s log of commands against the system journal, and nothing else ran in that window.</p>https://wjmaritz.dev/posts/nas-bought-a-server/Sun, 18 Oct 2026 00:00:00 +0000https://wjmaritz.dev/posts/nas-bought-a-server/<p>My ZimaBoard started as a NAS. By October it was also running Immich and Paperless, Uptime Kuma, Grafana and Prometheus, a Homepage dashboard, two small metrics bridges, and a container full of AI coding agents. All of that on 7.5 GiB of RAM, with <a href="https://wjmaritz.dev/posts/grafana-memory-limit/">Grafana alone needing a whole gigabyte</a> of it.</p> <p>The board was coping on average. What worried me was the agents&rsquo; container. It wasn&rsquo;t the steady use; it was what happens when an agent runs <code>npm install</code> or a test suite and that spike lands on the same memory Immich and Paperless are using. So on 16 October a GMKtec K10 went onto the desk beside it, and the board went back to being mostly a NAS.</p>