Skip to content

an open-source alternative to the dots, bots and muses of the world, run an office of claude code/codex like agents on your laptop, sandboxes or anywhere, uses your existing subscriptions

26.5 KB
Raw Blame
<!doctype html>
<html lang="en">
<head>
<!-- Google tag (gtag.js), Google Ads AW-18388216863. Loaded only when Do Not Track is
     off, so it follows the same rule as the PostHog block on this site. -->
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){ dataLayer.push(arguments); }
  if (navigator.doNotTrack !== '1') {
    var gtagScript = document.createElement('script');
    gtagScript.async = true;
    gtagScript.src = 'https://www.googletagmanager.com/gtag/js?id=AW-18388216863';
    document.head.appendChild(gtagScript);
    gtag('js', new Date());
    gtag('config', 'AW-18388216863');
  }
</script>

<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Observability for Agent Fleets: Seeing What Your Agents Do — Munder Difflin Blog</title>
<meta name="description" content="Agent fleet observability: the four questions your dashboard must answer about who&#39;s working, what they&#39;re doing, what it costs, and what they know." />
<link rel="canonical" href="https://munderdiffl.in/blog/observability-for-agent-fleets/" />

<link rel="icon" type="image/png" href="https://munderdiffl.in/logo.png" />
<link rel="apple-touch-icon" href="https://munderdiffl.in/logo.png" />
<meta name="theme-color" content="#F5F2E8" />

<!-- Open Graph -->
<meta property="og:site_name" content="Munder Difflin Blog" />
<meta property="og:type" content="article" />
<meta property="og:title" content="Observability for Agent Fleets: Seeing What Your Agents Do — Munder Difflin Blog" />
<meta property="og:description" content="Agent fleet observability: the four questions your dashboard must answer about who&#39;s working, what they&#39;re doing, what it costs, and what they know." />
<meta property="og:url" content="https://munderdiffl.in/blog/observability-for-agent-fleets/" />
<meta property="og:image" content="https://munderdiffl.in/blog/assets/media/observability-for-agent-fleets/hero.png" />
<meta property="og:image:width" content="1600" />
<meta property="og:image:height" content="900" />
<meta property="og:image:alt" content="Illustration: Observability for Agent Fleets: Seeing What Your Agents Do" />
<meta property="og:locale" content="en_US" />
<meta property="article:published_time" content="2026-06-04T00:00:00.000Z" />
<meta property="article:author" content="Chaitanya Giri" />
<meta property="article:tag" content="Internals" />
<meta property="article:tag" content="Observability" />
<meta property="article:tag" content="Multi-Agent" />
<meta property="article:tag" content="Claude Code" />


<!-- Twitter -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Observability for Agent Fleets: Seeing What Your Agents Do — Munder Difflin Blog" />
<meta name="twitter:description" content="Agent fleet observability: the four questions your dashboard must answer about who&#39;s working, what they&#39;re doing, what it costs, and what they know." />
<meta name="twitter:image" content="https://munderdiffl.in/blog/assets/media/observability-for-agent-fleets/hero.png" />
<meta name="twitter:image:alt" content="Illustration: Observability for Agent Fleets: Seeing What Your Agents Do" />

<link rel="alternate" type="application/atom+xml" title="Munder Difflin Blog" href="https://munderdiffl.in/blog/feed.xml" />
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link href="https://fonts.googleapis.com/css2?family=Fraunces:opsz,[email protected],500;9..144,600;9..144,700;9..144,900&amp;family=Source+Serif+4:opsz,[email protected],400;8..60,600;8..60,700&amp;family=Space+Grotesk:wght@500;600;700&amp;family=JetBrains+Mono:wght@400;600&amp;display=swap" rel="stylesheet" />
<link rel="stylesheet" href="/blog/assets/blog-press.css" />

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Observability for Agent Fleets: Seeing What Your Agents Do",
  "description": "Agent fleet observability: the four questions your dashboard must answer about who's working, what they're doing, what it costs, and what they know.",
  "image": ["https://munderdiffl.in/blog/assets/media/observability-for-agent-fleets/hero.png"],
  "datePublished": "2026-06-04T00:00:00.000Z",
  "dateModified": "2026-06-04T00:00:00.000Z",
  "author": { "@type": "Person", "name": "Chaitanya Giri" },
  "publisher": {
    "@type": "Organization",
    "name": "Munder Difflin",
    "logo": { "@type": "ImageObject", "url": "https://munderdiffl.in/logo.png" }
  },
  "mainEntityOfPage": { "@type": "WebPage", "@id": "https://munderdiffl.in/blog/observability-for-agent-fleets/" },
  "keywords": "ai agent observability, agent fleet monitoring, agent token cost tracking, multi-agent dashboard",
  "articleSection": "Internals",
  "inLanguage": "en-US",
  "url": "https://munderdiffl.in/blog/observability-for-agent-fleets/"
}
</script>
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://munderdiffl.in/" },
    { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://munderdiffl.in/blog/" },
    { "@type": "ListItem", "position": 3, "name": "Observability for Agent Fleets: Seeing What Your Agents Do", "item": "https://munderdiffl.in/blog/observability-for-agent-fleets/" }
  ]
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    { "@type": "Question", "name": "How is observability for AI agents different from normal app observability?", "acceptedAnswer": { "@type": "Answer", "text": "App observability watches deterministic services — latency, error rates, throughput. Agent observability watches non-deterministic actors that make their own choices: which tools they call, what they decide, what they spend, what they remember. You're not just asking 'is it up?' but 'what is it doing and why, and is that what I wanted?' That needs a feed of intent and actions, not just health metrics." } },
    { "@type": "Question", "name": "Why track token cost per agent?", "acceptedAnswer": { "@type": "Answer", "text": "Because autonomous agents spend money without asking, and a runaway loop or an over-eager agent shows up first as a cost spike. Per-agent token and dollar telemetry turns 'the bill is high' into 'this agent is the reason' — fast enough to intervene. It's the cheapest early-warning signal an agent fleet has." } },
    { "@type": "Question", "name": "Where does the telemetry come from?", "acceptedAnswer": { "@type": "Answer", "text": "Two sources: lifecycle hooks stream what each agent is doing in real time, and the agents' own transcript files record exact token counts. Combine the live event stream with the on-disk usage and you can reconstruct both 'what happened' and 'what it cost' without instrumenting the model itself." } }
    
  ]
}
</script>


<script>
  // Anonymous blog analytics (PostHog) — same posture as the main site and the
  // app's TELEMETRY.md: public write-only token ('' = inert), anonymous-only
  // (person_profiles 'never'), no autocapture/recording, DNT respected.
  (function () {
    var PH_KEY = 'phc_qJzsokwcbtTGHemnvywR3nSqivNNgMjHeNVEWkZNydFB';
    if (!PH_KEY || navigator.doNotTrack === '1') return;
    var s = document.createElement('script');
    s.async = true;
    s.src = 'https://us-assets.i.posthog.com/static/array.js';
    s.onload = function () {
      if (!window.posthog) return;
      window.posthog.init(PH_KEY, {
        api_host: 'https://us.i.posthog.com',
        person_profiles: 'never',
        autocapture: false,
        before_send: function (event) {
          // PostHog fills $ip from the connection unless the event carries one.
          // Null it here and disable the GeoIP lookup so no IP, city, postal
          // code or lat/long is ever derived or stored for this page view.
          if (event && event.properties) {
            event.properties.$ip = null;
            event.properties.$geoip_disable = true;
          }
          return event;
        },
        disable_session_recording: true,
        respect_dnt: true
      });
    };
    document.head.appendChild(s);
  })();
</script>
</head>
<body class="theme-press">
<a class="skip-link" href="#main">Skip to content</a>
<nav id="nav">
  <a class="brand" href="https://munderdiffl.in" aria-label="Munder Difflin home">
    <img class="brand-logo" src="https://munderdiffl.in/logo.png" width="1318" height="840" alt="Munder Difflin, Inc. — Multi-Agent Harness" />
  </a>
  <span class="spacer"></span>
  <div class="links">
    <a href="/blog/">Latest</a>
    <a href="/blog/topics/">Topics</a>
    <a href="/blog/about/">About</a>
    <a href="https://munderdiffl.in">↗ Product</a>
  </div>
  <div class="nav-actions">
    <a class="btn sm" href="https://munderdiffl.in/blog/feed.xml" aria-label="RSS feed">⤵ RSS</a>
    <a class="btn sm primary" href="https://munderdiffl.in/#install">⤓ Download</a>
  </div>
</nav>

<main id="main">

<article class="t-internals">
  <header class="post-head wrap">
    <nav class="crumbs" aria-label="Breadcrumb">
      <a href="/blog/">Blog</a>
      <span>/</span>
      <a href="/blog/topics/internals/">Internals</a>
    </nav>
    <h1>Observability for Agent Fleets: Seeing What Your Agents Do</h1>
    <p class="dek">Agent fleet observability: the four questions your dashboard must answer about who&#39;s working, what they&#39;re doing, what it costs, and what they know.</p>
    <div class="byline">
      <span class="av" aria-hidden="true">CG</span>
      <strong>Chaitanya Giri</strong>
      <span class="dot" aria-hidden="true">·</span>
      <time datetime="2026-06-04">Jun 4, 2026</time>
      <span class="dot" aria-hidden="true">·</span>
      <span>4 min read</span>
      <span class="tag kind">Internals</span>
    </div>
  </header>

  <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/observability-for-agent-fleets/hero.png" alt="Illustration: Observability for Agent Fleets: Seeing What Your Agents Do" loading="lazy" decoding="async" /></figure></div>

  <div class="post-wrap wrap">
    <div class="prose">
      <div class="callout tldr"><span class="ic">TL;DR</span><p>A fleet of autonomous agents you can't see is a
fleet you can't manage. Good agent observability answers four questions at a glance: <strong>who's
working</strong> (roster + status), <strong>what are they doing</strong> (a live activity feed from the
event log), <strong>what is it costing</strong> (per-agent token + dollar telemetry from their
transcripts), and <strong>what do they know</strong> (task board + memory). Build that dashboard and
"my agents are off doing something" becomes "I can see exactly what, and step in early."</p></div>
<p>When you run one agent, you watch its terminal. When you run twenty, you can’t — and the failure modes
change. An agent quietly loops and burns tokens. Two pick up overlapping work. One stalls waiting on a
message that never came. None of that shows up in a terminal you’re not staring at. A fleet needs a
dashboard, and “agent observability” is a different problem from watching a normal service. Here’s the
shape of one that works.</p>
<h2 id="the-four-questions-a-fleet-dashboard-must-answer" tabindex="-1">The four questions a fleet dashboard must answer <a class="anchor" href="#the-four-questions-a-fleet-dashboard-must-answer" aria-hidden="true">#</a></h2>
<p>App monitoring asks “is it healthy?” Agent monitoring asks four sharper questions:</p>
<ol>
<li><strong>Who’s working?</strong> Which agents are active vs idle vs archived.</li>
<li><strong>What are they doing?</strong> A live, human-readable stream of their actions and messages.</li>
<li><strong>What is it costing?</strong> Token and dollar spend, per agent, in near-real-time.</li>
<li><strong>What do they know?</strong> The shared task state and memory driving their decisions.</li>
</ol>
<p>Miss any one and you’re flying partly blind. Below is how each maps to something concrete.</p>
<h2 id="a-live-activity-feed-from-the-event-log" tabindex="-1">A live activity feed from the event log <a class="anchor" href="#a-live-activity-feed-from-the-event-log" aria-hidden="true">#</a></h2>
<p>The backbone is a single <a href="/blog/append-only-event-log-agents/">append-only event log</a>: every spawn,
message, inbox drain, and escalation gets one line. A dashboard renders that log as a human-readable feed —
not raw JSON, but sentences:</p>
<ul>
<li><code>spawned Pam</code></li>
<li><code>Jim → Stanley: Task from you</code></li>
<li><code>Stanley drained 2 msg(s)</code></li>
<li><code>escalated to human: merge approval</code></li>
</ul>
<p>Now “what’s the fleet doing right now” is a glance, not an investigation. The feed is fed by
<a href="/blog/the-hook-shim-pattern/">lifecycle hooks</a>: every agent’s tool-use, stops, and notifications stream
into the main process in real time, so the picture is live rather than a periodic poll. The same
<a href="/blog/how-the-god-orchestrator-works/">orchestrator</a> that routes work reads this feed to keep its
situational awareness current.</p>
<figure class="fig fig-inline"><img src="/blog/assets/media/observability-for-agent-fleets/note-1.png" alt="Hand-drawn sketch from “Observability for Agent Fleets: Seeing What Your Agents Do”" loading="lazy" decoding="async" /></figure>
<h2 id="token-and-cost-telemetry-per-agent" tabindex="-1">Token and cost telemetry, per agent <a class="anchor" href="#token-and-cost-telemetry-per-agent" aria-hidden="true">#</a></h2>
<p>This is the part teams skip and regret. Autonomous agents spend money on their own, so <strong>cost is a
first-class signal</strong>, not an end-of-month surprise.</p>
<p>The trick is that you don’t have to instrument the model — the usage is already on disk. Each agent’s
Claude Code transcripts record exact input and output token counts. A usage meter reads those transcripts
per agent (polling every few seconds), shows input/output tokens and an estimated dollar cost, and
normalizes a bar against the most-expensive agent so the outlier is obvious at a glance. A runaway loop or
an over-eager agent stops being “the bill looks high” and becomes “that row is three times everyone else”
— early enough to intervene. Cost telemetry is the cheapest smoke detector a fleet has.</p>
<h2 id="state-at-a-glance-task-board-memory-roster" tabindex="-1">State at a glance: task board, memory, roster <a class="anchor" href="#state-at-a-glance-task-board-memory-roster" aria-hidden="true">#</a></h2>
<p>Actions and cost tell you <em>what’s happening</em>; state tells you <em>why</em>.</p>
<ul>
<li><strong>A task board.</strong> A kanban of todo / doing / blocked / done makes coordination visible — what’s queued,
what’s stuck, who owns what. “Blocked” columns are where fleets silently stall.</li>
<li><strong>A memory view and graph.</strong> What the hive <a href="/blog/semantic-memory-for-ai-agents/">knows</a> — and being able
to jump into any agent’s memory — explains decisions. An agent acting oddly usually has an odd memory.</li>
<li><strong>A roster with per-agent model.</strong> Who exists, who’s active, and which model each runs. Useful for both
“is everyone alive?” and “why is the Opus agent the cost outlier?”</li>
</ul>
<p>Add a full-text search across the board, tasks, and memory and you can answer ad-hoc questions (“who
mentioned the release?”) without grepping files by hand.</p>
<figure class="fig fig-inline"><img src="/blog/assets/media/observability-for-agent-fleets/note-2.png" alt="Hand-drawn sketch from “Observability for Agent Fleets: Seeing What Your Agents Do”" loading="lazy" decoding="async" /></figure>
<h2 id="observability-vs-debugging" tabindex="-1">Observability vs debugging <a class="anchor" href="#observability-vs-debugging" aria-hidden="true">#</a></h2>
<p>These are different jobs. <a href="/blog/debugging-multi-agent-systems/">Debugging a multi-agent system</a> is
<em>reactive</em> — something broke, you reconstruct why. Observability is <em>proactive</em> — a standing picture that
lets you catch the loop, the collision, or the cost spike <strong>before</strong> it becomes an incident. The activity
feed and usage meter are how you notice; the event log and transcripts are how you then dig in. You want
both, and the observability layer is what tells you when to switch from watching to debugging.</p>
<p>The quiet payoff: once you can <em>see</em> a fleet cheaply, you trust it to run unattended. Visibility is what
makes “leave the agents working” a calm decision instead of a leap of faith.</p>
<h2 id="faq" tabindex="-1">FAQ <a class="anchor" href="#faq" aria-hidden="true">#</a></h2>
<p><strong>Do I need a metrics stack like Prometheus/Grafana?</strong> Not to start. A fleet of dozens of local agents is
well served by reading the event log and transcripts directly and rendering them. Reach for a heavy
metrics stack when you’re distributed across machines and need retention and alerting at scale.</p>
<p><strong>What’s the single highest-value signal?</strong> Per-agent cost. It catches runaway loops, surfaces the
expensive outlier, and is trivial to read from transcripts. If you add one thing, add that.</p>
<p><strong>How live is “live”?</strong> The activity feed is event-driven (pushed by hooks as things happen); the usage
meter polls transcripts every several seconds. Plenty fast for agent turns measured in seconds to minutes.</p>
<hr>
<p>Munder Difflin ships this as the orchestrator’s control surface — a live activity feed, per-agent token
and cost meters, a task board, and a memory graph for a whole
<a href="https://munderdiffl.in/#how">hive of Claude Code agents</a>, all local.
<a href="https://munderdiffl.in/#install">Download Munder Difflin</a> to watch your fleet at a glance; it’s free and
open source.</p>


      
      <section class="faq" aria-label="Frequently asked questions">
        <h2 id="faq">FAQ</h2>
        
        <div class="qa">
          <p class="q">How is observability for AI agents different from normal app observability?</p>
          <p class="a">App observability watches deterministic services — latency, error rates, throughput. Agent observability watches non-deterministic actors that make their own choices: which tools they call, what they decide, what they spend, what they remember. You&#39;re not just asking &#39;is it up?&#39; but &#39;what is it doing and why, and is that what I wanted?&#39; That needs a feed of intent and actions, not just health metrics.</p>
        </div>
        
        <div class="qa">
          <p class="q">Why track token cost per agent?</p>
          <p class="a">Because autonomous agents spend money without asking, and a runaway loop or an over-eager agent shows up first as a cost spike. Per-agent token and dollar telemetry turns &#39;the bill is high&#39; into &#39;this agent is the reason&#39; — fast enough to intervene. It&#39;s the cheapest early-warning signal an agent fleet has.</p>
        </div>
        
        <div class="qa">
          <p class="q">Where does the telemetry come from?</p>
          <p class="a">Two sources: lifecycle hooks stream what each agent is doing in real time, and the agents&#39; own transcript files record exact token counts. Combine the live event stream with the on-disk usage and you can reconstruct both &#39;what happened&#39; and &#39;what it cost&#39; without instrumenting the model itself.</p>
        </div>
        
      </section>
      

      
      <hr />
      <div class="share">
        <span class="lbl">Tags</span>
        <a class="tag" href="/blog/tags/internals/">Internals</a><a class="tag" href="/blog/tags/observability/">Observability</a><a class="tag" href="/blog/tags/multi-agent/">Multi-Agent</a><a class="tag" href="/blog/tags/claude-code/">Claude Code</a>
      </div>
      
    </div>

    
    <aside class="toc-rail" aria-label="Table of contents">
      <div class="tt">On this page</div>
      <ol>
        <li class="lvl-2"><a href="#the-four-questions-a-fleet-dashboard-must-answer">The four questions a fleet dashboard must answer</a></li><li class="lvl-2"><a href="#a-live-activity-feed-from-the-event-log">A live activity feed from the event log</a></li><li class="lvl-2"><a href="#token-and-cost-telemetry-per-agent">Token and cost telemetry, per agent</a></li><li class="lvl-2"><a href="#state-at-a-glance-task-board-memory-roster">State at a glance: task board, memory, roster</a></li><li class="lvl-2"><a href="#observability-vs-debugging">Observability vs debugging</a></li><li class="lvl-2"><a href="#faq">FAQ</a></li>
      </ol>
    </aside>
    
  </div>

  <footer class="post-foot wrap"><div class="prevnext">
      <a class="pn prev" href="/blog/open-source-ai-tools-on-purpose/"><span class="k">← Older</span><span class="t">Building AI Dev Tools in the Open, On Purpose</span></a>
      <a class="pn next" href="/blog/long-running-agents-the-2026-shift/"><span class="k">Newer →</span><span class="t">Long-Running Agents: The 2026 Shift from Minutes to Hours</span></a>
    </div>
    <section class="related">
      <h2>Related in Internals</h2>
      <div class="post-grid">
        <article class="card t-internals">
  <a class="thumb t-internals" href="/blog/the-spend-counter-that-went-back-to-zero/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/the-spend-counter-that-went-back-to-zero/hero.png" alt="" loading="lazy" decoding="async" /></a>
  <div class="body">
    <div class="meta">
      <time datetime="2026-08-22">Aug 22, 2026</time>
      <span class="dot" aria-hidden="true"></span>
      <span>10 min</span>
    </div>
    <h3><a href="/blog/the-spend-counter-that-went-back-to-zero/">The Spend Counter That Went Back to Zero</a></h3>
    <p class="dek">Our own floor was under reporting what it cost by 59 percent. The counter was cumulative since process start, the app restarts, and the session id stayed the same. Here is how a monotonic invariant let us recover the real number from an append-only log.</p>
    <div class="foot">
      <span class="tag kind">Internals</span>
      <a class="more" href="/blog/the-spend-counter-that-went-back-to-zero/" aria-label="Read: The Spend Counter That Went Back to Zero">Read →</a>
    </div>
  </div>
</article>
<article class="card t-internals">
  <a class="thumb t-internals" href="/blog/the-newline-that-silenced-windows-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/the-newline-that-silenced-windows-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
  <div class="body">
    <div class="meta">
      <time datetime="2026-08-19">Aug 19, 2026</time>
      <span class="dot" aria-hidden="true"></span>
      <span>4 min</span>
    </div>
    <h3><a href="/blog/the-newline-that-silenced-windows-agents/">The Newline That Silenced Every Windows Agent</a></h3>
    <p class="dek">A cmd.exe parsing rule from the 1980s meant Windows agents received exactly one line of their multi-line startup protocol — and nothing errored. The anatomy of our worst silent failure, and the fix.</p>
    <div class="foot">
      <span class="tag kind">Internals</span>
      <a class="more" href="/blog/the-newline-that-silenced-windows-agents/" aria-label="Read: The Newline That Silenced Every Windows Agent">Read →</a>
    </div>
  </div>
</article>
<article class="card t-internals">
  <a class="thumb t-internals" href="/blog/why-our-auto-update-never-ran/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/why-our-auto-update-never-ran/hero.png" alt="" loading="lazy" decoding="async" /></a>
  <div class="body">
    <div class="meta">
      <time datetime="2026-08-08">Aug 8, 2026</time>
      <span class="dot" aria-hidden="true"></span>
      <span>5 min</span>
    </div>
    <h3><a href="/blog/why-our-auto-update-never-ran/">Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace</a></h3>
    <p class="dek">Munder Difflin shipped auto-update in v0.3.4 and it silently never worked in a single packaged build. The cause was one destructuring assignment across the CommonJS/ESM boundary — and a catch block that threw the evidence away. Here&#39;s how we found it, and what v0.3.7 changes.</p>
    <div class="foot">
      <span class="tag kind">Internals</span>
      <a class="more" href="/blog/why-our-auto-update-never-ran/" aria-label="Read: Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace">Read →</a>
    </div>
  </div>
</article>

      </div>
    </section>
    
  </footer>
</article>

</main>
<footer class="site-foot">
  <div class="wrap">
    <div class="foot-top">
      <a class="foot-brand brand" href="https://munderdiffl.in" aria-label="Munder Difflin home">
        <img class="brand-logo" src="https://munderdiffl.in/logo.png" width="1318" height="840" alt="Munder Difflin, Inc. — Multi-Agent Harness" />
      </a>
      <div class="foot-links">
        <a href="/blog/">Latest</a>
        <a href="/blog/topics/">Topics</a>
        <a href="/blog/about/">About</a>
        <a href="https://munderdiffl.in/blog/feed.xml">RSS</a>
        <a href="https://github.com/chaitanyagiri/munder-difflin">GitHub</a>
        <a href="https://munderdiffl.in">munderdiffl.in ↗</a>
      </div>
    </div>
    <div class="foot-meta">
      © 2026 Munder Difflin · Local-first · MIT-licensed ·
      Built on <a href="https://munderdiffl.in">Electron, React, Pixi.js, xterm.js &amp; node-pty</a>.
      Run an office of agents while you sleep.
    </div>
  </div>
</footer>

<script>
  // sticky-nav border on scroll
  (function () {
    var nav = document.getElementById('nav');
    if (!nav) return;
    var onScroll = function () { nav.classList.toggle('scrolled', window.scrollY > 8); };
    onScroll(); window.addEventListener('scroll', onScroll, { passive: true });
  })();
  // YouTube click-to-load: thumbnail button → youtube-nocookie iframe
  (function () {
    document.addEventListener('click', function (e) {
      var btn = e.target.closest('.yt-load');
      if (!btn) return;
      var box = btn.closest('.yt');
      var id = box && box.getAttribute('data-yt');
      // Only an 11 character YouTube video id may reach the iframe URL.
      if (!id || !/^[A-Za-z0-9_-]{11}$/.test(id)) return;
      var frame = document.createElement('iframe');
      frame.src = 'https://www.youtube-nocookie.com/embed/' + encodeURIComponent(id) + '?autoplay=1';
      frame.title = box.getAttribute('data-title') || 'YouTube video';
      frame.allow = 'accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share';
      frame.setAttribute('allowfullscreen', '');
      box.replaceChildren(frame);
    });
  })();
</script>

</body>
</html>