<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Receipts on Fabian G. Williams</title>
    <link>https://www.fabswill.com/tags/receipts/</link>
    <description>Recent content in Receipts on Fabian G. Williams</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.fabswill.com/tags/receipts/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>My Agents Were Passing Notes Through a 313KB Text File. So I Built Them a Message Board.</title>
      <link>https://www.fabswill.com/blog/i-built-my-agents-a-message-board/</link>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/i-built-my-agents-a-message-board/</guid>
      <description>TL;DR My agents used to hand off work by appending to a single text file that had grown to 313KB. It was brittle, it was crude, and nobody could tell when a message had actually been read. This week, while the internet argued about Grok Bot, I read Grok Bot&amp;rsquo;s docs, looked hard at my own setup, and built my fleet a real message board: threaded, self-hosted on a Mac Mini, with an iMessage ping so a reply never sits unseen.</description>
    </item>
    
    <item>
      <title>Doug Was Right: I Swapped In The MoE, And The Concurrency Math Changed</title>
      <link>https://www.fabswill.com/blog/doug-was-right-i-measured-the-moe/</link>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/doug-was-right-i-measured-the-moe/</guid>
      <description>Two days ago I posted 36 barrier-synchronized loads against 1 local model and let the numbers answer a question Reddit handed me. That post ended with a promise. A reader named Doug Ware, who builds applied AI systems for a living, had replied with the one caveat I had not tested, and I said out loud that measuring it was the next thing I would do. This is that measurement.</description>
    </item>
    
    <item>
      <title>You Asked, So I Measured: What Concurrency Actually Costs On One Local Model</title>
      <link>https://www.fabswill.com/blog/you-asked-i-measured-the-concurrency-ceiling/</link>
      <pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/you-asked-i-measured-the-concurrency-ceiling/</guid>
      <description>Over last week and these last 2 days in this week I posted measured answers to readers both in Twitter and Reddit who asked whether my experiments of 2 local agents on 1 Mac run in parallel or take turns. The answers was that they share one continuous batch, batching is real, and 3 quiet choices collapse it. I thought that was the end of it. It was not. The comments were better than my post, WHICH IS AWESOME, becaue this is the crowdsourcing of brain power I love.</description>
    </item>
    
    <item>
      <title>I Added a Second Local Agent This Week. Here Is the Receipt for Every Human Decision Behind It.</title>
      <link>https://www.fabswill.com/blog/i-added-a-second-local-agent-and-kept-the-receipt/</link>
      <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/i-added-a-second-local-agent-and-kept-the-receipt/</guid>
      <description>This week I trialed a second local coding agent, Hermes from Nous Research, on my own MacBook Pro M3 Max, pointed at the same local Qwen 3.8 model I already run. I installed it additively, so nothing already working could break, governed it with manual approvals, and did not stop until it proved it behaves. Here is the trial, in tables and screenshots.
One housekeeping note before the story. Last week&amp;rsquo;s post got called AI slop on Reddit.</description>
    </item>
    
    <item>
      <title>Two Agents, One Local Model: Do They Run in Parallel, or Take Turns? I Measured It.</title>
      <link>https://www.fabswill.com/blog/two-agents-one-local-model-batching/</link>
      <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/two-agents-one-local-model-batching/</guid>
      <description>A reader on Reddit asked me a sharp question about my last post. I had trialed a second local coding agent, Hermes, pointed at the same local Qwen 3.8 model my other agent already uses. His question was simple. Did I ever run both agents at the same time, two separate harnesses hammering one model on one Mac at once. And what about Hermes spawning its own sub-agents against that same endpoint.</description>
    </item>
    
    <item>
      <title>I Made My Evals Replay Every Task on a Local Model. The Frontier Lead Got Thin.</title>
      <link>https://www.fabswill.com/blog/local-model-frontier-rematch-auto-replay-evals/</link>
      <pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/local-model-frontier-rematch-auto-replay-evals/</guid>
      <description>TL;DR My agents do real work on frontier models. Every dollar of that work is metered against my OpenAI and Anthropic bills. Meanwhile a perfectly capable local model, gpt-oss:20b, sits on a Mac Mini in my office costing me nothing. The obvious question: for which tasks could the free local model do the job just as well?
Today I answered it with a system instead of a guess. I taught my eval framework to automatically replay every writing task on the local model right after the frontier model runs it, then grade both with the same judge and record the gap.</description>
    </item>
    
    <item>
      <title>My Agents Left Me 116 Git Repos. So I Built a Source of Truth.</title>
      <link>https://www.fabswill.com/blog/my-agents-left-me-116-git-repos/</link>
      <pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/my-agents-left-me-116-git-repos/</guid>
      <description>A few weeks ago I asked an agent to pick up work on one of my own projects. It opened a fresh terminal, looked around, found nothing it recognized, and built a brand new copy of a project I already had. That was not the agent being careless. Nothing on the machine had ever told it where the real one lived. The only map of my own work was a memory in my head, and a memory does not survive contact with a machine where agents do the building.</description>
    </item>
    
    <item>
      <title>Your Agent Said It Did the Work. I Checked the Disk.</title>
      <link>https://www.fabswill.com/blog/your-agent-said-it-did-the-work/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/your-agent-said-it-did-the-work/</guid>
      <description>Every morning one of my agents sends me a clean status report. Posts cross-posted. Messages delivered. Contacts processed. For a while I read those reports the way you read a receipt from a cashier you trust. Then the automation started giving me time back, so I sat down to run a retrospective and checked the reports against what was actually on disk. The trust did not survive contact with the evidence.</description>
    </item>
    
  </channel>
</rss>