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

blog: 10 launch-week posts, and 2 sketches inside every post

Chaitanya Giri92461ab83042
diff --git a/blog/media-src/render.html b/blog/media-src/render.html
index 0ec656f7..42697bf9 100644
--- a/blog/media-src/render.html
+++ b/blog/media-src/render.html
@@ -1,14 +1,18 @@
<!doctype html>
<meta charset="utf-8">
<link href="https://fonts.googleapis.com/css2?family=Caveat:wght@500;600&display=swap" rel="stylesheet">
-<style>html,body{margin:0;width:1600px;height:900px;background:#fff;overflow:hidden}</style>
+<style>html,body{margin:0;background:#fff;overflow:hidden}</style>
<body>
<script src="scene-lib.js"></script>
<script src="spec.js"></script>
<script>
- const slug = new URLSearchParams(location.search).get("slug");
+ const q = new URLSearchParams(location.search);
+ const slug = q.get("slug");
+ const note = parseInt(q.get("note") || "0", 10); // 0 = hero, 1..n = inline note
const spec = SPEC[slug];
- document.body.innerHTML = spec ? buildScene(slug, spec) : `<h1 style="font:40px sans-serif;color:#c00">no spec for: ${slug}</h1>`;
+ document.body.innerHTML = spec
+ ? (note ? buildNote(slug, spec, note) : buildScene(slug, spec))
+ : `<h1 style="font:40px sans-serif;color:#c00">no spec for: ${slug}</h1>`;
document.fonts.ready.then(() => { document.title = "scene-ready"; });
</script>
</body>
diff --git a/blog/media-src/scene-lib.js b/blog/media-src/scene-lib.js
index 54b04a6d..15f837cf 100644
--- a/blog/media-src/scene-lib.js
+++ b/blog/media-src/scene-lib.js
@@ -220,6 +220,162 @@ const ARCH = {
},
};
+// ---- inline note vignettes (1200x560) ----
+// Small mid-post sketches. One or two parts, at most a tiny fixed label —
+// the post's own figcaption (if any) carries the meaning. Two variants per
+// archetype; per-slug rng keeps every render's jitter + wobble unique.
+const NOTE_W = 1200, NOTE_H = 560;
+const V = {
+ mail(r) {
+ let s = envelope(300 + J(r, 20), 300, 96, -6) + envelope(430, 230 + J(r, 16), 96, 5) + envelope(390, 370, 96, 2);
+ s += `<path d="M560 310 C 660 305, 720 300, 790 296" marker-end="url(#ah)"/>`;
+ s += box(820, 240, 150, 120) + `<path d="M845 300 h100"/>`;
+ return s + txt(842, 220, "inbox", AMBER, 28);
+ },
+ bell(r) {
+ let s = bell(500, 300 + J(r, 10), 1.5) + `<path d="M585 200 l18 -18 M600 232 l24 -8 M415 200 l-18 -18 M400 232 l-24 -8"/>`;
+ s += hei(800, 330, 0.85, { legs: "walk", armL: "up", armR: "up" });
+ return s;
+ },
+ desks(r) {
+ return miniAtDesk(360, 280 + J(r, 8)) + miniAtDesk(800, 280 + J(r, 8));
+ },
+ board(r) {
+ let s = `<rect x="420" y="120" width="440" height="330" rx="4"/><path d="M567 120 v330 M714 120 v330"/><path d="M420 180 h440"/>`;
+ s += sticky(445, 205 + J(r, 6), 62, -3) + sticky(452, 295, 62, 2) + sticky(590, 210, 62, 3) + sticky(740, 220 + J(r, 6), 62, -2);
+ s += `<path d="M756 310 l18 18 l30 -34" stroke-width="4"/>`;
+ return s + txt(455, 165, "todo", BLUE, 26) + txt(598, 165, "doing", BLUE, 26) + txt(748, 165, "done", BLUE, 26);
+ },
+ cards(r) {
+ let s = "";
+ [0, 1, 2].forEach(i => { s += `<rect x="${470 + J(r, 6)}" y="${180 + i * 96}" width="300" height="76" rx="3"/><path d="M${595} ${216 + i * 96} h60"/>`; });
+ s += hei(320, 330, 0.8, { legs: "stand", armR: "out", armL: "down" }) + sticky(400, 280, 42, -8);
+ return s;
+ },
+ vs(r) {
+ let s = box(260, 200 + J(r, 8), 230, 170, true) + box(710, 200 + J(r, 8), 230, 170, true);
+ s += `<text x="600" y="300" fill="${INK}" stroke="none" font-size="48" font-weight="600" text-anchor="middle" font-family="Caveat">vs</text>`;
+ s += hei(1030, 340, 0.75, { legs: "stand", armL: "out", armR: "down" }) + magnifier(950, 260, 0.9);
+ return s;
+ },
+ shield(r) {
+ let s = shield(560, 260 + J(r, 8), 1.3) + bolt(300, 160, 1) + bolt(260, 330, 0.9);
+ s += `<path d="M350 200 C 410 230, 440 250, 470 268" marker-end="url(#ah)"/>`;
+ s += hei(830, 330, 0.8, { legs: "stand", armL: "out", armR: "down" });
+ return s;
+ },
+ sleep(r) {
+ let s = desk(380, 380, 320);
+ s += `<g transform="rotate(-14 530 310)"><ellipse cx="530" cy="310" rx="52" ry="62" fill="${YEL}" stroke="${INK}"/><path d="M506 300 c 5 5 12 5 17 0 M536 296 c 5 5 12 5 17 0"/></g>`;
+ s += `<text x="640" y="200" font-size="40" fill="${INK}" stroke="none" font-family="Caveat">z</text><text x="672" y="170" font-size="32" fill="${INK}" stroke="none" font-family="Caveat">z</text><text x="696" y="146" font-size="25" fill="${INK}" stroke="none" font-family="Caveat">z</text>`;
+ s += terminal(760, 240, 130, 82);
+ return s;
+ },
+ nightowl(r) {
+ return moonzzz(360, 180 + J(r, 8)) + clock(800, 280, 66);
+ },
+ loop(r) {
+ let s = `<path d="M 600 140 C 780 140, 860 220, 860 290 C 860 380, 760 440, 600 440 C 440 440, 340 380, 340 290 C 340 235, 390 165, 510 145" marker-end="url(#ah)"/>`;
+ s += hei(600, 290, 0.8, { legs: "walk", armL: "out", armR: "down" });
+ s += `<path d="M880 260 l18 22 l34 -40" stroke-width="4"/>`;
+ return s;
+ },
+ coins(r) {
+ let s = desk(380, 400, 460);
+ s += coins(520, 370, 3 + Math.floor(r() * 3)) + coins(610, 370, 5);
+ s += `<rect x="700" y="200" width="150" height="190" rx="4"/><path d="M722 240 h106 M722 275 h70 M722 310 h106"/><path d="M700 390 l16 13 l20 -13 l20 13 l20 -13 l20 13 l20 -13 l20 13"/>`;
+ return s;
+ },
+ book(r) {
+ return book(400, 210 + J(r, 8), 440) + hei(300, 350, 0.72, { legs: "stand", armR: "out", armL: "down" });
+ },
+ term(r) {
+ let s = terminal(430, 130, 430, 260);
+ s += `<path d="M470 340 h24 l-10 -10 m10 10 l-10 10" stroke-width="3"/>`;
+ s += hei(340, 350, 0.7, { legs: "none", armR: "out", armL: "none" }) + desk(290, 420, 640);
+ return s;
+ },
+ ship(r) {
+ let s = `<path d="M280 430 L940 430"/>`;
+ s += box(620, 300, 190, 130, true) + flag(715, 300, 1.1);
+ s += hei(470, 320, 0.8, { legs: "walk", armL: "down", armR: "out" });
+ s += `<path d="M400 320 l-34 -8 M404 352 l-38 0 M400 384 l-34 10"/>`;
+ return s;
+ },
+ chat(r) {
+ let s = hei(420, 320, 0.8, { legs: "stand", armR: "out", armL: "down" });
+ s += hei(800, 320, 0.8, { legs: "stand", armL: "out", armR: "down" });
+ s += bubble(280, 140, 250, 86, 1) + bubble(700, 130, 260, 86, -1);
+ s += txt(330, 196, "…", BLUE, 30) + txt(760, 184, "!", BLUE, 30);
+ return s;
+ },
+ point(r) {
+ let s = `<path d="M540 430 l-52 90 M640 430 l52 90 M590 430 v90"/>`;
+ s += `<rect x="430" y="170" width="320" height="260" rx="6"/><path d="M430 216 h320"/>`;
+ s += `<path d="M465 265 h120 M465 310 h180 M465 355 h105"/>`;
+ s += hei(900, 340, 0.8, { legs: "stand", armL: "out", armR: "down" });
+ s += `<path d="M826 334 C 800 318, 780 305, 762 292"/>`;
+ return s;
+ },
+ stack(r) {
+ let s = "";
+ [0, 1, 2].forEach(i => { s += box(400, 430 - i * 82, 260 - i * 26, 74, true); });
+ s += hei(800, 320, 0.82, { legs: "stand", armL: "up", armR: "down" });
+ return s;
+ },
+ walk(r) {
+ let s = hei(520, 300 + J(r, 8), 0.85, { legs: "walk", armL: "down", armR: "out" });
+ s += envelope(610, 250, 64, 8);
+ s += `<path d="M700 300 C 800 295, 860 292, 930 290" marker-end="url(#ah)"/>`;
+ s += box(950, 240, 130, 110);
+ return s;
+ },
+};
+
+// archetype → [variant for note-1, variant for note-2]
+const NOTES = {
+ routing: [V.mail, V.walk],
+ fleet: [V.desks, V.board],
+ kanban: [V.board, V.walk],
+ memory: [V.cards, V.book],
+ versus: [V.vs, V.point],
+ guard: [V.shield, V.bell],
+ night: [V.sleep, V.nightowl],
+ wire: [V.bell, V.term],
+ stack: [V.stack, V.point],
+ loop: [V.loop, V.bell],
+ ledger: [V.coins, V.board],
+ book: [V.book, V.point],
+ terminal: [V.term, V.walk],
+ ship: [V.ship, V.board],
+ talk: [V.chat, V.mail],
+ spotlight: [V.point, V.chat],
+};
+
+// Build a 1200x560 inline-note SVG for a spec entry. `which` = 1, 2, 3…
+function buildNote(slug, spec, which) {
+ const r = rng(`${slug}#note${which}`);
+ const seed = Math.floor(r() * 900) + 2;
+ LABELS = "";
+ const variants = NOTES[spec.a] || [V.walk, V.point];
+ const inner = variants[(which - 1) % variants.length](r, spec);
+ return `<svg width="${NOTE_W}" height="${NOTE_H}" viewBox="0 0 ${NOTE_W} ${NOTE_H}" font-family="Caveat">
+ <defs>
+ <filter id="wob" x="-5%" y="-5%" width="110%" height="110%">
+ <feTurbulence type="fractalNoise" baseFrequency="0.015" numOctaves="2" seed="${seed}" result="n"/>
+ <feDisplacementMap in="SourceGraphic" in2="n" scale="6"/>
+ </filter>
+ <marker id="ah" viewBox="0 0 12 12" refX="9" refY="6" markerWidth="9" markerHeight="9" orient="auto-start-reverse">
+ <path d="M2 2 L10 6 L2 10" fill="none" stroke="${INK}" stroke-width="2"/>
+ </marker>
+ </defs>
+ <g filter="url(#wob)" fill="none" stroke="${INK}" stroke-width="3" stroke-linecap="round" stroke-linejoin="round">
+${inner}
+ </g>
+ <g>${LABELS}</g>
+</svg>`;
+}
+
// Build the full SVG document for a spec entry.
function buildScene(slug, spec) {
const r = rng(slug);
diff --git a/blog/media-src/spec.js b/blog/media-src/spec.js
index 4bf67414..389b0a19 100644
--- a/blog/media-src/spec.js
+++ b/blog/media-src/spec.js
@@ -118,4 +118,19 @@ const SPEC = {
"why-cli-agents-are-powerful": { a: "terminal", blue: "the CLI is the API", orange: "fewer tokens, same work" },
"why-local-first-matters-for-ai-agents": { a: "guard", blue: "local-first", orange: "your machine, your data", amber: "your code stays home" },
"why-our-auto-update-never-ran": { a: "loop", blue: "CJS export → ESM namespace", orange: "the update that never ran" },
+ // The next three posts have hand-authored pilot heroes (media-src/pilot/) —
+ // these entries exist only so buildNote() can draw their inline sketches.
+ "why-we-built-munder-difflin": { a: "fleet", blue: "one floor, many desks", orange: "the itch that started it" },
+ "your-first-hour-with-munder-difflin": { a: "terminal", blue: "first run", orange: "an office in an hour" },
+ "how-the-god-orchestrator-works": { a: "routing", blue: "michael routes the mail", orange: "one boss, many desks" },
+ "number-five-on-product-hunt": { a: "spotlight", blue: "195 upvotes · 326 followers", orange: "Nº5 product of the day" },
+ "what-reddit-told-us-about-munder-difflin": { a: "talk", blue: "516 comments", blue2: "we read every one", orange: "the stadium had notes" },
+ "launching-munder-difflin-v0-4-4": { a: "ship", blue: "v0.4.4", orange: "windows agents can finally talk" },
+ "seven-releases-in-eight-days": { a: "kanban", blue: "0.3.8 → 0.4.4", orange: "seven releases, eight days" },
+ "the-newline-that-silenced-windows-agents": { a: "wire", blue: "cmd.exe stops at the first newline", orange: "the agents never got the memo" },
+ "agents-ran-our-launch-week-analytics": { a: "memory", blue: "one agent per channel", orange: "every comment accounted for", amber: "reddit · PH · github" },
+ "an-agent-redesigned-this-blog": { a: "terminal", blue: "119 heroes, drawn as code", orange: "this blog, by an agent" },
+ "run-a-release-train-with-agents": { a: "ship", blue: "bump · notes · tag · check", orange: "the train leaves on time" },
+ "turn-feedback-into-a-backlog-with-agents": { a: "routing", blue: "comments in → cards out", orange: "feedback becomes work", amber: "516 incoming" },
+ "we-opened-a-discord": { a: "talk", blue: "come say hi", blue2: "employee of the month", orange: "the office got a lobby" },
};
diff --git a/blog/scripts/add-inline-notes.mjs b/blog/scripts/add-inline-notes.mjs
new file mode 100644
index 00000000..550b71de
--- /dev/null
+++ b/blog/scripts/add-inline-notes.mjs
@@ -0,0 +1,76 @@
+// Give every post 2 inline sketch figures ("notes") between sections, and
+// register every {% img %} slot in the media manifest.
+//
+// - Posts that already contain {% img "note-… %} shortcodes (hand-placed, with
+// captions) are left untouched textually.
+// - All other posts get `{% img "note-1" %}` and `{% img "note-2" %}` inserted
+// at roughly 1/3 and 2/3 of their H2 sections (outside code fences).
+// - Then every slot referenced by any post gets an inline entry in
+// src/_data/media.json (existing entries are preserved).
+//
+// The sketches themselves are drawn by media-src/scene-lib.js buildNote() and
+// rendered via render.html?slug=<slug>&note=<n>. Run this, render, then build.
+//
+// Usage: node scripts/add-inline-notes.mjs (cwd = blog/)
+import { readdir, readFile, writeFile } from "node:fs/promises";
+import path from "node:path";
+
+const POSTS_DIR = "src/posts";
+const MANIFEST = "src/_data/media.json";
+
+const media = JSON.parse(await readFile(MANIFEST, "utf8"));
+const files = (await readdir(POSTS_DIR)).filter((f) => f.endsWith(".md")).sort();
+
+let injected = 0, slotsAdded = 0;
+
+for (const file of files) {
+ const slug = path.basename(file, ".md");
+ const p = path.join(POSTS_DIR, file);
+ let text = await readFile(p, "utf8");
+
+ if (!/\{%\s*img\s+"note-/.test(text)) {
+ // find H2 lines outside code fences, after frontmatter
+ const lines = text.split("\n");
+ let inFence = false;
+ const h2 = [];
+ let fmEnd = 0, dashes = 0;
+ for (let i = 0; i < lines.length; i++) {
+ if (/^---\s*$/.test(lines[i]) && dashes < 2) { dashes++; if (dashes === 2) fmEnd = i; continue; }
+ if (/^```/.test(lines[i])) { inFence = !inFence; continue; }
+ if (!inFence && /^## /.test(lines[i]) && i > fmEnd) h2.push(i);
+ }
+ if (h2.length >= 2) {
+ const p1 = Math.max(1, Math.floor(h2.length / 3));
+ let p2 = Math.min(h2.length - 1, Math.floor((2 * h2.length) / 3));
+ if (p2 <= p1) p2 = p1 + 1 <= h2.length - 1 ? p1 + 1 : -1;
+ const inserts = [[h2[p1], 1]];
+ if (p2 > 0) inserts.push([h2[p2], 2]);
+ // insert bottom-up so line numbers stay valid
+ for (const [line, n] of inserts.reverse()) {
+ lines.splice(line, 0, `{% img "note-${n}" %}`, "");
+ }
+ text = lines.join("\n");
+ await writeFile(p, text);
+ injected++;
+ }
+ }
+
+ // register every referenced slot in the manifest
+ const entry = media[slug];
+ if (!entry) continue;
+ entry.inline = entry.inline || {};
+ for (const m of text.matchAll(/\{%\s*img\s+"([\w-]+)"/g)) {
+ const slot = m[1];
+ if (entry.inline[slot]) continue;
+ entry.inline[slot] = {
+ file: `assets/media/${slug}/${slot}.png`,
+ alt: `Hand-drawn sketch from “${entry.title}”`,
+ prompt: "",
+ status: "ready",
+ };
+ slotsAdded++;
+ }
+}
+
+await writeFile(MANIFEST, JSON.stringify(media, null, 2) + "\n");
+console.log(`[notes] injected shortcodes into ${injected} posts, added ${slotsAdded} inline slots to ${MANIFEST}`);
diff --git a/blog/src/_data/media.json b/blog/src/_data/media.json
index 769d5506..1b4d17f0 100644
--- a/blog/src/_data/media.json
+++ b/blog/src/_data/media.json
@@ -1,5 +1,5 @@
{
- "_style": "Ian Xiaohei style (ian-xiaohei-illustrations skill): 16:9 landscape, pure white background, thin hand-drawn black linework with slight wobble, generous whitespace (subject fills 40-60% of frame), one core concept/structure/metaphor per image. The recurring character Xiaohei \u2014 bean-shaped body filled with Munder Difflin accent yellow #FFCA54 with a thin black outline, two small black dot eyes, thin legs, blank expression \u2014 must actively participate in the core action as an earnest office worker, never stand aside as decoration. Sparse hand-written English annotations in orange, blue, and yellow only \u2014 never red. No paper texture, no gradients, no shadows, not cute, not childish.",
+ "_style": "Warm, hand-drawn editorial illustration for a developer blog. Flat colors, visible texture, generous negative space, no text in the image. The recurring world is a cozy pixel-art office of small AI agents at desks (The Office homage): terminals, sticky notes, coffee mugs, a kanban wall. Palette keyed to the post's topic color. 16:9, crisp at 1600x900.",
"agent-security-and-sandboxing": {
"title": "Running AI Agents Safely: Permission Modes and Sandboxing",
"category": "guides",
@@ -9,7 +9,45 @@
"prompt": "Hero image for a blog post titled \"Running AI Agents Safely: Permission Modes and Sandboxing\". The post is about: How to run autonomous AI agents safely: permission modes and the bypassPermissions foot-gun, workspace isolation, and what to gate vs. allow.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/agent-security-and-sandboxing/note-1.png",
+ "alt": "Hand-drawn sketch from “Running AI Agents Safely: Permission Modes and Sandboxing”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/agent-security-and-sandboxing/note-2.png",
+ "alt": "Hand-drawn sketch from “Running AI Agents Safely: Permission Modes and Sandboxing”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "agents-ran-our-launch-week-analytics": {
+ "title": "Our Agents Ran Our Launch-Week Analytics",
+ "category": "use-cases",
+ "hero": {
+ "file": "assets/media/agents-ran-our-launch-week-analytics/hero.png",
+ "alt": "Illustration: Our Agents Ran Our Launch-Week Analytics",
+ "prompt": "Hero image for a blog post titled \"Our Agents Ran Our Launch-Week Analytics\". The post is about: Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/agents-ran-our-launch-week-analytics/note-1.png",
+ "alt": "Hand-drawn sketch from “Our Agents Ran Our Launch-Week Analytics”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/agents-ran-our-launch-week-analytics/note-2.png",
+ "alt": "Hand-drawn sketch from “Our Agents Ran Our Launch-Week Analytics”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"agents-rule-of-two": {
@@ -18,10 +56,23 @@
"hero": {
"file": "assets/media/agents-rule-of-two/hero.png",
"alt": "Illustration: The Agents Rule of Two: A Simple Safety Rule for Coding Agents",
- "prompt": "Hero image for a blog post titled \"The Agents Rule of Two: A Simple Safety Rule for Coding Agents\". The post is about: Meta's Agents Rule of Two for coding agents: don't let one session combine untrusted input, private data, and external reach at once \u2014 or supervise.",
+ "prompt": "Hero image for a blog post titled \"The Agents Rule of Two: A Simple Safety Rule for Coding Agents\". The post is about: Meta's Agents Rule of Two for coding agents: don't let one session combine untrusted input, private data, and external reach at once — or supervise.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/agents-rule-of-two/note-1.png",
+ "alt": "Hand-drawn sketch from “The Agents Rule of Two: A Simple Safety Rule for Coding Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/agents-rule-of-two/note-2.png",
+ "alt": "Hand-drawn sketch from “The Agents Rule of Two: A Simple Safety Rule for Coding Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"ai-agent-glossary": {
@@ -30,10 +81,48 @@
"hero": {
"file": "assets/media/ai-agent-glossary/hero.png",
"alt": "Illustration: The AI Coding Agent Glossary: Harness, Orchestrator, Hive, Subagent",
- "prompt": "Hero image for a blog post titled \"The AI Coding Agent Glossary: Harness, Orchestrator, Hive, Subagent\". The post is about: Plain-English definitions of the AI coding agent terms everyone trips over \u2014 harness, orchestrator, hive, subagent, agent memory \u2014 each in one line.",
+ "prompt": "Hero image for a blog post titled \"The AI Coding Agent Glossary: Harness, Orchestrator, Hive, Subagent\". The post is about: Plain-English definitions of the AI coding agent terms everyone trips over — harness, orchestrator, hive, subagent, agent memory — each in one line.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/ai-agent-glossary/note-1.png",
+ "alt": "Hand-drawn sketch from “The AI Coding Agent Glossary: Harness, Orchestrator, Hive, Subagent”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/ai-agent-glossary/note-2.png",
+ "alt": "Hand-drawn sketch from “The AI Coding Agent Glossary: Harness, Orchestrator, Hive, Subagent”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "an-agent-redesigned-this-blog": {
+ "title": "An Agent Redesigned the Blog You're Reading",
+ "category": "use-cases",
+ "hero": {
+ "file": "assets/media/an-agent-redesigned-this-blog/hero.png",
+ "alt": "Illustration: An Agent Redesigned the Blog You're Reading",
+ "prompt": "Hero image for a blog post titled \"An Agent Redesigned the Blog You're Reading\". The post is about: Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/an-agent-redesigned-this-blog/note-1.png",
+ "alt": "Hand-drawn sketch from “An Agent Redesigned the Blog You're Reading”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/an-agent-redesigned-this-blog/note-2.png",
+ "alt": "Hand-drawn sketch from “An Agent Redesigned the Blog You're Reading”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"append-only-event-log-agents": {
@@ -45,7 +134,20 @@
"prompt": "Hero image for a blog post titled \"An Append-Only Event Log for a Hive of Agents\". The post is about: How an append-only event log makes a multi-agent system debuggable and replayable: what to record, and why one JSON line per event beats a database.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/append-only-event-log-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “An Append-Only Event Log for a Hive of Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/append-only-event-log-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “An Append-Only Event Log for a Hive of Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"architecture-two-planes-one-renderer": {
@@ -57,7 +159,20 @@
"prompt": "Hero image for a blog post titled \"Munder Difflin's Architecture: Two Data Planes, One Renderer\". The post is about: A walkthrough of the multi-agent harness architecture: a node-pty terminal plane and a hooks/hive event plane feeding one React + Pixi.js renderer.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/architecture-two-planes-one-renderer/note-1.png",
+ "alt": "Hand-drawn sketch from “Munder Difflin's Architecture: Two Data Planes, One Renderer”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/architecture-two-planes-one-renderer/note-2.png",
+ "alt": "Hand-drawn sketch from “Munder Difflin's Architecture: Two Data Planes, One Renderer”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"atomic-file-mailboxes-for-agents": {
@@ -66,10 +181,23 @@
"hero": {
"file": "assets/media/atomic-file-mailboxes-for-agents/hero.png",
"alt": "Illustration: Atomic File Mailboxes: How Agents Message Each Other",
- "prompt": "Hero image for a blog post titled \"Atomic File Mailboxes: How Agents Message Each Other\". The post is about: Can Claude Code agents talk to each other? Yes \u2014 the outbox-router-inbox design that lets agents message safely using plain files and atomic renames.",
+ "prompt": "Hero image for a blog post titled \"Atomic File Mailboxes: How Agents Message Each Other\". The post is about: Can Claude Code agents talk to each other? Yes — the outbox-router-inbox design that lets agents message safely using plain files and atomic renames.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/atomic-file-mailboxes-for-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Atomic File Mailboxes: How Agents Message Each Other”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/atomic-file-mailboxes-for-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Atomic File Mailboxes: How Agents Message Each Other”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"best-ai-coding-agents": {
@@ -78,10 +206,23 @@
"hero": {
"file": "assets/media/best-ai-coding-agents/hero.png",
"alt": "Illustration: The Best AI Coding Agents in 2026: A Field Guide",
- "prompt": "Hero image for a blog post titled \"The Best AI Coding Agents in 2026: A Field Guide\". The post is about: A fair 2026 field guide to the best AI coding agents \u2014 Cursor, Aider, Cline, Devin, Copilot \u2014 by category, plus where a local multi-agent hive fits.",
+ "prompt": "Hero image for a blog post titled \"The Best AI Coding Agents in 2026: A Field Guide\". The post is about: A fair 2026 field guide to the best AI coding agents — Cursor, Aider, Cline, Devin, Copilot — by category, plus where a local multi-agent hive fits.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/best-ai-coding-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “The Best AI Coding Agents in 2026: A Field Guide”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/best-ai-coding-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “The Best AI Coding Agents in 2026: A Field Guide”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"best-claude-code-multi-agent-tools": {
@@ -90,10 +231,23 @@
"hero": {
"file": "assets/media/best-claude-code-multi-agent-tools/hero.png",
"alt": "Illustration: The Best Tools to Run Multiple Claude Code Agents (2026)",
- "prompt": "Hero image for a blog post titled \"The Best Tools to Run Multiple Claude Code Agents (2026)\". The post is about: An honest 2026 roundup of tools to run multiple Claude Code agents \u2014 Claude Squad, Conductor, Crystal, vibe-kanban, and Munder Difflin \u2014 compared.",
+ "prompt": "Hero image for a blog post titled \"The Best Tools to Run Multiple Claude Code Agents (2026)\". The post is about: An honest 2026 roundup of tools to run multiple Claude Code agents — Claude Squad, Conductor, Crystal, vibe-kanban, and Munder Difflin — compared.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/best-claude-code-multi-agent-tools/note-1.png",
+ "alt": "Hand-drawn sketch from “The Best Tools to Run Multiple Claude Code Agents (2026)”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/best-claude-code-multi-agent-tools/note-2.png",
+ "alt": "Hand-drawn sketch from “The Best Tools to Run Multiple Claude Code Agents (2026)”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"building-a-terminal-ui-xterm-node-pty": {
@@ -105,7 +259,20 @@
"prompt": "Hero image for a blog post titled \"Building a Terminal UI with xterm.js and node-pty\". The post is about: Wire xterm.js to a node-pty backend: stream output, write keystrokes back, handle resize, and keep many live terminals fast with a terminal pool.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/building-a-terminal-ui-xterm-node-pty/note-1.png",
+ "alt": "Hand-drawn sketch from “Building a Terminal UI with xterm.js and node-pty”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/building-a-terminal-ui-xterm-node-pty/note-2.png",
+ "alt": "Hand-drawn sketch from “Building a Terminal UI with xterm.js and node-pty”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"building-an-ai-office-floor": {
@@ -117,7 +284,20 @@
"prompt": "Hero image for a blog post titled \"Building an AI \\\"Office Floor\\\": Avatars, Pathfinding, Envelopes\". The post is about: The game-dev techniques behind a dev tool's office floor: Tiled maps, BFS pathfinding, sprite recoloring, and flying message envelopes in Pixi.js.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/building-an-ai-office-floor/note-1.png",
+ "alt": "Hand-drawn sketch from “Building an AI \\\"Office Floor\\\": Avatars, Pathfinding, Envelopes”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/building-an-ai-office-floor/note-2.png",
+ "alt": "Hand-drawn sketch from “Building an AI \\\"Office Floor\\\": Avatars, Pathfinding, Envelopes”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"building-reliable-ai-agents": {
@@ -126,10 +306,23 @@
"hero": {
"file": "assets/media/building-reliable-ai-agents/hero.png",
"alt": "Illustration: Building Reliable AI Agents: Failure Is the Default",
- "prompt": "Hero image for a blog post titled \"Building Reliable AI Agents: Failure Is the Default\". The post is about: Agents fail constantly: tools error, steps stall, output goes wrong. Reliability isn't avoiding failure \u2014 it's making each one contained and recoverable.",
+ "prompt": "Hero image for a blog post titled \"Building Reliable AI Agents: Failure Is the Default\". The post is about: Agents fail constantly: tools error, steps stall, output goes wrong. Reliability isn't avoiding failure — it's making each one contained and recoverable.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/building-reliable-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Building Reliable AI Agents: Failure Is the Default”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/building-reliable-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Building Reliable AI Agents: Failure Is the Default”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"can-claude-code-agents-talk-to-each-other": {
@@ -138,10 +331,23 @@
"hero": {
"file": "assets/media/can-claude-code-agents-talk-to-each-other/hero.png",
"alt": "Illustration: Can Claude Code Agents Talk to Each Other?",
- "prompt": "Hero image for a blog post titled \"Can Claude Code Agents Talk to Each Other?\". The post is about: Can Claude Code agents talk to each other? By default they report to their launcher \u2014 but a small coordination layer lets them message peer-to-peer.",
+ "prompt": "Hero image for a blog post titled \"Can Claude Code Agents Talk to Each Other?\". The post is about: Can Claude Code agents talk to each other? By default they report to their launcher — but a small coordination layer lets them message peer-to-peer.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/can-claude-code-agents-talk-to-each-other/note-1.png",
+ "alt": "Hand-drawn sketch from “Can Claude Code Agents Talk to Each Other?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/can-claude-code-agents-talk-to-each-other/note-2.png",
+ "alt": "Hand-drawn sketch from “Can Claude Code Agents Talk to Each Other?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-code-automation-while-you-sleep": {
@@ -153,7 +359,20 @@
"prompt": "Hero image for a blog post titled \"Claude Code Automation: Let Agents Build While You Sleep\". The post is about: Claude Code automation that runs overnight: an autonomous Stop-hook loop, safe permission bypass, and guardrails so you wake up to progress, not chaos.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-code-automation-while-you-sleep/note-1.png",
+ "alt": "Hand-drawn sketch from “Claude Code Automation: Let Agents Build While You Sleep”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-code-automation-while-you-sleep/note-2.png",
+ "alt": "Hand-drawn sketch from “Claude Code Automation: Let Agents Build While You Sleep”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-code-git-worktrees-vs-hive": {
@@ -165,7 +384,20 @@
"prompt": "Hero image for a blog post titled \"Git Worktrees vs a Hive: Two Ways to Parallelize Claude Code\". The post is about: Claude Code git worktrees vs a hive: when isolated worktrees suffice for parallel agents, and when you need memory, messaging, and an orchestrator on top.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-code-git-worktrees-vs-hive/note-1.png",
+ "alt": "Hand-drawn sketch from “Git Worktrees vs a Hive: Two Ways to Parallelize Claude Code”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-code-git-worktrees-vs-hive/note-2.png",
+ "alt": "Hand-drawn sketch from “Git Worktrees vs a Hive: Two Ways to Parallelize Claude Code”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-code-hooks-explained": {
@@ -174,10 +406,23 @@
"hero": {
"file": "assets/media/claude-code-hooks-explained/hero.png",
"alt": "Illustration: Claude Code Hooks, Explained (PreToolUse, PostToolUse, Stop)",
- "prompt": "Hero image for a blog post titled \"Claude Code Hooks, Explained (PreToolUse, PostToolUse, Stop)\". The post is about: A practical tour of Claude Code hooks \u2014 the PreToolUse, PostToolUse, and Stop lifecycle \u2014 and how a Unix-socket hook shim drives a live office floor.",
+ "prompt": "Hero image for a blog post titled \"Claude Code Hooks, Explained (PreToolUse, PostToolUse, Stop)\". The post is about: A practical tour of Claude Code hooks — the PreToolUse, PostToolUse, and Stop lifecycle — and how a Unix-socket hook shim drives a live office floor.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-code-hooks-explained/note-1.png",
+ "alt": "Hand-drawn sketch from “Claude Code Hooks, Explained (PreToolUse, PostToolUse, Stop)”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-code-hooks-explained/note-2.png",
+ "alt": "Hand-drawn sketch from “Claude Code Hooks, Explained (PreToolUse, PostToolUse, Stop)”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-code-multi-agent-setup-tutorial": {
@@ -189,7 +434,20 @@
"prompt": "Hero image for a blog post titled \"Set Up a Claude Code Multi-Agent Workflow in 10 Minutes\". The post is about: A from-zero Claude Code multi-agent setup: install Munder Difflin, onboard, spawn a few agents, and watch the GOD orchestrator route your first task.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-code-multi-agent-setup-tutorial/note-1.png",
+ "alt": "Hand-drawn sketch from “Set Up a Claude Code Multi-Agent Workflow in 10 Minutes”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-code-multi-agent-setup-tutorial/note-2.png",
+ "alt": "Hand-drawn sketch from “Set Up a Claude Code Multi-Agent Workflow in 10 Minutes”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-code-orchestration-guide": {
@@ -201,7 +459,20 @@
"prompt": "Hero image for a blog post titled \"Orchestrating Claude Code Agents: A Practical Guide\". The post is about: How to orchestrate Claude Code agents in practice: what orchestration means, how a GOD orchestrator routes and escalates work, and how to wire it up.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-code-orchestration-guide/note-1.png",
+ "alt": "Hand-drawn sketch from “Orchestrating Claude Code Agents: A Practical Guide”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-code-orchestration-guide/note-2.png",
+ "alt": "Hand-drawn sketch from “Orchestrating Claude Code Agents: A Practical Guide”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-code-orchestration-tools-compared": {
@@ -210,10 +481,23 @@
"hero": {
"file": "assets/media/claude-code-orchestration-tools-compared/hero.png",
"alt": "Illustration: Claude Code Orchestration Tools, Compared",
- "prompt": "Hero image for a blog post titled \"Claude Code Orchestration Tools, Compared\". The post is about: Claude Code orchestration tools compared on memory, messaging, visibility, control, and local-first \u2014 across Claude Squad, Conductor, Crystal, and more.",
+ "prompt": "Hero image for a blog post titled \"Claude Code Orchestration Tools, Compared\". The post is about: Claude Code orchestration tools compared on memory, messaging, visibility, control, and local-first — across Claude Squad, Conductor, Crystal, and more.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-code-orchestration-tools-compared/note-1.png",
+ "alt": "Hand-drawn sketch from “Claude Code Orchestration Tools, Compared”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-code-orchestration-tools-compared/note-2.png",
+ "alt": "Hand-drawn sketch from “Claude Code Orchestration Tools, Compared”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-code-subagents-vs-multi-agent-harness": {
@@ -225,7 +509,20 @@
"prompt": "Hero image for a blog post titled \"Claude Code Subagents vs a Multi-Agent Harness\". The post is about: Claude Code subagents vs a multi-agent harness: where subagents stop and a harness with shared memory, messaging, and an orchestrator takes over.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-code-subagents-vs-multi-agent-harness/note-1.png",
+ "alt": "Hand-drawn sketch from “Claude Code Subagents vs a Multi-Agent Harness”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-code-subagents-vs-multi-agent-harness/note-2.png",
+ "alt": "Hand-drawn sketch from “Claude Code Subagents vs a Multi-Agent Harness”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-squad-alternative": {
@@ -237,7 +534,20 @@
"prompt": "Hero image for a blog post titled \"Looking for a Claude Squad Alternative?\". The post is about: What Claude Squad does well, where it stops, and why a memory-backed, orchestrated hive may be the Claude Squad alternative you're after.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-squad-alternative/note-1.png",
+ "alt": "Hand-drawn sketch from “Looking for a Claude Squad Alternative?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-squad-alternative/note-2.png",
+ "alt": "Hand-drawn sketch from “Looking for a Claude Squad Alternative?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"claude-squad-vs-munder-difflin": {
@@ -249,7 +559,20 @@
"prompt": "Hero image for a blog post titled \"Claude Squad vs Munder Difflin: Which Should You Use?\". The post is about: Claude Squad vs Munder Difflin: a lean terminal session manager against a memory-backed, orchestrated, visual hive. Feature table and an honest verdict.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/claude-squad-vs-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “Claude Squad vs Munder Difflin: Which Should You Use?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/claude-squad-vs-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “Claude Squad vs Munder Difflin: Which Should You Use?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"cline-vs-munder-difflin": {
@@ -258,10 +581,23 @@
"hero": {
"file": "assets/media/cline-vs-munder-difflin/hero.png",
"alt": "Illustration: Cline vs Munder Difflin: In-Editor Agent or Local Hive?",
- "prompt": "Hero image for a blog post titled \"Cline vs Munder Difflin: In-Editor Agent or Local Hive?\". The post is about: A fair comparison of Cline and Munder Difflin \u2014 an in-editor BYOK coding agent vs a local multi-agent orchestration hive \u2014 and when to pick which.",
+ "prompt": "Hero image for a blog post titled \"Cline vs Munder Difflin: In-Editor Agent or Local Hive?\". The post is about: A fair comparison of Cline and Munder Difflin — an in-editor BYOK coding agent vs a local multi-agent orchestration hive — and when to pick which.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/cline-vs-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “Cline vs Munder Difflin: In-Editor Agent or Local Hive?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/cline-vs-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “Cline vs Munder Difflin: In-Editor Agent or Local Hive?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"command-center-guide": {
@@ -270,10 +606,23 @@
"hero": {
"file": "assets/media/command-center-guide/hero.png",
"alt": "Illustration: The Command Center: Kanban, Fleet, and Budgets in One Place",
- "prompt": "Hero image for a blog post titled \"The Command Center: Kanban, Fleet, and Budgets in One Place\". The post is about: A guide to Munder Difflin's Command Center \u2014 the task kanban, live fleet monitoring, per-agent budgets and cost telemetry \u2014 and when to watch the board instead of the floor.",
+ "prompt": "Hero image for a blog post titled \"The Command Center: Kanban, Fleet, and Budgets in One Place\". The post is about: A guide to Munder Difflin's Command Center — the task kanban, live fleet monitoring, per-agent budgets and cost telemetry — and when to watch the board instead of the floor.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/command-center-guide/note-1.png",
+ "alt": "Hand-drawn sketch from “The Command Center: Kanban, Fleet, and Budgets in One Place”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/command-center-guide/note-2.png",
+ "alt": "Hand-drawn sketch from “The Command Center: Kanban, Fleet, and Budgets in One Place”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"compressing-agent-memory": {
@@ -285,7 +634,20 @@
"prompt": "Hero image for a blog post titled \"Compressing Agent Memory Without Losing the Original\". The post is about: How and why to compress an agent's long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/compressing-agent-memory/note-1.png",
+ "alt": "Hand-drawn sketch from “Compressing Agent Memory Without Losing the Original”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/compressing-agent-memory/note-2.png",
+ "alt": "Hand-drawn sketch from “Compressing Agent Memory Without Losing the Original”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"conductor-claude-code-alternative": {
@@ -297,7 +659,20 @@
"prompt": "Hero image for a blog post titled \"A Conductor Alternative for Orchestrating Claude Code\". The post is about: Conductor is a polished macOS app for parallel Claude Code worktrees. When to pick a cross-platform, orchestrated hive as your Conductor alternative.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/conductor-claude-code-alternative/note-1.png",
+ "alt": "Hand-drawn sketch from “A Conductor Alternative for Orchestrating Claude Code”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/conductor-claude-code-alternative/note-2.png",
+ "alt": "Hand-drawn sketch from “A Conductor Alternative for Orchestrating Claude Code”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"context-engineering-for-ai-agents": {
@@ -306,10 +681,23 @@
"hero": {
"file": "assets/media/context-engineering-for-ai-agents/hero.png",
"alt": "Illustration: Context Engineering for AI Agents: Budgeting the Window",
- "prompt": "Hero image for a blog post titled \"Context Engineering for AI Agents: Budgeting the Window\". The post is about: Why context engineering beats prompt wording for agents \u2014 and the tactics (isolation, retrieval, externalized state, compaction) that keep the window lean.",
+ "prompt": "Hero image for a blog post titled \"Context Engineering for AI Agents: Budgeting the Window\". The post is about: Why context engineering beats prompt wording for agents — and the tactics (isolation, retrieval, externalized state, compaction) that keep the window lean.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/context-engineering-for-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Context Engineering for AI Agents: Budgeting the Window”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/context-engineering-for-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Context Engineering for AI Agents: Budgeting the Window”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"coordinating-ai-coding-agents": {
@@ -318,10 +706,23 @@
"hero": {
"file": "assets/media/coordinating-ai-coding-agents/hero.png",
"alt": "Illustration: The Best Way to Coordinate AI Coding Agents",
- "prompt": "Hero image for a blog post titled \"The Best Way to Coordinate AI Coding Agents\". The post is about: The best way to coordinate AI coding agents: single-writer files, a message router, a one-scribe plan, and an orchestrator \u2014 cooperate, not clobber.",
+ "prompt": "Hero image for a blog post titled \"The Best Way to Coordinate AI Coding Agents\". The post is about: The best way to coordinate AI coding agents: single-writer files, a message router, a one-scribe plan, and an orchestrator — cooperate, not clobber.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/coordinating-ai-coding-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “The Best Way to Coordinate AI Coding Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/coordinating-ai-coding-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “The Best Way to Coordinate AI Coding Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"crewai-autogen-vs-a-local-agent-harness": {
@@ -330,10 +731,23 @@
"hero": {
"file": "assets/media/crewai-autogen-vs-a-local-agent-harness/hero.png",
"alt": "Illustration: CrewAI and AutoGen vs a Local Agent Harness: Framework or App?",
- "prompt": "Hero image for a blog post titled \"CrewAI and AutoGen vs a Local Agent Harness: Framework or App?\". The post is about: CrewAI, AutoGen (now Microsoft Agent Framework), and LangGraph are frameworks \u2014 Python you write to build your own agent system. A multi-agent harness is an app you download that runs a team on your repos today. Here's how to tell which one you actually need.",
+ "prompt": "Hero image for a blog post titled \"CrewAI and AutoGen vs a Local Agent Harness: Framework or App?\". The post is about: CrewAI, AutoGen (now Microsoft Agent Framework), and LangGraph are frameworks — Python you write to build your own agent system. A multi-agent harness is an app you download that runs a team on your repos today. Here's how to tell which one you actually need.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/crewai-autogen-vs-a-local-agent-harness/note-1.png",
+ "alt": "Hand-drawn sketch from “CrewAI and AutoGen vs a Local Agent Harness: Framework or App?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/crewai-autogen-vs-a-local-agent-harness/note-2.png",
+ "alt": "Hand-drawn sketch from “CrewAI and AutoGen vs a Local Agent Harness: Framework or App?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"crystal-claude-code-alternative": {
@@ -342,10 +756,23 @@
"hero": {
"file": "assets/media/crystal-claude-code-alternative/hero.png",
"alt": "Illustration: A Crystal Alternative: Multi-Agent Claude Code with Memory",
- "prompt": "Hero image for a blog post titled \"A Crystal Alternative: Multi-Agent Claude Code with Memory\". The post is about: Crystal runs parallel Claude Code worktrees well. Where a memory-backed, orchestrated hive changes the workflow \u2014 and when to stick with Crystal.",
+ "prompt": "Hero image for a blog post titled \"A Crystal Alternative: Multi-Agent Claude Code with Memory\". The post is about: Crystal runs parallel Claude Code worktrees well. Where a memory-backed, orchestrated hive changes the workflow — and when to stick with Crystal.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/crystal-claude-code-alternative/note-1.png",
+ "alt": "Hand-drawn sketch from “A Crystal Alternative: Multi-Agent Claude Code with Memory”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/crystal-claude-code-alternative/note-2.png",
+ "alt": "Hand-drawn sketch from “A Crystal Alternative: Multi-Agent Claude Code with Memory”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"debugging-multi-agent-systems": {
@@ -357,7 +784,20 @@
"prompt": "Hero image for a blog post titled \"How to Debug a Multi-Agent System\". The post is about: How to debug a multi-agent system: use the event log, per-agent terminals, message trails, and git history to find why a hive of AI agents went sideways.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/debugging-multi-agent-systems/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Debug a Multi-Agent System”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/debugging-multi-agent-systems/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Debug a Multi-Agent System”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"deploy-a-blog-writer-agent": {
@@ -366,22 +806,48 @@
"hero": {
"file": "assets/media/deploy-a-blog-writer-agent/hero.png",
"alt": "Illustration: Deploy a Blog-Writer Agent: The One That Wrote This Post",
- "prompt": "Hero image for a blog post titled \"Deploy a Blog-Writer Agent: The One That Wrote This Post\". The post is about: How Munder Difflin's blog is written by an automated writer agent in the hive \u2014 drafts in a worktree, single-committer integration, Eleventy build, human-gated deploy. Build your own.",
+ "prompt": "Hero image for a blog post titled \"Deploy a Blog-Writer Agent: The One That Wrote This Post\". The post is about: How Munder Difflin's blog is written by an automated writer agent in the hive — drafts in a worktree, single-committer integration, Eleventy build, human-gated deploy. Build your own.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/deploy-a-blog-writer-agent/note-1.png",
+ "alt": "Hand-drawn sketch from “Deploy a Blog-Writer Agent: The One That Wrote This Post”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/deploy-a-blog-writer-agent/note-2.png",
+ "alt": "Hand-drawn sketch from “Deploy a Blog-Writer Agent: The One That Wrote This Post”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"deploy-automated-pr-reviewer-agent": {
- "title": "Deploy a PR Reviewer That Never Sleeps \u2014 In About One Prompt",
+ "title": "Deploy a PR Reviewer That Never Sleeps — In About One Prompt",
"category": "orchestration",
"hero": {
"file": "assets/media/deploy-automated-pr-reviewer-agent/hero.png",
- "alt": "Illustration: Deploy a PR Reviewer That Never Sleeps \u2014 In About One Prompt",
- "prompt": "Hero image for a blog post titled \"Deploy a PR Reviewer That Never Sleeps \u2014 In About One Prompt\". The post is about: A how-to for standing up a fully automated PR-reviewing agent in Munder Difflin \u2014 one that reads your real source (not just the PR description), de-dupes noise, and only escalates what matters. With a real triage run that turned 22 duplicate firings into a clean v0.2.5 patch queue.",
+ "alt": "Illustration: Deploy a PR Reviewer That Never Sleeps — In About One Prompt",
+ "prompt": "Hero image for a blog post titled \"Deploy a PR Reviewer That Never Sleeps — In About One Prompt\". The post is about: A how-to for standing up a fully automated PR-reviewing agent in Munder Difflin — one that reads your real source (not just the PR description), de-dupes noise, and only escalates what matters. With a real triage run that turned 22 duplicate firings into a clean v0.2.5 patch queue.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/deploy-automated-pr-reviewer-agent/note-1.png",
+ "alt": "Hand-drawn sketch from “Deploy a PR Reviewer That Never Sleeps — In About One Prompt”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/deploy-automated-pr-reviewer-agent/note-2.png",
+ "alt": "Hand-drawn sketch from “Deploy a PR Reviewer That Never Sleeps — In About One Prompt”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"do-more-with-less-model-routing": {
@@ -390,10 +856,23 @@
"hero": {
"file": "assets/media/do-more-with-less-model-routing/hero.png",
"alt": "Illustration: Do More With Less: Smart Model Routing Across Agents",
- "prompt": "Hero image for a blog post titled \"Do More With Less: Smart Model Routing Across Agents\". The post is about: Why a hive of agents shouldn't all run the biggest model \u2014 and how routing the right task to the right model cuts cost and latency without losing quality.",
+ "prompt": "Hero image for a blog post titled \"Do More With Less: Smart Model Routing Across Agents\". The post is about: Why a hive of agents shouldn't all run the biggest model — and how routing the right task to the right model cuts cost and latency without losing quality.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/do-more-with-less-model-routing/note-1.png",
+ "alt": "Hand-drawn sketch from “Do More With Less: Smart Model Routing Across Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/do-more-with-less-model-routing/note-2.png",
+ "alt": "Hand-drawn sketch from “Do More With Less: Smart Model Routing Across Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"does-the-june-2026-agent-sdk-change-affect-munder-difflin": {
@@ -405,7 +884,20 @@
"prompt": "Hero image for a blog post titled \"Does the June 2026 Agent SDK Change Affect Munder Difflin?\". The post is about: From June 15, 2026 the Claude Agent SDK gets a separate credit. Munder Difflin drives the native Claude Code CLI, so your hive runs on your plan as before.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “Does the June 2026 Agent SDK Change Affect Munder Difflin?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “Does the June 2026 Agent SDK Change Affect Munder Difflin?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"evaluating-ai-agent-reliability": {
@@ -417,7 +909,20 @@
"prompt": "Hero image for a blog post titled \"Evaluating AI Agent Reliability: How to Measure What You Can Trust\". The post is about: How to measure whether an AI agent is reliable enough to trust: reliability thresholds, why benchmarks overstate, and evaluating on your own codebase.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/evaluating-ai-agent-reliability/note-1.png",
+ "alt": "Hand-drawn sketch from “Evaluating AI Agent Reliability: How to Measure What You Can Trust”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/evaluating-ai-agent-reliability/note-2.png",
+ "alt": "Hand-drawn sketch from “Evaluating AI Agent Reliability: How to Measure What You Can Trust”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"file-based-coordination-vs-message-queues": {
@@ -429,7 +934,20 @@
"prompt": "Hero image for a blog post titled \"File-Based Coordination vs Message Queues for AI Agents\". The post is about: Why a local agent hive coordinates through plain files, not Redis or RabbitMQ: the zero-ops wins, the real tradeoffs, and where files hit a ceiling.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/file-based-coordination-vs-message-queues/note-1.png",
+ "alt": "Hand-drawn sketch from “File-Based Coordination vs Message Queues for AI Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/file-based-coordination-vs-message-queues/note-2.png",
+ "alt": "Hand-drawn sketch from “File-Based Coordination vs Message Queues for AI Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"from-one-terminal-to-a-team": {
@@ -438,10 +956,23 @@
"hero": {
"file": "assets/media/from-one-terminal-to-a-team/hero.png",
"alt": "Illustration: From One Terminal to a Team: Scaling Your Claude Code Workflow",
- "prompt": "Hero image for a blog post titled \"From One Terminal to a Team: Scaling Your Claude Code Workflow\". The post is about: The workflow shift from a single Claude Code session to a coordinated team of agents \u2014 what changes, where it breaks, and the concrete before-and-after.",
+ "prompt": "Hero image for a blog post titled \"From One Terminal to a Team: Scaling Your Claude Code Workflow\". The post is about: The workflow shift from a single Claude Code session to a coordinated team of agents — what changes, where it breaks, and the concrete before-and-after.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/from-one-terminal-to-a-team/note-1.png",
+ "alt": "Hand-drawn sketch from “From One Terminal to a Team: Scaling Your Claude Code Workflow”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/from-one-terminal-to-a-team/note-2.png",
+ "alt": "Hand-drawn sketch from “From One Terminal to a Team: Scaling Your Claude Code Workflow”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"generative-engine-optimization-techniques": {
@@ -450,10 +981,23 @@
"hero": {
"file": "assets/media/generative-engine-optimization-techniques/hero.png",
"alt": "Illustration: Generative Engine Optimization: The Techniques the Research Backs",
- "prompt": "Hero image for a blog post titled \"Generative Engine Optimization: The Techniques the Research Backs\". The post is about: What the first peer-reviewed GEO study found works to get content cited by AI \u2014 statistics, source citations, quotes \u2014 and why keyword stuffing backfires.",
+ "prompt": "Hero image for a blog post titled \"Generative Engine Optimization: The Techniques the Research Backs\". The post is about: What the first peer-reviewed GEO study found works to get content cited by AI — statistics, source citations, quotes — and why keyword stuffing backfires.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/generative-engine-optimization-techniques/note-1.png",
+ "alt": "Hand-drawn sketch from “Generative Engine Optimization: The Techniques the Research Backs”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/generative-engine-optimization-techniques/note-2.png",
+ "alt": "Hand-drawn sketch from “Generative Engine Optimization: The Techniques the Research Backs”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"github-copilot-cli-vs-claude-code-for-hive-work": {
@@ -462,10 +1006,23 @@
"hero": {
"file": "assets/media/github-copilot-cli-vs-claude-code-for-hive-work/hero.png",
"alt": "Illustration: GitHub Copilot CLI vs Claude Code as Hive Workers",
- "prompt": "Hero image for a blog post titled \"GitHub Copilot CLI vs Claude Code as Hive Workers\". The post is about: How GitHub Copilot CLI and Claude Code behave as agent engines inside a multi-agent harness: hooks, inbox mail, orchestration, session lifecycle \u2014 and why the right answer is to run both.",
+ "prompt": "Hero image for a blog post titled \"GitHub Copilot CLI vs Claude Code as Hive Workers\". The post is about: How GitHub Copilot CLI and Claude Code behave as agent engines inside a multi-agent harness: hooks, inbox mail, orchestration, session lifecycle — and why the right answer is to run both.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-1.png",
+ "alt": "Hand-drawn sketch from “GitHub Copilot CLI vs Claude Code as Hive Workers”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-2.png",
+ "alt": "Hand-drawn sketch from “GitHub Copilot CLI vs Claude Code as Hive Workers”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"give-claude-code-long-term-memory": {
@@ -477,7 +1034,20 @@
"prompt": "Hero image for a blog post titled \"How to Give Claude Code Long-Term Memory\". The post is about: Claude Code forgets between sessions. Here's how a markdown-first memory layer with semantic recall lets your agents remember across runs.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/give-claude-code-long-term-memory/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Give Claude Code Long-Term Memory”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/give-claude-code-long-term-memory/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Give Claude Code Long-Term Memory”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"hire-manifest-untrusted-input": {
@@ -489,7 +1059,20 @@
"prompt": "Hero image for a blog post titled \"Treating a Hire Manifest as Untrusted Input\". The post is about: A shareable agent-config manifest is attacker input. How Munder Difflin's import pipeline stays inert: no auto-spawn, default-deny flags, and an SSRF-safe bounded fetch.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/hire-manifest-untrusted-input/note-1.png",
+ "alt": "Hand-drawn sketch from “Treating a Hire Manifest as Untrusted Input”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/hire-manifest-untrusted-input/note-2.png",
+ "alt": "Hand-drawn sketch from “Treating a Hire Manifest as Untrusted Input”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-agents-remember-semantic-memory": {
@@ -498,10 +1081,23 @@
"hero": {
"file": "assets/media/how-agents-remember-semantic-memory/hero.png",
"alt": "Illustration: How AI Agents Remember: Semantic Memory in a Hive",
- "prompt": "Hero image for a blog post titled \"How AI Agents Remember: Semantic Memory in a Hive\". The post is about: A code-grounded guide to how AI agents remember \u2014 the MemPalace mine loop, per-agent wings, and wake-up digest that give a Claude Code hive shared recall.",
+ "prompt": "Hero image for a blog post titled \"How AI Agents Remember: Semantic Memory in a Hive\". The post is about: A code-grounded guide to how AI agents remember — the MemPalace mine loop, per-agent wings, and wake-up digest that give a Claude Code hive shared recall.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-agents-remember-semantic-memory/note-1.png",
+ "alt": "Hand-drawn sketch from “How AI Agents Remember: Semantic Memory in a Hive”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-agents-remember-semantic-memory/note-2.png",
+ "alt": "Hand-drawn sketch from “How AI Agents Remember: Semantic Memory in a Hive”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-ai-agents-verify-their-own-work": {
@@ -510,10 +1106,23 @@
"hero": {
"file": "assets/media/how-ai-agents-verify-their-own-work/hero.png",
"alt": "Illustration: How AI Agents Verify Their Own Work (Before Saying 'Done')",
- "prompt": "Hero image for a blog post titled \"How AI Agents Verify Their Own Work (Before Saying 'Done')\". The post is about: The discipline that makes an autonomous coding agent trustworthy: prove every claim, reproduce the green, and check the fix \u2014 not just the intent.",
+ "prompt": "Hero image for a blog post titled \"How AI Agents Verify Their Own Work (Before Saying 'Done')\". The post is about: The discipline that makes an autonomous coding agent trustworthy: prove every claim, reproduce the green, and check the fix — not just the intent.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-ai-agents-verify-their-own-work/note-1.png",
+ "alt": "Hand-drawn sketch from “How AI Agents Verify Their Own Work (Before Saying 'Done')”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-ai-agents-verify-their-own-work/note-2.png",
+ "alt": "Hand-drawn sketch from “How AI Agents Verify Their Own Work (Before Saying 'Done')”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-ai-answer-engines-choose-sources": {
@@ -522,10 +1131,23 @@
"hero": {
"file": "assets/media/how-ai-answer-engines-choose-sources/hero.png",
"alt": "Illustration: How AI Answer Engines Choose What to Cite",
- "prompt": "Hero image for a blog post titled \"How AI Answer Engines Choose What to Cite\". The post is about: How ChatGPT, Claude, Perplexity, and Google AI Overviews actually pick and cite sources in 2026 \u2014 the per-engine signals, and why there's no single rank.",
+ "prompt": "Hero image for a blog post titled \"How AI Answer Engines Choose What to Cite\". The post is about: How ChatGPT, Claude, Perplexity, and Google AI Overviews actually pick and cite sources in 2026 — the per-engine signals, and why there's no single rank.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-ai-answer-engines-choose-sources/note-1.png",
+ "alt": "Hand-drawn sketch from “How AI Answer Engines Choose What to Cite”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-ai-answer-engines-choose-sources/note-2.png",
+ "alt": "Hand-drawn sketch from “How AI Answer Engines Choose What to Cite”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-the-god-orchestrator-works": {
@@ -537,7 +1159,20 @@
"prompt": "Hero image for a blog post titled \"Inside the GOD Orchestrator: Routing, Adjudication, Escalation\". The post is about: A deep dive into the Claude Code orchestrator: how a GOD agent reads requests, routes work, adjudicates routine traffic, and escalates the critical few.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-the-god-orchestrator-works/note-1.png",
+ "alt": "Hand-drawn sketch from “Inside the GOD Orchestrator: Routing, Adjudication, Escalation”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-the-god-orchestrator-works/note-2.png",
+ "alt": "Hand-drawn sketch from “Inside the GOD Orchestrator: Routing, Adjudication, Escalation”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-to-add-a-github-copilot-cli-agent": {
@@ -549,7 +1184,20 @@
"prompt": "Hero image for a blog post titled \"How to Add a GitHub Copilot CLI Agent to Your Floor\". The post is about: A step-by-step v0.3.3 walkthrough: install GitHub Copilot CLI (or let the harness install it for you), hire a Copilot worker, pick a model, and know exactly what print mode can and can't do.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-to-add-a-github-copilot-cli-agent/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Add a GitHub Copilot CLI Agent to Your Floor”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-to-add-a-github-copilot-cli-agent/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Add a GitHub Copilot CLI Agent to Your Floor”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-to-choose-a-multi-agent-tool": {
@@ -558,22 +1206,48 @@
"hero": {
"file": "assets/media/how-to-choose-a-multi-agent-tool/hero.png",
"alt": "Illustration: How to Choose a Multi-Agent Coding Tool: A Buyer's Checklist",
- "prompt": "Hero image for a blog post titled \"How to Choose a Multi-Agent Coding Tool: A Buyer's Checklist\". The post is about: A decision framework for choosing a multi-agent coding tool \u2014 memory, control, visibility, cost, local-first \u2014 with a simple scoring rubric you can run.",
+ "prompt": "Hero image for a blog post titled \"How to Choose a Multi-Agent Coding Tool: A Buyer's Checklist\". The post is about: A decision framework for choosing a multi-agent coding tool — memory, control, visibility, cost, local-first — with a simple scoring rubric you can run.",
"status": "ready"
},
- "inline": {},
- "youtube": []
- },
- "how-to-hire-from-the-agent-gallery": {
- "title": "How to Hire From the Agent Gallery",
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-to-choose-a-multi-agent-tool/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Choose a Multi-Agent Coding Tool: A Buyer's Checklist”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-to-choose-a-multi-agent-tool/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Choose a Multi-Agent Coding Tool: A Buyer's Checklist”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "how-to-hire-from-the-agent-gallery": {
+ "title": "How to Hire From the Agent Gallery",
"category": "guides",
"hero": {
"file": "assets/media/how-to-hire-from-the-agent-gallery/hero.png",
"alt": "Illustration: How to Hire From the Agent Gallery",
- "prompt": "Hero image for a blog post titled \"How to Hire From the Agent Gallery\". The post is about: A practical guide to Munder Difflin's Agent Gallery: browse six off-the-shelf hires, import one from a link or file, review the pre-filled manifest, customize identity, workspace, engine, and briefing \u2014 then spawn it yourself.",
+ "prompt": "Hero image for a blog post titled \"How to Hire From the Agent Gallery\". The post is about: A practical guide to Munder Difflin's Agent Gallery: browse six off-the-shelf hires, import one from a link or file, review the pre-filled manifest, customize identity, workspace, engine, and briefing — then spawn it yourself.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-to-hire-from-the-agent-gallery/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Hire From the Agent Gallery”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-to-hire-from-the-agent-gallery/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Hire From the Agent Gallery”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-to-install-and-use-munder-difflin": {
@@ -582,10 +1256,23 @@
"hero": {
"file": "assets/media/how-to-install-and-use-munder-difflin/hero.png",
"alt": "Illustration: How to Install and Use Munder Difflin",
- "prompt": "Hero image for a blog post titled \"How to Install and Use Munder Difflin\". The post is about: Install Munder Difflin on macOS, Windows, or Linux and put a hive of Claude Code agents to work on ambitious, long-horizon tasks \u2014 start to finish.",
+ "prompt": "Hero image for a blog post titled \"How to Install and Use Munder Difflin\". The post is about: Install Munder Difflin on macOS, Windows, or Linux and put a hive of Claude Code agents to work on ambitious, long-horizon tasks — start to finish.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-to-install-and-use-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Install and Use Munder Difflin”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-to-install-and-use-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Install and Use Munder Difflin”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-to-run-multiple-claude-code-agents": {
@@ -597,7 +1284,20 @@
"prompt": "Hero image for a blog post titled \"How to Run Multiple Claude Code Agents (Without Losing Track)\". The post is about: Run several Claude Code agents in parallel without the chaos: give each a role, let them coordinate, and stop alt-tabbing between terminal windows.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-to-run-multiple-claude-code-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Run Multiple Claude Code Agents (Without Losing Track)”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-to-run-multiple-claude-code-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Run Multiple Claude Code Agents (Without Losing Track)”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-to-talk-to-your-orchestrator": {
@@ -609,7 +1309,20 @@
"prompt": "Hero image for a blog post titled \"How to Brief Your Orchestrator (So the Floor Actually Ships)\". The post is about: A practical guide to briefing Munder Difflin's GOD orchestrator: state the goal not the steps, set constraints and budgets, name the deliverable, and let Michael staff the floor. With bad-vs-good brief examples, mid-run steering, and Talk mode.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-to-talk-to-your-orchestrator/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Brief Your Orchestrator (So the Floor Actually Ships)”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-to-talk-to-your-orchestrator/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Brief Your Orchestrator (So the Floor Actually Ships)”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"how-to-use-the-built-in-monaco-ide": {
@@ -618,10 +1331,23 @@
"hero": {
"file": "assets/media/how-to-use-the-built-in-monaco-ide/hero.png",
"alt": "Illustration: How to Use the Built-in Monaco IDE",
- "prompt": "Hero image for a blog post titled \"How to Use the Built-in Monaco IDE\". The post is about: A practical walkthrough of Munder Difflin v0.3.3's built-in Monaco IDE: the title-bar IDE button, the git CHANGES rail with side-by-side diffs vs HEAD, the file tree, tabs, Cmd/Ctrl+S save \u2014 and the agent review workflow it enables.",
+ "prompt": "Hero image for a blog post titled \"How to Use the Built-in Monaco IDE\". The post is about: A practical walkthrough of Munder Difflin v0.3.3's built-in Monaco IDE: the title-bar IDE button, the git CHANGES rail with side-by-side diffs vs HEAD, the file tree, tabs, Cmd/Ctrl+S save — and the agent review workflow it enables.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/how-to-use-the-built-in-monaco-ide/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Use the Built-in Monaco IDE”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/how-to-use-the-built-in-monaco-ide/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Use the Built-in Monaco IDE”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"human-in-the-loop-ai-agents": {
@@ -633,7 +1359,20 @@
"prompt": "Hero image for a blog post titled \"Human-in-the-Loop AI Agents: Approvals That Don't Slow You Down\". The post is about: Design human-in-the-loop AI agents that stay autonomous: an approvals queue that escalates only spend, destructive ops, and scope changes.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/human-in-the-loop-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Human-in-the-Loop AI Agents: Approvals That Don't Slow You Down”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/human-in-the-loop-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Human-in-the-Loop AI Agents: Approvals That Don't Slow You Down”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"human-in-the-loop-approving-ai-agents": {
@@ -645,7 +1384,20 @@
"prompt": "Hero image for a blog post titled \"Approving AI Agents: Human-in-the-Loop Without a Queue\". The post is about: How to approve what AI agents do without a parallel approval queue: native permission prompts, routing 'to: human' to the orchestrator, remote approval.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/human-in-the-loop-approving-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Approving AI Agents: Human-in-the-Loop Without a Queue”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/human-in-the-loop-approving-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Approving AI Agents: Human-in-the-Loop Without a Queue”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"keep-agent-semantic-memory-clean": {
@@ -654,10 +1406,23 @@
"hero": {
"file": "assets/media/keep-agent-semantic-memory-clean/hero.png",
"alt": "Illustration: Keep Your Agent's Semantic Memory Clean: Don't Index the Config",
- "prompt": "Hero image for a blog post titled \"Keep Your Agent's Semantic Memory Clean: Don't Index the Config\". The post is about: A semantic memory layer is only as good as what you feed it \u2014 how an agent's recall got swamped by config and logs, and the .gitignore + prune fix.",
+ "prompt": "Hero image for a blog post titled \"Keep Your Agent's Semantic Memory Clean: Don't Index the Config\". The post is about: A semantic memory layer is only as good as what you feed it — how an agent's recall got swamped by config and logs, and the .gitignore + prune fix.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/keep-agent-semantic-memory-clean/note-1.png",
+ "alt": "Hand-drawn sketch from “Keep Your Agent's Semantic Memory Clean: Don't Index the Config”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/keep-agent-semantic-memory-clean/note-2.png",
+ "alt": "Hand-drawn sketch from “Keep Your Agent's Semantic Memory Clean: Don't Index the Config”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"launching-munder-difflin-v0-2-0": {
@@ -669,7 +1434,20 @@
"prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.2.0\". The post is about: Munder Difflin v0.2.0 is here: a Command Center overhaul, per-agent token budgets, live OpenTelemetry observability, a circuit breaker, durable SQLite persistence, and a big round of community fixes.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/launching-munder-difflin-v0-2-0/note-1.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.2.0”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/launching-munder-difflin-v0-2-0/note-2.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.2.0”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"launching-munder-difflin-v0-2-4": {
@@ -678,10 +1456,23 @@
"hero": {
"file": "assets/media/launching-munder-difflin-v0-2-4/hero.png",
"alt": "Illustration: Launching Munder Difflin v0.2.4",
- "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.2.4\". The post is about: Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity \u2014 no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.",
+ "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.2.4\". The post is about: Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/launching-munder-difflin-v0-2-4/note-1.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.2.4”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/launching-munder-difflin-v0-2-4/note-2.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.2.4”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"launching-munder-difflin-v0-2-8": {
@@ -693,7 +1484,20 @@
"prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.2.8: Shareable Hires\". The post is about: Munder Difflin v0.2.8 ships Shareable Hires: a one-click, portable agent role manifest + The Hiring Fair gallery. Click a hire link, review every field, then spawn it yourself.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/launching-munder-difflin-v0-2-8/note-1.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.2.8: Shareable Hires”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/launching-munder-difflin-v0-2-8/note-2.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.2.8: Shareable Hires”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"launching-munder-difflin-v0-3-0": {
@@ -702,10 +1506,23 @@
"hero": {
"file": "assets/media/launching-munder-difflin-v0-3-0/hero.png",
"alt": "Illustration: Launching Munder Difflin v0.3.0: Selectable Engines, Integrations & Slack-Spawned Workers",
- "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.3.0: Selectable Engines, Integrations & Slack-Spawned Workers\". The post is about: Munder Difflin v0.3.0 makes every hire \u2014 and Michael himself \u2014 a pluggable engine, adds an integrations registry with a write-only secret broker, and lets the god orchestrator spawn an ephemeral worker straight from Slack.",
+ "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.3.0: Selectable Engines, Integrations & Slack-Spawned Workers\". The post is about: Munder Difflin v0.3.0 makes every hire — and Michael himself — a pluggable engine, adds an integrations registry with a write-only secret broker, and lets the god orchestrator spawn an ephemeral worker straight from Slack.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/launching-munder-difflin-v0-3-0/note-1.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.3.0: Selectable Engines, Integrations & Slack-Spawned Workers”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/launching-munder-difflin-v0-3-0/note-2.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.3.0: Selectable Engines, Integrations & Slack-Spawned Workers”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"launching-munder-difflin-v0-3-2": {
@@ -714,10 +1531,23 @@
"hero": {
"file": "assets/media/launching-munder-difflin-v0-3-2/hero.png",
"alt": "Illustration: Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator",
- "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator\". The post is about: Munder Difflin v0.3.2 adds Realtime Michael \u2014 a low-latency voice channel to the GOD orchestrator. Talk to Michael and he listens, answers, and acts: reading the hive and, behind spoken echo-back confirmation, dispatching, spawning, and steering the floor in real time.",
+ "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator\". The post is about: Munder Difflin v0.3.2 adds Realtime Michael — a low-latency voice channel to the GOD orchestrator. Talk to Michael and he listens, answers, and acts: reading the hive and, behind spoken echo-back confirmation, dispatching, spawning, and steering the floor in real time.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/launching-munder-difflin-v0-3-2/note-1.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/launching-munder-difflin-v0-3-2/note-2.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"launching-munder-difflin-v0-3-3": {
@@ -726,10 +1556,23 @@
"hero": {
"file": "assets/media/launching-munder-difflin-v0-3-3/hero.png",
"alt": "Illustration: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support",
- "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support\". The post is about: Munder Difflin v0.3.3 adds a full Monaco IDE \u2014 file tree, editor tabs, save, and side-by-side git diffs of your agents' changes \u2014 plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.",
+ "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support\". The post is about: Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents' changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/launching-munder-difflin-v0-3-3/note-1.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/launching-munder-difflin-v0-3-3/note-2.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"launching-munder-difflin-v0-3-5": {
@@ -741,7 +1584,51 @@
"prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself\". The post is about: The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/launching-munder-difflin-v0-3-5/note-1.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/launching-munder-difflin-v0-3-5/note-2.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "launching-munder-difflin-v0-4-4": {
+ "title": "Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk",
+ "category": "story",
+ "hero": {
+ "file": "assets/media/launching-munder-difflin-v0-4-4/hero.png",
+ "alt": "Illustration: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk",
+ "prompt": "Hero image for a blog post titled \"Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk\". The post is about: v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/launching-munder-difflin-v0-4-4/note-1.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/launching-munder-difflin-v0-4-4/note-2.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-3": {
+ "file": "assets/media/launching-munder-difflin-v0-4-4/note-3.png",
+ "alt": "Hand-drawn sketch from “Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"local-first-ai-agent-orchestration": {
@@ -750,10 +1637,23 @@
"hero": {
"file": "assets/media/local-first-ai-agent-orchestration/hero.png",
"alt": "Illustration: Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud",
- "prompt": "Hero image for a blog post titled \"Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud\". The post is about: How local-first AI agent orchestration works under the hood \u2014 the loop, mailboxes, scheduler, and audit log that coordinate a hive on one machine.",
+ "prompt": "Hero image for a blog post titled \"Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud\". The post is about: How local-first AI agent orchestration works under the hood — the loop, mailboxes, scheduler, and audit log that coordinate a hive on one machine.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/local-first-ai-agent-orchestration/note-1.png",
+ "alt": "Hand-drawn sketch from “Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/local-first-ai-agent-orchestration/note-2.png",
+ "alt": "Hand-drawn sketch from “Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"local-first-vs-cloud-agent-sdks": {
@@ -765,7 +1665,20 @@
"prompt": "Hero image for a blog post titled \"Local-First vs Cloud Agent SDKs: Which Wins in 2026?\". The post is about: Local-first agent hives vs the 2026 cloud agent SDK wave (OpenAI, Google ADK, Microsoft, MCP/A2A): what each optimizes for, and when to pick which.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/local-first-vs-cloud-agent-sdks/note-1.png",
+ "alt": "Hand-drawn sketch from “Local-First vs Cloud Agent SDKs: Which Wins in 2026?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/local-first-vs-cloud-agent-sdks/note-2.png",
+ "alt": "Hand-drawn sketch from “Local-First vs Cloud Agent SDKs: Which Wins in 2026?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"long-running-agents-the-2026-shift": {
@@ -774,10 +1687,23 @@
"hero": {
"file": "assets/media/long-running-agents-the-2026-shift/hero.png",
"alt": "Illustration: Long-Running Agents: The 2026 Shift from Minutes to Hours",
- "prompt": "Hero image for a blog post titled \"Long-Running Agents: The 2026 Shift from Minutes to Hours\". The post is about: Agents used to answer in seconds; now they run for hours. The data behind the shift \u2014 and why a longer agent is a different problem, not just a bigger one.",
+ "prompt": "Hero image for a blog post titled \"Long-Running Agents: The 2026 Shift from Minutes to Hours\". The post is about: Agents used to answer in seconds; now they run for hours. The data behind the shift — and why a longer agent is a different problem, not just a bigger one.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/long-running-agents-the-2026-shift/note-1.png",
+ "alt": "Hand-drawn sketch from “Long-Running Agents: The 2026 Shift from Minutes to Hours”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/long-running-agents-the-2026-shift/note-2.png",
+ "alt": "Hand-drawn sketch from “Long-Running Agents: The 2026 Shift from Minutes to Hours”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"loop-engineering-for-ai-agents": {
@@ -786,10 +1712,23 @@
"hero": {
"file": "assets/media/loop-engineering-for-ai-agents/hero.png",
"alt": "Illustration: Loop Engineering: Designing Agent Loops That Converge",
- "prompt": "Hero image for a blog post titled \"Loop Engineering: Designing Agent Loops That Converge\". The post is about: Everyone engineers the prompt; almost nobody engineers the loop around it. Stop conditions, drain loops, retry with backoff, compaction cycles, breaker escalation, budgets, and human gates \u2014 the outer-loop mechanics that make an agent converge instead of run away.",
+ "prompt": "Hero image for a blog post titled \"Loop Engineering: Designing Agent Loops That Converge\". The post is about: Everyone engineers the prompt; almost nobody engineers the loop around it. Stop conditions, drain loops, retry with backoff, compaction cycles, breaker escalation, budgets, and human gates — the outer-loop mechanics that make an agent converge instead of run away.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/loop-engineering-for-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Loop Engineering: Designing Agent Loops That Converge”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/loop-engineering-for-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Loop Engineering: Designing Agent Loops That Converge”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"manage-multiple-claude-code-sessions": {
@@ -801,7 +1740,20 @@
"prompt": "Hero image for a blog post titled \"How to Manage Multiple Claude Code Sessions Like a Pro\". The post is about: Tactics to manage multiple Claude Code sessions without losing track: naming, roles, context isolation, and when a harness beats juggling terminal tabs.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/manage-multiple-claude-code-sessions/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Manage Multiple Claude Code Sessions Like a Pro”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/manage-multiple-claude-code-sessions/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Manage Multiple Claude Code Sessions Like a Pro”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"markdown-first-agent-memory": {
@@ -813,7 +1765,20 @@
"prompt": "Hero image for a blog post titled \"Why We Built Agent Memory Markdown-First\". The post is about: Markdown-first AI agent long-term memory: plain notes a human can read and git can diff, with a semantic index on top that degrades gracefully.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/markdown-first-agent-memory/note-1.png",
+ "alt": "Hand-drawn sketch from “Why We Built Agent Memory Markdown-First”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/markdown-first-agent-memory/note-2.png",
+ "alt": "Hand-drawn sketch from “Why We Built Agent Memory Markdown-First”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"mcp-and-skills-in-a-hive": {
@@ -822,10 +1787,23 @@
"hero": {
"file": "assets/media/mcp-and-skills-in-a-hive/hero.png",
"alt": "Illustration: Bringing Your MCP Servers and Skills Into a Hive of Agents",
- "prompt": "Hero image for a blog post titled \"Bringing Your MCP Servers and Skills Into a Hive of Agents\". The post is about: How agents in a hive inherit your existing Claude Code MCP servers, skills, and tools \u2014 and how to scope which agent gets which capability.",
+ "prompt": "Hero image for a blog post titled \"Bringing Your MCP Servers and Skills Into a Hive of Agents\". The post is about: How agents in a hive inherit your existing Claude Code MCP servers, skills, and tools — and how to scope which agent gets which capability.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/mcp-and-skills-in-a-hive/note-1.png",
+ "alt": "Hand-drawn sketch from “Bringing Your MCP Servers and Skills Into a Hive of Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/mcp-and-skills-in-a-hive/note-2.png",
+ "alt": "Hand-drawn sketch from “Bringing Your MCP Servers and Skills Into a Hive of Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"mcp-security-tool-poisoning": {
@@ -834,10 +1812,23 @@
"hero": {
"file": "assets/media/mcp-security-tool-poisoning/hero.png",
"alt": "Illustration: MCP Tool Poisoning: How to Secure the Model Context Protocol",
- "prompt": "Hero image for a blog post titled \"MCP Tool Poisoning: How to Secure the Model Context Protocol\". The post is about: How the Model Context Protocol gets attacked \u2014 tool poisoning, rug pulls, command injection \u2014 and the layered defenses that secure your MCP tools.",
+ "prompt": "Hero image for a blog post titled \"MCP Tool Poisoning: How to Secure the Model Context Protocol\". The post is about: How the Model Context Protocol gets attacked — tool poisoning, rug pulls, command injection — and the layered defenses that secure your MCP tools.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/mcp-security-tool-poisoning/note-1.png",
+ "alt": "Hand-drawn sketch from “MCP Tool Poisoning: How to Secure the Model Context Protocol”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/mcp-security-tool-poisoning/note-2.png",
+ "alt": "Hand-drawn sketch from “MCP Tool Poisoning: How to Secure the Model Context Protocol”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"multi-agent-orchestration-patterns": {
@@ -846,10 +1837,23 @@
"hero": {
"file": "assets/media/multi-agent-orchestration-patterns/hero.png",
"alt": "Illustration: Multi-Agent Orchestration Patterns: Which Topology, and When",
- "prompt": "Hero image for a blog post titled \"Multi-Agent Orchestration Patterns: Which Topology, and When\". The post is about: The multi-agent orchestration patterns \u2014 orchestrator-worker, pipeline, fan-out, debate, swarm, blackboard \u2014 when to use each, and when one agent wins.",
+ "prompt": "Hero image for a blog post titled \"Multi-Agent Orchestration Patterns: Which Topology, and When\". The post is about: The multi-agent orchestration patterns — orchestrator-worker, pipeline, fan-out, debate, swarm, blackboard — when to use each, and when one agent wins.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/multi-agent-orchestration-patterns/note-1.png",
+ "alt": "Hand-drawn sketch from “Multi-Agent Orchestration Patterns: Which Topology, and When”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/multi-agent-orchestration-patterns/note-2.png",
+ "alt": "Hand-drawn sketch from “Multi-Agent Orchestration Patterns: Which Topology, and When”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"munder-difflin-faq": {
@@ -858,10 +1862,17 @@
"hero": {
"file": "assets/media/munder-difflin-faq/hero.png",
"alt": "Illustration: Munder Difflin FAQ: Everything People Ask",
- "prompt": "Hero image for a blog post titled \"Munder Difflin FAQ: Everything People Ask\". The post is about: Answers to the top Munder Difflin questions \u2014 what it is, is it free, does it run locally, which platforms, and how it differs from many terminals.",
+ "prompt": "Hero image for a blog post titled \"Munder Difflin FAQ: Everything People Ask\". The post is about: Answers to the top Munder Difflin questions — what it is, is it free, does it run locally, which platforms, and how it differs from many terminals.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/munder-difflin-faq/note-1.png",
+ "alt": "Hand-drawn sketch from “Munder Difflin FAQ: Everything People Ask”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"munder-difflin-v0-2-4-feature-walkthrough": {
@@ -870,10 +1881,23 @@
"hero": {
"file": "assets/media/munder-difflin-v0-2-4-feature-walkthrough/hero.png",
"alt": "Illustration: Munder Difflin v0.2.4 Feature Walkthrough",
- "prompt": "Hero image for a blog post titled \"Munder Difflin v0.2.4 Feature Walkthrough\". The post is about: A comprehensive guide to every change in Munder Difflin v0.2.4 \u2014 how the Codex lifecycle-hook bridge achieves full hive parity, what the Schedules tab adds, why tunnelmole replaced localtunnel, and what else shipped.",
+ "prompt": "Hero image for a blog post titled \"Munder Difflin v0.2.4 Feature Walkthrough\". The post is about: A comprehensive guide to every change in Munder Difflin v0.2.4 — how the Codex lifecycle-hook bridge achieves full hive parity, what the Schedules tab adds, why tunnelmole replaced localtunnel, and what else shipped.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-1.png",
+ "alt": "Hand-drawn sketch from “Munder Difflin v0.2.4 Feature Walkthrough”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-2.png",
+ "alt": "Hand-drawn sketch from “Munder Difflin v0.2.4 Feature Walkthrough”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"node-pty-electron-real-terminals": {
@@ -885,7 +1909,45 @@
"prompt": "Hero image for a blog post titled \"Real Terminals in Electron with node-pty\". The post is about: How to run byte-for-byte authentic shells inside Electron with node-pty: the native-rebuild gotcha, the macOS PATH trap, and streaming PTY output over IPC.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/node-pty-electron-real-terminals/note-1.png",
+ "alt": "Hand-drawn sketch from “Real Terminals in Electron with node-pty”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/node-pty-electron-real-terminals/note-2.png",
+ "alt": "Hand-drawn sketch from “Real Terminals in Electron with node-pty”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "number-five-on-product-hunt": {
+ "title": "Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers",
+ "category": "story",
+ "hero": {
+ "file": "assets/media/number-five-on-product-hunt/hero.png",
+ "alt": "Illustration: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers",
+ "prompt": "Hero image for a blog post titled \"Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers\". The post is about: Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek's harness launch that day. Here's what actually happened: the numbers, the people who showed up, and the two pieces of feedback we're already shipping fixes for.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/number-five-on-product-hunt/note-1.png",
+ "alt": "Hand-drawn sketch from “Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/number-five-on-product-hunt/note-2.png",
+ "alt": "Hand-drawn sketch from “Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"observability-for-agent-fleets": {
@@ -897,19 +1959,45 @@
"prompt": "Hero image for a blog post titled \"Observability for Agent Fleets: Seeing What Your Agents Do\". The post is about: 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.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/observability-for-agent-fleets/note-1.png",
+ "alt": "Hand-drawn sketch from “Observability for Agent Fleets: Seeing What Your Agents Do”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/observability-for-agent-fleets/note-2.png",
+ "alt": "Hand-drawn sketch from “Observability for Agent Fleets: Seeing What Your Agents Do”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"one-prompt-automated-pr-review": {
- "title": "One Prompt, Five PR Reviews, and an Hourly Automation \u2014 A Dogfooding Story",
+ "title": "One Prompt, Five PR Reviews, and an Hourly Automation — A Dogfooding Story",
"category": "story",
"hero": {
"file": "assets/media/one-prompt-automated-pr-review/hero.png",
- "alt": "Illustration: One Prompt, Five PR Reviews, and an Hourly Automation \u2014 A Dogfooding Story",
- "prompt": "Hero image for a blog post titled \"One Prompt, Five PR Reviews, and an Hourly Automation \u2014 A Dogfooding Story\". The post is about: How a single prompt to the Munder Difflin god agent reviewed all open PRs and set up a recurring hourly PR reviewer \u2014 while the repo was blowing up with 400+ stars.",
+ "alt": "Illustration: One Prompt, Five PR Reviews, and an Hourly Automation — A Dogfooding Story",
+ "prompt": "Hero image for a blog post titled \"One Prompt, Five PR Reviews, and an Hourly Automation — A Dogfooding Story\". The post is about: How a single prompt to the Munder Difflin god agent reviewed all open PRs and set up a recurring hourly PR reviewer — while the repo was blowing up with 400+ stars.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/one-prompt-automated-pr-review/note-1.png",
+ "alt": "Hand-drawn sketch from “One Prompt, Five PR Reviews, and an Hourly Automation — A Dogfooding Story”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/one-prompt-automated-pr-review/note-2.png",
+ "alt": "Hand-drawn sketch from “One Prompt, Five PR Reviews, and an Hourly Automation — A Dogfooding Story”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"open-source-ai-tools-on-purpose": {
@@ -918,10 +2006,23 @@
"hero": {
"file": "assets/media/open-source-ai-tools-on-purpose/hero.png",
"alt": "Illustration: Building AI Dev Tools in the Open, On Purpose",
- "prompt": "Hero image for a blog post titled \"Building AI Dev Tools in the Open, On Purpose\". The post is about: Agents touch your code, keys, and memory. That's why agent tooling should be open source and local-first \u2014 so you can verify it, not just trust it.",
+ "prompt": "Hero image for a blog post titled \"Building AI Dev Tools in the Open, On Purpose\". The post is about: Agents touch your code, keys, and memory. That's why agent tooling should be open source and local-first — so you can verify it, not just trust it.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/open-source-ai-tools-on-purpose/note-1.png",
+ "alt": "Hand-drawn sketch from “Building AI Dev Tools in the Open, On Purpose”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/open-source-ai-tools-on-purpose/note-2.png",
+ "alt": "Hand-drawn sketch from “Building AI Dev Tools in the Open, On Purpose”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"orca-vs-munder-difflin": {
@@ -930,10 +2031,23 @@
"hero": {
"file": "assets/media/orca-vs-munder-difflin/hero.png",
"alt": "Illustration: Orca vs Munder Difflin: Agent IDE or Agent Office?",
- "prompt": "Hero image for a blog post titled \"Orca vs Munder Difflin: Agent IDE or Agent Office?\". The post is about: Orca is a YC-backed Agent IDE for driving coding agents side by side in isolated worktrees. Munder Difflin is an agent office that runs itself. An honest comparison of the two \u2014 and when each one is the right pick.",
+ "prompt": "Hero image for a blog post titled \"Orca vs Munder Difflin: Agent IDE or Agent Office?\". The post is about: Orca is a YC-backed Agent IDE for driving coding agents side by side in isolated worktrees. Munder Difflin is an agent office that runs itself. An honest comparison of the two — and when each one is the right pick.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/orca-vs-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “Orca vs Munder Difflin: Agent IDE or Agent Office?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/orca-vs-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “Orca vs Munder Difflin: Agent IDE or Agent Office?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"overnight-ai-coding-realistic-expectations": {
@@ -942,10 +2056,23 @@
"hero": {
"file": "assets/media/overnight-ai-coding-realistic-expectations/hero.png",
"alt": "Illustration: Overnight AI Coding: What's Realistic (and What's Not)",
- "prompt": "Hero image for a blog post titled \"Overnight AI Coding: What's Realistic (and What's Not)\". The post is about: An honest look at letting AI coding agents run overnight \u2014 what works today, where guardrails matter, and what still needs a human in the morning.",
+ "prompt": "Hero image for a blog post titled \"Overnight AI Coding: What's Realistic (and What's Not)\". The post is about: An honest look at letting AI coding agents run overnight — what works today, where guardrails matter, and what still needs a human in the morning.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/overnight-ai-coding-realistic-expectations/note-1.png",
+ "alt": "Hand-drawn sketch from “Overnight AI Coding: What's Realistic (and What's Not)”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/overnight-ai-coding-realistic-expectations/note-2.png",
+ "alt": "Hand-drawn sketch from “Overnight AI Coding: What's Realistic (and What's Not)”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"prompt-caching-for-ai-agents": {
@@ -954,10 +2081,23 @@
"hero": {
"file": "assets/media/prompt-caching-for-ai-agents/hero.png",
"alt": "Illustration: Prompt Caching for AI Agents: Stop Paying for the Same Tokens Twice",
- "prompt": "Hero image for a blog post titled \"Prompt Caching for AI Agents: Stop Paying for the Same Tokens Twice\". The post is about: An agent re-sends the same prompt, tools, and context every turn. Prompt caching makes you pay for that prefix once \u2014 here's how to design for it.",
+ "prompt": "Hero image for a blog post titled \"Prompt Caching for AI Agents: Stop Paying for the Same Tokens Twice\". The post is about: An agent re-sends the same prompt, tools, and context every turn. Prompt caching makes you pay for that prefix once — here's how to design for it.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/prompt-caching-for-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Prompt Caching for AI Agents: Stop Paying for the Same Tokens Twice”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/prompt-caching-for-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Prompt Caching for AI Agents: Stop Paying for the Same Tokens Twice”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"qm-vs-munder-difflin": {
@@ -966,10 +2106,23 @@
"hero": {
"file": "assets/media/qm-vs-munder-difflin/hero.png",
"alt": "Illustration: qm vs Munder Difflin: YC's Multiplayer Harness or a Local-First Agent Office?",
- "prompt": "Hero image for a blog post titled \"qm vs Munder Difflin: YC's Multiplayer Harness or a Local-First Agent Office?\". The post is about: An honest comparison of YC's qm and Munder Difflin: both orchestrate fleets of CLI coding agents with security postures, scheduled background work, and Slack \u2014 one as a headless multiplayer harness for teams, one as a local-first desktop office with real terminals, voice, and a built-in IDE.",
+ "prompt": "Hero image for a blog post titled \"qm vs Munder Difflin: YC's Multiplayer Harness or a Local-First Agent Office?\". The post is about: An honest comparison of YC's qm and Munder Difflin: both orchestrate fleets of CLI coding agents with security postures, scheduled background work, and Slack — one as a headless multiplayer harness for teams, one as a local-first desktop office with real terminals, voice, and a built-in IDE.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/qm-vs-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “qm vs Munder Difflin: YC's Multiplayer Harness or a Local-First Agent Office?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/qm-vs-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “qm vs Munder Difflin: YC's Multiplayer Harness or a Local-First Agent Office?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"recovering-from-agent-failures": {
@@ -981,7 +2134,20 @@
"prompt": "Hero image for a blog post titled \"Recovering From Agent Failures: Resilience Patterns for a Hive\". The post is about: How multi-agent systems survive partial failure: retry with stale-lock recovery, poison-message quarantine, hop-cap circuit breaking, idempotent handling.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/recovering-from-agent-failures/note-1.png",
+ "alt": "Hand-drawn sketch from “Recovering From Agent Failures: Resilience Patterns for a Hive”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/recovering-from-agent-failures/note-2.png",
+ "alt": "Hand-drawn sketch from “Recovering From Agent Failures: Resilience Patterns for a Hive”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"rendering-many-live-terminals-performance": {
@@ -993,7 +2159,20 @@
"prompt": "Hero image for a blog post titled \"Rendering Many Live Terminals Without Melting the CPU\". The post is about: xterm.js performance for many live PTYs: a terminal pool, render-only-visible, smart scrollback, and accelerated rendering to stream dozens at once.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/rendering-many-live-terminals-performance/note-1.png",
+ "alt": "Hand-drawn sketch from “Rendering Many Live Terminals Without Melting the CPU”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/rendering-many-live-terminals-performance/note-2.png",
+ "alt": "Hand-drawn sketch from “Rendering Many Live Terminals Without Melting the CPU”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"review-agent-work-where-it-happens": {
@@ -1005,7 +2184,20 @@
"prompt": "Hero image for a blog post titled \"Review Agent Work Where It Happens\". The post is about: AI agents produce diffs faster than humans can review them, and alt-tabbing to an external editor breaks supervision flow. The case for review-in-place: Munder Difflin's built-in Monaco IDE puts a CHANGES rail and side-by-side diffs vs HEAD right on the office floor.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/review-agent-work-where-it-happens/note-1.png",
+ "alt": "Hand-drawn sketch from “Review Agent Work Where It Happens”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/review-agent-work-where-it-happens/note-2.png",
+ "alt": "Hand-drawn sketch from “Review Agent Work Where It Happens”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"run-a-mixed-engine-office": {
@@ -1017,7 +2209,45 @@
"prompt": "Hero image for a blog post titled \"Run a Mixed-Engine Office: the Right CLI for Every Desk\". The post is about: A practical guide to mixing agent engines on one Munder Difflin floor: Claude Code as orchestrator, Codex for coding bursts, Copilot for dispatched tasks, and OpenCode/Crush/pi.dev for BYOK keys and local models.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/run-a-mixed-engine-office/note-1.png",
+ "alt": "Hand-drawn sketch from “Run a Mixed-Engine Office: the Right CLI for Every Desk”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/run-a-mixed-engine-office/note-2.png",
+ "alt": "Hand-drawn sketch from “Run a Mixed-Engine Office: the Right CLI for Every Desk”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "run-a-release-train-with-agents": {
+ "title": "Run a Release Train with Agents",
+ "category": "use-cases",
+ "hero": {
+ "file": "assets/media/run-a-release-train-with-agents/hero.png",
+ "alt": "Illustration: Run a Release Train with Agents",
+ "prompt": "Hero image for a blog post titled \"Run a Release Train with Agents\". The post is about: Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/run-a-release-train-with-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Run a Release Train with Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/run-a-release-train-with-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Run a Release Train with Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"run-ai-agent-hive-from-slack-setup": {
@@ -1026,10 +2256,23 @@
"hero": {
"file": "assets/media/run-ai-agent-hive-from-slack-setup/hero.png",
"alt": "Illustration: Run Your AI Agent Hive from Slack: The Complete Setup",
- "prompt": "Hero image for a blog post titled \"Run Your AI Agent Hive from Slack: The Complete Setup\". The post is about: Step-by-step setup for driving Munder Difflin's AI agent hive from Slack: create the app, set scopes, paste the tunnel Request URL, and @mention your bot to start work \u2014 done-summaries post back in-thread.",
+ "prompt": "Hero image for a blog post titled \"Run Your AI Agent Hive from Slack: The Complete Setup\". The post is about: Step-by-step setup for driving Munder Difflin's AI agent hive from Slack: create the app, set scopes, paste the tunnel Request URL, and @mention your bot to start work — done-summaries post back in-thread.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/run-ai-agent-hive-from-slack-setup/note-1.png",
+ "alt": "Hand-drawn sketch from “Run Your AI Agent Hive from Slack: The Complete Setup”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/run-ai-agent-hive-from-slack-setup/note-2.png",
+ "alt": "Hand-drawn sketch from “Run Your AI Agent Hive from Slack: The Complete Setup”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"run-an-office-of-ai-agents": {
@@ -1038,10 +2281,23 @@
"hero": {
"file": "assets/media/run-an-office-of-ai-agents/hero.png",
"alt": "Illustration: Run an Office of AI Agents While You Sleep",
- "prompt": "Hero image for a blog post titled \"Run an Office of AI Agents While You Sleep\". The post is about: What it takes to run a self-coordinating office of AI coding agents that keeps shipping after you log off \u2014 and the guardrails that keep it sane.",
+ "prompt": "Hero image for a blog post titled \"Run an Office of AI Agents While You Sleep\". The post is about: What it takes to run a self-coordinating office of AI coding agents that keeps shipping after you log off — and the guardrails that keep it sane.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/run-an-office-of-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Run an Office of AI Agents While You Sleep”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/run-an-office-of-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Run an Office of AI Agents While You Sleep”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"run-munder-difflin-on-a-mac-mini": {
@@ -1050,22 +2306,48 @@
"hero": {
"file": "assets/media/run-munder-difflin-on-a-mac-mini/hero.png",
"alt": "Illustration: Run Munder Difflin Locally on a Mac Mini",
- "prompt": "Hero image for a blog post titled \"Run Munder Difflin Locally on a Mac Mini\". The post is about: A step-by-step guide to running a whole Munder Difflin hive offline on an Apple Silicon Mac Mini \u2014 how to size models to your unified memory, install Ollama or LM Studio, and wire OpenCode and Crush to a local endpoint.",
+ "prompt": "Hero image for a blog post titled \"Run Munder Difflin Locally on a Mac Mini\". The post is about: A step-by-step guide to running a whole Munder Difflin hive offline on an Apple Silicon Mac Mini — how to size models to your unified memory, install Ollama or LM Studio, and wire OpenCode and Crush to a local endpoint.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/run-munder-difflin-on-a-mac-mini/note-1.png",
+ "alt": "Hand-drawn sketch from “Run Munder Difflin Locally on a Mac Mini”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/run-munder-difflin-on-a-mac-mini/note-2.png",
+ "alt": "Hand-drawn sketch from “Run Munder Difflin Locally on a Mac Mini”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"run-munder-difflin-on-open-models": {
- "title": "Run Munder Difflin on Open-Source Models \u2014 Fully Local or via a Third-Party Provider",
+ "title": "Run Munder Difflin on Open-Source Models — Fully Local or via a Third-Party Provider",
"category": "guides",
"hero": {
"file": "assets/media/run-munder-difflin-on-open-models/hero.png",
- "alt": "Illustration: Run Munder Difflin on Open-Source Models \u2014 Fully Local or via a Third-Party Provider",
- "prompt": "Hero image for a blog post titled \"Run Munder Difflin on Open-Source Models \u2014 Fully Local or via a Third-Party Provider\". The post is about: Munder Difflin v0.3.1 runs your agent floor on open-weight models \u2014 gpt-oss, Qwen3, DeepSeek, Llama, Mistral, GLM, Kimi \u2014 either fully local (Ollama/LM Studio/vLLM) or through a third-party OSS provider. Here's how to wire each across the OpenCode, Crush, and pi engines.",
+ "alt": "Illustration: Run Munder Difflin on Open-Source Models — Fully Local or via a Third-Party Provider",
+ "prompt": "Hero image for a blog post titled \"Run Munder Difflin on Open-Source Models — Fully Local or via a Third-Party Provider\". The post is about: Munder Difflin v0.3.1 runs your agent floor on open-weight models — gpt-oss, Qwen3, DeepSeek, Llama, Mistral, GLM, Kimi — either fully local (Ollama/LM Studio/vLLM) or through a third-party OSS provider. Here's how to wire each across the OpenCode, Crush, and pi engines.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/run-munder-difflin-on-open-models/note-1.png",
+ "alt": "Hand-drawn sketch from “Run Munder Difflin on Open-Source Models — Fully Local or via a Third-Party Provider”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/run-munder-difflin-on-open-models/note-2.png",
+ "alt": "Hand-drawn sketch from “Run Munder Difflin on Open-Source Models — Fully Local or via a Third-Party Provider”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"scheduling-autonomous-agent-missions": {
@@ -1074,10 +2356,23 @@
"hero": {
"file": "assets/media/scheduling-autonomous-agent-missions/hero.png",
"alt": "Illustration: Make a Hive Work While You Sleep: Scheduling Autonomous Agent Missions",
- "prompt": "Hero image for a blog post titled \"Make a Hive Work While You Sleep: Scheduling Autonomous Agent Missions\". The post is about: How scheduled missions make a Claude Code hive work on a cadence \u2014 recurring requests that fire on an interval and land in an agent's queue, hands-free.",
+ "prompt": "Hero image for a blog post titled \"Make a Hive Work While You Sleep: Scheduling Autonomous Agent Missions\". The post is about: How scheduled missions make a Claude Code hive work on a cadence — recurring requests that fire on an interval and land in an agent's queue, hands-free.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/scheduling-autonomous-agent-missions/note-1.png",
+ "alt": "Hand-drawn sketch from “Make a Hive Work While You Sleep: Scheduling Autonomous Agent Missions”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/scheduling-autonomous-agent-missions/note-2.png",
+ "alt": "Hand-drawn sketch from “Make a Hive Work While You Sleep: Scheduling Autonomous Agent Missions”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"security-for-ai-coding-agents": {
@@ -1089,7 +2384,20 @@
"prompt": "Hero image for a blog post titled \"Security for AI Coding Agents: A Practical Guide\". The post is about: How to run AI coding agents safely: contain the blast radius, scope every task, treat agent input as untrusted, and gate the irreversible behind a human.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/security-for-ai-coding-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Security for AI Coding Agents: A Practical Guide”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/security-for-ai-coding-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Security for AI Coding Agents: A Practical Guide”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"semantic-memory-for-ai-agents": {
@@ -1101,7 +2409,51 @@
"prompt": "Hero image for a blog post titled \"Semantic Memory for AI Agents: Recall in Milliseconds\". The post is about: What semantic memory for AI agents is, why a markdown-first store beats a heavy DB, and how a shared palace lets a hive recall a note by meaning, fast.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/semantic-memory-for-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Semantic Memory for AI Agents: Recall in Milliseconds”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/semantic-memory-for-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Semantic Memory for AI Agents: Recall in Milliseconds”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "seven-releases-in-eight-days": {
+ "title": "Seven Releases in Eight Days: 0.3.8 → 0.4.4",
+ "category": "story",
+ "hero": {
+ "file": "assets/media/seven-releases-in-eight-days/hero.png",
+ "alt": "Illustration: Seven Releases in Eight Days: 0.3.8 → 0.4.4",
+ "prompt": "Hero image for a blog post titled \"Seven Releases in Eight Days: 0.3.8 → 0.4.4\". The post is about: Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/seven-releases-in-eight-days/note-1.png",
+ "alt": "Hand-drawn sketch from “Seven Releases in Eight Days: 0.3.8 → 0.4.4”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/seven-releases-in-eight-days/note-2.png",
+ "alt": "Hand-drawn sketch from “Seven Releases in Eight Days: 0.3.8 → 0.4.4”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-3": {
+ "file": "assets/media/seven-releases-in-eight-days/note-3.png",
+ "alt": "Hand-drawn sketch from “Seven Releases in Eight Days: 0.3.8 → 0.4.4”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"shareable-agent-roles": {
@@ -1113,7 +2465,20 @@
"prompt": "Hero image for a blog post titled \"Shareable Agent Roles: A Portable Format for Hiring AI Coworkers\". The post is about: Why agent roles should be portable: what a hire manifest encodes, how one-click hiring stays safe, and how The Hiring Fair turns tacit setup into a shareable artifact.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/shareable-agent-roles/note-1.png",
+ "alt": "Hand-drawn sketch from “Shareable Agent Roles: A Portable Format for Hiring AI Coworkers”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/shareable-agent-roles/note-2.png",
+ "alt": "Hand-drawn sketch from “Shareable Agent Roles: A Portable Format for Hiring AI Coworkers”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"single-committer-git-pattern": {
@@ -1122,10 +2487,23 @@
"hero": {
"file": "assets/media/single-committer-git-pattern/hero.png",
"alt": "Illustration: The Single-Committer Pattern: Multi-Agent Git Without Corruption",
- "prompt": "Hero image for a blog post titled \"The Single-Committer Pattern: Multi-Agent Git Without Corruption\". The post is about: Parallel agents corrupt a repo with index.lock races. The single-committer pattern \u2014 agents write, one process commits \u2014 fixes concurrent git writes.",
+ "prompt": "Hero image for a blog post titled \"The Single-Committer Pattern: Multi-Agent Git Without Corruption\". The post is about: Parallel agents corrupt a repo with index.lock races. The single-committer pattern — agents write, one process commits — fixes concurrent git writes.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/single-committer-git-pattern/note-1.png",
+ "alt": "Hand-drawn sketch from “The Single-Committer Pattern: Multi-Agent Git Without Corruption”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/single-committer-git-pattern/note-2.png",
+ "alt": "Hand-drawn sketch from “The Single-Committer Pattern: Multi-Agent Git Without Corruption”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"small-team-ai-agents-playbook": {
@@ -1134,10 +2512,23 @@
"hero": {
"file": "assets/media/small-team-ai-agents-playbook/hero.png",
"alt": "Illustration: A Small-Team Playbook for AI Coding Agents",
- "prompt": "Hero image for a blog post titled \"A Small-Team Playbook for AI Coding Agents\". The post is about: How a small team adopts a hive of AI coding agents without chaos \u2014 the roles to assign, the cadence to run, and the guardrails that keep it safe.",
+ "prompt": "Hero image for a blog post titled \"A Small-Team Playbook for AI Coding Agents\". The post is about: How a small team adopts a hive of AI coding agents without chaos — the roles to assign, the cadence to run, and the guardrails that keep it safe.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/small-team-ai-agents-playbook/note-1.png",
+ "alt": "Hand-drawn sketch from “A Small-Team Playbook for AI Coding Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/small-team-ai-agents-playbook/note-2.png",
+ "alt": "Hand-drawn sketch from “A Small-Team Playbook for AI Coding Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"the-clone-army-trap-mixed-swarm-vs-identical-agents": {
@@ -1146,10 +2537,23 @@
"hero": {
"file": "assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/hero.png",
"alt": "Illustration: The Clone Army Is a Trap: Why a Mixed Swarm Beats Ten Identical Agents",
- "prompt": "Hero image for a blog post titled \"The Clone Army Is a Trap: Why a Mixed Swarm Beats Ten Identical Agents\". The post is about: Spinning up tens of identical top-tier CLI agents feels powerful and burns tokens on work a cheaper agent could do. A mixed-capability swarm with shared memory wins on cost \u2014 and often on quality.",
+ "prompt": "Hero image for a blog post titled \"The Clone Army Is a Trap: Why a Mixed Swarm Beats Ten Identical Agents\". The post is about: Spinning up tens of identical top-tier CLI agents feels powerful and burns tokens on work a cheaper agent could do. A mixed-capability swarm with shared memory wins on cost — and often on quality.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “The Clone Army Is a Trap: Why a Mixed Swarm Beats Ten Identical Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “The Clone Army Is a Trap: Why a Mixed Swarm Beats Ten Identical Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"the-hook-shim-pattern": {
@@ -1161,7 +2565,20 @@
"prompt": "Hero image for a blog post titled \"The Hook Shim Pattern: Wiring Agent Hooks to a Live Process\". The post is about: How a tiny shim bridges Claude Code's lifecycle hooks to one live process over a Unix socket, turning per-event hooks into a telemetry and control channel.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/the-hook-shim-pattern/note-1.png",
+ "alt": "Hand-drawn sketch from “The Hook Shim Pattern: Wiring Agent Hooks to a Live Process”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/the-hook-shim-pattern/note-2.png",
+ "alt": "Hand-drawn sketch from “The Hook Shim Pattern: Wiring Agent Hooks to a Live Process”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"the-lethal-trifecta-for-coding-agents": {
@@ -1170,10 +2587,23 @@
"hero": {
"file": "assets/media/the-lethal-trifecta-for-coding-agents/hero.png",
"alt": "Illustration: The Lethal Trifecta for Coding Agents",
- "prompt": "Hero image for a blog post titled \"The Lethal Trifecta for Coding Agents\". The post is about: A coding agent reads private code, ingests untrusted content, and runs commands \u2014 the lethal trifecta. How a poisoned dependency leaks your secrets.",
+ "prompt": "Hero image for a blog post titled \"The Lethal Trifecta for Coding Agents\". The post is about: A coding agent reads private code, ingests untrusted content, and runs commands — the lethal trifecta. How a poisoned dependency leaks your secrets.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/the-lethal-trifecta-for-coding-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “The Lethal Trifecta for Coding Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/the-lethal-trifecta-for-coding-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “The Lethal Trifecta for Coding Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"the-multi-agent-cost-playbook": {
@@ -1182,10 +2612,48 @@
"hero": {
"file": "assets/media/the-multi-agent-cost-playbook/hero.png",
"alt": "Illustration: The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend",
- "prompt": "Hero image for a blog post titled \"The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend\". The post is about: Caching, batching, model tiering, context discipline, local-first \u2014 the five levers that cut a multi-agent fleet's bill, and how they compound.",
+ "prompt": "Hero image for a blog post titled \"The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend\". The post is about: Caching, batching, model tiering, context discipline, local-first — the five levers that cut a multi-agent fleet's bill, and how they compound.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/the-multi-agent-cost-playbook/note-1.png",
+ "alt": "Hand-drawn sketch from “The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/the-multi-agent-cost-playbook/note-2.png",
+ "alt": "Hand-drawn sketch from “The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "the-newline-that-silenced-windows-agents": {
+ "title": "The Newline That Silenced Every Windows Agent",
+ "category": "internals",
+ "hero": {
+ "file": "assets/media/the-newline-that-silenced-windows-agents/hero.png",
+ "alt": "Illustration: The Newline That Silenced Every Windows Agent",
+ "prompt": "Hero image for a blog post titled \"The Newline That Silenced Every Windows Agent\". The post is about: 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.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/the-newline-that-silenced-windows-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “The Newline That Silenced Every Windows Agent”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/the-newline-that-silenced-windows-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “The Newline That Silenced Every Windows Agent”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"the-office-parody-behind-munder-difflin": {
@@ -1194,10 +2662,23 @@
"hero": {
"file": "assets/media/the-office-parody-behind-munder-difflin/hero.png",
"alt": "Illustration: The Office Parody Behind Munder Difflin (and Why It Helps)",
- "prompt": "Hero image for a blog post titled \"The Office Parody Behind Munder Difflin (and Why It Helps)\". The post is about: Why Munder Difflin is a loving parody of The Office \u2014 and how the office metaphor makes a hive of AI agents genuinely easier to understand and trust.",
+ "prompt": "Hero image for a blog post titled \"The Office Parody Behind Munder Difflin (and Why It Helps)\". The post is about: Why Munder Difflin is a loving parody of The Office — and how the office metaphor makes a hive of AI agents genuinely easier to understand and trust.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/the-office-parody-behind-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “The Office Parody Behind Munder Difflin (and Why It Helps)”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/the-office-parody-behind-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “The Office Parody Behind Munder Difflin (and Why It Helps)”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"tmux-and-scripts-vs-an-agent-harness": {
@@ -1209,7 +2690,20 @@
"prompt": "Hero image for a blog post titled \"Running Agents in tmux vs an Agent Harness\". The post is about: tmux panes, git worktrees, shell scripts, and cron will absolutely run several Claude Code sessions at once. Here's what that DIY setup does well, where it breaks at scale, and what a purpose-built agent harness automates.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/tmux-and-scripts-vs-an-agent-harness/note-1.png",
+ "alt": "Hand-drawn sketch from “Running Agents in tmux vs an Agent Harness”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/tmux-and-scripts-vs-an-agent-harness/note-2.png",
+ "alt": "Hand-drawn sketch from “Running Agents in tmux vs an Agent Harness”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"trigger-ai-agents-from-github-webhook": {
@@ -1218,10 +2712,23 @@
"hero": {
"file": "assets/media/trigger-ai-agents-from-github-webhook/hero.png",
"alt": "Illustration: How to Trigger Your AI Agent Hive from a GitHub Webhook",
- "prompt": "Hero image for a blog post titled \"How to Trigger Your AI Agent Hive from a GitHub Webhook\". The post is about: Wire a GitHub webhook to Munder Difflin: a secret-gated local endpoint turns each repo event into a task for your GOD orchestrator \u2014 POST a message, get a token, poll the result. No server to host.",
+ "prompt": "Hero image for a blog post titled \"How to Trigger Your AI Agent Hive from a GitHub Webhook\". The post is about: Wire a GitHub webhook to Munder Difflin: a secret-gated local endpoint turns each repo event into a task for your GOD orchestrator — POST a message, get a token, poll the result. No server to host.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/trigger-ai-agents-from-github-webhook/note-1.png",
+ "alt": "Hand-drawn sketch from “How to Trigger Your AI Agent Hive from a GitHub Webhook”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/trigger-ai-agents-from-github-webhook/note-2.png",
+ "alt": "Hand-drawn sketch from “How to Trigger Your AI Agent Hive from a GitHub Webhook”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"trigger-ai-agents-from-slack": {
@@ -1230,10 +2737,48 @@
"hero": {
"file": "assets/media/trigger-ai-agents-from-slack/hero.png",
"alt": "Illustration: Trigger Your AI Agent Hive from Slack",
- "prompt": "Hero image for a blog post titled \"Trigger Your AI Agent Hive from Slack\". The post is about: Trigger an AI agent hive from Slack: a local webhook verifies each message and drops it into your orchestrator's queue as a task \u2014 no server to host.",
+ "prompt": "Hero image for a blog post titled \"Trigger Your AI Agent Hive from Slack\". The post is about: Trigger an AI agent hive from Slack: a local webhook verifies each message and drops it into your orchestrator's queue as a task — no server to host.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/trigger-ai-agents-from-slack/note-1.png",
+ "alt": "Hand-drawn sketch from “Trigger Your AI Agent Hive from Slack”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/trigger-ai-agents-from-slack/note-2.png",
+ "alt": "Hand-drawn sketch from “Trigger Your AI Agent Hive from Slack”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "turn-feedback-into-a-backlog-with-agents": {
+ "title": "Turn a Firehose of Feedback into a Backlog with Agents",
+ "category": "use-cases",
+ "hero": {
+ "file": "assets/media/turn-feedback-into-a-backlog-with-agents/hero.png",
+ "alt": "Illustration: Turn a Firehose of Feedback into a Backlog with Agents",
+ "prompt": "Hero image for a blog post titled \"Turn a Firehose of Feedback into a Backlog with Agents\". The post is about: 516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/turn-feedback-into-a-backlog-with-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Turn a Firehose of Feedback into a Backlog with Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/turn-feedback-into-a-backlog-with-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Turn a Firehose of Feedback into a Backlog with Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"vibe-kanban-alternative": {
@@ -1242,10 +2787,23 @@
"hero": {
"file": "assets/media/vibe-kanban-alternative/hero.png",
"alt": "Illustration: A vibe-kanban Alternative for Coordinating AI Agents",
- "prompt": "Hero image for a blog post titled \"A vibe-kanban Alternative for Coordinating AI Agents\". The post is about: vibe-kanban gives you a board to assign tasks to coding agents. When a self-routing hive is the better vibe-kanban alternative \u2014 and when a board wins.",
+ "prompt": "Hero image for a blog post titled \"A vibe-kanban Alternative for Coordinating AI Agents\". The post is about: vibe-kanban gives you a board to assign tasks to coding agents. When a self-routing hive is the better vibe-kanban alternative — and when a board wins.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/vibe-kanban-alternative/note-1.png",
+ "alt": "Hand-drawn sketch from “A vibe-kanban Alternative for Coordinating AI Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/vibe-kanban-alternative/note-2.png",
+ "alt": "Hand-drawn sketch from “A vibe-kanban Alternative for Coordinating AI Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"visualizing-ai-agents-pixijs": {
@@ -1254,10 +2812,23 @@
"hero": {
"file": "assets/media/visualizing-ai-agents-pixijs/hero.png",
"alt": "Illustration: Visualizing AI Agents with Pixi.js: An Office You Can Watch",
- "prompt": "Hero image for a blog post titled \"Visualizing AI Agents with Pixi.js: An Office You Can Watch\". The post is about: How we render AI agents as avatars on a Pixi.js office floor \u2014 driven by real hook and message events, with seat assignment, pathing, and flying envelopes.",
+ "prompt": "Hero image for a blog post titled \"Visualizing AI Agents with Pixi.js: An Office You Can Watch\". The post is about: How we render AI agents as avatars on a Pixi.js office floor — driven by real hook and message events, with seat assignment, pathing, and flying envelopes.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/visualizing-ai-agents-pixijs/note-1.png",
+ "alt": "Hand-drawn sketch from “Visualizing AI Agents with Pixi.js: An Office You Can Watch”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/visualizing-ai-agents-pixijs/note-2.png",
+ "alt": "Hand-drawn sketch from “Visualizing AI Agents with Pixi.js: An Office You Can Watch”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"voice-as-a-control-plane-for-agent-fleets": {
@@ -1266,10 +2837,48 @@
"hero": {
"file": "assets/media/voice-as-a-control-plane-for-agent-fleets/hero.png",
"alt": "Illustration: Voice Is a Control Plane, Not a Gimmick",
- "prompt": "Hero image for a blog post titled \"Voice Is a Control Plane, Not a Gimmick\". The post is about: Voice is a terrible way to write code and a great way to run a fleet. Why low-bandwidth commands over high-bandwidth work is the right split \u2014 with Munder Difflin's Talk mode (echo-back confirmation, spend caps, michael-voice attribution) as the case study.",
+ "prompt": "Hero image for a blog post titled \"Voice Is a Control Plane, Not a Gimmick\". The post is about: Voice is a terrible way to write code and a great way to run a fleet. Why low-bandwidth commands over high-bandwidth work is the right split — with Munder Difflin's Talk mode (echo-back confirmation, spend caps, michael-voice attribution) as the case study.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/voice-as-a-control-plane-for-agent-fleets/note-1.png",
+ "alt": "Hand-drawn sketch from “Voice Is a Control Plane, Not a Gimmick”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/voice-as-a-control-plane-for-agent-fleets/note-2.png",
+ "alt": "Hand-drawn sketch from “Voice Is a Control Plane, Not a Gimmick”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "we-opened-a-discord": {
+ "title": "We Opened a Discord (Merge a PR, Become Employee of the Month)",
+ "category": "story",
+ "hero": {
+ "file": "assets/media/we-opened-a-discord/hero.png",
+ "alt": "Illustration: We Opened a Discord (Merge a PR, Become Employee of the Month)",
+ "prompt": "Hero image for a blog post titled \"We Opened a Discord (Merge a PR, Become Employee of the Month)\". The post is about: Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/we-opened-a-discord/note-1.png",
+ "alt": "Hand-drawn sketch from “We Opened a Discord (Merge a PR, Become Employee of the Month)”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/we-opened-a-discord/note-2.png",
+ "alt": "Hand-drawn sketch from “We Opened a Discord (Merge a PR, Become Employee of the Month)”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"what-are-claude-code-agents": {
@@ -1278,10 +2887,23 @@
"hero": {
"file": "assets/media/what-are-claude-code-agents/hero.png",
"alt": "Illustration: What Are Claude Code Agents? And How to Use Many at Once",
- "prompt": "Hero image for a blog post titled \"What Are Claude Code Agents? And How to Use Many at Once\". The post is about: Claude Code agents explained in plain English \u2014 what an agent actually is, how subagents differ, and the leap from one agent to a coordinated team.",
+ "prompt": "Hero image for a blog post titled \"What Are Claude Code Agents? And How to Use Many at Once\". The post is about: Claude Code agents explained in plain English — what an agent actually is, how subagents differ, and the leap from one agent to a coordinated team.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/what-are-claude-code-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “What Are Claude Code Agents? And How to Use Many at Once”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/what-are-claude-code-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “What Are Claude Code Agents? And How to Use Many at Once”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"what-is-a-multi-agent-harness": {
@@ -1290,10 +2912,23 @@
"hero": {
"file": "assets/media/what-is-a-multi-agent-harness/hero.png",
"alt": "Illustration: What Is a Multi-Agent Harness? (Plain-English Guide)",
- "prompt": "Hero image for a blog post titled \"What Is a Multi-Agent Harness? (Plain-English Guide)\". The post is about: A multi-agent harness coordinates several AI coding agents into one team \u2014 here's what that means, and how it differs from a single agent or a framework.",
+ "prompt": "Hero image for a blog post titled \"What Is a Multi-Agent Harness? (Plain-English Guide)\". The post is about: A multi-agent harness coordinates several AI coding agents into one team — here's what that means, and how it differs from a single agent or a framework.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/what-is-a-multi-agent-harness/note-1.png",
+ "alt": "Hand-drawn sketch from “What Is a Multi-Agent Harness? (Plain-English Guide)”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/what-is-a-multi-agent-harness/note-2.png",
+ "alt": "Hand-drawn sketch from “What Is a Multi-Agent Harness? (Plain-English Guide)”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"what-is-aeo-for-dev-tools": {
@@ -1305,7 +2940,20 @@
"prompt": "Hero image for a blog post titled \"AEO for Dev Tools: Getting Cited by ChatGPT and Claude\". The post is about: Answer Engine Optimization for dev tools: how to get cited by ChatGPT, Claude, and Perplexity with the right robots.txt, JSON-LD, and writing patterns.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/what-is-aeo-for-dev-tools/note-1.png",
+ "alt": "Hand-drawn sketch from “AEO for Dev Tools: Getting Cited by ChatGPT and Claude”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/what-is-aeo-for-dev-tools/note-2.png",
+ "alt": "Hand-drawn sketch from “AEO for Dev Tools: Getting Cited by ChatGPT and Claude”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"what-is-an-agent-development-environment": {
@@ -1314,10 +2962,23 @@
"hero": {
"file": "assets/media/what-is-an-agent-development-environment/hero.png",
"alt": "Illustration: What Is an Agent Development Environment (ADE)?",
- "prompt": "Hero image for a blog post titled \"What Is an Agent Development Environment (ADE)?\". The post is about: ADE means two things in 2026: a platform for building agents (Letta's sense) and a workspace for shipping code with fleets of coding agents (Orca's sense). Here's the full tooling map \u2014 chat IDEs, agent CLIs, agent IDEs, and agent harnesses \u2014 and how to pick.",
+ "prompt": "Hero image for a blog post titled \"What Is an Agent Development Environment (ADE)?\". The post is about: ADE means two things in 2026: a platform for building agents (Letta's sense) and a workspace for shipping code with fleets of coding agents (Orca's sense). Here's the full tooling map — chat IDEs, agent CLIs, agent IDEs, and agent harnesses — and how to pick.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/what-is-an-agent-development-environment/note-1.png",
+ "alt": "Hand-drawn sketch from “What Is an Agent Development Environment (ADE)?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/what-is-an-agent-development-environment/note-2.png",
+ "alt": "Hand-drawn sketch from “What Is an Agent Development Environment (ADE)?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"what-is-harness-engineering": {
@@ -1326,10 +2987,48 @@
"hero": {
"file": "assets/media/what-is-harness-engineering/hero.png",
"alt": "Illustration: What Is Harness Engineering?",
- "prompt": "Hero image for a blog post titled \"What Is Harness Engineering?\". The post is about: Harness engineering is the discipline of building everything around the model \u2014 PTY plumbing, lifecycle hooks, mailboxes, memory, budgets, human gates, observability \u2014 because that's where agent reliability actually comes from. A definition, and four case studies from inside Munder Difflin.",
+ "prompt": "Hero image for a blog post titled \"What Is Harness Engineering?\". The post is about: Harness engineering is the discipline of building everything around the model — PTY plumbing, lifecycle hooks, mailboxes, memory, budgets, human gates, observability — because that's where agent reliability actually comes from. A definition, and four case studies from inside Munder Difflin.",
+ "status": "ready"
+ },
+ "inline": {
+ "note-1": {
+ "file": "assets/media/what-is-harness-engineering/note-1.png",
+ "alt": "Hand-drawn sketch from “What Is Harness Engineering?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/what-is-harness-engineering/note-2.png",
+ "alt": "Hand-drawn sketch from “What Is Harness Engineering?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
+ "youtube": []
+ },
+ "what-reddit-told-us-about-munder-difflin": {
+ "title": "What 516 Reddit Comments Told Us About Munder Difflin",
+ "category": "story",
+ "hero": {
+ "file": "assets/media/what-reddit-told-us-about-munder-difflin/hero.png",
+ "alt": "Illustration: What 516 Reddit Comments Told Us About Munder Difflin",
+ "prompt": "Hero image for a blog post titled \"What 516 Reddit Comments Told Us About Munder Difflin\". The post is about: We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/what-reddit-told-us-about-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “What 516 Reddit Comments Told Us About Munder Difflin”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/what-reddit-told-us-about-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “What 516 Reddit Comments Told Us About Munder Difflin”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"whats-new-in-agentic-ai-june-2026": {
@@ -1341,7 +3040,20 @@
"prompt": "Hero image for a blog post titled \"What's New in Agentic AI: A June 2026 Field Guide\". The post is about: A grounded June 2026 roundup of agentic AI: Claude Opus 4.8, the MCP and A2A protocol layer, usage-based agent billing, and agent governance.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/whats-new-in-agentic-ai-june-2026/note-1.png",
+ "alt": "Hand-drawn sketch from “What's New in Agentic AI: A June 2026 Field Guide”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/whats-new-in-agentic-ai-june-2026/note-2.png",
+ "alt": "Hand-drawn sketch from “What's New in Agentic AI: A June 2026 Field Guide”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"whats-up-with-munder-difflin": {
@@ -1350,10 +3062,23 @@
"hero": {
"file": "assets/media/whats-up-with-munder-difflin/hero.png",
"alt": "Illustration: What's Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own",
- "prompt": "Hero image for a blog post titled \"What's Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own\". The post is about: Everything that shipped between v0.3.3 and v0.3.7 \u2014 a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.",
+ "prompt": "Hero image for a blog post titled \"What's Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own\". The post is about: Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/whats-up-with-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “What's Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/whats-up-with-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “What's Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"when-do-agents-need-an-agent-protocol": {
@@ -1365,19 +3090,45 @@
"prompt": "Hero image for a blog post titled \"When Do AI Agents Actually Need an Agent Protocol?\". The post is about: When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/when-do-agents-need-an-agent-protocol/note-1.png",
+ "alt": "Hand-drawn sketch from “When Do AI Agents Actually Need an Agent Protocol?”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/when-do-agents-need-an-agent-protocol/note-2.png",
+ "alt": "Hand-drawn sketch from “When Do AI Agents Actually Need an Agent Protocol?”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"why-cli-agents-are-powerful": {
- "title": "Why CLI Agents Are So Powerful \u2014 and How Munder Difflin Spends Fewer Tokens Doing the Same Work",
+ "title": "Why CLI Agents Are So Powerful — and How Munder Difflin Spends Fewer Tokens Doing the Same Work",
"category": "concepts",
"hero": {
"file": "assets/media/why-cli-agents-are-powerful/hero.png",
- "alt": "Illustration: Why CLI Agents Are So Powerful \u2014 and How Munder Difflin Spends Fewer Tokens Doing the Same Work",
- "prompt": "Hero image for a blog post titled \"Why CLI Agents Are So Powerful \u2014 and How Munder Difflin Spends Fewer Tokens Doing the Same Work\". The post is about: CLI agents are powerful because they have terminal-level access: they run builds, tests, and git, and verify their own work by executing it. Here's why that matters \u2014 and the concrete ways Munder Difflin cuts token consumption while doing it.",
+ "alt": "Illustration: Why CLI Agents Are So Powerful — and How Munder Difflin Spends Fewer Tokens Doing the Same Work",
+ "prompt": "Hero image for a blog post titled \"Why CLI Agents Are So Powerful — and How Munder Difflin Spends Fewer Tokens Doing the Same Work\". The post is about: CLI agents are powerful because they have terminal-level access: they run builds, tests, and git, and verify their own work by executing it. Here's why that matters — and the concrete ways Munder Difflin cuts token consumption while doing it.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/why-cli-agents-are-powerful/note-1.png",
+ "alt": "Hand-drawn sketch from “Why CLI Agents Are So Powerful — and How Munder Difflin Spends Fewer Tokens Doing the Same Work”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/why-cli-agents-are-powerful/note-2.png",
+ "alt": "Hand-drawn sketch from “Why CLI Agents Are So Powerful — and How Munder Difflin Spends Fewer Tokens Doing the Same Work”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"why-local-first-matters-for-ai-agents": {
@@ -1386,10 +3137,23 @@
"hero": {
"file": "assets/media/why-local-first-matters-for-ai-agents/hero.png",
"alt": "Illustration: Why Local-First Matters for Your AI Agents",
- "prompt": "Hero image for a blog post titled \"Why Local-First Matters for Your AI Agents\". The post is about: The control, privacy, and cost case for keeping your AI agents and their memory on your own machine \u2014 and what cloud orchestration quietly costs.",
+ "prompt": "Hero image for a blog post titled \"Why Local-First Matters for Your AI Agents\". The post is about: The control, privacy, and cost case for keeping your AI agents and their memory on your own machine — and what cloud orchestration quietly costs.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/why-local-first-matters-for-ai-agents/note-1.png",
+ "alt": "Hand-drawn sketch from “Why Local-First Matters for Your AI Agents”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/why-local-first-matters-for-ai-agents/note-2.png",
+ "alt": "Hand-drawn sketch from “Why Local-First Matters for Your AI Agents”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"why-our-auto-update-never-ran": {
@@ -1398,10 +3162,23 @@
"hero": {
"file": "assets/media/why-our-auto-update-never-ran/hero.png",
"alt": "Illustration: Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace",
- "prompt": "Hero image for a blog post titled \"Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace\". The post is about: 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 \u2014 and a catch block that threw the evidence away. Here's how we found it, and what v0.3.7 changes.",
+ "prompt": "Hero image for a blog post titled \"Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace\". The post is about: 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's how we found it, and what v0.3.7 changes.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/why-our-auto-update-never-ran/note-1.png",
+ "alt": "Hand-drawn sketch from “Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/why-our-auto-update-never-ran/note-2.png",
+ "alt": "Hand-drawn sketch from “Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"why-we-built-munder-difflin": {
@@ -1410,10 +3187,23 @@
"hero": {
"file": "assets/media/why-we-built-munder-difflin/hero.png",
"alt": "Illustration: Why We Built Munder Difflin",
- "prompt": "Hero image for a blog post titled \"Why We Built Munder Difflin\". The post is about: The origin story of Munder Difflin \u2014 how the pain of juggling Claude Code terminals led to a coordinated, memory-backed hive of agents you can watch.",
+ "prompt": "Hero image for a blog post titled \"Why We Built Munder Difflin\". The post is about: The origin story of Munder Difflin — how the pain of juggling Claude Code terminals led to a coordinated, memory-backed hive of agents you can watch.",
"status": "ready"
},
- "inline": {},
+ "inline": {
+ "note-1": {
+ "file": "assets/media/why-we-built-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “Why We Built Munder Difflin”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/why-we-built-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “Why We Built Munder Difflin”",
+ "prompt": "",
+ "status": "ready"
+ }
+ },
"youtube": []
},
"your-first-hour-with-munder-difflin": {
@@ -1431,14 +3221,26 @@
"alt": "The office floor: suited agents at desks, one carrying a sticky note to the kanban wall",
"prompt": "Inline figure: the office floor as a system, mid-task. Several suited Xiaohei agents at simple hand-drawn desks with terminals; one Xiaohei carries a sticky note from his desk toward a kanban wall with three columns. Annotate the columns 'todo', 'doing', 'done' in blue, and the walking agent 'message in transit' in orange.",
"status": "ready"
+ },
+ "note-1": {
+ "file": "assets/media/your-first-hour-with-munder-difflin/note-1.png",
+ "alt": "Hand-drawn sketch from “Your First Hour With Munder Difflin”",
+ "prompt": "",
+ "status": "ready"
+ },
+ "note-2": {
+ "file": "assets/media/your-first-hour-with-munder-difflin/note-2.png",
+ "alt": "Hand-drawn sketch from “Your First Hour With Munder Difflin”",
+ "prompt": "",
+ "status": "ready"
}
},
"youtube": [
{
"id": "",
- "title": "Your first hour with Munder Difflin \u2014 full walkthrough",
+ "title": "Your first hour with Munder Difflin — full walkthrough",
"status": "placeholder"
}
]
}
-}
\ No newline at end of file
+}
diff --git a/blog/src/assets/blog-press.css b/blog/src/assets/blog-press.css
index 1773bf75..2b2eed3e 100644
--- a/blog/src/assets/blog-press.css
+++ b/blog/src/assets/blog-press.css
@@ -182,9 +182,12 @@ a.tag:hover { background: var(--ink); color: var(--paper); }
.ph-art { text-align: center; display: grid; gap: 8px; }
.ph-art .ph-glyph { font-size: 46px; color: var(--c, var(--accent)); }
.ph-art .ph-note { font-family: var(--grot); font-weight: 700; font-size: 12px; letter-spacing: 0.24em; text-transform: uppercase; color: var(--ink-soft); }
-.fig-inline { margin: 38px 0; }
-.fig-inline img { border: 3px solid var(--rule); }
-.fig-inline.fig-placeholder { aspect-ratio: 2/1; }
+.fig-inline { margin: 42px auto; max-width: 620px; }
+.fig-inline img { display: block; width: 100%; border: 3px solid var(--rule); border-radius: 6px; background: #fff; }
+.fig-inline figcaption { text-align: center; }
+.fig-inline:nth-of-type(odd) img { transform: rotate(-0.4deg); }
+.fig-inline:nth-of-type(even) img { transform: rotate(0.35deg); }
+.fig-inline.fig-placeholder { aspect-ratio: 15/7; }
/* post body layout */
.post-wrap { display: grid; grid-template-columns: minmax(0, 1fr) 240px; gap: 56px; padding-top: 44px; max-width: 1120px; }
diff --git a/blog/src/assets/media/agent-security-and-sandboxing/note-1.png b/blog/src/assets/media/agent-security-and-sandboxing/note-1.png
new file mode 100644
index 00000000..adcb8566
Binary files /dev/null and b/blog/src/assets/media/agent-security-and-sandboxing/note-1.png differ
diff --git a/blog/src/assets/media/agent-security-and-sandboxing/note-2.png b/blog/src/assets/media/agent-security-and-sandboxing/note-2.png
new file mode 100644
index 00000000..21327235
Binary files /dev/null and b/blog/src/assets/media/agent-security-and-sandboxing/note-2.png differ
diff --git a/blog/src/assets/media/agents-ran-our-launch-week-analytics/hero.png b/blog/src/assets/media/agents-ran-our-launch-week-analytics/hero.png
new file mode 100644
index 00000000..62dfc607
Binary files /dev/null and b/blog/src/assets/media/agents-ran-our-launch-week-analytics/hero.png differ
diff --git a/blog/src/assets/media/agents-ran-our-launch-week-analytics/note-1.png b/blog/src/assets/media/agents-ran-our-launch-week-analytics/note-1.png
new file mode 100644
index 00000000..e2ebf3c5
Binary files /dev/null and b/blog/src/assets/media/agents-ran-our-launch-week-analytics/note-1.png differ
diff --git a/blog/src/assets/media/agents-ran-our-launch-week-analytics/note-2.png b/blog/src/assets/media/agents-ran-our-launch-week-analytics/note-2.png
new file mode 100644
index 00000000..004b88a2
Binary files /dev/null and b/blog/src/assets/media/agents-ran-our-launch-week-analytics/note-2.png differ
diff --git a/blog/src/assets/media/agents-rule-of-two/note-1.png b/blog/src/assets/media/agents-rule-of-two/note-1.png
new file mode 100644
index 00000000..924a09d2
Binary files /dev/null and b/blog/src/assets/media/agents-rule-of-two/note-1.png differ
diff --git a/blog/src/assets/media/agents-rule-of-two/note-2.png b/blog/src/assets/media/agents-rule-of-two/note-2.png
new file mode 100644
index 00000000..43d215e9
Binary files /dev/null and b/blog/src/assets/media/agents-rule-of-two/note-2.png differ
diff --git a/blog/src/assets/media/ai-agent-glossary/note-1.png b/blog/src/assets/media/ai-agent-glossary/note-1.png
new file mode 100644
index 00000000..b47a17e0
Binary files /dev/null and b/blog/src/assets/media/ai-agent-glossary/note-1.png differ
diff --git a/blog/src/assets/media/ai-agent-glossary/note-2.png b/blog/src/assets/media/ai-agent-glossary/note-2.png
new file mode 100644
index 00000000..1b4b8fdd
Binary files /dev/null and b/blog/src/assets/media/ai-agent-glossary/note-2.png differ
diff --git a/blog/src/assets/media/an-agent-redesigned-this-blog/hero.png b/blog/src/assets/media/an-agent-redesigned-this-blog/hero.png
new file mode 100644
index 00000000..bd8bbcde
Binary files /dev/null and b/blog/src/assets/media/an-agent-redesigned-this-blog/hero.png differ
diff --git a/blog/src/assets/media/an-agent-redesigned-this-blog/note-1.png b/blog/src/assets/media/an-agent-redesigned-this-blog/note-1.png
new file mode 100644
index 00000000..da5caa17
Binary files /dev/null and b/blog/src/assets/media/an-agent-redesigned-this-blog/note-1.png differ
diff --git a/blog/src/assets/media/an-agent-redesigned-this-blog/note-2.png b/blog/src/assets/media/an-agent-redesigned-this-blog/note-2.png
new file mode 100644
index 00000000..25ab43f4
Binary files /dev/null and b/blog/src/assets/media/an-agent-redesigned-this-blog/note-2.png differ
diff --git a/blog/src/assets/media/append-only-event-log-agents/note-1.png b/blog/src/assets/media/append-only-event-log-agents/note-1.png
new file mode 100644
index 00000000..38acd856
Binary files /dev/null and b/blog/src/assets/media/append-only-event-log-agents/note-1.png differ
diff --git a/blog/src/assets/media/append-only-event-log-agents/note-2.png b/blog/src/assets/media/append-only-event-log-agents/note-2.png
new file mode 100644
index 00000000..1b6ccc21
Binary files /dev/null and b/blog/src/assets/media/append-only-event-log-agents/note-2.png differ
diff --git a/blog/src/assets/media/architecture-two-planes-one-renderer/note-1.png b/blog/src/assets/media/architecture-two-planes-one-renderer/note-1.png
new file mode 100644
index 00000000..21518af5
Binary files /dev/null and b/blog/src/assets/media/architecture-two-planes-one-renderer/note-1.png differ
diff --git a/blog/src/assets/media/architecture-two-planes-one-renderer/note-2.png b/blog/src/assets/media/architecture-two-planes-one-renderer/note-2.png
new file mode 100644
index 00000000..0f8e70de
Binary files /dev/null and b/blog/src/assets/media/architecture-two-planes-one-renderer/note-2.png differ
diff --git a/blog/src/assets/media/atomic-file-mailboxes-for-agents/note-1.png b/blog/src/assets/media/atomic-file-mailboxes-for-agents/note-1.png
new file mode 100644
index 00000000..1d11ed60
Binary files /dev/null and b/blog/src/assets/media/atomic-file-mailboxes-for-agents/note-1.png differ
diff --git a/blog/src/assets/media/atomic-file-mailboxes-for-agents/note-2.png b/blog/src/assets/media/atomic-file-mailboxes-for-agents/note-2.png
new file mode 100644
index 00000000..6ebb8726
Binary files /dev/null and b/blog/src/assets/media/atomic-file-mailboxes-for-agents/note-2.png differ
diff --git a/blog/src/assets/media/best-ai-coding-agents/note-1.png b/blog/src/assets/media/best-ai-coding-agents/note-1.png
new file mode 100644
index 00000000..5f41f0de
Binary files /dev/null and b/blog/src/assets/media/best-ai-coding-agents/note-1.png differ
diff --git a/blog/src/assets/media/best-ai-coding-agents/note-2.png b/blog/src/assets/media/best-ai-coding-agents/note-2.png
new file mode 100644
index 00000000..d9fb4f13
Binary files /dev/null and b/blog/src/assets/media/best-ai-coding-agents/note-2.png differ
diff --git a/blog/src/assets/media/best-claude-code-multi-agent-tools/note-1.png b/blog/src/assets/media/best-claude-code-multi-agent-tools/note-1.png
new file mode 100644
index 00000000..352823b2
Binary files /dev/null and b/blog/src/assets/media/best-claude-code-multi-agent-tools/note-1.png differ
diff --git a/blog/src/assets/media/best-claude-code-multi-agent-tools/note-2.png b/blog/src/assets/media/best-claude-code-multi-agent-tools/note-2.png
new file mode 100644
index 00000000..9ac66b29
Binary files /dev/null and b/blog/src/assets/media/best-claude-code-multi-agent-tools/note-2.png differ
diff --git a/blog/src/assets/media/building-a-terminal-ui-xterm-node-pty/note-1.png b/blog/src/assets/media/building-a-terminal-ui-xterm-node-pty/note-1.png
new file mode 100644
index 00000000..37dfd9c4
Binary files /dev/null and b/blog/src/assets/media/building-a-terminal-ui-xterm-node-pty/note-1.png differ
diff --git a/blog/src/assets/media/building-a-terminal-ui-xterm-node-pty/note-2.png b/blog/src/assets/media/building-a-terminal-ui-xterm-node-pty/note-2.png
new file mode 100644
index 00000000..083b1949
Binary files /dev/null and b/blog/src/assets/media/building-a-terminal-ui-xterm-node-pty/note-2.png differ
diff --git a/blog/src/assets/media/building-an-ai-office-floor/note-1.png b/blog/src/assets/media/building-an-ai-office-floor/note-1.png
new file mode 100644
index 00000000..d2cb5ee4
Binary files /dev/null and b/blog/src/assets/media/building-an-ai-office-floor/note-1.png differ
diff --git a/blog/src/assets/media/building-an-ai-office-floor/note-2.png b/blog/src/assets/media/building-an-ai-office-floor/note-2.png
new file mode 100644
index 00000000..95c07312
Binary files /dev/null and b/blog/src/assets/media/building-an-ai-office-floor/note-2.png differ
diff --git a/blog/src/assets/media/building-reliable-ai-agents/note-1.png b/blog/src/assets/media/building-reliable-ai-agents/note-1.png
new file mode 100644
index 00000000..5bd94ce8
Binary files /dev/null and b/blog/src/assets/media/building-reliable-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/building-reliable-ai-agents/note-2.png b/blog/src/assets/media/building-reliable-ai-agents/note-2.png
new file mode 100644
index 00000000..16f618ac
Binary files /dev/null and b/blog/src/assets/media/building-reliable-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/can-claude-code-agents-talk-to-each-other/note-1.png b/blog/src/assets/media/can-claude-code-agents-talk-to-each-other/note-1.png
new file mode 100644
index 00000000..9082074b
Binary files /dev/null and b/blog/src/assets/media/can-claude-code-agents-talk-to-each-other/note-1.png differ
diff --git a/blog/src/assets/media/can-claude-code-agents-talk-to-each-other/note-2.png b/blog/src/assets/media/can-claude-code-agents-talk-to-each-other/note-2.png
new file mode 100644
index 00000000..48a04c23
Binary files /dev/null and b/blog/src/assets/media/can-claude-code-agents-talk-to-each-other/note-2.png differ
diff --git a/blog/src/assets/media/claude-code-automation-while-you-sleep/note-1.png b/blog/src/assets/media/claude-code-automation-while-you-sleep/note-1.png
new file mode 100644
index 00000000..062f5895
Binary files /dev/null and b/blog/src/assets/media/claude-code-automation-while-you-sleep/note-1.png differ
diff --git a/blog/src/assets/media/claude-code-automation-while-you-sleep/note-2.png b/blog/src/assets/media/claude-code-automation-while-you-sleep/note-2.png
new file mode 100644
index 00000000..8633ad2b
Binary files /dev/null and b/blog/src/assets/media/claude-code-automation-while-you-sleep/note-2.png differ
diff --git a/blog/src/assets/media/claude-code-git-worktrees-vs-hive/note-1.png b/blog/src/assets/media/claude-code-git-worktrees-vs-hive/note-1.png
new file mode 100644
index 00000000..c4764b99
Binary files /dev/null and b/blog/src/assets/media/claude-code-git-worktrees-vs-hive/note-1.png differ
diff --git a/blog/src/assets/media/claude-code-git-worktrees-vs-hive/note-2.png b/blog/src/assets/media/claude-code-git-worktrees-vs-hive/note-2.png
new file mode 100644
index 00000000..a0a83f3a
Binary files /dev/null and b/blog/src/assets/media/claude-code-git-worktrees-vs-hive/note-2.png differ
diff --git a/blog/src/assets/media/claude-code-hooks-explained/note-1.png b/blog/src/assets/media/claude-code-hooks-explained/note-1.png
new file mode 100644
index 00000000..8eee8d4b
Binary files /dev/null and b/blog/src/assets/media/claude-code-hooks-explained/note-1.png differ
diff --git a/blog/src/assets/media/claude-code-hooks-explained/note-2.png b/blog/src/assets/media/claude-code-hooks-explained/note-2.png
new file mode 100644
index 00000000..aec462f0
Binary files /dev/null and b/blog/src/assets/media/claude-code-hooks-explained/note-2.png differ
diff --git a/blog/src/assets/media/claude-code-multi-agent-setup-tutorial/note-1.png b/blog/src/assets/media/claude-code-multi-agent-setup-tutorial/note-1.png
new file mode 100644
index 00000000..bc13df48
Binary files /dev/null and b/blog/src/assets/media/claude-code-multi-agent-setup-tutorial/note-1.png differ
diff --git a/blog/src/assets/media/claude-code-multi-agent-setup-tutorial/note-2.png b/blog/src/assets/media/claude-code-multi-agent-setup-tutorial/note-2.png
new file mode 100644
index 00000000..f0ad2980
Binary files /dev/null and b/blog/src/assets/media/claude-code-multi-agent-setup-tutorial/note-2.png differ
diff --git a/blog/src/assets/media/claude-code-orchestration-guide/note-1.png b/blog/src/assets/media/claude-code-orchestration-guide/note-1.png
new file mode 100644
index 00000000..37a55826
Binary files /dev/null and b/blog/src/assets/media/claude-code-orchestration-guide/note-1.png differ
diff --git a/blog/src/assets/media/claude-code-orchestration-guide/note-2.png b/blog/src/assets/media/claude-code-orchestration-guide/note-2.png
new file mode 100644
index 00000000..e1dd5332
Binary files /dev/null and b/blog/src/assets/media/claude-code-orchestration-guide/note-2.png differ
diff --git a/blog/src/assets/media/claude-code-orchestration-tools-compared/note-1.png b/blog/src/assets/media/claude-code-orchestration-tools-compared/note-1.png
new file mode 100644
index 00000000..554bf3b9
Binary files /dev/null and b/blog/src/assets/media/claude-code-orchestration-tools-compared/note-1.png differ
diff --git a/blog/src/assets/media/claude-code-orchestration-tools-compared/note-2.png b/blog/src/assets/media/claude-code-orchestration-tools-compared/note-2.png
new file mode 100644
index 00000000..53b64897
Binary files /dev/null and b/blog/src/assets/media/claude-code-orchestration-tools-compared/note-2.png differ
diff --git a/blog/src/assets/media/claude-code-subagents-vs-multi-agent-harness/note-1.png b/blog/src/assets/media/claude-code-subagents-vs-multi-agent-harness/note-1.png
new file mode 100644
index 00000000..9d56a5a9
Binary files /dev/null and b/blog/src/assets/media/claude-code-subagents-vs-multi-agent-harness/note-1.png differ
diff --git a/blog/src/assets/media/claude-code-subagents-vs-multi-agent-harness/note-2.png b/blog/src/assets/media/claude-code-subagents-vs-multi-agent-harness/note-2.png
new file mode 100644
index 00000000..87c062a6
Binary files /dev/null and b/blog/src/assets/media/claude-code-subagents-vs-multi-agent-harness/note-2.png differ
diff --git a/blog/src/assets/media/claude-squad-alternative/note-1.png b/blog/src/assets/media/claude-squad-alternative/note-1.png
new file mode 100644
index 00000000..64c7bb30
Binary files /dev/null and b/blog/src/assets/media/claude-squad-alternative/note-1.png differ
diff --git a/blog/src/assets/media/claude-squad-alternative/note-2.png b/blog/src/assets/media/claude-squad-alternative/note-2.png
new file mode 100644
index 00000000..46025211
Binary files /dev/null and b/blog/src/assets/media/claude-squad-alternative/note-2.png differ
diff --git a/blog/src/assets/media/claude-squad-vs-munder-difflin/note-1.png b/blog/src/assets/media/claude-squad-vs-munder-difflin/note-1.png
new file mode 100644
index 00000000..5f7c322a
Binary files /dev/null and b/blog/src/assets/media/claude-squad-vs-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/claude-squad-vs-munder-difflin/note-2.png b/blog/src/assets/media/claude-squad-vs-munder-difflin/note-2.png
new file mode 100644
index 00000000..817ac478
Binary files /dev/null and b/blog/src/assets/media/claude-squad-vs-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/cline-vs-munder-difflin/note-1.png b/blog/src/assets/media/cline-vs-munder-difflin/note-1.png
new file mode 100644
index 00000000..2f6b4403
Binary files /dev/null and b/blog/src/assets/media/cline-vs-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/cline-vs-munder-difflin/note-2.png b/blog/src/assets/media/cline-vs-munder-difflin/note-2.png
new file mode 100644
index 00000000..faf1300c
Binary files /dev/null and b/blog/src/assets/media/cline-vs-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/command-center-guide/note-1.png b/blog/src/assets/media/command-center-guide/note-1.png
new file mode 100644
index 00000000..45c20adf
Binary files /dev/null and b/blog/src/assets/media/command-center-guide/note-1.png differ
diff --git a/blog/src/assets/media/command-center-guide/note-2.png b/blog/src/assets/media/command-center-guide/note-2.png
new file mode 100644
index 00000000..7262351a
Binary files /dev/null and b/blog/src/assets/media/command-center-guide/note-2.png differ
diff --git a/blog/src/assets/media/compressing-agent-memory/note-1.png b/blog/src/assets/media/compressing-agent-memory/note-1.png
new file mode 100644
index 00000000..317a7161
Binary files /dev/null and b/blog/src/assets/media/compressing-agent-memory/note-1.png differ
diff --git a/blog/src/assets/media/compressing-agent-memory/note-2.png b/blog/src/assets/media/compressing-agent-memory/note-2.png
new file mode 100644
index 00000000..561f01f8
Binary files /dev/null and b/blog/src/assets/media/compressing-agent-memory/note-2.png differ
diff --git a/blog/src/assets/media/conductor-claude-code-alternative/note-1.png b/blog/src/assets/media/conductor-claude-code-alternative/note-1.png
new file mode 100644
index 00000000..2b5650ef
Binary files /dev/null and b/blog/src/assets/media/conductor-claude-code-alternative/note-1.png differ
diff --git a/blog/src/assets/media/conductor-claude-code-alternative/note-2.png b/blog/src/assets/media/conductor-claude-code-alternative/note-2.png
new file mode 100644
index 00000000..9d7ef0b3
Binary files /dev/null and b/blog/src/assets/media/conductor-claude-code-alternative/note-2.png differ
diff --git a/blog/src/assets/media/context-engineering-for-ai-agents/note-1.png b/blog/src/assets/media/context-engineering-for-ai-agents/note-1.png
new file mode 100644
index 00000000..db033df5
Binary files /dev/null and b/blog/src/assets/media/context-engineering-for-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/context-engineering-for-ai-agents/note-2.png b/blog/src/assets/media/context-engineering-for-ai-agents/note-2.png
new file mode 100644
index 00000000..8848bad4
Binary files /dev/null and b/blog/src/assets/media/context-engineering-for-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/coordinating-ai-coding-agents/note-1.png b/blog/src/assets/media/coordinating-ai-coding-agents/note-1.png
new file mode 100644
index 00000000..0eba121d
Binary files /dev/null and b/blog/src/assets/media/coordinating-ai-coding-agents/note-1.png differ
diff --git a/blog/src/assets/media/coordinating-ai-coding-agents/note-2.png b/blog/src/assets/media/coordinating-ai-coding-agents/note-2.png
new file mode 100644
index 00000000..44daa838
Binary files /dev/null and b/blog/src/assets/media/coordinating-ai-coding-agents/note-2.png differ
diff --git a/blog/src/assets/media/crewai-autogen-vs-a-local-agent-harness/note-1.png b/blog/src/assets/media/crewai-autogen-vs-a-local-agent-harness/note-1.png
new file mode 100644
index 00000000..2c2130e4
Binary files /dev/null and b/blog/src/assets/media/crewai-autogen-vs-a-local-agent-harness/note-1.png differ
diff --git a/blog/src/assets/media/crewai-autogen-vs-a-local-agent-harness/note-2.png b/blog/src/assets/media/crewai-autogen-vs-a-local-agent-harness/note-2.png
new file mode 100644
index 00000000..ef4ce841
Binary files /dev/null and b/blog/src/assets/media/crewai-autogen-vs-a-local-agent-harness/note-2.png differ
diff --git a/blog/src/assets/media/crystal-claude-code-alternative/note-1.png b/blog/src/assets/media/crystal-claude-code-alternative/note-1.png
new file mode 100644
index 00000000..bc4e4c9f
Binary files /dev/null and b/blog/src/assets/media/crystal-claude-code-alternative/note-1.png differ
diff --git a/blog/src/assets/media/crystal-claude-code-alternative/note-2.png b/blog/src/assets/media/crystal-claude-code-alternative/note-2.png
new file mode 100644
index 00000000..70a47f77
Binary files /dev/null and b/blog/src/assets/media/crystal-claude-code-alternative/note-2.png differ
diff --git a/blog/src/assets/media/debugging-multi-agent-systems/note-1.png b/blog/src/assets/media/debugging-multi-agent-systems/note-1.png
new file mode 100644
index 00000000..54d7bf43
Binary files /dev/null and b/blog/src/assets/media/debugging-multi-agent-systems/note-1.png differ
diff --git a/blog/src/assets/media/debugging-multi-agent-systems/note-2.png b/blog/src/assets/media/debugging-multi-agent-systems/note-2.png
new file mode 100644
index 00000000..4b7f4747
Binary files /dev/null and b/blog/src/assets/media/debugging-multi-agent-systems/note-2.png differ
diff --git a/blog/src/assets/media/deploy-a-blog-writer-agent/note-1.png b/blog/src/assets/media/deploy-a-blog-writer-agent/note-1.png
new file mode 100644
index 00000000..d7faecc4
Binary files /dev/null and b/blog/src/assets/media/deploy-a-blog-writer-agent/note-1.png differ
diff --git a/blog/src/assets/media/deploy-a-blog-writer-agent/note-2.png b/blog/src/assets/media/deploy-a-blog-writer-agent/note-2.png
new file mode 100644
index 00000000..f3f4c1e7
Binary files /dev/null and b/blog/src/assets/media/deploy-a-blog-writer-agent/note-2.png differ
diff --git a/blog/src/assets/media/deploy-automated-pr-reviewer-agent/note-1.png b/blog/src/assets/media/deploy-automated-pr-reviewer-agent/note-1.png
new file mode 100644
index 00000000..738806fc
Binary files /dev/null and b/blog/src/assets/media/deploy-automated-pr-reviewer-agent/note-1.png differ
diff --git a/blog/src/assets/media/deploy-automated-pr-reviewer-agent/note-2.png b/blog/src/assets/media/deploy-automated-pr-reviewer-agent/note-2.png
new file mode 100644
index 00000000..6dafa86e
Binary files /dev/null and b/blog/src/assets/media/deploy-automated-pr-reviewer-agent/note-2.png differ
diff --git a/blog/src/assets/media/do-more-with-less-model-routing/note-1.png b/blog/src/assets/media/do-more-with-less-model-routing/note-1.png
new file mode 100644
index 00000000..25c04638
Binary files /dev/null and b/blog/src/assets/media/do-more-with-less-model-routing/note-1.png differ
diff --git a/blog/src/assets/media/do-more-with-less-model-routing/note-2.png b/blog/src/assets/media/do-more-with-less-model-routing/note-2.png
new file mode 100644
index 00000000..2bd3e113
Binary files /dev/null and b/blog/src/assets/media/do-more-with-less-model-routing/note-2.png differ
diff --git a/blog/src/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-1.png b/blog/src/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-1.png
new file mode 100644
index 00000000..4d87ccae
Binary files /dev/null and b/blog/src/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-2.png b/blog/src/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-2.png
new file mode 100644
index 00000000..152ddc8c
Binary files /dev/null and b/blog/src/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/evaluating-ai-agent-reliability/note-1.png b/blog/src/assets/media/evaluating-ai-agent-reliability/note-1.png
new file mode 100644
index 00000000..ff888d5d
Binary files /dev/null and b/blog/src/assets/media/evaluating-ai-agent-reliability/note-1.png differ
diff --git a/blog/src/assets/media/evaluating-ai-agent-reliability/note-2.png b/blog/src/assets/media/evaluating-ai-agent-reliability/note-2.png
new file mode 100644
index 00000000..aa9fe574
Binary files /dev/null and b/blog/src/assets/media/evaluating-ai-agent-reliability/note-2.png differ
diff --git a/blog/src/assets/media/file-based-coordination-vs-message-queues/note-1.png b/blog/src/assets/media/file-based-coordination-vs-message-queues/note-1.png
new file mode 100644
index 00000000..edff9817
Binary files /dev/null and b/blog/src/assets/media/file-based-coordination-vs-message-queues/note-1.png differ
diff --git a/blog/src/assets/media/file-based-coordination-vs-message-queues/note-2.png b/blog/src/assets/media/file-based-coordination-vs-message-queues/note-2.png
new file mode 100644
index 00000000..2d016f2e
Binary files /dev/null and b/blog/src/assets/media/file-based-coordination-vs-message-queues/note-2.png differ
diff --git a/blog/src/assets/media/from-one-terminal-to-a-team/note-1.png b/blog/src/assets/media/from-one-terminal-to-a-team/note-1.png
new file mode 100644
index 00000000..10c5cf99
Binary files /dev/null and b/blog/src/assets/media/from-one-terminal-to-a-team/note-1.png differ
diff --git a/blog/src/assets/media/from-one-terminal-to-a-team/note-2.png b/blog/src/assets/media/from-one-terminal-to-a-team/note-2.png
new file mode 100644
index 00000000..2fece6fc
Binary files /dev/null and b/blog/src/assets/media/from-one-terminal-to-a-team/note-2.png differ
diff --git a/blog/src/assets/media/generative-engine-optimization-techniques/note-1.png b/blog/src/assets/media/generative-engine-optimization-techniques/note-1.png
new file mode 100644
index 00000000..67073a07
Binary files /dev/null and b/blog/src/assets/media/generative-engine-optimization-techniques/note-1.png differ
diff --git a/blog/src/assets/media/generative-engine-optimization-techniques/note-2.png b/blog/src/assets/media/generative-engine-optimization-techniques/note-2.png
new file mode 100644
index 00000000..6f5888dc
Binary files /dev/null and b/blog/src/assets/media/generative-engine-optimization-techniques/note-2.png differ
diff --git a/blog/src/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-1.png b/blog/src/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-1.png
new file mode 100644
index 00000000..c2e94da5
Binary files /dev/null and b/blog/src/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-1.png differ
diff --git a/blog/src/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-2.png b/blog/src/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-2.png
new file mode 100644
index 00000000..0256cf19
Binary files /dev/null and b/blog/src/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-2.png differ
diff --git a/blog/src/assets/media/give-claude-code-long-term-memory/note-1.png b/blog/src/assets/media/give-claude-code-long-term-memory/note-1.png
new file mode 100644
index 00000000..da291474
Binary files /dev/null and b/blog/src/assets/media/give-claude-code-long-term-memory/note-1.png differ
diff --git a/blog/src/assets/media/give-claude-code-long-term-memory/note-2.png b/blog/src/assets/media/give-claude-code-long-term-memory/note-2.png
new file mode 100644
index 00000000..e11a0d28
Binary files /dev/null and b/blog/src/assets/media/give-claude-code-long-term-memory/note-2.png differ
diff --git a/blog/src/assets/media/hire-manifest-untrusted-input/note-1.png b/blog/src/assets/media/hire-manifest-untrusted-input/note-1.png
new file mode 100644
index 00000000..22309b54
Binary files /dev/null and b/blog/src/assets/media/hire-manifest-untrusted-input/note-1.png differ
diff --git a/blog/src/assets/media/hire-manifest-untrusted-input/note-2.png b/blog/src/assets/media/hire-manifest-untrusted-input/note-2.png
new file mode 100644
index 00000000..dbea7f7e
Binary files /dev/null and b/blog/src/assets/media/hire-manifest-untrusted-input/note-2.png differ
diff --git a/blog/src/assets/media/how-agents-remember-semantic-memory/note-1.png b/blog/src/assets/media/how-agents-remember-semantic-memory/note-1.png
new file mode 100644
index 00000000..d1e0c619
Binary files /dev/null and b/blog/src/assets/media/how-agents-remember-semantic-memory/note-1.png differ
diff --git a/blog/src/assets/media/how-agents-remember-semantic-memory/note-2.png b/blog/src/assets/media/how-agents-remember-semantic-memory/note-2.png
new file mode 100644
index 00000000..92282a81
Binary files /dev/null and b/blog/src/assets/media/how-agents-remember-semantic-memory/note-2.png differ
diff --git a/blog/src/assets/media/how-ai-agents-verify-their-own-work/note-1.png b/blog/src/assets/media/how-ai-agents-verify-their-own-work/note-1.png
new file mode 100644
index 00000000..d50b3362
Binary files /dev/null and b/blog/src/assets/media/how-ai-agents-verify-their-own-work/note-1.png differ
diff --git a/blog/src/assets/media/how-ai-agents-verify-their-own-work/note-2.png b/blog/src/assets/media/how-ai-agents-verify-their-own-work/note-2.png
new file mode 100644
index 00000000..03965ca0
Binary files /dev/null and b/blog/src/assets/media/how-ai-agents-verify-their-own-work/note-2.png differ
diff --git a/blog/src/assets/media/how-ai-answer-engines-choose-sources/note-1.png b/blog/src/assets/media/how-ai-answer-engines-choose-sources/note-1.png
new file mode 100644
index 00000000..6a67fc79
Binary files /dev/null and b/blog/src/assets/media/how-ai-answer-engines-choose-sources/note-1.png differ
diff --git a/blog/src/assets/media/how-ai-answer-engines-choose-sources/note-2.png b/blog/src/assets/media/how-ai-answer-engines-choose-sources/note-2.png
new file mode 100644
index 00000000..30ba4898
Binary files /dev/null and b/blog/src/assets/media/how-ai-answer-engines-choose-sources/note-2.png differ
diff --git a/blog/src/assets/media/how-the-god-orchestrator-works/note-1.png b/blog/src/assets/media/how-the-god-orchestrator-works/note-1.png
new file mode 100644
index 00000000..a3295b30
Binary files /dev/null and b/blog/src/assets/media/how-the-god-orchestrator-works/note-1.png differ
diff --git a/blog/src/assets/media/how-the-god-orchestrator-works/note-2.png b/blog/src/assets/media/how-the-god-orchestrator-works/note-2.png
new file mode 100644
index 00000000..d0e28303
Binary files /dev/null and b/blog/src/assets/media/how-the-god-orchestrator-works/note-2.png differ
diff --git a/blog/src/assets/media/how-to-add-a-github-copilot-cli-agent/note-1.png b/blog/src/assets/media/how-to-add-a-github-copilot-cli-agent/note-1.png
new file mode 100644
index 00000000..eb8fd28b
Binary files /dev/null and b/blog/src/assets/media/how-to-add-a-github-copilot-cli-agent/note-1.png differ
diff --git a/blog/src/assets/media/how-to-add-a-github-copilot-cli-agent/note-2.png b/blog/src/assets/media/how-to-add-a-github-copilot-cli-agent/note-2.png
new file mode 100644
index 00000000..725bd5d8
Binary files /dev/null and b/blog/src/assets/media/how-to-add-a-github-copilot-cli-agent/note-2.png differ
diff --git a/blog/src/assets/media/how-to-choose-a-multi-agent-tool/note-1.png b/blog/src/assets/media/how-to-choose-a-multi-agent-tool/note-1.png
new file mode 100644
index 00000000..67b1f86b
Binary files /dev/null and b/blog/src/assets/media/how-to-choose-a-multi-agent-tool/note-1.png differ
diff --git a/blog/src/assets/media/how-to-choose-a-multi-agent-tool/note-2.png b/blog/src/assets/media/how-to-choose-a-multi-agent-tool/note-2.png
new file mode 100644
index 00000000..6c1f1923
Binary files /dev/null and b/blog/src/assets/media/how-to-choose-a-multi-agent-tool/note-2.png differ
diff --git a/blog/src/assets/media/how-to-hire-from-the-agent-gallery/note-1.png b/blog/src/assets/media/how-to-hire-from-the-agent-gallery/note-1.png
new file mode 100644
index 00000000..601446e6
Binary files /dev/null and b/blog/src/assets/media/how-to-hire-from-the-agent-gallery/note-1.png differ
diff --git a/blog/src/assets/media/how-to-hire-from-the-agent-gallery/note-2.png b/blog/src/assets/media/how-to-hire-from-the-agent-gallery/note-2.png
new file mode 100644
index 00000000..b04d572f
Binary files /dev/null and b/blog/src/assets/media/how-to-hire-from-the-agent-gallery/note-2.png differ
diff --git a/blog/src/assets/media/how-to-install-and-use-munder-difflin/note-1.png b/blog/src/assets/media/how-to-install-and-use-munder-difflin/note-1.png
new file mode 100644
index 00000000..81d7bfb7
Binary files /dev/null and b/blog/src/assets/media/how-to-install-and-use-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/how-to-install-and-use-munder-difflin/note-2.png b/blog/src/assets/media/how-to-install-and-use-munder-difflin/note-2.png
new file mode 100644
index 00000000..758755e2
Binary files /dev/null and b/blog/src/assets/media/how-to-install-and-use-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/how-to-run-multiple-claude-code-agents/note-1.png b/blog/src/assets/media/how-to-run-multiple-claude-code-agents/note-1.png
new file mode 100644
index 00000000..f3e4e360
Binary files /dev/null and b/blog/src/assets/media/how-to-run-multiple-claude-code-agents/note-1.png differ
diff --git a/blog/src/assets/media/how-to-run-multiple-claude-code-agents/note-2.png b/blog/src/assets/media/how-to-run-multiple-claude-code-agents/note-2.png
new file mode 100644
index 00000000..9f0f0396
Binary files /dev/null and b/blog/src/assets/media/how-to-run-multiple-claude-code-agents/note-2.png differ
diff --git a/blog/src/assets/media/how-to-talk-to-your-orchestrator/note-1.png b/blog/src/assets/media/how-to-talk-to-your-orchestrator/note-1.png
new file mode 100644
index 00000000..eeb39ecb
Binary files /dev/null and b/blog/src/assets/media/how-to-talk-to-your-orchestrator/note-1.png differ
diff --git a/blog/src/assets/media/how-to-talk-to-your-orchestrator/note-2.png b/blog/src/assets/media/how-to-talk-to-your-orchestrator/note-2.png
new file mode 100644
index 00000000..41f90b1f
Binary files /dev/null and b/blog/src/assets/media/how-to-talk-to-your-orchestrator/note-2.png differ
diff --git a/blog/src/assets/media/how-to-use-the-built-in-monaco-ide/note-1.png b/blog/src/assets/media/how-to-use-the-built-in-monaco-ide/note-1.png
new file mode 100644
index 00000000..cc12e699
Binary files /dev/null and b/blog/src/assets/media/how-to-use-the-built-in-monaco-ide/note-1.png differ
diff --git a/blog/src/assets/media/how-to-use-the-built-in-monaco-ide/note-2.png b/blog/src/assets/media/how-to-use-the-built-in-monaco-ide/note-2.png
new file mode 100644
index 00000000..98b19878
Binary files /dev/null and b/blog/src/assets/media/how-to-use-the-built-in-monaco-ide/note-2.png differ
diff --git a/blog/src/assets/media/human-in-the-loop-ai-agents/note-1.png b/blog/src/assets/media/human-in-the-loop-ai-agents/note-1.png
new file mode 100644
index 00000000..1db28186
Binary files /dev/null and b/blog/src/assets/media/human-in-the-loop-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/human-in-the-loop-ai-agents/note-2.png b/blog/src/assets/media/human-in-the-loop-ai-agents/note-2.png
new file mode 100644
index 00000000..d02e3bb6
Binary files /dev/null and b/blog/src/assets/media/human-in-the-loop-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/human-in-the-loop-approving-ai-agents/note-1.png b/blog/src/assets/media/human-in-the-loop-approving-ai-agents/note-1.png
new file mode 100644
index 00000000..cff78e5e
Binary files /dev/null and b/blog/src/assets/media/human-in-the-loop-approving-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/human-in-the-loop-approving-ai-agents/note-2.png b/blog/src/assets/media/human-in-the-loop-approving-ai-agents/note-2.png
new file mode 100644
index 00000000..ad521fa1
Binary files /dev/null and b/blog/src/assets/media/human-in-the-loop-approving-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/keep-agent-semantic-memory-clean/note-1.png b/blog/src/assets/media/keep-agent-semantic-memory-clean/note-1.png
new file mode 100644
index 00000000..ac496b7a
Binary files /dev/null and b/blog/src/assets/media/keep-agent-semantic-memory-clean/note-1.png differ
diff --git a/blog/src/assets/media/keep-agent-semantic-memory-clean/note-2.png b/blog/src/assets/media/keep-agent-semantic-memory-clean/note-2.png
new file mode 100644
index 00000000..6279a843
Binary files /dev/null and b/blog/src/assets/media/keep-agent-semantic-memory-clean/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-2-0/note-1.png b/blog/src/assets/media/launching-munder-difflin-v0-2-0/note-1.png
new file mode 100644
index 00000000..28558a1c
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-2-0/note-1.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-2-0/note-2.png b/blog/src/assets/media/launching-munder-difflin-v0-2-0/note-2.png
new file mode 100644
index 00000000..70b39933
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-2-0/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-2-4/note-1.png b/blog/src/assets/media/launching-munder-difflin-v0-2-4/note-1.png
new file mode 100644
index 00000000..ed0f8dd1
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-2-4/note-1.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-2-4/note-2.png b/blog/src/assets/media/launching-munder-difflin-v0-2-4/note-2.png
new file mode 100644
index 00000000..78f7ca23
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-2-4/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-2-8/note-1.png b/blog/src/assets/media/launching-munder-difflin-v0-2-8/note-1.png
new file mode 100644
index 00000000..b2984c64
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-2-8/note-1.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-2-8/note-2.png b/blog/src/assets/media/launching-munder-difflin-v0-2-8/note-2.png
new file mode 100644
index 00000000..8b55b423
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-2-8/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-3-0/note-1.png b/blog/src/assets/media/launching-munder-difflin-v0-3-0/note-1.png
new file mode 100644
index 00000000..15345b74
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-3-0/note-1.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-3-0/note-2.png b/blog/src/assets/media/launching-munder-difflin-v0-3-0/note-2.png
new file mode 100644
index 00000000..7bae6983
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-3-0/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-3-2/note-1.png b/blog/src/assets/media/launching-munder-difflin-v0-3-2/note-1.png
new file mode 100644
index 00000000..cc4b2944
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-3-2/note-1.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-3-2/note-2.png b/blog/src/assets/media/launching-munder-difflin-v0-3-2/note-2.png
new file mode 100644
index 00000000..0c72f561
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-3-2/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-3-3/note-1.png b/blog/src/assets/media/launching-munder-difflin-v0-3-3/note-1.png
new file mode 100644
index 00000000..6fe67f5c
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-3-3/note-1.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-3-3/note-2.png b/blog/src/assets/media/launching-munder-difflin-v0-3-3/note-2.png
new file mode 100644
index 00000000..faced389
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-3-3/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-3-5/note-1.png b/blog/src/assets/media/launching-munder-difflin-v0-3-5/note-1.png
new file mode 100644
index 00000000..cec4fc39
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-3-5/note-1.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-3-5/note-2.png b/blog/src/assets/media/launching-munder-difflin-v0-3-5/note-2.png
new file mode 100644
index 00000000..e21408b3
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-3-5/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-4-4/hero.png b/blog/src/assets/media/launching-munder-difflin-v0-4-4/hero.png
new file mode 100644
index 00000000..90bf6507
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-4-4/hero.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-1.png b/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-1.png
new file mode 100644
index 00000000..dd54baa0
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-1.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-2.png b/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-2.png
new file mode 100644
index 00000000..e20d3db8
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-2.png differ
diff --git a/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-3.png b/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-3.png
new file mode 100644
index 00000000..4da97143
Binary files /dev/null and b/blog/src/assets/media/launching-munder-difflin-v0-4-4/note-3.png differ
diff --git a/blog/src/assets/media/local-first-ai-agent-orchestration/note-1.png b/blog/src/assets/media/local-first-ai-agent-orchestration/note-1.png
new file mode 100644
index 00000000..4befc9eb
Binary files /dev/null and b/blog/src/assets/media/local-first-ai-agent-orchestration/note-1.png differ
diff --git a/blog/src/assets/media/local-first-ai-agent-orchestration/note-2.png b/blog/src/assets/media/local-first-ai-agent-orchestration/note-2.png
new file mode 100644
index 00000000..1c4d7696
Binary files /dev/null and b/blog/src/assets/media/local-first-ai-agent-orchestration/note-2.png differ
diff --git a/blog/src/assets/media/local-first-vs-cloud-agent-sdks/note-1.png b/blog/src/assets/media/local-first-vs-cloud-agent-sdks/note-1.png
new file mode 100644
index 00000000..e50056d3
Binary files /dev/null and b/blog/src/assets/media/local-first-vs-cloud-agent-sdks/note-1.png differ
diff --git a/blog/src/assets/media/local-first-vs-cloud-agent-sdks/note-2.png b/blog/src/assets/media/local-first-vs-cloud-agent-sdks/note-2.png
new file mode 100644
index 00000000..6b0928cf
Binary files /dev/null and b/blog/src/assets/media/local-first-vs-cloud-agent-sdks/note-2.png differ
diff --git a/blog/src/assets/media/long-running-agents-the-2026-shift/note-1.png b/blog/src/assets/media/long-running-agents-the-2026-shift/note-1.png
new file mode 100644
index 00000000..b4ac9164
Binary files /dev/null and b/blog/src/assets/media/long-running-agents-the-2026-shift/note-1.png differ
diff --git a/blog/src/assets/media/long-running-agents-the-2026-shift/note-2.png b/blog/src/assets/media/long-running-agents-the-2026-shift/note-2.png
new file mode 100644
index 00000000..875cb4d5
Binary files /dev/null and b/blog/src/assets/media/long-running-agents-the-2026-shift/note-2.png differ
diff --git a/blog/src/assets/media/loop-engineering-for-ai-agents/note-1.png b/blog/src/assets/media/loop-engineering-for-ai-agents/note-1.png
new file mode 100644
index 00000000..89c0e187
Binary files /dev/null and b/blog/src/assets/media/loop-engineering-for-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/loop-engineering-for-ai-agents/note-2.png b/blog/src/assets/media/loop-engineering-for-ai-agents/note-2.png
new file mode 100644
index 00000000..e34f4caa
Binary files /dev/null and b/blog/src/assets/media/loop-engineering-for-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/manage-multiple-claude-code-sessions/note-1.png b/blog/src/assets/media/manage-multiple-claude-code-sessions/note-1.png
new file mode 100644
index 00000000..8f055b85
Binary files /dev/null and b/blog/src/assets/media/manage-multiple-claude-code-sessions/note-1.png differ
diff --git a/blog/src/assets/media/manage-multiple-claude-code-sessions/note-2.png b/blog/src/assets/media/manage-multiple-claude-code-sessions/note-2.png
new file mode 100644
index 00000000..2251d235
Binary files /dev/null and b/blog/src/assets/media/manage-multiple-claude-code-sessions/note-2.png differ
diff --git a/blog/src/assets/media/markdown-first-agent-memory/note-1.png b/blog/src/assets/media/markdown-first-agent-memory/note-1.png
new file mode 100644
index 00000000..6651136d
Binary files /dev/null and b/blog/src/assets/media/markdown-first-agent-memory/note-1.png differ
diff --git a/blog/src/assets/media/markdown-first-agent-memory/note-2.png b/blog/src/assets/media/markdown-first-agent-memory/note-2.png
new file mode 100644
index 00000000..9020ba66
Binary files /dev/null and b/blog/src/assets/media/markdown-first-agent-memory/note-2.png differ
diff --git a/blog/src/assets/media/mcp-and-skills-in-a-hive/note-1.png b/blog/src/assets/media/mcp-and-skills-in-a-hive/note-1.png
new file mode 100644
index 00000000..4ff5db92
Binary files /dev/null and b/blog/src/assets/media/mcp-and-skills-in-a-hive/note-1.png differ
diff --git a/blog/src/assets/media/mcp-and-skills-in-a-hive/note-2.png b/blog/src/assets/media/mcp-and-skills-in-a-hive/note-2.png
new file mode 100644
index 00000000..08633f63
Binary files /dev/null and b/blog/src/assets/media/mcp-and-skills-in-a-hive/note-2.png differ
diff --git a/blog/src/assets/media/mcp-security-tool-poisoning/note-1.png b/blog/src/assets/media/mcp-security-tool-poisoning/note-1.png
new file mode 100644
index 00000000..d09e8303
Binary files /dev/null and b/blog/src/assets/media/mcp-security-tool-poisoning/note-1.png differ
diff --git a/blog/src/assets/media/mcp-security-tool-poisoning/note-2.png b/blog/src/assets/media/mcp-security-tool-poisoning/note-2.png
new file mode 100644
index 00000000..43d8a9f3
Binary files /dev/null and b/blog/src/assets/media/mcp-security-tool-poisoning/note-2.png differ
diff --git a/blog/src/assets/media/multi-agent-orchestration-patterns/note-1.png b/blog/src/assets/media/multi-agent-orchestration-patterns/note-1.png
new file mode 100644
index 00000000..c95bd7e3
Binary files /dev/null and b/blog/src/assets/media/multi-agent-orchestration-patterns/note-1.png differ
diff --git a/blog/src/assets/media/multi-agent-orchestration-patterns/note-2.png b/blog/src/assets/media/multi-agent-orchestration-patterns/note-2.png
new file mode 100644
index 00000000..ca18f41a
Binary files /dev/null and b/blog/src/assets/media/multi-agent-orchestration-patterns/note-2.png differ
diff --git a/blog/src/assets/media/munder-difflin-faq/note-1.png b/blog/src/assets/media/munder-difflin-faq/note-1.png
new file mode 100644
index 00000000..adcbea65
Binary files /dev/null and b/blog/src/assets/media/munder-difflin-faq/note-1.png differ
diff --git a/blog/src/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-1.png b/blog/src/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-1.png
new file mode 100644
index 00000000..601446e6
Binary files /dev/null and b/blog/src/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-1.png differ
diff --git a/blog/src/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-2.png b/blog/src/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-2.png
new file mode 100644
index 00000000..2f4c9f42
Binary files /dev/null and b/blog/src/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-2.png differ
diff --git a/blog/src/assets/media/node-pty-electron-real-terminals/note-1.png b/blog/src/assets/media/node-pty-electron-real-terminals/note-1.png
new file mode 100644
index 00000000..047b6bfe
Binary files /dev/null and b/blog/src/assets/media/node-pty-electron-real-terminals/note-1.png differ
diff --git a/blog/src/assets/media/node-pty-electron-real-terminals/note-2.png b/blog/src/assets/media/node-pty-electron-real-terminals/note-2.png
new file mode 100644
index 00000000..9f00b037
Binary files /dev/null and b/blog/src/assets/media/node-pty-electron-real-terminals/note-2.png differ
diff --git a/blog/src/assets/media/number-five-on-product-hunt/hero.png b/blog/src/assets/media/number-five-on-product-hunt/hero.png
new file mode 100644
index 00000000..be23a966
Binary files /dev/null and b/blog/src/assets/media/number-five-on-product-hunt/hero.png differ
diff --git a/blog/src/assets/media/number-five-on-product-hunt/note-1.png b/blog/src/assets/media/number-five-on-product-hunt/note-1.png
new file mode 100644
index 00000000..3c184ac0
Binary files /dev/null and b/blog/src/assets/media/number-five-on-product-hunt/note-1.png differ
diff --git a/blog/src/assets/media/number-five-on-product-hunt/note-2.png b/blog/src/assets/media/number-five-on-product-hunt/note-2.png
new file mode 100644
index 00000000..b6d0e6c1
Binary files /dev/null and b/blog/src/assets/media/number-five-on-product-hunt/note-2.png differ
diff --git a/blog/src/assets/media/observability-for-agent-fleets/note-1.png b/blog/src/assets/media/observability-for-agent-fleets/note-1.png
new file mode 100644
index 00000000..09e8f326
Binary files /dev/null and b/blog/src/assets/media/observability-for-agent-fleets/note-1.png differ
diff --git a/blog/src/assets/media/observability-for-agent-fleets/note-2.png b/blog/src/assets/media/observability-for-agent-fleets/note-2.png
new file mode 100644
index 00000000..8367a2a4
Binary files /dev/null and b/blog/src/assets/media/observability-for-agent-fleets/note-2.png differ
diff --git a/blog/src/assets/media/one-prompt-automated-pr-review/note-1.png b/blog/src/assets/media/one-prompt-automated-pr-review/note-1.png
new file mode 100644
index 00000000..f5ebf957
Binary files /dev/null and b/blog/src/assets/media/one-prompt-automated-pr-review/note-1.png differ
diff --git a/blog/src/assets/media/one-prompt-automated-pr-review/note-2.png b/blog/src/assets/media/one-prompt-automated-pr-review/note-2.png
new file mode 100644
index 00000000..e6e6a3e1
Binary files /dev/null and b/blog/src/assets/media/one-prompt-automated-pr-review/note-2.png differ
diff --git a/blog/src/assets/media/open-source-ai-tools-on-purpose/note-1.png b/blog/src/assets/media/open-source-ai-tools-on-purpose/note-1.png
new file mode 100644
index 00000000..806dd622
Binary files /dev/null and b/blog/src/assets/media/open-source-ai-tools-on-purpose/note-1.png differ
diff --git a/blog/src/assets/media/open-source-ai-tools-on-purpose/note-2.png b/blog/src/assets/media/open-source-ai-tools-on-purpose/note-2.png
new file mode 100644
index 00000000..9ac66b29
Binary files /dev/null and b/blog/src/assets/media/open-source-ai-tools-on-purpose/note-2.png differ
diff --git a/blog/src/assets/media/orca-vs-munder-difflin/note-1.png b/blog/src/assets/media/orca-vs-munder-difflin/note-1.png
new file mode 100644
index 00000000..51c6c574
Binary files /dev/null and b/blog/src/assets/media/orca-vs-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/orca-vs-munder-difflin/note-2.png b/blog/src/assets/media/orca-vs-munder-difflin/note-2.png
new file mode 100644
index 00000000..80e94d6c
Binary files /dev/null and b/blog/src/assets/media/orca-vs-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/overnight-ai-coding-realistic-expectations/note-1.png b/blog/src/assets/media/overnight-ai-coding-realistic-expectations/note-1.png
new file mode 100644
index 00000000..ed437891
Binary files /dev/null and b/blog/src/assets/media/overnight-ai-coding-realistic-expectations/note-1.png differ
diff --git a/blog/src/assets/media/overnight-ai-coding-realistic-expectations/note-2.png b/blog/src/assets/media/overnight-ai-coding-realistic-expectations/note-2.png
new file mode 100644
index 00000000..47e84bdb
Binary files /dev/null and b/blog/src/assets/media/overnight-ai-coding-realistic-expectations/note-2.png differ
diff --git a/blog/src/assets/media/prompt-caching-for-ai-agents/note-1.png b/blog/src/assets/media/prompt-caching-for-ai-agents/note-1.png
new file mode 100644
index 00000000..f077c2f6
Binary files /dev/null and b/blog/src/assets/media/prompt-caching-for-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/prompt-caching-for-ai-agents/note-2.png b/blog/src/assets/media/prompt-caching-for-ai-agents/note-2.png
new file mode 100644
index 00000000..739cf531
Binary files /dev/null and b/blog/src/assets/media/prompt-caching-for-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/qm-vs-munder-difflin/note-1.png b/blog/src/assets/media/qm-vs-munder-difflin/note-1.png
new file mode 100644
index 00000000..f27f9b81
Binary files /dev/null and b/blog/src/assets/media/qm-vs-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/qm-vs-munder-difflin/note-2.png b/blog/src/assets/media/qm-vs-munder-difflin/note-2.png
new file mode 100644
index 00000000..10e03b1c
Binary files /dev/null and b/blog/src/assets/media/qm-vs-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/recovering-from-agent-failures/note-1.png b/blog/src/assets/media/recovering-from-agent-failures/note-1.png
new file mode 100644
index 00000000..e5e4cf44
Binary files /dev/null and b/blog/src/assets/media/recovering-from-agent-failures/note-1.png differ
diff --git a/blog/src/assets/media/recovering-from-agent-failures/note-2.png b/blog/src/assets/media/recovering-from-agent-failures/note-2.png
new file mode 100644
index 00000000..75fab1fa
Binary files /dev/null and b/blog/src/assets/media/recovering-from-agent-failures/note-2.png differ
diff --git a/blog/src/assets/media/rendering-many-live-terminals-performance/note-1.png b/blog/src/assets/media/rendering-many-live-terminals-performance/note-1.png
new file mode 100644
index 00000000..b616c37a
Binary files /dev/null and b/blog/src/assets/media/rendering-many-live-terminals-performance/note-1.png differ
diff --git a/blog/src/assets/media/rendering-many-live-terminals-performance/note-2.png b/blog/src/assets/media/rendering-many-live-terminals-performance/note-2.png
new file mode 100644
index 00000000..0b36f667
Binary files /dev/null and b/blog/src/assets/media/rendering-many-live-terminals-performance/note-2.png differ
diff --git a/blog/src/assets/media/review-agent-work-where-it-happens/note-1.png b/blog/src/assets/media/review-agent-work-where-it-happens/note-1.png
new file mode 100644
index 00000000..61586a7b
Binary files /dev/null and b/blog/src/assets/media/review-agent-work-where-it-happens/note-1.png differ
diff --git a/blog/src/assets/media/review-agent-work-where-it-happens/note-2.png b/blog/src/assets/media/review-agent-work-where-it-happens/note-2.png
new file mode 100644
index 00000000..31881a8c
Binary files /dev/null and b/blog/src/assets/media/review-agent-work-where-it-happens/note-2.png differ
diff --git a/blog/src/assets/media/run-a-mixed-engine-office/note-1.png b/blog/src/assets/media/run-a-mixed-engine-office/note-1.png
new file mode 100644
index 00000000..b701b328
Binary files /dev/null and b/blog/src/assets/media/run-a-mixed-engine-office/note-1.png differ
diff --git a/blog/src/assets/media/run-a-mixed-engine-office/note-2.png b/blog/src/assets/media/run-a-mixed-engine-office/note-2.png
new file mode 100644
index 00000000..d566f023
Binary files /dev/null and b/blog/src/assets/media/run-a-mixed-engine-office/note-2.png differ
diff --git a/blog/src/assets/media/run-a-release-train-with-agents/hero.png b/blog/src/assets/media/run-a-release-train-with-agents/hero.png
new file mode 100644
index 00000000..46b5b9f1
Binary files /dev/null and b/blog/src/assets/media/run-a-release-train-with-agents/hero.png differ
diff --git a/blog/src/assets/media/run-a-release-train-with-agents/note-1.png b/blog/src/assets/media/run-a-release-train-with-agents/note-1.png
new file mode 100644
index 00000000..76d00f49
Binary files /dev/null and b/blog/src/assets/media/run-a-release-train-with-agents/note-1.png differ
diff --git a/blog/src/assets/media/run-a-release-train-with-agents/note-2.png b/blog/src/assets/media/run-a-release-train-with-agents/note-2.png
new file mode 100644
index 00000000..2211c106
Binary files /dev/null and b/blog/src/assets/media/run-a-release-train-with-agents/note-2.png differ
diff --git a/blog/src/assets/media/run-ai-agent-hive-from-slack-setup/note-1.png b/blog/src/assets/media/run-ai-agent-hive-from-slack-setup/note-1.png
new file mode 100644
index 00000000..e3e51b1a
Binary files /dev/null and b/blog/src/assets/media/run-ai-agent-hive-from-slack-setup/note-1.png differ
diff --git a/blog/src/assets/media/run-ai-agent-hive-from-slack-setup/note-2.png b/blog/src/assets/media/run-ai-agent-hive-from-slack-setup/note-2.png
new file mode 100644
index 00000000..280a68c5
Binary files /dev/null and b/blog/src/assets/media/run-ai-agent-hive-from-slack-setup/note-2.png differ
diff --git a/blog/src/assets/media/run-an-office-of-ai-agents/note-1.png b/blog/src/assets/media/run-an-office-of-ai-agents/note-1.png
new file mode 100644
index 00000000..7719cccc
Binary files /dev/null and b/blog/src/assets/media/run-an-office-of-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/run-an-office-of-ai-agents/note-2.png b/blog/src/assets/media/run-an-office-of-ai-agents/note-2.png
new file mode 100644
index 00000000..014f1f67
Binary files /dev/null and b/blog/src/assets/media/run-an-office-of-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/run-munder-difflin-on-a-mac-mini/note-1.png b/blog/src/assets/media/run-munder-difflin-on-a-mac-mini/note-1.png
new file mode 100644
index 00000000..a6dee762
Binary files /dev/null and b/blog/src/assets/media/run-munder-difflin-on-a-mac-mini/note-1.png differ
diff --git a/blog/src/assets/media/run-munder-difflin-on-a-mac-mini/note-2.png b/blog/src/assets/media/run-munder-difflin-on-a-mac-mini/note-2.png
new file mode 100644
index 00000000..fc3b628f
Binary files /dev/null and b/blog/src/assets/media/run-munder-difflin-on-a-mac-mini/note-2.png differ
diff --git a/blog/src/assets/media/run-munder-difflin-on-open-models/note-1.png b/blog/src/assets/media/run-munder-difflin-on-open-models/note-1.png
new file mode 100644
index 00000000..2939e3ec
Binary files /dev/null and b/blog/src/assets/media/run-munder-difflin-on-open-models/note-1.png differ
diff --git a/blog/src/assets/media/run-munder-difflin-on-open-models/note-2.png b/blog/src/assets/media/run-munder-difflin-on-open-models/note-2.png
new file mode 100644
index 00000000..2e66282e
Binary files /dev/null and b/blog/src/assets/media/run-munder-difflin-on-open-models/note-2.png differ
diff --git a/blog/src/assets/media/scheduling-autonomous-agent-missions/note-1.png b/blog/src/assets/media/scheduling-autonomous-agent-missions/note-1.png
new file mode 100644
index 00000000..701b5d8d
Binary files /dev/null and b/blog/src/assets/media/scheduling-autonomous-agent-missions/note-1.png differ
diff --git a/blog/src/assets/media/scheduling-autonomous-agent-missions/note-2.png b/blog/src/assets/media/scheduling-autonomous-agent-missions/note-2.png
new file mode 100644
index 00000000..31a16615
Binary files /dev/null and b/blog/src/assets/media/scheduling-autonomous-agent-missions/note-2.png differ
diff --git a/blog/src/assets/media/security-for-ai-coding-agents/note-1.png b/blog/src/assets/media/security-for-ai-coding-agents/note-1.png
new file mode 100644
index 00000000..3537f52b
Binary files /dev/null and b/blog/src/assets/media/security-for-ai-coding-agents/note-1.png differ
diff --git a/blog/src/assets/media/security-for-ai-coding-agents/note-2.png b/blog/src/assets/media/security-for-ai-coding-agents/note-2.png
new file mode 100644
index 00000000..4848b307
Binary files /dev/null and b/blog/src/assets/media/security-for-ai-coding-agents/note-2.png differ
diff --git a/blog/src/assets/media/semantic-memory-for-ai-agents/note-1.png b/blog/src/assets/media/semantic-memory-for-ai-agents/note-1.png
new file mode 100644
index 00000000..c3601515
Binary files /dev/null and b/blog/src/assets/media/semantic-memory-for-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/semantic-memory-for-ai-agents/note-2.png b/blog/src/assets/media/semantic-memory-for-ai-agents/note-2.png
new file mode 100644
index 00000000..e79db157
Binary files /dev/null and b/blog/src/assets/media/semantic-memory-for-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/seven-releases-in-eight-days/hero.png b/blog/src/assets/media/seven-releases-in-eight-days/hero.png
new file mode 100644
index 00000000..624dc0cb
Binary files /dev/null and b/blog/src/assets/media/seven-releases-in-eight-days/hero.png differ
diff --git a/blog/src/assets/media/seven-releases-in-eight-days/note-1.png b/blog/src/assets/media/seven-releases-in-eight-days/note-1.png
new file mode 100644
index 00000000..199aafca
Binary files /dev/null and b/blog/src/assets/media/seven-releases-in-eight-days/note-1.png differ
diff --git a/blog/src/assets/media/seven-releases-in-eight-days/note-2.png b/blog/src/assets/media/seven-releases-in-eight-days/note-2.png
new file mode 100644
index 00000000..3b4ae830
Binary files /dev/null and b/blog/src/assets/media/seven-releases-in-eight-days/note-2.png differ
diff --git a/blog/src/assets/media/seven-releases-in-eight-days/note-3.png b/blog/src/assets/media/seven-releases-in-eight-days/note-3.png
new file mode 100644
index 00000000..02e0b1e4
Binary files /dev/null and b/blog/src/assets/media/seven-releases-in-eight-days/note-3.png differ
diff --git a/blog/src/assets/media/shareable-agent-roles/note-1.png b/blog/src/assets/media/shareable-agent-roles/note-1.png
new file mode 100644
index 00000000..c712933d
Binary files /dev/null and b/blog/src/assets/media/shareable-agent-roles/note-1.png differ
diff --git a/blog/src/assets/media/shareable-agent-roles/note-2.png b/blog/src/assets/media/shareable-agent-roles/note-2.png
new file mode 100644
index 00000000..25e618f2
Binary files /dev/null and b/blog/src/assets/media/shareable-agent-roles/note-2.png differ
diff --git a/blog/src/assets/media/single-committer-git-pattern/note-1.png b/blog/src/assets/media/single-committer-git-pattern/note-1.png
new file mode 100644
index 00000000..3e2d623e
Binary files /dev/null and b/blog/src/assets/media/single-committer-git-pattern/note-1.png differ
diff --git a/blog/src/assets/media/single-committer-git-pattern/note-2.png b/blog/src/assets/media/single-committer-git-pattern/note-2.png
new file mode 100644
index 00000000..9aed84e6
Binary files /dev/null and b/blog/src/assets/media/single-committer-git-pattern/note-2.png differ
diff --git a/blog/src/assets/media/small-team-ai-agents-playbook/note-1.png b/blog/src/assets/media/small-team-ai-agents-playbook/note-1.png
new file mode 100644
index 00000000..f047fff9
Binary files /dev/null and b/blog/src/assets/media/small-team-ai-agents-playbook/note-1.png differ
diff --git a/blog/src/assets/media/small-team-ai-agents-playbook/note-2.png b/blog/src/assets/media/small-team-ai-agents-playbook/note-2.png
new file mode 100644
index 00000000..36ab55dc
Binary files /dev/null and b/blog/src/assets/media/small-team-ai-agents-playbook/note-2.png differ
diff --git a/blog/src/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-1.png b/blog/src/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-1.png
new file mode 100644
index 00000000..61983efe
Binary files /dev/null and b/blog/src/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-1.png differ
diff --git a/blog/src/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-2.png b/blog/src/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-2.png
new file mode 100644
index 00000000..c0e2ddb1
Binary files /dev/null and b/blog/src/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-2.png differ
diff --git a/blog/src/assets/media/the-hook-shim-pattern/note-1.png b/blog/src/assets/media/the-hook-shim-pattern/note-1.png
new file mode 100644
index 00000000..d06b9c8e
Binary files /dev/null and b/blog/src/assets/media/the-hook-shim-pattern/note-1.png differ
diff --git a/blog/src/assets/media/the-hook-shim-pattern/note-2.png b/blog/src/assets/media/the-hook-shim-pattern/note-2.png
new file mode 100644
index 00000000..818ede31
Binary files /dev/null and b/blog/src/assets/media/the-hook-shim-pattern/note-2.png differ
diff --git a/blog/src/assets/media/the-lethal-trifecta-for-coding-agents/note-1.png b/blog/src/assets/media/the-lethal-trifecta-for-coding-agents/note-1.png
new file mode 100644
index 00000000..881b4ada
Binary files /dev/null and b/blog/src/assets/media/the-lethal-trifecta-for-coding-agents/note-1.png differ
diff --git a/blog/src/assets/media/the-lethal-trifecta-for-coding-agents/note-2.png b/blog/src/assets/media/the-lethal-trifecta-for-coding-agents/note-2.png
new file mode 100644
index 00000000..cdc599a5
Binary files /dev/null and b/blog/src/assets/media/the-lethal-trifecta-for-coding-agents/note-2.png differ
diff --git a/blog/src/assets/media/the-multi-agent-cost-playbook/note-1.png b/blog/src/assets/media/the-multi-agent-cost-playbook/note-1.png
new file mode 100644
index 00000000..d659683c
Binary files /dev/null and b/blog/src/assets/media/the-multi-agent-cost-playbook/note-1.png differ
diff --git a/blog/src/assets/media/the-multi-agent-cost-playbook/note-2.png b/blog/src/assets/media/the-multi-agent-cost-playbook/note-2.png
new file mode 100644
index 00000000..21b6e13e
Binary files /dev/null and b/blog/src/assets/media/the-multi-agent-cost-playbook/note-2.png differ
diff --git a/blog/src/assets/media/the-newline-that-silenced-windows-agents/hero.png b/blog/src/assets/media/the-newline-that-silenced-windows-agents/hero.png
new file mode 100644
index 00000000..5af951ed
Binary files /dev/null and b/blog/src/assets/media/the-newline-that-silenced-windows-agents/hero.png differ
diff --git a/blog/src/assets/media/the-newline-that-silenced-windows-agents/note-1.png b/blog/src/assets/media/the-newline-that-silenced-windows-agents/note-1.png
new file mode 100644
index 00000000..486dc9ac
Binary files /dev/null and b/blog/src/assets/media/the-newline-that-silenced-windows-agents/note-1.png differ
diff --git a/blog/src/assets/media/the-newline-that-silenced-windows-agents/note-2.png b/blog/src/assets/media/the-newline-that-silenced-windows-agents/note-2.png
new file mode 100644
index 00000000..e67ebddd
Binary files /dev/null and b/blog/src/assets/media/the-newline-that-silenced-windows-agents/note-2.png differ
diff --git a/blog/src/assets/media/the-office-parody-behind-munder-difflin/note-1.png b/blog/src/assets/media/the-office-parody-behind-munder-difflin/note-1.png
new file mode 100644
index 00000000..6f15d3e3
Binary files /dev/null and b/blog/src/assets/media/the-office-parody-behind-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/the-office-parody-behind-munder-difflin/note-2.png b/blog/src/assets/media/the-office-parody-behind-munder-difflin/note-2.png
new file mode 100644
index 00000000..33786821
Binary files /dev/null and b/blog/src/assets/media/the-office-parody-behind-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/tmux-and-scripts-vs-an-agent-harness/note-1.png b/blog/src/assets/media/tmux-and-scripts-vs-an-agent-harness/note-1.png
new file mode 100644
index 00000000..f7d00ea9
Binary files /dev/null and b/blog/src/assets/media/tmux-and-scripts-vs-an-agent-harness/note-1.png differ
diff --git a/blog/src/assets/media/tmux-and-scripts-vs-an-agent-harness/note-2.png b/blog/src/assets/media/tmux-and-scripts-vs-an-agent-harness/note-2.png
new file mode 100644
index 00000000..69c8d032
Binary files /dev/null and b/blog/src/assets/media/tmux-and-scripts-vs-an-agent-harness/note-2.png differ
diff --git a/blog/src/assets/media/trigger-ai-agents-from-github-webhook/note-1.png b/blog/src/assets/media/trigger-ai-agents-from-github-webhook/note-1.png
new file mode 100644
index 00000000..4358e59e
Binary files /dev/null and b/blog/src/assets/media/trigger-ai-agents-from-github-webhook/note-1.png differ
diff --git a/blog/src/assets/media/trigger-ai-agents-from-github-webhook/note-2.png b/blog/src/assets/media/trigger-ai-agents-from-github-webhook/note-2.png
new file mode 100644
index 00000000..f798482d
Binary files /dev/null and b/blog/src/assets/media/trigger-ai-agents-from-github-webhook/note-2.png differ
diff --git a/blog/src/assets/media/trigger-ai-agents-from-slack/note-1.png b/blog/src/assets/media/trigger-ai-agents-from-slack/note-1.png
new file mode 100644
index 00000000..6bc65b5f
Binary files /dev/null and b/blog/src/assets/media/trigger-ai-agents-from-slack/note-1.png differ
diff --git a/blog/src/assets/media/trigger-ai-agents-from-slack/note-2.png b/blog/src/assets/media/trigger-ai-agents-from-slack/note-2.png
new file mode 100644
index 00000000..7d35aa76
Binary files /dev/null and b/blog/src/assets/media/trigger-ai-agents-from-slack/note-2.png differ
diff --git a/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/hero.png b/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/hero.png
new file mode 100644
index 00000000..b1293ae1
Binary files /dev/null and b/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/hero.png differ
diff --git a/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/note-1.png b/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/note-1.png
new file mode 100644
index 00000000..1703a5e8
Binary files /dev/null and b/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/note-1.png differ
diff --git a/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/note-2.png b/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/note-2.png
new file mode 100644
index 00000000..978d5748
Binary files /dev/null and b/blog/src/assets/media/turn-feedback-into-a-backlog-with-agents/note-2.png differ
diff --git a/blog/src/assets/media/vibe-kanban-alternative/note-1.png b/blog/src/assets/media/vibe-kanban-alternative/note-1.png
new file mode 100644
index 00000000..8e1e9155
Binary files /dev/null and b/blog/src/assets/media/vibe-kanban-alternative/note-1.png differ
diff --git a/blog/src/assets/media/vibe-kanban-alternative/note-2.png b/blog/src/assets/media/vibe-kanban-alternative/note-2.png
new file mode 100644
index 00000000..cde99706
Binary files /dev/null and b/blog/src/assets/media/vibe-kanban-alternative/note-2.png differ
diff --git a/blog/src/assets/media/visualizing-ai-agents-pixijs/note-1.png b/blog/src/assets/media/visualizing-ai-agents-pixijs/note-1.png
new file mode 100644
index 00000000..c741379d
Binary files /dev/null and b/blog/src/assets/media/visualizing-ai-agents-pixijs/note-1.png differ
diff --git a/blog/src/assets/media/visualizing-ai-agents-pixijs/note-2.png b/blog/src/assets/media/visualizing-ai-agents-pixijs/note-2.png
new file mode 100644
index 00000000..e7ad845f
Binary files /dev/null and b/blog/src/assets/media/visualizing-ai-agents-pixijs/note-2.png differ
diff --git a/blog/src/assets/media/voice-as-a-control-plane-for-agent-fleets/note-1.png b/blog/src/assets/media/voice-as-a-control-plane-for-agent-fleets/note-1.png
new file mode 100644
index 00000000..b526ba88
Binary files /dev/null and b/blog/src/assets/media/voice-as-a-control-plane-for-agent-fleets/note-1.png differ
diff --git a/blog/src/assets/media/voice-as-a-control-plane-for-agent-fleets/note-2.png b/blog/src/assets/media/voice-as-a-control-plane-for-agent-fleets/note-2.png
new file mode 100644
index 00000000..dc960b85
Binary files /dev/null and b/blog/src/assets/media/voice-as-a-control-plane-for-agent-fleets/note-2.png differ
diff --git a/blog/src/assets/media/we-opened-a-discord/hero.png b/blog/src/assets/media/we-opened-a-discord/hero.png
new file mode 100644
index 00000000..ebca5d82
Binary files /dev/null and b/blog/src/assets/media/we-opened-a-discord/hero.png differ
diff --git a/blog/src/assets/media/we-opened-a-discord/note-1.png b/blog/src/assets/media/we-opened-a-discord/note-1.png
new file mode 100644
index 00000000..d6de30ee
Binary files /dev/null and b/blog/src/assets/media/we-opened-a-discord/note-1.png differ
diff --git a/blog/src/assets/media/we-opened-a-discord/note-2.png b/blog/src/assets/media/we-opened-a-discord/note-2.png
new file mode 100644
index 00000000..06628136
Binary files /dev/null and b/blog/src/assets/media/we-opened-a-discord/note-2.png differ
diff --git a/blog/src/assets/media/what-are-claude-code-agents/note-1.png b/blog/src/assets/media/what-are-claude-code-agents/note-1.png
new file mode 100644
index 00000000..a0943a9a
Binary files /dev/null and b/blog/src/assets/media/what-are-claude-code-agents/note-1.png differ
diff --git a/blog/src/assets/media/what-are-claude-code-agents/note-2.png b/blog/src/assets/media/what-are-claude-code-agents/note-2.png
new file mode 100644
index 00000000..f7d36213
Binary files /dev/null and b/blog/src/assets/media/what-are-claude-code-agents/note-2.png differ
diff --git a/blog/src/assets/media/what-is-a-multi-agent-harness/note-1.png b/blog/src/assets/media/what-is-a-multi-agent-harness/note-1.png
new file mode 100644
index 00000000..bb3c415b
Binary files /dev/null and b/blog/src/assets/media/what-is-a-multi-agent-harness/note-1.png differ
diff --git a/blog/src/assets/media/what-is-a-multi-agent-harness/note-2.png b/blog/src/assets/media/what-is-a-multi-agent-harness/note-2.png
new file mode 100644
index 00000000..77a27a9e
Binary files /dev/null and b/blog/src/assets/media/what-is-a-multi-agent-harness/note-2.png differ
diff --git a/blog/src/assets/media/what-is-aeo-for-dev-tools/note-1.png b/blog/src/assets/media/what-is-aeo-for-dev-tools/note-1.png
new file mode 100644
index 00000000..68eda8d8
Binary files /dev/null and b/blog/src/assets/media/what-is-aeo-for-dev-tools/note-1.png differ
diff --git a/blog/src/assets/media/what-is-aeo-for-dev-tools/note-2.png b/blog/src/assets/media/what-is-aeo-for-dev-tools/note-2.png
new file mode 100644
index 00000000..9d215c17
Binary files /dev/null and b/blog/src/assets/media/what-is-aeo-for-dev-tools/note-2.png differ
diff --git a/blog/src/assets/media/what-is-an-agent-development-environment/note-1.png b/blog/src/assets/media/what-is-an-agent-development-environment/note-1.png
new file mode 100644
index 00000000..cbd0b93e
Binary files /dev/null and b/blog/src/assets/media/what-is-an-agent-development-environment/note-1.png differ
diff --git a/blog/src/assets/media/what-is-an-agent-development-environment/note-2.png b/blog/src/assets/media/what-is-an-agent-development-environment/note-2.png
new file mode 100644
index 00000000..a3344d01
Binary files /dev/null and b/blog/src/assets/media/what-is-an-agent-development-environment/note-2.png differ
diff --git a/blog/src/assets/media/what-is-harness-engineering/note-1.png b/blog/src/assets/media/what-is-harness-engineering/note-1.png
new file mode 100644
index 00000000..fa42660b
Binary files /dev/null and b/blog/src/assets/media/what-is-harness-engineering/note-1.png differ
diff --git a/blog/src/assets/media/what-is-harness-engineering/note-2.png b/blog/src/assets/media/what-is-harness-engineering/note-2.png
new file mode 100644
index 00000000..e3caa6f1
Binary files /dev/null and b/blog/src/assets/media/what-is-harness-engineering/note-2.png differ
diff --git a/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/hero.png b/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/hero.png
new file mode 100644
index 00000000..69edea31
Binary files /dev/null and b/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/hero.png differ
diff --git a/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/note-1.png b/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/note-1.png
new file mode 100644
index 00000000..a1dd4017
Binary files /dev/null and b/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/note-2.png b/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/note-2.png
new file mode 100644
index 00000000..6f7f300b
Binary files /dev/null and b/blog/src/assets/media/what-reddit-told-us-about-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/whats-new-in-agentic-ai-june-2026/note-1.png b/blog/src/assets/media/whats-new-in-agentic-ai-june-2026/note-1.png
new file mode 100644
index 00000000..f16921d0
Binary files /dev/null and b/blog/src/assets/media/whats-new-in-agentic-ai-june-2026/note-1.png differ
diff --git a/blog/src/assets/media/whats-new-in-agentic-ai-june-2026/note-2.png b/blog/src/assets/media/whats-new-in-agentic-ai-june-2026/note-2.png
new file mode 100644
index 00000000..6b798e6d
Binary files /dev/null and b/blog/src/assets/media/whats-new-in-agentic-ai-june-2026/note-2.png differ
diff --git a/blog/src/assets/media/whats-up-with-munder-difflin/note-1.png b/blog/src/assets/media/whats-up-with-munder-difflin/note-1.png
new file mode 100644
index 00000000..cc9c7e9b
Binary files /dev/null and b/blog/src/assets/media/whats-up-with-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/whats-up-with-munder-difflin/note-2.png b/blog/src/assets/media/whats-up-with-munder-difflin/note-2.png
new file mode 100644
index 00000000..341ce65f
Binary files /dev/null and b/blog/src/assets/media/whats-up-with-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/when-do-agents-need-an-agent-protocol/note-1.png b/blog/src/assets/media/when-do-agents-need-an-agent-protocol/note-1.png
new file mode 100644
index 00000000..ed5755e8
Binary files /dev/null and b/blog/src/assets/media/when-do-agents-need-an-agent-protocol/note-1.png differ
diff --git a/blog/src/assets/media/when-do-agents-need-an-agent-protocol/note-2.png b/blog/src/assets/media/when-do-agents-need-an-agent-protocol/note-2.png
new file mode 100644
index 00000000..910f78e3
Binary files /dev/null and b/blog/src/assets/media/when-do-agents-need-an-agent-protocol/note-2.png differ
diff --git a/blog/src/assets/media/why-cli-agents-are-powerful/note-1.png b/blog/src/assets/media/why-cli-agents-are-powerful/note-1.png
new file mode 100644
index 00000000..295b42ee
Binary files /dev/null and b/blog/src/assets/media/why-cli-agents-are-powerful/note-1.png differ
diff --git a/blog/src/assets/media/why-cli-agents-are-powerful/note-2.png b/blog/src/assets/media/why-cli-agents-are-powerful/note-2.png
new file mode 100644
index 00000000..9788f649
Binary files /dev/null and b/blog/src/assets/media/why-cli-agents-are-powerful/note-2.png differ
diff --git a/blog/src/assets/media/why-local-first-matters-for-ai-agents/note-1.png b/blog/src/assets/media/why-local-first-matters-for-ai-agents/note-1.png
new file mode 100644
index 00000000..c498ea9f
Binary files /dev/null and b/blog/src/assets/media/why-local-first-matters-for-ai-agents/note-1.png differ
diff --git a/blog/src/assets/media/why-local-first-matters-for-ai-agents/note-2.png b/blog/src/assets/media/why-local-first-matters-for-ai-agents/note-2.png
new file mode 100644
index 00000000..e8eee765
Binary files /dev/null and b/blog/src/assets/media/why-local-first-matters-for-ai-agents/note-2.png differ
diff --git a/blog/src/assets/media/why-our-auto-update-never-ran/note-1.png b/blog/src/assets/media/why-our-auto-update-never-ran/note-1.png
new file mode 100644
index 00000000..67f12b89
Binary files /dev/null and b/blog/src/assets/media/why-our-auto-update-never-ran/note-1.png differ
diff --git a/blog/src/assets/media/why-our-auto-update-never-ran/note-2.png b/blog/src/assets/media/why-our-auto-update-never-ran/note-2.png
new file mode 100644
index 00000000..228c8e31
Binary files /dev/null and b/blog/src/assets/media/why-our-auto-update-never-ran/note-2.png differ
diff --git a/blog/src/assets/media/why-we-built-munder-difflin/note-1.png b/blog/src/assets/media/why-we-built-munder-difflin/note-1.png
new file mode 100644
index 00000000..cbe1357b
Binary files /dev/null and b/blog/src/assets/media/why-we-built-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/why-we-built-munder-difflin/note-2.png b/blog/src/assets/media/why-we-built-munder-difflin/note-2.png
new file mode 100644
index 00000000..92f855a4
Binary files /dev/null and b/blog/src/assets/media/why-we-built-munder-difflin/note-2.png differ
diff --git a/blog/src/assets/media/your-first-hour-with-munder-difflin/note-1.png b/blog/src/assets/media/your-first-hour-with-munder-difflin/note-1.png
new file mode 100644
index 00000000..1800b639
Binary files /dev/null and b/blog/src/assets/media/your-first-hour-with-munder-difflin/note-1.png differ
diff --git a/blog/src/assets/media/your-first-hour-with-munder-difflin/note-2.png b/blog/src/assets/media/your-first-hour-with-munder-difflin/note-2.png
new file mode 100644
index 00000000..9c648739
Binary files /dev/null and b/blog/src/assets/media/your-first-hour-with-munder-difflin/note-2.png differ
diff --git a/blog/src/posts/agent-security-and-sandboxing.md b/blog/src/posts/agent-security-and-sandboxing.md
index bcef735f..653c8c20 100644
--- a/blog/src/posts/agent-security-and-sandboxing.md
+++ b/blog/src/posts/agent-security-and-sandboxing.md
@@ -50,6 +50,8 @@ That honesty is the right framing. Bypass mode isn't reckless — it's the *corr
unattended control room. But it removes the last interactive gate, so the safety has to live somewhere
else. The rest of this post is "somewhere else."
+{% img "note-1" %}
+
## When the prompt is off, structure is your safety
If you can't rely on a human clicking "approve," you make the dangerous things structurally hard to
@@ -87,6 +89,8 @@ log](/blog/append-only-event-log-agents/) records every action in order, so "wha
through [native approvals](/blog/human-in-the-loop-approving-ai-agents/). Bypass mode and a human gate
aren't mutually exclusive: most actions flow, the few that matter still wait.
+{% img "note-2" %}
+
## What to gate vs. what to allow
Security theater is gating everything until the human rubber-stamps a hundred prompts and stops reading.
diff --git a/blog/src/posts/agents-ran-our-launch-week-analytics.md b/blog/src/posts/agents-ran-our-launch-week-analytics.md
new file mode 100644
index 00000000..cbbf274f
--- /dev/null
+++ b/blog/src/posts/agents-ran-our-launch-week-analytics.md
@@ -0,0 +1,109 @@
+---
+title: "Our Agents Ran Our Launch-Week Analytics"
+description: "Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch."
+date: 2026-08-19
+category: use-cases
+categoryLabel: Use Cases
+type: Non-technical
+primaryKeyword: "ai agents launch analytics"
+secondaryKeywords: ["analyze reddit comments with ai", "multi-agent research workflow", "launch retrospective automation", "product hunt analysis ai", "munder difflin use case"]
+tags: ["Use Cases", "Research", "Launch", "Workflow", "Multi-Agent"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "What did the agents actually analyze?"
+ a: "Four channels in parallel: ten Reddit launch threads (501 comments including every nested reply), the full Product Hunt page (27 comments plus the page's own data), GitHub traffic, and PostHog funnels. Each agent produced a structured report — a readable markdown brief plus a JSON file — and the orchestrator synthesized them into one picture."
+ - q: "Why use multiple agents instead of one long session?"
+ a: "Each channel is a full context window of raw material on its own. One agent per channel means each report is written by something that actually read every comment, not a skim. The orchestrator then works from the four distilled reports — which is exactly the fan-out-then-synthesize pattern hives are good at."
+ - q: "Can I run this on my own launch?"
+ a: "Yes — the recipe is at the end of the post. You need the raw threads saved locally (Reddit's JSON endpoints work), one agent per channel with a clear brief, a shared folder for reports, and one synthesis pass at the end. A weekend launch produces an evening of agent work."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>After launch week we had ten Reddit
+threads, 516 comments, a Product Hunt page, and analytics dashboards — far more than any human
+was going to read honestly. So we didn't. <strong>A hive of agents read all of it</strong>: one
+agent per channel, structured briefs in, markdown + JSON reports out, one synthesis at the end.
+Every launch decision we've made since traces to those reports. Here's the workflow.</p></div>
+
+There's a specific kind of lying founders do after a launch: they remember the five most
+emotional comments and call it "what the community said." We had 516 comments across ten
+subreddits. Nobody's memory survives that honestly.
+
+But we make a tool whose whole job is
+[coordinating agents on real work](/blog/run-an-office-of-ai-agents/). Launch analytics turned
+out to be the best dogfood we've ever had.
+
+## The floor plan
+
+Four agents, one channel each, spawned with a written brief:
+
+- **Reddit agent** — the big one. Ten launch threads saved as raw JSON, 501 comments including
+ every nested reply. Brief: account for *every* comment — bucket objections, praise,
+ feature asks, and pricing signals, with quotes and usernames preserved.
+- **Product Hunt agent** — the launch page: all 27 comments, the review, and the page's own
+ embedded data, read straight from the source rather than eyeballing rendered numbers.
+- **GitHub agent** — stars, traffic, referrers, clones: which channel actually moved the repo.
+- **Analytics agent** — PostHog funnels: installs, first runs, and where new users stalled.
+
+{% img "note-1", "One channel per agent: Reddit, Product Hunt, GitHub, PostHog. Each reads everything, each files a report." %}
+
+Each agent wrote two artifacts into a shared research folder: a **markdown brief** a human
+actually wants to read, and a **JSON file** with the counted, bucketed data so later questions
+don't require re-reading anything. Then the orchestrator synthesized the four into one picture.
+
+## Why the fan-out matters
+
+The naive version of this is pasting comments into one chat session until it fills up. The
+problem isn't just context size — it's that a model skimming its 400th comment gets exactly as
+lazy as a human does. One agent per channel keeps each report grounded in a full, careful read,
+and the [orchestrator](/blog/how-the-god-orchestrator-works/) works from four distilled reports
+instead of raw sludge. Fan out, then synthesize. It's the same
+[pattern](/blog/multi-agent-orchestration-patterns/) that works for code.
+
+The other thing a hive gets you is **iteration without re-reading**. Days later we came back
+with sharper questions — "split willingness-to-pay by supporter motive versus buyer motive,"
+"which commenters were blocked from even running it?" — and dispatched them to the same agent,
+which still had [its memory](/blog/how-agents-remember-semantic-memory/) of the corpus. Each
+pass appended to the same reports. The research got *thicker* instead of starting over.
+
+{% img "note-2", "Sharper question, same agent, same corpus — the reports grow instead of restarting." %}
+
+## What fell out of it
+
+Findings we would have missed by skimming, all of which changed real decisions:
+
+- **46% of all engagement came from one subreddit.** r/ClaudeCode delivered 1,017 of 2,233
+ combined upvotes. Two other communities flatlined. That's next launch's channel budget,
+ decided.
+- **Product Hunt sent 195 upvotes and ~25 visitors.** Credibility channel, not traffic channel.
+ We'd have guessed wrong.
+- **The two most serious evaluators asked for the same missing feature** — a visible
+ "this decision needs your eyes" flag — in different words on different platforms. Only
+ cross-channel synthesis caught that they were the same request.
+- **Every blocked-user story on two channels traced to the same bug class** (the non-Claude-Code
+ path on Windows), which moved it to the top of
+ [0.4.4](/blog/launching-munder-difflin-v0-4-4/).
+
+The Reddit and Product Hunt halves of this analysis became
+[their](/blog/what-reddit-told-us-about-munder-difflin/)
+[own](/blog/number-five-on-product-hunt/) posts — both written *from the agents' reports*, which
+is why they have real numbers in them instead of vibes.
+
+## Run it on your launch
+
+The recipe, portable to any hive setup:
+
+1. **Capture raw sources locally first.** Reddit threads have JSON endpoints; save them to
+ disk so agents parse structure instead of scraping rendered pages.
+2. **One agent per channel, written briefs.** The brief that worked: *account for every
+ comment; bucket, count, and quote; write both a human brief and a JSON dataset; flag what
+ you couldn't verify.* That last clause matters — our Reddit agent correctly flagged that
+ view counts are null in public JSON rather than inventing them.
+3. **A shared research folder** all agents write into, so reports reference each other.
+4. **One synthesis pass** at the end — and keep the agents around, because your best questions
+ arrive three days later.
+
+An evening of agent work, and launch week stops being a feeling and becomes a dataset. The
+[overnight version](/blog/claude-code-automation-while-you-sleep/) works too — we know, because
+half of this ran while we slept off the launch.
diff --git a/blog/src/posts/agents-rule-of-two.md b/blog/src/posts/agents-rule-of-two.md
index 3207e39c..515b9794 100644
--- a/blog/src/posts/agents-rule-of-two.md
+++ b/blog/src/posts/agents-rule-of-two.md
@@ -65,6 +65,8 @@ just that observation made actionable: stay at two legs and the worst case is of
credits both Willison's framing and the older Chromium "Rule of 2" as
inspiration.)
+{% img "note-1" %}
+
## A coding agent wants all three by default
Here's the uncomfortable part for our domain: a capable coding agent is *born* at the full trifecta.
@@ -95,6 +97,8 @@ You don't have to neuter the agent — you have to make sure no single session q
In practice you rarely remove a leg entirely — you weaken it enough that a single compromised session
can't complete the chain.
+{% img "note-2" %}
+
## When you genuinely need all three: supervise
Sometimes the task really does want the full [trifecta](/blog/the-lethal-trifecta-for-coding-agents/) — read an untrusted issue, touch private code,
diff --git a/blog/src/posts/ai-agent-glossary.md b/blog/src/posts/ai-agent-glossary.md
index 3be4216b..31185ace 100644
--- a/blog/src/posts/ai-agent-glossary.md
+++ b/blog/src/posts/ai-agent-glossary.md
@@ -45,6 +45,8 @@ Great for parallelism within one task; it doesn't persist or share memory across
**A tool is a capability an agent can call — read a file, run a command, search the web.** Tools are
what let an agent *do* things instead of just talk.
+{% img "note-1" %}
+
## The coordination layer
### Harness
@@ -80,6 +82,8 @@ fetch the few most relevant.** It's what keeps recall instant as the knowledge b
**A mailbox lets one agent hand a message or result to another directly, instead of routing through
you.** It's how a hive coordinates without a human courier.
+{% img "note-2" %}
+
## Workflow patterns
### Git worktree
diff --git a/blog/src/posts/an-agent-redesigned-this-blog.md b/blog/src/posts/an-agent-redesigned-this-blog.md
new file mode 100644
index 00000000..e580d662
--- /dev/null
+++ b/blog/src/posts/an-agent-redesigned-this-blog.md
@@ -0,0 +1,99 @@
+---
+title: "An Agent Redesigned the Blog You're Reading"
+description: "Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of."
+date: 2026-08-19
+category: use-cases
+categoryLabel: Use Cases
+type: Non-technical
+primaryKeyword: "ai agent website redesign"
+secondaryKeywords: ["eleventy blog redesign", "svg illustrations generated by code", "claude code design workflow", "ai generated blog images alternative", "munder difflin blog"]
+tags: ["Use Cases", "Design", "Eleventy", "Workflow", "Meta"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "Who designed the new Munder Difflin blog?"
+ a: "A single agent, working in Claude Code, over one long session with founder feedback in the loop. It proposed two complete themes, and after one was chosen, it restyled the whole site, drew a hero illustration for all 119 posts, and shipped the result through CI to production."
+ - q: "How were 119 hero images made for $0?"
+ a: "They're not AI-generated bitmaps — they're drawn as code. A small SVG parts library (a character, desks, terminals, envelopes, a kanban wall) plus 16 composition archetypes and a per-post spec file produce each scene; a headless browser screenshots them at 1600×900. Editing an image means editing a line of JavaScript, and regenerating costs nothing."
+ - q: "What's the character in the illustrations?"
+ a: "An adaptation of Xiaohei, an open-source (MIT) illustration character we found through a starred repo — recolored to our brand yellow and put to work at tiny desks and terminals across every post. Credit to the original ian-xiaohei-illustrations project."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>The redesign you're looking at —
+the fonts, the yellow, the little hand-drawn scenes on every post — was shipped end to end by
+one agent after Reddit told us the old blog read like AI slop. The part worth stealing:
+<strong>all 119 hero illustrations are drawn as code</strong> — an SVG parts library, 16
+composition archetypes, one spec file — and rendered by screenshotting a browser.
+Image-API bill: $0.</p></div>
+
+During [launch week](/blog/what-reddit-told-us-about-munder-difflin/), among the feedback about
+the product, there was a quieter thread of feedback about this blog. It was not kind. The old
+design was the marketing site's mono-font brutalism stretched over long-form text, there wasn't
+a single image on any post, and more than one person used the phrase "AI-written."
+
+Fair. So we handed the problem to an agent, with a brief instead of a mockup: *make it readable,
+make it human, give every post images, and don't you dare use red.*
+
+## Two themes, one survivor
+
+The agent's first deliverable was two complete, buildable themes — not moodboards, actual
+switchable CSS behind an environment flag, previewable side by side. One warm and bookish, one
+editorial-magazine. The magazine won: serif headlines with real weight, a reading column set in
+a proper text face, the app's own cream-paper palette, and the website's yellow as the single
+accent — always as a highlighter fill, never as colored text.
+
+The founder's role in this phase was one sentence at a time: *use the app's colors. The accent
+is yellow, not red. No red anywhere.* Each note came back applied across every template within
+minutes. That loop — human taste, agent hands — is the whole
+[reason this product exists](/blog/why-we-built-munder-difflin/).
+
+## The image problem, and the $0 answer
+
+Then the hard part: 119 posts needed images, and AI image generation was the obvious move — and
+the wrong one. Quotes came out between $5 and $20 in API costs, every regeneration would cost
+again, and the results would have exactly the generic sheen the redesign was trying to escape.
+
+The agent proposed something better: **draw them as code.**
+
+{% img "note-1", "A parts library, 16 archetypes, and one spec file — that's the entire illustration system behind 119 unique heroes." %}
+
+The system has three layers, all plain JavaScript and SVG:
+
+- **A parts library** — one small character (an adaptation of the MIT-licensed *Xiaohei*,
+ recolored to our brand yellow), desks, terminals, envelopes, a kanban wall, clocks, shields,
+ coffee. A hand-drawn wobble comes from an SVG turbulence filter, seeded per post so no two
+ images wobble identically.
+- **16 composition archetypes** — "agents talking," "night shift," "versus," "the routing
+ desk" — each a function that arranges parts into a scene.
+- **One spec file** — a line per post choosing an archetype and the handwritten annotations:
+ the blue mechanism labels and the orange punchline you see in the corners.
+
+A headless browser opens each scene at 1600×900 and screenshots it into the post's media
+folder. All 119 rendered in three batches. Total image-API spend: **zero**. And when one scene
+looked wrong — a sleeping character whose eyes were open, which is nightmare material — the fix
+was editing a function, not re-prompting a diffusion model and praying.
+
+{% img "note-2", "When a drawing is code, 'his eyes should be closed' is a one-line fix — not a re-roll." %}
+
+## One manifest to rule the media
+
+Under the hood, a single `media.json` drives every image, inline figure, and video embed on the
+blog — per-post entries with a file path, alt text, and a status flag. Templates render a
+designed placeholder until an entry flips to `ready`, so the site never shows a broken image,
+and adding [this very image pipeline](/blog/deploy-a-blog-writer-agent/) to a new post is one
+JSON entry. YouTube embeds got the same treatment: click-to-load, privacy-friendly, with a
+placeholder state for videos that don't exist yet.
+
+## The making-of, honestly
+
+The parts nobody puts in the case study: the agent got the category badge black-on-black on the
+first pass and fixed it when told. It got told "I do not want any red things" *after* it had
+already picked a coral topic color, and remapped the entire palette. The founder's browser
+cached the old build twice, producing two rounds of "you haven't changed anything" that were
+resolved by an agent-written no-cache dev server. Real work looks like this.
+
+But the scoreboard at the end: a full editorial redesign, 119 bespoke illustrations, a media
+pipeline, and CI deployment to production — one agent, one extended session, zero image-API
+dollars. The blog you're reading is the artifact. If it still reads like AI slop, at least now
+it's *hand-drawn* AI slop.
diff --git a/blog/src/posts/append-only-event-log-agents.md b/blog/src/posts/append-only-event-log-agents.md
index 927e4694..c0eaf8cf 100644
--- a/blog/src/posts/append-only-event-log-agents.md
+++ b/blog/src/posts/append-only-event-log-agents.md
@@ -70,6 +70,8 @@ Why JSONL specifically:
A database would give you indexes and queries you mostly don't need here, at the cost of a schema and a
server. For an audit/observability log, plain JSONL is the right amount of technology.
+{% img "note-1" %}
+
## What to record per event
The art is choosing events that are **small, typed, and factual.** Each line carries a `ts`
@@ -97,6 +99,8 @@ interleaved, half-written lines, and it pairs with the
[single-committer git pattern](/blog/single-committer-git-pattern/): each batch of coordination is
both appended to the log *and* committed, so the log's history and git's history line up.
+{% img "note-2" %}
+
## Replay and debugging
Here's where the log earns its keep. Because it's an ordered, immutable record, you can **replay** the
diff --git a/blog/src/posts/architecture-two-planes-one-renderer.md b/blog/src/posts/architecture-two-planes-one-renderer.md
index 0c14c65a..d50e7b19 100644
--- a/blog/src/posts/architecture-two-planes-one-renderer.md
+++ b/blog/src/posts/architecture-two-planes-one-renderer.md
@@ -71,6 +71,8 @@ What the terminal plane gives you: the unfiltered truth of what each agent did.
give you: a reliable "which tool is running right now?" without scraping and guessing at output. That's
the other plane's job.
+{% img "note-1" %}
+
## The event plane (hooks + hive)
The event plane is about *structure*. It has two sources, both feeding the main process:
@@ -102,6 +104,8 @@ Together they're complementary: the office floor is **event-driven** (precise, s
render), and the terminal view is **byte-for-byte authentic** (the full detail when you want it). Two
planes, two questions, both answered well.
+{% img "note-2" %}
+
## One renderer convergence
Both planes terminate in a single Electron renderer running React and Pixi.js:
diff --git a/blog/src/posts/atomic-file-mailboxes-for-agents.md b/blog/src/posts/atomic-file-mailboxes-for-agents.md
index 4600faa5..a21a48e0 100644
--- a/blog/src/posts/atomic-file-mailboxes-for-agents.md
+++ b/blog/src/posts/atomic-file-mailboxes-for-agents.md
@@ -79,6 +79,8 @@ rename inbox/<id>.json.tmp-9f3a → inbox/<id>.json ← appears atomically, wh
This one trick is why files beat a naive shared log. A log every agent appends to is a multi-writer
race; a directory of atomically-renamed files is conflict-free by construction.
+{% img "note-1" %}
+
## The message itself: speech acts, not free text
A message isn't just a blob of text — it carries intent. The design borrows the one genuinely useful
@@ -125,6 +127,8 @@ that:
These are small rules with a big payoff: the messaging layer can be busy and still provably converge.
+{% img "note-2" %}
+
## Broadcast and escalation
Two special addresses round out the system:
diff --git a/blog/src/posts/best-ai-coding-agents.md b/blog/src/posts/best-ai-coding-agents.md
index 27c23a5d..69c099c2 100644
--- a/blog/src/posts/best-ai-coding-agents.md
+++ b/blog/src/posts/best-ai-coding-agents.md
@@ -60,6 +60,8 @@ shipping bigger work. The "one tool wins everything" framing is over.
| **Copilot agent mode** | Platform-native | Partial BYOM (Claude/Codex) | Assist→autopilot | GitHub-native teams |
| **Local multi-agent hive** | Orchestration | Local-first | Coordinated team | Running many agents as a team |
+{% img "note-1" %}
+
## The tools, fairly
**Cursor** — a dedicated AI-first IDE that leads on in-editor agent ergonomics; reference pricing runs
@@ -98,6 +100,8 @@ enough. If that's your need specifically with Claude Code, the
[multi-agent tools roundup](/blog/best-claude-code-multi-agent-tools/) goes deeper, and
[local-first vs cloud agent SDKs](/blog/local-first-vs-cloud-agent-sdks/) covers the build-vs-buy angle.
+{% img "note-2" %}
+
## How to choose
- **You live in an editor** → Cursor (polished IDE) or Cline (local/BYOK in VS Code).
diff --git a/blog/src/posts/best-claude-code-multi-agent-tools.md b/blog/src/posts/best-claude-code-multi-agent-tools.md
index 2538ea5e..0e167892 100644
--- a/blog/src/posts/best-claude-code-multi-agent-tools.md
+++ b/blog/src/posts/best-claude-code-multi-agent-tools.md
@@ -67,6 +67,8 @@ Most tools live cleanly in one camp. Knowing which camp you need is most of the
The single row that most separates the field is **shared memory + orchestrator**: that's the jump
from "running agents in parallel" to "running a team."
+{% img "note-1" %}
+
## Claude Squad — the lean terminal option
[Claude Squad](https://github.com/smtg-ai/claude-squad) is a terminal UI that manages multiple AI
@@ -111,6 +113,8 @@ concurrently, and review diffs and test results across worktrees in one window.
Best for: developers who want an open, visual, worktree-based parallel workflow without the terminal.
More on the trade-offs in [a Crystal alternative](/blog/crystal-claude-code-alternative/).
+{% img "note-2" %}
+
## vibe-kanban — the task board for agents
[vibe-kanban](https://github.com/BloopAI/vibe-kanban) takes a different angle: a kanban board where
diff --git a/blog/src/posts/building-a-terminal-ui-xterm-node-pty.md b/blog/src/posts/building-a-terminal-ui-xterm-node-pty.md
index c67e3f1c..069cc877 100644
--- a/blog/src/posts/building-a-terminal-ui-xterm-node-pty.md
+++ b/blog/src/posts/building-a-terminal-ui-xterm-node-pty.md
@@ -93,6 +93,8 @@ window.cth.onPtyExit(ptyId, ({ exitCode, signal }) =>
xterm's whole job. Writing a dim "process exited" line on `onExit` is a nice touch so a dead terminal
doesn't just freeze silently.
+{% img "note-1" %}
+
## Step 3 — Send keystrokes back
`term.onData` fires for every keystroke (already encoded as the bytes a terminal would send — arrow
@@ -189,6 +191,8 @@ function attachTerminal(entry: TerminalEntry, container: HTMLElement) {
Switching agents becomes a DOM move, not a teardown. The terminal is always populated and always
visible immediately — which is what you need when a user is flicking between a dozen live sessions.
+{% img "note-2" %}
+
## Performance notes for dozens of terminals
A pool keeps correctness; a few habits keep it fast:
diff --git a/blog/src/posts/building-an-ai-office-floor.md b/blog/src/posts/building-an-ai-office-floor.md
index 0c804c17..981037f7 100644
--- a/blog/src/posts/building-an-ai-office-floor.md
+++ b/blog/src/posts/building-an-ai-office-floor.md
@@ -80,6 +80,8 @@ On an unweighted grid, BFS returns the shortest path for free — no heuristic,
needed at office scale. It's a dozen lines and it's correct, which is the right trade for a map this
size.
+{% img "note-1" %}
+
## Avatars: one sheet, many people
Drawing fifteen unique characters by hand would be a slog. Instead, avatars start from a shared
@@ -125,6 +127,8 @@ moved — you see *who asked whom, and what kind of ask it was*, at a glance.
That envelope is pure presentation riding on real data: it only flies because the
[message router](/blog/atomic-file-mailboxes-for-agents/) actually delivered something.
+{% img "note-2" %}
+
## Keeping it lightweight
The whole point is that this is *game tech in a dev tool*, not a game. So the implementation stays
diff --git a/blog/src/posts/building-reliable-ai-agents.md b/blog/src/posts/building-reliable-ai-agents.md
index e851ad1b..1cd4c8a3 100644
--- a/blog/src/posts/building-reliable-ai-agents.md
+++ b/blog/src/posts/building-reliable-ai-agents.md
@@ -68,6 +68,8 @@ For transient errors, retry — but **with a budget**. Three rules keep retries
An unbounded retry is the single most common way a "resilient" agent turns into a money fire. The retry
*budget* is what makes retrying a feature instead of a hazard.
+{% img "note-1" %}
+
## Catch bad output before it spreads
The sneakiest failure is the one that looks like success. A model returns confident nonsense, or JSON
@@ -113,6 +115,8 @@ system-wide reset.
Contain the blast radius and a single failure stays a single failure, instead of becoming an outage.
+{% img "note-2" %}
+
## A reliability checklist
When an agent run dies and takes its progress with it, it usually skipped one of these:
diff --git a/blog/src/posts/can-claude-code-agents-talk-to-each-other.md b/blog/src/posts/can-claude-code-agents-talk-to-each-other.md
index aa84c857..8e60c767 100644
--- a/blog/src/posts/can-claude-code-agents-talk-to-each-other.md
+++ b/blog/src/posts/can-claude-code-agents-talk-to-each-other.md
@@ -73,6 +73,8 @@ The one rule that keeps it clean: **never write into another agent's folder.** Y
your own outbox; the router does the routing. Single-writer-per-file is what makes the whole thing
safe under concurrency.
+{% img "note-1" %}
+
## What's actually in a message
A message isn't just free text — it carries a little structure so the receiving agent knows what's
@@ -106,6 +108,8 @@ message. That's how an agent reaches a human for the genuinely critical calls wi
watch a terminal, the same loop we describe in
[keeping a human in the loop](/blog/human-in-the-loop-ai-agents/).
+{% img "note-2" %}
+
## Memory is a slower kind of talking
There's one more channel that's easy to miss: **shared memory.** Messages are how agents coordinate in
diff --git a/blog/src/posts/claude-code-automation-while-you-sleep.md b/blog/src/posts/claude-code-automation-while-you-sleep.md
index 15a9d444..12ce8bb2 100644
--- a/blog/src/posts/claude-code-automation-while-you-sleep.md
+++ b/blog/src/posts/claude-code-automation-while-you-sleep.md
@@ -60,6 +60,8 @@ The important word is **deliberately.** Bypassing approvals is a real grant of a
it with the boundaries below. Turn it off when you want to confirm each action; turn it on when you've
scoped the work and you trust the guardrails.
+{% img "note-1" %}
+
## Ingredient 2 — The autonomous loop
The second ingredient is the loop that keeps an agent moving from one task to the next without you
@@ -123,6 +125,8 @@ Run a 30-minute unattended session before you run an 8-hour one. Watch what the
autonomy you've granted, tighten the escalation policy where they overstepped, and only then extend the
duration. Trust is earned by observation, not assumed.
+{% img "note-2" %}
+
## A realistic overnight setup
Putting it together, a sane overnight automation looks like this:
diff --git a/blog/src/posts/claude-code-git-worktrees-vs-hive.md b/blog/src/posts/claude-code-git-worktrees-vs-hive.md
index 250a44a2..d542879d 100644
--- a/blog/src/posts/claude-code-git-worktrees-vs-hive.md
+++ b/blog/src/posts/claude-code-git-worktrees-vs-hive.md
@@ -77,6 +77,8 @@ aren't fully independent, the gaps show:
In other words, worktrees make parallel agents *safe to run*, not *able to cooperate*. That's a real
and useful guarantee — it's just not the same as a team.
+{% img "note-1" %}
+
## What a hive gives you
A **hive** is the coordination layer worktrees lack. It wraps several long-lived agents and adds:
@@ -113,6 +115,8 @@ The layers don't conflict; they stack. Worktrees are a git feature for workspace
coordination feature for teamwork. Asking which to use is like asking whether to use seatbelts or a
steering wheel.
+{% img "note-2" %}
+
## A decision guide
Pick based on how *interdependent* your parallel work is:
diff --git a/blog/src/posts/claude-code-hooks-explained.md b/blog/src/posts/claude-code-hooks-explained.md
index 87f50c9e..75fc67df 100644
--- a/blog/src/posts/claude-code-hooks-explained.md
+++ b/blog/src/posts/claude-code-hooks-explained.md
@@ -56,6 +56,8 @@ You configure hooks in settings, mapping each event to one or more commands:
The `matcher` (for tool events) lets you scope a hook to specific tools — `*` means "every tool." Tool
events carry that matcher; lifecycle events like `Stop` don't need one.
+{% img "note-1" %}
+
## The lifecycle events that matter
There are several hook events; these are the ones you'll reach for most.
@@ -156,6 +158,8 @@ nothing left — the foundation of [letting agents build while you sleep](/blog/
It's also how the [GOD orchestrator](/blog/how-the-god-orchestrator-works/) keeps the whole floor
moving: route a task into an agent's inbox, and its next Stop hook picks it up automatically.
+{% img "note-2" %}
+
## Writing your own hooks: practical tips
If you're building with hooks directly, a few lessons that save pain:
diff --git a/blog/src/posts/claude-code-multi-agent-setup-tutorial.md b/blog/src/posts/claude-code-multi-agent-setup-tutorial.md
index 30d7b05e..25de9f01 100644
--- a/blog/src/posts/claude-code-multi-agent-setup-tutorial.md
+++ b/blog/src/posts/claude-code-multi-agent-setup-tutorial.md
@@ -60,6 +60,8 @@ Onboarding also sets a **harness home** — a folder where the harness keeps its
git repo, each agent's memory, and the shared semantic memory palace. You never edit it by hand; it's
just where coordination lives.
+{% img "note-1" %}
+
## Step 2 — Meet the GOD orchestrator (1 minute)
When the hive comes up, one agent is already there: the **GOD orchestrator**, seated in the corner
@@ -109,6 +111,8 @@ Here's what happens, and what you'll see on the floor:
You've gone from a blank app to a coordinated team acting on one sentence. That's the setup.
+{% img "note-2" %}
+
## What you just avoided
Doing this by hand means you become the message bus: copy-pasting findings between windows, manually
diff --git a/blog/src/posts/claude-code-orchestration-guide.md b/blog/src/posts/claude-code-orchestration-guide.md
index d82d73ec..6b26400c 100644
--- a/blog/src/posts/claude-code-orchestration-guide.md
+++ b/blog/src/posts/claude-code-orchestration-guide.md
@@ -66,6 +66,8 @@ codebase, you tune *how* it routes and *what* it considers critical by editing i
by redeploying. That's the practical heart of
[how the GOD orchestrator works](/blog/how-the-god-orchestrator-works/).
+{% img "note-1" %}
+
## How a request flows through the orchestrator
Here's the path a single instruction takes, end to end:
@@ -123,6 +125,8 @@ ones that thrash:
when the team goes sideways you can replay what happened. For the broader patterns here, see
[the best way to coordinate AI coding agents](/blog/coordinating-ai-coding-agents/).
+{% img "note-2" %}
+
## When you actually need an orchestrator
You don't need orchestration for one agent, or even for two or three independent tasks you're happy to
diff --git a/blog/src/posts/claude-code-orchestration-tools-compared.md b/blog/src/posts/claude-code-orchestration-tools-compared.md
index 622de204..c0e98f1d 100644
--- a/blog/src/posts/claude-code-orchestration-tools-compared.md
+++ b/blog/src/posts/claude-code-orchestration-tools-compared.md
@@ -38,6 +38,8 @@ agents](/#how), and how the main tools stack up against each.
A sixth practical factor — **footprint** — decides whether a tool is overkill for your workload.
We'll fold it into the verdict.
+{% img "note-1" %}
+
## The comparison
Scored as ●●● strong · ●●○ partial · ●○○ minimal, to the best of our knowledge at the time of writing.
@@ -56,6 +58,8 @@ Read the table as a fit, not a scoreboard. The tools clustered on the left optim
simplicity**; Munder Difflin optimizes for **coordination** (memory + messaging + a routing
orchestrator). Both are legitimate.
+{% img "note-2" %}
+
## How to read each criterion
### Shared memory is the real divider
diff --git a/blog/src/posts/claude-code-subagents-vs-multi-agent-harness.md b/blog/src/posts/claude-code-subagents-vs-multi-agent-harness.md
index 541b4084..fdaceca9 100644
--- a/blog/src/posts/claude-code-subagents-vs-multi-agent-harness.md
+++ b/blog/src/posts/claude-code-subagents-vs-multi-agent-harness.md
@@ -63,6 +63,8 @@ The limits all stem from one fact: a subagent is **scoped to its parent's run**.
None of this is a flaw — it's the scope. Subagents are an *intra-agent* concurrency primitive. They
were never meant to be a standing team.
+{% img "note-1" %}
+
## What a harness adds
A [multi-agent harness](https://munderdiffl.in/#what) wraps agents you already run — full Claude Code
@@ -95,6 +97,8 @@ Put simply: subagents give one agent *helpers*; a harness gives you a *team*.
The table isn't a scoreboard — it's a map. Each column wins its own territory.
+{% img "note-2" %}
+
## They're better together
The framing that trips people up is "subagents *or* a harness." In practice it's both:
diff --git a/blog/src/posts/claude-squad-alternative.md b/blog/src/posts/claude-squad-alternative.md
index eea4cbb5..c6687ec7 100644
--- a/blog/src/posts/claude-squad-alternative.md
+++ b/blog/src/posts/claude-squad-alternative.md
@@ -39,6 +39,8 @@ you launch agents, switch between them, background long-running ones, and review
If your need is "run a few independent Claude Code tasks in parallel from the terminal," Claude Squad
may be all you ever want. Switching costs you simplicity — so switch only for a real reason.
+{% img "note-1" %}
+
## Where a session manager stops
A session manager parallelizes agents; it doesn't *coordinate* them. Three things stay your job:
@@ -59,6 +61,8 @@ becomes the bottleneck — and there's no orchestrator to take it off your plate
None of these are bugs — they're simply outside a session manager's scope. They're also exactly the
things people go looking for an alternative to solve.
+{% img "note-2" %}
+
## What a coordinated hive adds
The alternative isn't "a fancier terminal." It's a different *shape*: a [multi-agent harness](/#what)
diff --git a/blog/src/posts/claude-squad-vs-munder-difflin.md b/blog/src/posts/claude-squad-vs-munder-difflin.md
index 8685cb1b..0f375535 100644
--- a/blog/src/posts/claude-squad-vs-munder-difflin.md
+++ b/blog/src/posts/claude-squad-vs-munder-difflin.md
@@ -36,6 +36,8 @@ head-to-head: where each is genuinely better, and how to decide.
Everything below is detail on that distinction.
+{% img "note-1" %}
+
## Feature comparison
| | Claude Squad | Munder Difflin |
@@ -66,6 +68,8 @@ Munder Difflin optimizes for *coordination*.
If that's you, Claude Squad is the right tool and the visual floor would just be overhead. Be honest
about your workload before you reach for more.
+{% img "note-2" %}
+
## Where Munder Difflin is the better pick
- **Your agents need to share what they learn.** [Long-term
diff --git a/blog/src/posts/cline-vs-munder-difflin.md b/blog/src/posts/cline-vs-munder-difflin.md
index 18762902..1af7b8db 100644
--- a/blog/src/posts/cline-vs-munder-difflin.md
+++ b/blog/src/posts/cline-vs-munder-difflin.md
@@ -66,6 +66,8 @@ It's worth being clear about what they share, because it's real:
So if your priority is "keep it on my machine, on my models," both qualify. The decision is about
*scope*.
+{% img "note-1" %}
+
## Where Cline wins
- **In-editor ergonomics.** If you live in VS Code and want an agent right there — reading the file you
@@ -91,6 +93,8 @@ would be overkill.
If your problem is "I want a coordinated team of agents working a goal," that's Munder Difflin's lane,
not an editor extension's.
+{% img "note-2" %}
+
## How to choose
| If you want… | Pick |
diff --git a/blog/src/posts/command-center-guide.md b/blog/src/posts/command-center-guide.md
index e8e626f9..9ec6d129 100644
--- a/blog/src/posts/command-center-guide.md
+++ b/blog/src/posts/command-center-guide.md
@@ -57,6 +57,8 @@ The load-bearing word is *dependency-aware*. Real work has ordering: the refacto
Work gets onto the board a few ways: you create tasks yourself, Michael creates and assigns them as he routes requests, and you can **pull open GitHub issues from any registered repo** (via the `gh` CLI) and assign them to agents with one click. Issue in, task tracked, agent dispatched — and when the work ships, the **CI status watcher** in the Activity tab shows live pass/fail/in-progress for the repo's GitHub Actions runs. The loop closes in the same window it opened in.
+{% img "note-1" %}
+
## Fleet status: the roster at a glance
The Floor tab is where the fleet stops being a set of individual terminals and becomes a roster. Each agent card shows what that agent is up to, and the card's progress bar doubles as a **context-window gauge** — a glanceable read on how much of the model's context each agent has burned. An agent near the top of its gauge is an agent about to compact or slow down; you can see it coming instead of discovering it.
@@ -73,6 +75,8 @@ This is the part that makes a 24/7 fleet safe to leave running.
**Observability.** Also in Activity: a live **OpenTelemetry collector** with per-model cost attribution, a fleet grid, and a **per-agent tool-span waterfall** — the "what exactly is this agent doing, step by step, and what does each step cost" view. It's the same discipline we covered in [observability for agent fleets](/blog/observability-for-agent-fleets/), built into the harness instead of bolted on.
+{% img "note-2" %}
+
## Triggers: the board's fourth dimension
The kanban answers "what's in flight." The **Triggers tab** answers "what happens next without me" — every way the hive wakes up when you aren't typing. **Schedules** are the first and oldest of them: recurring missions carry a label, an interval, a target agent, and a body, and the tab shows last-fired and next-fired times, so drift is visible. A scheduler **heartbeat** re-engages the floor when it goes quiet. Together with the board, it turns the hive from something you drive into something you supervise — the full pattern is in [scheduling autonomous agent missions](/blog/scheduling-autonomous-agent-missions/).
diff --git a/blog/src/posts/compressing-agent-memory.md b/blog/src/posts/compressing-agent-memory.md
index 936af44f..9dd7c0bb 100644
--- a/blog/src/posts/compressing-agent-memory.md
+++ b/blog/src/posts/compressing-agent-memory.md
@@ -64,6 +64,8 @@ A few techniques, cheapest to deepest:
These differ in where they run, but they share one goal: fewer tokens, same meaning.
+{% img "note-1" %}
+
## The trap: lossy in ways you can't predict
Compression is not deterministically lossy — it can drop *exactly the wrong thing*. A revenue definition
@@ -96,6 +98,8 @@ compressed index is an accelerator built on top of it — never instead of it. T
trick: **compression buys speed; the preserved original buys correctness.** You get the small wake-up
digest without ever betting your only copy on a summary.
+{% img "note-2" %}
+
## When not to compress
Compression is a tradeoff, not a default. Skip it (or always keep the original alongside) when the working
diff --git a/blog/src/posts/conductor-claude-code-alternative.md b/blog/src/posts/conductor-claude-code-alternative.md
index 4ea91b54..3bd13c96 100644
--- a/blog/src/posts/conductor-claude-code-alternative.md
+++ b/blog/src/posts/conductor-claude-code-alternative.md
@@ -37,6 +37,8 @@ git worktree, with a refined GUI for launching tasks and reviewing the diffs the
If you're a Mac user whose workflow is "spin up N parallel attempts and review the diffs," Conductor
is a strong fit. The reasons to look elsewhere are specific.
+{% img "note-1" %}
+
## Where you'd want an alternative
### It's macOS-only
@@ -54,6 +56,8 @@ ferrying context between worktrees.
You can't read the internals, self-host changes, or extend it. For some teams that's fine; for others
— especially open-source-minded ones — it's a dealbreaker.
+{% img "note-2" %}
+
## What "orchestration" actually means
The word *conductor* implies coordination, so it's worth being precise about what full
diff --git a/blog/src/posts/context-engineering-for-ai-agents.md b/blog/src/posts/context-engineering-for-ai-agents.md
index e281ed01..152130bd 100644
--- a/blog/src/posts/context-engineering-for-ai-agents.md
+++ b/blog/src/posts/context-engineering-for-ai-agents.md
@@ -66,6 +66,8 @@ It helps to name the ways a window goes bad. The 2025 taxonomy that stuck:
Notice that three of the four get *worse* as you add tokens. That's the whole argument for treating
context as something to curate, not accumulate.
+{% img "note-1" %}
+
## Multi-agent makes it sharper
In a single-agent setup you can sometimes get away with a messy window. In a hive you can't. Every
@@ -138,6 +140,8 @@ stays on disk for anyone who needs to replay it; the *summary* is what travels.
agent compacting its own session or a team compacting into a standup, the move is the same: trade fidelity
you no longer need for window you do.
+{% img "note-2" %}
+
## A practical checklist
When an agent underperforms, resist the urge to rewrite its prompt first. Audit its window instead:
diff --git a/blog/src/posts/coordinating-ai-coding-agents.md b/blog/src/posts/coordinating-ai-coding-agents.md
index 2a2d67ec..9725124b 100644
--- a/blog/src/posts/coordinating-ai-coding-agents.md
+++ b/blog/src/posts/coordinating-ai-coding-agents.md
@@ -61,6 +61,8 @@ that every agent appends to (that file is just a multi-writer conflict by anothe
design — speech acts, hop caps to prevent ping-pong, idempotent delivery — is in
[atomic file mailboxes for agents](/blog/atomic-file-mailboxes-for-agents/).
+{% img "note-1" %}
+
## Rule 3 — One committer for git
Here's the rule people learn the hard way. Git is not safe to drive from many processes at once. The
@@ -85,6 +87,8 @@ Resolve the tension by separating reading from writing: everyone can **read** th
them. The plan stays coherent because it has one author, and it stays current because everyone can
suggest edits. Same single-writer principle, applied to the one genuinely co-owned artifact.
+{% img "note-2" %}
+
## Rule 5 — An orchestrator to route and break ties
The first four rules make collisions impossible. The fifth makes the team *productive*: someone has to
diff --git a/blog/src/posts/crewai-autogen-vs-a-local-agent-harness.md b/blog/src/posts/crewai-autogen-vs-a-local-agent-harness.md
index 3724fb50..0c8b8f5f 100644
--- a/blog/src/posts/crewai-autogen-vs-a-local-agent-harness.md
+++ b/blog/src/posts/crewai-autogen-vs-a-local-agent-harness.md
@@ -42,6 +42,8 @@ Those are different jobs, and the tools for them belong to different categories.
Notice what all three have in common. They're **libraries**. `pip install`, import, write Python. That's not a criticism — it's the point. A framework's job is to give a developer building blocks.
+{% img "note-1" %}
+
## What a framework doesn't give you
Here's the part the comparison charts skip: when you pick a framework, **you've signed up to build the harness yourself.** The agent loop is maybe a fifth of a working multi-agent system. Around it you still need:
@@ -62,6 +64,8 @@ The pieces you'd have built around a framework are already there: [human approva
The honest flip side: you can't `import` Munder Difflin into your SaaS. It won't run your custom document pipeline inside your product. It's an app for a specific job — a team of agents working your repositories, visible on one screen — not a toolkit for arbitrary agent systems.
+{% img "note-2" %}
+
## The honest decision rule
**Choose a framework (CrewAI, Agent Framework, LangGraph) when:**
diff --git a/blog/src/posts/crystal-claude-code-alternative.md b/blog/src/posts/crystal-claude-code-alternative.md
index e214a3ac..4e10c79d 100644
--- a/blog/src/posts/crystal-claude-code-alternative.md
+++ b/blog/src/posts/crystal-claude-code-alternative.md
@@ -39,6 +39,8 @@ one window.
For "run a few variations in parallel and pick the best diff," Crystal is a good answer. The reason to
look further is usually one word: *memory*.
+{% img "note-1" %}
+
## Where parallel sessions hit a ceiling
Crystal, like other parallel-worktree apps, runs agents *beside* each other. What it doesn't add is a
@@ -57,6 +59,8 @@ There's no mailbox for one agent to hand a result to another. Coordination route
You launch and assign each session. Nothing decomposes a goal and routes the pieces across the team
for you.
+{% img "note-2" %}
+
## What memory changes, day to day
Adding a shared brain to a team of agents is a bigger shift than it sounds:
diff --git a/blog/src/posts/debugging-multi-agent-systems.md b/blog/src/posts/debugging-multi-agent-systems.md
index c9de677a..c9bdc1da 100644
--- a/blog/src/posts/debugging-multi-agent-systems.md
+++ b/blog/src/posts/debugging-multi-agent-systems.md
@@ -67,6 +67,8 @@ Reading the trail answers the relational question: did A actually ask B what you
B get it? Half of "the hive stalled" bugs resolve right here — a message that was malformed, misrouted,
or never sent.
+{% img "note-1" %}
+
## Drop into the agent's terminal
Now — and only now — open the specific agent's terminal. Because every agent runs in a real
@@ -87,6 +89,8 @@ The hive's coordination state lives in a git repo that the main process commits
what the hive knew at any point — the roster, the pending messages, the board. When "what state was the
system in when it broke?" matters, the git log answers it precisely instead of from memory.
+{% img "note-2" %}
+
## Check the usual suspects
Some failure modes recur in multi-agent systems. When you're stuck, check these directly:
diff --git a/blog/src/posts/deploy-a-blog-writer-agent.md b/blog/src/posts/deploy-a-blog-writer-agent.md
index fb83b1ca..64a9db15 100644
--- a/blog/src/posts/deploy-a-blog-writer-agent.md
+++ b/blog/src/posts/deploy-a-blog-writer-agent.md
@@ -63,6 +63,8 @@ is how a one-person project publishes like a content team.
And crucially: it's *largely hands-off*. The expensive part of blogging isn't typing — it's the discipline
to keep shipping. An agent has no problem with discipline.
+{% img "note-1" %}
+
## The pipeline, end to end
The writer agent isn't a magic monolith. It's one role in a hive, and the post moves through the same
@@ -130,6 +132,8 @@ the next backlog item each time. One prompt to the orchestrator stood up [an hou
reviewer](/blog/one-prompt-automated-pr-review/) for us the same way — automation that just keeps running.
Point that same scheduling at content and the blog writes itself on a timer.
+{% img "note-2" %}
+
## The meta-point
A multi-agent hive isn't only for code. Once you have a writer that drafts, an orchestrator that integrates
diff --git a/blog/src/posts/deploy-automated-pr-reviewer-agent.md b/blog/src/posts/deploy-automated-pr-reviewer-agent.md
index d575de14..5711a21f 100644
--- a/blog/src/posts/deploy-automated-pr-reviewer-agent.md
+++ b/blog/src/posts/deploy-automated-pr-reviewer-agent.md
@@ -38,6 +38,8 @@ That framing matters because of what it unlocks:
- **It sees the whole backlog at once.** Reading the full set of open issues plus shared hive memory, it can notice that issues #41, #43, and #47 are three faces of the same bug — rather than reviewing each in a vacuum.
- **It escalates through the same inbox you use.** A serious finding becomes a message to you, routed like any other hive mail. No separate alerting system.
+{% img "note-1" %}
+
## Deploying it: the one-prompt version
You don't configure this. You brief it. Open Munder Difflin, select the GOD orchestrator, and describe the outcome the way you'd brief a coworker:
@@ -81,6 +83,8 @@ It's tempting to frame this as "it reviewed PRs fast." But the load-bearing part
That's the difference between an automated commenter and an automated *reviewer*.
+{% img "note-2" %}
+
## What to be honest about
Two limits worth stating plainly, because overselling this helps no one:
diff --git a/blog/src/posts/do-more-with-less-model-routing.md b/blog/src/posts/do-more-with-less-model-routing.md
index a80d0aec..c2ee4810 100644
--- a/blog/src/posts/do-more-with-less-model-routing.md
+++ b/blog/src/posts/do-more-with-less-model-routing.md
@@ -66,6 +66,8 @@ The third option typically cuts total spend by more than half while *keeping* qu
spend big where capability actually changes the outcome. "Do more with less" isn't a slogan here; it's
just what falls out of matching price to need.
+{% img "note-1" %}
+
## The orchestrator is the natural router
In a single-agent setup, routing is a manual choice you make per session. In a hive, you can do better,
@@ -103,6 +105,8 @@ a few cheap heuristics catch most of it:
Everything that trips none of these — the bulk of the day — stays lean.
+{% img "note-2" %}
+
## You can't route what you can't see
The honest caveat: routing decisions are only as good as your visibility into cost. If you don't know
diff --git a/blog/src/posts/does-the-june-2026-agent-sdk-change-affect-munder-difflin.md b/blog/src/posts/does-the-june-2026-agent-sdk-change-affect-munder-difflin.md
index 73379501..7409f92f 100644
--- a/blog/src/posts/does-the-june-2026-agent-sdk-change-affect-munder-difflin.md
+++ b/blog/src/posts/does-the-june-2026-agent-sdk-change-affect-munder-difflin.md
@@ -68,6 +68,8 @@ A useful test: if a tool **embeds the SDK** to run agents headlessly, it's affec
Claude Code CLI** the way you would by hand, it isn't. Munder Difflin is firmly the latter — it's a
[harness around Claude Code, not a wrapper around the SDK](/blog/claude-code-subagents-vs-multi-agent-harness/).
+{% img "note-1" %}
+
## Why this doesn't change how Munder Difflin runs
Munder Difflin is a [multi-agent harness](/#what) that orchestrates the **native Claude Code CLI**. Each
@@ -99,6 +101,8 @@ even with enrich turned on, you're covered; with it off, the change is invisible
That's the honest shape of it: **the agents are unaffected; the optional enrich assistant uses
`claude -p`, which the new credit covers.** No "100% unaffected" hand-waving.
+{% img "note-2" %}
+
## How to check for yourself
You don't have to take our word for it. In Munder Difflin, every agent is a tab you can watch — a live
diff --git a/blog/src/posts/evaluating-ai-agent-reliability.md b/blog/src/posts/evaluating-ai-agent-reliability.md
index 49a260aa..782753ac 100644
--- a/blog/src/posts/evaluating-ai-agent-reliability.md
+++ b/blog/src/posts/evaluating-ai-agent-reliability.md
@@ -60,6 +60,8 @@ a leaderboard score is a starting point, not a verdict — real-world reliabilit
The takeaway isn't "ignore benchmarks." It's: use them to *rank*, then re-measure on *your* work before
you trust anything.
+{% img "note-1" %}
+
## Measure the things that actually break
Final-answer accuracy hides the failure modes that matter for an autonomous agent. What predicts
@@ -98,6 +100,8 @@ A practical recipe, drawn from current
- **Human calibration on a sample.** Have a person review 1–2% of cases and check the judge agrees;
when they diverge, fix the rubric. Automated eval scales; human eval keeps it honest.
+{% img "note-2" %}
+
## Close the loop with observability
A reliability number is only as good as the data behind it, and a [multi-agent harness](/#what) is already
diff --git a/blog/src/posts/file-based-coordination-vs-message-queues.md b/blog/src/posts/file-based-coordination-vs-message-queues.md
index 126d9785..e73c3677 100644
--- a/blog/src/posts/file-based-coordination-vs-message-queues.md
+++ b/blog/src/posts/file-based-coordination-vs-message-queues.md
@@ -53,6 +53,8 @@ a router moves each outbox file to its recipient. Shared plans live in one markd
[board](/blog/how-the-god-orchestrator-works/). History is an [append-only log](/blog/append-only-event-log-agents/).
Nothing here is a database or a daemon — it's files on disk, and that's the point.
+{% img "note-1" %}
+
## Why files beat a broker for a hive
**You can read it.** A message is a file you can `cat`. The whole system state is a directory you can
@@ -89,6 +91,8 @@ Files are not magic. Choosing them means accepting real limits:
- **It doesn't cross machines.** Files coordinate processes on one host. The moment your agents live on
different boxes, you need something networked.
+{% img "note-2" %}
+
## When to actually reach for a queue
Use the decision, not the dogma. Files are right when your hive is **local, supervised, and dozens of
diff --git a/blog/src/posts/from-one-terminal-to-a-team.md b/blog/src/posts/from-one-terminal-to-a-team.md
index 6355cc2f..12ee02fa 100644
--- a/blog/src/posts/from-one-terminal-to-a-team.md
+++ b/blog/src/posts/from-one-terminal-to-a-team.md
@@ -32,6 +32,8 @@ parallelism in the room.
**The pain that pushes you forward:** you're waiting on the agent while three other things you could
parallelize sit idle.
+{% img "note-1" %}
+
## Stage 2: A few manual terminals
So you open more terminals — a [classic move](/blog/how-to-run-multiple-claude-code-agents/). One
@@ -63,6 +65,8 @@ team:
That's the leap from juggling [Claude Code agents](/blog/what-are-claude-code-agents/) to running a
[multi-agent harness](/#what). It's the stage where adding agents stops adding *overhead*.
+{% img "note-2" %}
+
## The before-and-after
The same morning, two ways:
diff --git a/blog/src/posts/generative-engine-optimization-techniques.md b/blog/src/posts/generative-engine-optimization-techniques.md
index 4f2e83aa..77a85a36 100644
--- a/blog/src/posts/generative-engine-optimization-techniques.md
+++ b/blog/src/posts/generative-engine-optimization-techniques.md
@@ -74,6 +74,8 @@ The through-line: generative engines reward content that is *quotable and eviden
statistic, a citation, and a clear claim is exactly the kind of thing an LLM can lift into an answer
with confidence — which is the whole game.
+{% img "note-1" %}
+
## What flopped: keyword stuffing
Here's the finding worth tattooing on the SEO reflex: **keyword stuffing didn't work.** In the GEO
@@ -100,6 +102,8 @@ Depth means naming the limits, and the GEO research has them — several practit
None of that invalidates the core lesson; it just means you treat the study as strong evidence for a
*direction* and confirm with your own testing. Which is the scientific posture anyway.
+{% img "note-2" %}
+
## How to apply it
For a blog, docs, or a product page you want cited:
diff --git a/blog/src/posts/github-copilot-cli-vs-claude-code-for-hive-work.md b/blog/src/posts/github-copilot-cli-vs-claude-code-for-hive-work.md
index f687d807..454436a0 100644
--- a/blog/src/posts/github-copilot-cli-vs-claude-code-for-hive-work.md
+++ b/blog/src/posts/github-copilot-cli-vs-claude-code-for-hive-work.md
@@ -42,6 +42,8 @@ A [multi-agent harness](/blog/what-is-a-multi-agent-harness/) wraps real CLI pro
Claude Code and Copilot CLI give very different answers — and neither answer is wrong. They're different shapes for different jobs.
+{% img "note-1" %}
+
## Claude Code: the hive-aware resident
Claude Code runs as a persistent interactive session in its pseudo-terminal, and it exposes native hooks — external commands fired at lifecycle points. Munder Difflin leans on those hard:
@@ -71,6 +73,8 @@ The honest limitation: with no resident process between turns, there's nothing t
To be fair to Copilot CLI: the tool itself is more extensible than the print-mode integration uses. GitHub ships its own hooks system (JSON files in `.github/hooks/` or `~/.copilot/hooks/`, with `sessionStart`/`sessionEnd` events), MCP server support, and custom instructions. A deeper bridge is conceivable; v0.3.3 ships the documented, honest version.
+{% img "note-2" %}
+
## Verdict: don't pick — mix
The comparison table writes itself once you frame it as lifecycle:
diff --git a/blog/src/posts/give-claude-code-long-term-memory.md b/blog/src/posts/give-claude-code-long-term-memory.md
index 207fc8d3..08e6c0c6 100644
--- a/blog/src/posts/give-claude-code-long-term-memory.md
+++ b/blog/src/posts/give-claude-code-long-term-memory.md
@@ -31,6 +31,8 @@ Nothing it learned persists unless you **write it somewhere the next session wil
whole trick: long-term memory is just durable storage plus a habit of reading it on startup. This is
the foundation of [agent long-term memory](https://munderdiffl.in/#how) in general.
+{% img "note-1" %}
+
## Step 1: Write durable facts to markdown
Give each agent a `memory.md` and a rule: when you learn something durable — a decision, a
@@ -70,6 +72,8 @@ One trap: if several agents write the same memory file at once, you get torn wri
its **own** memory file and let a shared index aggregate them read-only. Same principle that keeps
multi-agent git safe — one writer per file.
+{% img "note-2" %}
+
## Step 3: Make reading a startup ritual
Memory only helps if it's read. Bake it into the agent's startup: "before starting a task, recall
diff --git a/blog/src/posts/hire-manifest-untrusted-input.md b/blog/src/posts/hire-manifest-untrusted-input.md
index 2e8cd88f..e4573453 100644
--- a/blog/src/posts/hire-manifest-untrusted-input.md
+++ b/blog/src/posts/hire-manifest-untrusted-input.md
@@ -67,6 +67,8 @@ The second structural defense is an absence. **There is no `command` or `executa
So the worst a manifest can do on the "what runs" axis is *select among providers you already trust*. It picks `claude` or `codex`; it cannot introduce `curl` or `/bin/sh`. That shrinks the attack surface to the *arguments* passed to a binary you already chose to install — which is exactly where the interesting bug lived.
+{% img "note-1" %}
+
## The HIGH-severity bug: Windows command injection via `model`
The first review found it. `commandFlags` were validated tightly from day one — but `model` was only **length-capped**, never **shape-checked**. And `model` is not inert: it flows onto the spawn command line as `--model <model>`, quoted only if it contained whitespace.
@@ -120,6 +122,8 @@ A token must (a) match `FLAG_RE` — so no whitespace, no shell metacharacters,
The general principle is worth stating plainly: **for attacker-controlled input, an allowlist beats a denylist.** A denylist is a bet that you enumerated every *bad* value — and that bet loses every time the world adds a new bad value you didn't anticipate. An allowlist is a bet that you enumerated every *safe* value — and the safe set is small, well-understood, and changes slowly. When the input is hostile and the surface keeps growing, you want to be betting on the small stable set, not the unbounded one.
+{% img "note-2" %}
+
## SSRF-safe, bounded fetch
The deep link `munderdifflin://hire?src=<url>` hands the app a URL it will fetch from the **main** process — which has the network and the OS at its disposal. A naive fetch here is a classic server-side request forgery (SSRF) primitive: a remote page tells *your* app to make a request *you* didn't intend. The transport (`src/main/hire.ts`) is hardened on three axes, each of which started out wrong in the first cut.
diff --git a/blog/src/posts/how-agents-remember-semantic-memory.md b/blog/src/posts/how-agents-remember-semantic-memory.md
index 85ecce0b..ce248e29 100644
--- a/blog/src/posts/how-agents-remember-semantic-memory.md
+++ b/blog/src/posts/how-agents-remember-semantic-memory.md
@@ -85,6 +85,8 @@ would hang on it indefinitely. The fix in `memory.ts` is to **skip init entirely
`mempalace mine` lazily create the palace (downloading the local embedding model once, on first run).
One less moving part, and no hang.
+{% img "note-1" %}
+
## Recall: `search` and `wake-up`
With notes mined, an agent recalls in two ways — both plain CLI calls it runs itself:
@@ -121,6 +123,8 @@ The embedding model is configurable (`minilm` by default for snappy local recall
when you want a heavier multilingual model). Everything runs locally — the palace, the model, the
mining — so memory stays [local-first](/blog/why-local-first-matters-for-ai-agents/) and private.
+{% img "note-2" %}
+
## Why this matters for a hive (not just one agent)
A single agent with memory is useful. A *hive* with shared memory compounds:
diff --git a/blog/src/posts/how-ai-agents-verify-their-own-work.md b/blog/src/posts/how-ai-agents-verify-their-own-work.md
index 9fb54c71..64a1ebb4 100644
--- a/blog/src/posts/how-ai-agents-verify-their-own-work.md
+++ b/blog/src/posts/how-ai-agents-verify-their-own-work.md
@@ -72,6 +72,8 @@ npm run build # paste the result — green that reproduces is green
"It works on my branch" is worthless if your branch is a state no one else can reach.
+{% img "note-1" %}
+
## Verify the fix, not the intent
A subtler failure than skipping the check: running a check that doesn't prove the thing you fixed. You
@@ -103,6 +105,8 @@ naturally with [human-in-the-loop gates](/blog/human-in-the-loop-ai-agents/): th
re-verifies, and the human approves what's hard to reverse. Each layer assumes the one before it can be
wrong — which is why the chain holds.
+{% img "note-2" %}
+
## A self-verification checklist
Before an agent writes "done," it should answer yes to all of these:
diff --git a/blog/src/posts/how-ai-answer-engines-choose-sources.md b/blog/src/posts/how-ai-answer-engines-choose-sources.md
index 04ae916a..246ee21e 100644
--- a/blog/src/posts/how-ai-answer-engines-choose-sources.md
+++ b/blog/src/posts/how-ai-answer-engines-choose-sources.md
@@ -51,6 +51,8 @@ lifted a source's visibility in AI answers by [up to roughly 40%](https://aithin
with the biggest gains from **adding statistics, citing sources, and including quotations**. In other
words: specific, verifiable, quotable content is what gets pulled into answers.
+{% img "note-1" %}
+
## The engines don't agree — a per-engine tour
Here's the part most "AI SEO" advice glosses over: the major engines cite *strikingly different*
@@ -91,6 +93,8 @@ Translate the divergence into action:
None of this replaces good SEO — crawlable, fast, well-structured pages still matter. It layers a
second discipline on top, aimed at the quotable claim instead of the click.
+{% img "note-2" %}
+
## How to know if it's working
AEO has no clean "position 3" metric, so measure it directly: each month, ask ChatGPT, Claude, and
diff --git a/blog/src/posts/how-the-god-orchestrator-works.md b/blog/src/posts/how-the-god-orchestrator-works.md
index b982e6c2..061c3305 100644
--- a/blog/src/posts/how-the-god-orchestrator-works.md
+++ b/blog/src/posts/how-the-god-orchestrator-works.md
@@ -86,6 +86,8 @@ The harness fills in the id, sender, hop count, and timestamps. A good task spec
start without a follow-up question — which is the difference between routing that accelerates the team
and routing that just adds a hop.
+{% img "note-1" %}
+
## Job 3 — Adjudicate the routine traffic
This is the job that makes autonomy real. As agents work, they raise questions *for each other*: which
@@ -146,6 +148,8 @@ Putting the four jobs together, here's the life of one instruction:
6. Every step is committed to the hive's git repo and written to an append-only log, so the whole
episode is auditable and replayable.
+{% img "note-2" %}
+
## What makes it robust
A few properties keep the orchestrator from being a single point of failure:
diff --git a/blog/src/posts/how-to-add-a-github-copilot-cli-agent.md b/blog/src/posts/how-to-add-a-github-copilot-cli-agent.md
index 03f736ea..cbe3fbf2 100644
--- a/blog/src/posts/how-to-add-a-github-copilot-cli-agent.md
+++ b/blog/src/posts/how-to-add-a-github-copilot-cli-agent.md
@@ -48,6 +48,8 @@ Then log in once with your GitHub account if you haven't (`copilot` walks you th
You can also skip this step entirely. Munder Difflin has a self-healing installer for missing engine CLIs: if you pick Copilot in Add Agent and the `copilot` binary isn't on your `PATH`, the harness offers the official `npm install -g @github/copilot`, runs it in the terminal, then auto restarts-and-continues into the freshly installed binary. No dead end, no manual retry.
+{% img "note-1" %}
+
## Step 2: Add Agent, pick Copilot
Click **Add Agent** on the floor. The visual provider picker now lists GitHub Copilot CLI alongside the other six engines. Pick it, name your hire, choose a working directory — and if you flip the git-isolation toggle, the agent gets its own dedicated worktree so it never collides with other agents on branches (more on why that matters in [worktrees vs the hive](/blog/claude-code-git-worktrees-vs-hive/)).
@@ -82,6 +84,8 @@ The auto-approval flags — `-s --allow-all-tools --no-ask-user` — are **gated
Session continuity is handled with `--resume` (best-effort): print mode exits after every turn, but the next turn reattaches the prior session, so follow-ups don't start cold.
+{% img "note-2" %}
+
## The honest inbox caveat
This is the part worth reading twice. Print mode **exits per turn and exposes no hook bridge**, which means a Copilot worker can't do the thing hive-aware engines do: sit idle, notice mail in its inbox, and drain it. The engine is registered as non-hive-aware (`canReceiveInbox: false`) on purpose.
diff --git a/blog/src/posts/how-to-choose-a-multi-agent-tool.md b/blog/src/posts/how-to-choose-a-multi-agent-tool.md
index bfbb4464..6d8d5755 100644
--- a/blog/src/posts/how-to-choose-a-multi-agent-tool.md
+++ b/blog/src/posts/how-to-choose-a-multi-agent-tool.md
@@ -37,6 +37,8 @@ Before scoring anything, name your actual bottleneck. Most people are solving on
If you're in the first camp, optimize for simplicity. If you're in the second, the checklist below
will steer you toward heavier, more coordinated tools — and that's correct.
+{% img "note-1" %}
+
## The six criteria
### 1. Memory
@@ -96,6 +98,8 @@ manager wins handily — that's the point. The rubric encodes *your* priorities,
answer. For a ready-made criteria breakdown across the real tools, see [Claude Code orchestration
tools, compared](/blog/claude-code-orchestration-tools-compared/).
+{% img "note-2" %}
+
## Three traps to avoid
- **Buying for a workload you don't have.** A coordinated hive is overkill for two independent tasks;
diff --git a/blog/src/posts/how-to-hire-from-the-agent-gallery.md b/blog/src/posts/how-to-hire-from-the-agent-gallery.md
index cd98b198..8089b9e1 100644
--- a/blog/src/posts/how-to-hire-from-the-agent-gallery.md
+++ b/blog/src/posts/how-to-hire-from-the-agent-gallery.md
@@ -38,6 +38,8 @@ The gallery lives at [munderdiffl.in/hires](https://munderdiffl.in/hires/) — a
Every card tells you what you're getting before you click anything: the role's goal, its capability tags, and which provider it's written for. Don't overthink the choice — you're picking a starting point, not signing a contract. Everything on the card is editable after import.
+{% img "note-1" %}
+
## Step 2: Import the hire
Two ways in, both landing in the same place:
@@ -57,6 +59,8 @@ The imported banner is your cue to slow down for thirty seconds. A hire manifest
- **Model and flags** tell you what it costs to run and how it behaves. The allowlist keeps flags safe; it doesn't make them right for you.
- **Token budget** is the spend ceiling the author suggested. Set it to what *you* are comfortable with — the harness enforces per-agent budgets with live fleet monitoring and a circuit breaker behind it.
+{% img "note-2" %}
+
## Step 4: Customize the four things that matter
A gallery hire is deliberately generic. Four edits turn it into *your* hire:
diff --git a/blog/src/posts/how-to-install-and-use-munder-difflin.md b/blog/src/posts/how-to-install-and-use-munder-difflin.md
index 5af69886..8f928bd3 100644
--- a/blog/src/posts/how-to-install-and-use-munder-difflin.md
+++ b/blog/src/posts/how-to-install-and-use-munder-difflin.md
@@ -110,6 +110,8 @@ The first time you open Munder Difflin, a three-step wizard sets up your control
Finish the wizard and you land on the office floor. Michael — your orchestrator — boots into his
office automatically; give him a few seconds to clock in.
+{% img "note-1" %}
+
## Step 4: Meet Michael, your GOD orchestrator
Michael is the **GOD agent**: he runs the floor, triages requests, assigns work, and escalates only
@@ -191,6 +193,8 @@ the practical guardrails behind it are in [Claude Code automation while you
sleep](/blog/claude-code-automation-while-you-sleep/). Be honest with yourself about scope — bounded,
well-specified jobs go best.
+{% img "note-2" %}
+
## Step 8: Use Michael's Command Center
Select Michael on the floor and open his panel — it's not a plain terminal. It's a control surface
diff --git a/blog/src/posts/how-to-run-multiple-claude-code-agents.md b/blog/src/posts/how-to-run-multiple-claude-code-agents.md
index 0496de42..481d93fd 100644
--- a/blog/src/posts/how-to-run-multiple-claude-code-agents.md
+++ b/blog/src/posts/how-to-run-multiple-claude-code-agents.md
@@ -41,6 +41,8 @@ cd ~/project && claude
This works for two or three **independent** tasks. The moment they overlap, three problems appear.
+{% img "note-1" %}
+
## Where the manual approach breaks
### 1. They collide on files
@@ -80,6 +82,8 @@ Seeing the team work — who's busy, who's idle, what messages are flying — tu
something you can supervise. Visibility is what makes running many agents feel calm instead of
chaotic.
+{% img "note-2" %}
+
## From tabs to a team
The progression is always the same: one session → a few manual tabs → a coordinated team. Once you
diff --git a/blog/src/posts/how-to-talk-to-your-orchestrator.md b/blog/src/posts/how-to-talk-to-your-orchestrator.md
index 07adf74d..a6ae1ba4 100644
--- a/blog/src/posts/how-to-talk-to-your-orchestrator.md
+++ b/blog/src/posts/how-to-talk-to-your-orchestrator.md
@@ -54,6 +54,8 @@ State the outcome and the definition of done. Let the plan be his problem.
**4. The deliverable.** Name the artifact that proves completion: a PR against main, a green test suite, a markdown report, a rendered page. "Done" without an artifact is a vibe; agents ship vibes enthusiastically.
+{% img "note-1" %}
+
## Bad brief, good brief
**Bad:** "Fix the login bug."
@@ -72,6 +74,8 @@ That last sentence is the pro move: telling the orchestrator what to do with *ad
Don't specify which agent does what unless you have a real reason. Michael assigns work across the roster, and each hire can run a different engine — Claude Code, Codex, Antigravity, OpenCode, Crush, pi.dev, or GitHub Copilot CLI — so routing is part of the value. If you *do* care ("use the cheap local-model worker for the boilerplate"), say it as a constraint, not by micromanaging assignments.
+{% img "note-2" %}
+
## Mid-run: steering, status, approvals
A brief is not a launch-and-pray. Three controls matter while the floor runs:
diff --git a/blog/src/posts/how-to-use-the-built-in-monaco-ide.md b/blog/src/posts/how-to-use-the-built-in-monaco-ide.md
index bde79524..18a7ddf2 100644
--- a/blog/src/posts/how-to-use-the-built-in-monaco-ide.md
+++ b/blog/src/posts/how-to-use-the-built-in-monaco-ide.md
@@ -44,6 +44,8 @@ The left rail has two jobs, in priority order.
**The workspace file tree** sits alongside it. Click any file there and it opens as a normal, *editable* Monaco tab. So the rail gives you both motions: *review* (CHANGES → diff) and *fix* (tree → edit).
+{% img "note-1" %}
+
## Tabs, dirty dots, and Cmd/Ctrl+S
Open files stack up as **editor tabs** on the right, each with a **dirty-state dot** when it has unsaved edits, plus save and close. **Cmd/Ctrl+S** saves the active tab.
@@ -60,6 +62,8 @@ The IDE has to pick a repo to show, and it snapshots the workspace root from an
Practical consequence: **select the agent whose work you want to review, then click IDE.** That drops you straight into its directory — which matters on a floor where [each agent can run in its own isolated git worktree](/blog/claude-code-git-worktrees-vs-hive/), so "the repo" isn't one place.
+{% img "note-2" %}
+
## The security posture: the renderer never touches disk
Everything the IDE does — listing the tree, reading files, writing saves, computing diffs — is **brokered through main-process IPC**. The diff view rides a `git:diff` IPC channel plus the preload bridge; the renderer process holds no filesystem or git access of its own. That's the same architecture as the rest of the harness: the sandboxed renderer asks, the main process does, and the attack surface of "web content with disk access" simply doesn't exist here.
diff --git a/blog/src/posts/human-in-the-loop-ai-agents.md b/blog/src/posts/human-in-the-loop-ai-agents.md
index 14b50a1f..702890c8 100644
--- a/blog/src/posts/human-in-the-loop-ai-agents.md
+++ b/blog/src/posts/human-in-the-loop-ai-agents.md
@@ -58,6 +58,8 @@ interruptions? Tighten the list. Agents doing things that scare you? Loosen what
decide alone. In a hive, this policy lives in the [orchestrator's](/blog/how-the-god-orchestrator-works/)
instructions — so you adjust behavior by editing a prompt, not by shipping code.
+{% img "note-1" %}
+
## How escalation actually works
When an agent (or the orchestrator on its behalf) hits something critical, it doesn't act. It addresses
@@ -95,6 +97,8 @@ A couple of structural safeguards keep escalation from being gamed or from livel
These mean the queue catches the things that *should* reach you even when the agents don't explicitly
flag them.
+{% img "note-2" %}
+
## Why this beats "approve everything" and "approve nothing"
- **vs. approve everything:** you keep autonomy and your attention. The agents do the 95% that's
diff --git a/blog/src/posts/human-in-the-loop-approving-ai-agents.md b/blog/src/posts/human-in-the-loop-approving-ai-agents.md
index ca8fd1af..740ffa16 100644
--- a/blog/src/posts/human-in-the-loop-approving-ai-agents.md
+++ b/blog/src/posts/human-in-the-loop-approving-ai-agents.md
@@ -59,6 +59,8 @@ an approval re-routed the message back into the queue. The
"Moving to native HITL removes the panel and the bug." Deleting the abstraction deleted the class of bug
with it.
+{% img "note-1" %}
+
## The native approach: approve where the work happens
Here's the shift. Coding agents *already have* a human-in-the-loop mechanism — the **permission prompt**.
@@ -99,6 +101,8 @@ envelope on the office-floor visualization. As the code comments note, it's "Cos
behind it." The system even guards against a `god → "human"` message looping back to itself. One
recipient, one source of truth, no parallel inbox to babysit.
+{% img "note-2" %}
+
## Approve from anywhere
A nice property falls out of doing it this way: because approval rides on the native session prompt,
diff --git a/blog/src/posts/keep-agent-semantic-memory-clean.md b/blog/src/posts/keep-agent-semantic-memory-clean.md
index 527bdf9f..d7dec8a8 100644
--- a/blog/src/posts/keep-agent-semantic-memory-clean.md
+++ b/blog/src/posts/keep-agent-semantic-memory-clean.md
@@ -60,6 +60,8 @@ The "essential story" was almost entirely a hooks configuration file, repeated a
occasional real note wedged between the blobs. The most important context an agent could load was
being spent on JSON it would never need to recall.
+{% img "note-1" %}
+
## The cause: the index ate the whole directory
The miner does what most file-based indexers do — it walks the target directory and files every file it
@@ -102,6 +104,8 @@ it.** A `.gitignore` is a readable, version-controlled declaration of "these fil
knowledge." That's better than burying an exclude list inside the miner, where the next person has to go
read source code to find out why their config isn't showing up in recall.
+{% img "note-2" %}
+
## The fix, part two: prune what's already filed
Adding a `.gitignore` stops *future* noise. It does nothing about the thousands of config drawers
diff --git a/blog/src/posts/launching-munder-difflin-v0-2-0.md b/blog/src/posts/launching-munder-difflin-v0-2-0.md
index 43a3a51f..8315da3a 100644
--- a/blog/src/posts/launching-munder-difflin-v0-2-0.md
+++ b/blog/src/posts/launching-munder-difflin-v0-2-0.md
@@ -73,6 +73,8 @@ quantified picture of the whole fleet.
This is the layer we wrote about wanting in [observability for agent fleets](/blog/observability-for-agent-fleets/):
not a dashboard bolted on the side, but the live state of the team where you're already looking.
+{% img "note-1" %}
+
## ...and you can stay in control of it
Seeing is half of it. The other half is being able to *act* — gently or firmly — without killing everything.
@@ -110,6 +112,8 @@ Coordination is only as good as what the hive remembers across runs, so v0.2.0 m
no more re-adding agents one by one. (Thanks @Gulum — #16.)
- **Delete scheduled missions.** Scheduled missions now have a delete button. (Thanks @Gulum — #9.)
+{% img "note-2" %}
+
## Legibility and cross-platform fixes
A big chunk of v0.2.0 is the unglamorous, high-impact work of making the thing actually pleasant to read and
diff --git a/blog/src/posts/launching-munder-difflin-v0-2-4.md b/blog/src/posts/launching-munder-difflin-v0-2-4.md
index e1bb1ecf..a900761e 100644
--- a/blog/src/posts/launching-munder-difflin-v0-2-4.md
+++ b/blog/src/posts/launching-munder-difflin-v0-2-4.md
@@ -48,6 +48,8 @@ The best part? **you don't pay for any of it twice.** No API keys. Munder Diffli
Drop the CLIs you want on your `PATH`, add them as workers, done. Mix and match however you like. The hive layer underneath is the same no matter who's running.
+{% img "note-1" %}
+
## the real flex: automate basically anything in *one prompt*
Here's where it stops being a tech demo and starts being a thing you actually use.
@@ -99,6 +101,8 @@ This is the one people don't believe until they see it. When agents are mid-turn
The whole point of a floor is that you can *watch* it. Every agent is a real terminal under the hood — `claude`, `agy`, or `codex` — rendered as a little pixel coworker doing its thing. The cast is an affectionate *Office* parody (Michael runs the floor; the rest of the gang fills the desks), they take coffee breaks when idle, and you can see at a glance who's working, who's thinking, and who's stuck. It's genuinely fun to leave running on a second monitor. Identity theft is not a joke, Jim.
+{% img "note-2" %}
+
## also new in 0.2.4 (the quiet reliability glow-up)
The stuff that doesn't get a headline but makes the floor feel solid:
@@ -107,6 +111,13 @@ The stuff that doesn't get a headline but makes the floor feel solid:
- **God opens to its Terminal by default** — selecting the orchestrator mounts straight to its terminal instead of reopening a stale "ASK ME" tab. (ASK ME is still one click away.)
- **Tougher public ingress** — the Slack/webhook tunnel no longer crashes at load, and a permanently-failing Slack reply (like a bot token missing a scope) gets logged once instead of retrying forever and spamming your console.
+## credits
+
+A run of fixes in the 0.2.2 wave that this release builds on came from the community —
+[@Gulum](https://github.com/Gulum) landed eight of them, from the Windows usage meter that
+always read $0.00 to un-black-holing mail sent to the prep assistant. First sustained outside
+contributor the project ever had. Thank you.
+
## get v0.2.4
Munder Difflin is **free, open source, and local-first** on macOS, Windows, and Linux. No account. No cloud. Your machine, your subscriptions, your floor.
diff --git a/blog/src/posts/launching-munder-difflin-v0-2-8.md b/blog/src/posts/launching-munder-difflin-v0-2-8.md
index 9a96321d..5bf6078f 100644
--- a/blog/src/posts/launching-munder-difflin-v0-2-8.md
+++ b/blog/src/posts/launching-munder-difflin-v0-2-8.md
@@ -67,6 +67,8 @@ prefer files? there's an **import hire…** button right inside the Add-Agent mo
both paths converge. link or file, you land in the same review screen.
+{% img "note-1" %}
+
## the part that matters: import never spawns anything
read this twice, because it's the whole trust promise:
@@ -100,6 +102,8 @@ the loop is dead simple:
that's it. that's the whole onboarding. instead of "here's an empty floor, good luck," it's "here's Pam, want her to write your docs? yes? she's at her desk now."
+{% img "note-2" %}
+
## why this is secretly a growth thing
here's the bit we're genuinely excited about. the hardest moment in any tool like this is the **first five minutes**. an empty office asks too much of a newcomer.
diff --git a/blog/src/posts/launching-munder-difflin-v0-3-0.md b/blog/src/posts/launching-munder-difflin-v0-3-0.md
index 73429dd5..68294088 100644
--- a/blog/src/posts/launching-munder-difflin-v0-3-0.md
+++ b/blog/src/posts/launching-munder-difflin-v0-3-0.md
@@ -61,6 +61,8 @@ the bit that matters is how secrets are handled:
so the UI can let you configure an integration without the secret ever round-tripping through the part of the app that draws windows. and the connectivity-**test** path — the "is this hooked up right?" button — is **confined**, so it can't be bent into a secret-exfiltration or [SSRF](/blog/agent-security-and-sandboxing/) trick. write-only in, brokered access out.
+{% img "note-1" %}
+
## Slack → spawn → reply → safe teardown
the third headline is the one that feels like magic the first time: **Michael can spawn a worker straight from Slack.**
@@ -87,6 +89,8 @@ a release this big has a long tail of quality-of-life wins:
- 🧭 **feature-aware onboarding** — first-run setup adapts to what you actually have available, with an explicit permissions & reliability step.
- 🔧 **a visible engine-CLI installer** — if the engine binary for your chosen provider is missing, the installer runs *visibly* and self-heals instead of failing in silence.
+{% img "note-2" %}
+
## reliability: the floor survives a closed lid
if you run agents overnight, two fixes are for you:
diff --git a/blog/src/posts/launching-munder-difflin-v0-3-2.md b/blog/src/posts/launching-munder-difflin-v0-3-2.md
index fbe5ec3a..facddf71 100644
--- a/blog/src/posts/launching-munder-difflin-v0-3-2.md
+++ b/blog/src/posts/launching-munder-difflin-v0-3-2.md
@@ -65,6 +65,8 @@ and if you've already closed the session? the completion isn't lost. it **queues
fire-and-forget by default; tell-me-the-second-it's-done without you asking. that's the loop.
+{% img "note-1" %}
+
## it stays on a budget
a live voice session is a meter running. so v0.3.2 keeps it honest:
@@ -87,6 +89,8 @@ the renderer's content-security policy is opened *just* enough to let the WebRTC
the whole loop is **human-verified end-to-end** — connect, mic, answer, *and* the full spawn / kill / dispatch action path, exercised live on a real key.
+{% img "note-2" %}
+
## the smaller things that add up
a release with a headline this big still has a tail of quality-of-life wins:
diff --git a/blog/src/posts/launching-munder-difflin-v0-3-3.md b/blog/src/posts/launching-munder-difflin-v0-3-3.md
index d5257bb6..ef6f97f0 100644
--- a/blog/src/posts/launching-munder-difflin-v0-3-3.md
+++ b/blog/src/posts/launching-munder-difflin-v0-3-3.md
@@ -53,6 +53,8 @@ It's built on **Monaco**, the editor engine that powers VS Code, and it's the re
The workspace root snapshots from your selected agent (or the orchestrator), so the IDE opens
exactly where the work is happening.
+{% img "note-1" %}
+
## GitHub Copilot CLI joins the hive
The engine roster grows to **seven**: Claude Code, OpenAI Codex, Antigravity (Gemini), OpenCode,
@@ -88,6 +90,8 @@ outside the project, complete with a registry test and live verification against
That's exactly the kind of contribution the preset registry was designed for. Thank you, Anas. If
there's a CLI agent you want on the floor, [the door is open](https://github.com/chaitanyagiri/munder-difflin/blob/main/CONTRIBUTING.md).
+{% img "note-2" %}
+
## Get it
**[Download v0.3.3](https://github.com/chaitanyagiri/munder-difflin/releases/latest)** for macOS,
diff --git a/blog/src/posts/launching-munder-difflin-v0-3-5.md b/blog/src/posts/launching-munder-difflin-v0-3-5.md
index 1150dd03..b5b530ba 100644
--- a/blog/src/posts/launching-munder-difflin-v0-3-5.md
+++ b/blog/src/posts/launching-munder-difflin-v0-3-5.md
@@ -73,6 +73,8 @@ any `.md` path an agent prints in its terminal** to open a rendered preview inst
Safe by construction: no raw-HTML pipeline exists, links never navigate the app, and remote
images are blocked by CSP.
+{% img "note-1" %}
+
## A queue you can trust — and escape
The reliability heart of this wave is Vyapak's work: **one delivery gate for every
@@ -102,6 +104,8 @@ usage reads.
"Restart to update" — installation is always your click. v0.3.5 is the first release
delivered this way; if you're on 0.3.4, it's probably already waiting for you.
+{% img "note-2" %}
+
## Where this fits
If you've seen [YC's qm](https://github.com/yc-software/qm) — a multiplayer agent harness
diff --git a/blog/src/posts/launching-munder-difflin-v0-4-4.md b/blog/src/posts/launching-munder-difflin-v0-4-4.md
new file mode 100644
index 00000000..308658ec
--- /dev/null
+++ b/blog/src/posts/launching-munder-difflin-v0-4-4.md
@@ -0,0 +1,116 @@
+---
+title: "Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk"
+description: "v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes."
+date: 2026-08-19
+category: story
+categoryLabel: Story
+type: Non-technical
+primaryKeyword: "munder difflin v0.4.4"
+secondaryKeywords: ["munder difflin release", "claude code multi-agent windows", "windows ai agents", "skills catalog claude code", "electron dark mode contrast"]
+tags: ["Story", "Release", "Windows", "Skills", "Open Source"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "What's the headline fix in Munder Difflin v0.4.4?"
+ a: "Agent-to-agent messaging now works on Windows. A cmd.exe quirk was silently cutting the hive protocol out of every agent's startup prompt, so Windows agents booted, looked healthy, and had no idea they could message anyone. v0.4.4 launches the real interpreter directly with a proper argument array, so the full protocol arrives intact."
+ - q: "What's new besides the fixes?"
+ a: "A browsable catalog of 227 skills you can install across Claude Code, OpenCode and Codex; a Prerequisites page in Settings that shows live status for git, Node, uv, MemPalace and every engine; release notes that can carry their own designed page; an update toast that says what actually changed; and a rebuilt dark mode with readable contrast everywhere."
+ - q: "Do I need to do anything to upgrade?"
+ a: "No. The app updates itself from GitHub releases — you'll get a toast that now tells you what's in the update, and installation happens only when you click Restart. Fresh installs additionally benefit from first-run fixes: hive services now start on a brand-new install, and onboarding validates your home folder at step one."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p><strong>v0.4.4 is the release where
+Windows stops being a second-class citizen.</strong> Agent-to-agent messaging worked everywhere
+except the platform with roughly half our downloads — a cmd.exe quirk ate the hive protocol
+mid-prompt, silently. That's fixed, along with a first run that never started its own services,
+a setup wizard you couldn't finish, and a dark mode you couldn't read. Plus: a 227-skill catalog,
+a Prerequisites page, and release notes with their own designed pages.</p></div>
+
+Some releases are about new toys. This one is about a hard truth we learned during
+[launch week](/blog/what-reddit-told-us-about-munder-difflin/): a lot of the people who bounced
+off Munder Difflin weren't rejecting the idea — they were hitting bugs we couldn't see from a
+Mac.
+
+## The Windows bug that looked like nothing
+
+Here's the failure that headlines this release. When Munder Difflin spawns an agent, it hands it
+the hive protocol — a multi-line prompt that tells the agent where its `inbox/` and `outbox/`
+live, how to message other agents, where its memory is. On Windows, any engine installed as an
+npm `.cmd` shim can't go straight to `CreateProcess`, so it ran via `cmd.exe /c "…"`. And cmd.exe
+cuts an argument at its first newline.
+
+{% img "note-1", "cmd.exe kept the first line of the hive protocol and quietly dropped the rest — inbox, outbox, memory, everything." %}
+
+So Windows agents received exactly one line of their job description. They booted, rendered,
+answered prompts, looked completely healthy — and had no idea they could talk to anyone. No
+error, anywhere, because nothing *failed*. The floor just never came alive.
+
+v0.4.4 decodes the npm shim and launches its real interpreter with a proper argv array — no
+cmd.exe in the middle, no truncation. A second pass handles OpenCode's compiled-binary shims,
+which the first fix didn't model. The full autopsy is in
+[its own post](/blog/the-newline-that-silenced-windows-agents/), because bugs this quiet deserve
+a paper trail.
+
+## First runs that actually run
+
+Three more launch-week wounds, closed:
+
+- **A fresh install never started its hive services.** The message router, hook server, and
+ mission scheduler all waited for a home folder that a first run doesn't have yet — and nothing
+ re-kicked them once onboarding set one. New installs now bootstrap the moment the home exists.
+- **The setup wizard could not be finished** if it suggested `~/HarnessAgents` — the `~` was
+ taken literally and `mkdir` died. Onboarding now validates the folder at step one instead of
+ failing after step four.
+- **Dark mode was unreadable in a specific, measurable way.** The structural border token
+ measured under 2.1:1 contrast against every surface — 187 uses, 93 of them as 1px borders —
+ so the whole UI read as flat grey. It's rebuilt at 3.4–4.0:1 on a warmer ground.
+
+Did it matter? As of August 19, the share of fresh installs that go on to actually run an
+agent has moved from **50.2% to 57.5%** since these fixes shipped. That's dozens of people a
+week who used to hit a wall and now hit an office floor.
+
+## The new toys (there are some)
+
+{% img "note-2", "227 skills, searchable and installable across Claude Code, OpenCode and Codex — with scope precedence handled for you." %}
+
+**Skills.** A browsable catalog of 227 skills with search, category and publisher filters, and
+one-click install across Claude Code, OpenCode and Codex — with scope precedence handled, and
+uninstall guarded so it refuses anything that isn't a real `SKILL.md` folder inside a managed
+root. If you've read [our take on MCP and skills in a hive](/blog/mcp-and-skills-in-a-hive/),
+this is that opinion, shipped.
+
+**Prerequisites.** A Settings page that answers "why won't this engine start?" before you ask:
+live status for uv, git, Node, MemPalace and every agent engine, real paths, platform-correct
+install commands — and a button that asks Michael to fill the gaps for you.
+
+**Release drops.** A release can now carry its own authored HTML page, rendered in a fully
+sandboxed iframe. Release notes shouldn't have to be bullet points forever.
+
+And smaller things you'll notice: the update toast now says what's actually in the update, the
+IDE previews images, fullscreen roster cards show model, project and a context gauge, and Grok
+4.6 joined the model picker.
+
+## Credits where they're due
+
+This is the first release where community fixes are a *run*, not a cameo — and that deserves
+names, not a footnote. **[@gts-47](https://github.com/gts-47) landed eight pull requests** in
+this release (#129–#134, #143, #144): among them, terminal copy no longer drags the CLI's quote
+rail along, agent terminals run in UTF-8, task-ledger writes are atomic, and one odd message id
+no longer silences an agent's wake nudge. **[@baziyer](https://github.com/baziyer)** fixed the
+office floor rendering when nobody's looking at it (#142) — the politest possible performance
+win.
+
+{% img "note-3", "Nine community PRs in one release. Contributors now get the 'employee of the month' role in Discord when their PR lands." %}
+
+Contributors now also get something small and silly for it: merge a PR and a workflow hands you
+the **employee of the month** role in [our new Discord](/blog/we-opened-a-discord/). It felt
+thematically required.
+
+## Get it
+
+If you're already on 0.3.5 or later, do nothing — the app will offer the update itself, and the
+toast will tell you exactly what's inside. Fresh install:
+[munderdiffl.in](https://munderdiffl.in). And if Windows burned you during launch week, this is
+the release that's owed to you — [the full changelog](https://github.com/chaitanyagiri/munder-difflin/blob/main/CHANGELOG.md)
+has every receipt.
diff --git a/blog/src/posts/local-first-ai-agent-orchestration.md b/blog/src/posts/local-first-ai-agent-orchestration.md
index 18965025..94af0bb4 100644
--- a/blog/src/posts/local-first-ai-agent-orchestration.md
+++ b/blog/src/posts/local-first-ai-agent-orchestration.md
@@ -74,6 +74,8 @@ agents](/blog/atomic-file-mailboxes-for-agents/):
It's the backbone of [how a hive coordinates its agents](/blog/coordinating-ai-coding-agents/), and it
never leaves your disk.
+{% img "note-1" %}
+
## Scheduling on your own clock
Recurring work doesn't need a cloud cron either. The scheduler arms ordinary in-process timers — a
@@ -99,6 +101,8 @@ Coordination also needs memory, and here too everything is local:
Nothing in that list is a network call. The team's shared brain is a folder you own.
+{% img "note-2" %}
+
## The loop is local, too
What keeps an agent *going* without you clicking "continue"? A local hook. When an agent finishes a
diff --git a/blog/src/posts/local-first-vs-cloud-agent-sdks.md b/blog/src/posts/local-first-vs-cloud-agent-sdks.md
index 7738419d..0587fada 100644
--- a/blog/src/posts/local-first-vs-cloud-agent-sdks.md
+++ b/blog/src/posts/local-first-vs-cloud-agent-sdks.md
@@ -64,6 +64,8 @@ can speak MCP to your tools just like a cloud SDK does — [bringing your MCP se
hive](/blog/mcp-and-skills-in-a-hive/) is a feature, not a contradiction. Interop is about protocols,
not about where the agents run.
+{% img "note-1" %}
+
## They're not opposites — pick the axis that matters
It's tempting to frame this as local *versus* cloud, but most of the headline features (MCP, A2A,
@@ -103,6 +105,8 @@ And where the local model is the better fit:
For one person or a handful of developers shipping against their own code, the control and cost story
usually outweighs managed convenience.
+{% img "note-2" %}
+
## The cost axis is shifting — in local-first's favor
Cost deserves its own note, because 2026 changed the math. GitHub Copilot
diff --git a/blog/src/posts/long-running-agents-the-2026-shift.md b/blog/src/posts/long-running-agents-the-2026-shift.md
index 9f888e37..6039fe3f 100644
--- a/blog/src/posts/long-running-agents-the-2026-shift.md
+++ b/blog/src/posts/long-running-agents-the-2026-shift.md
@@ -64,6 +64,8 @@ grind out the unglamorous refactor nobody scheduled. The unit of delegation chan
promise people mean when they say agents are starting to feel less like autocomplete and more like
teammates.
+{% img "note-1" %}
+
## Why "longer" is a different problem
Here's the catch, and it's the part the headline numbers skip: **a longer agent fails in new ways.**
@@ -108,6 +110,8 @@ agent runs for hours:
None of these are new ideas. What's new is that the shift to long-running agents turned them from
optional polish into the price of admission.
+{% img "note-2" %}
+
## One long agent, or a coordinated team?
There's a tempting picture of a single heroic agent grinding autonomously for ten hours. Often the better
diff --git a/blog/src/posts/loop-engineering-for-ai-agents.md b/blog/src/posts/loop-engineering-for-ai-agents.md
index 229469f0..b50ba9ff 100644
--- a/blog/src/posts/loop-engineering-for-ai-agents.md
+++ b/blog/src/posts/loop-engineering-for-ai-agents.md
@@ -46,6 +46,8 @@ Borrow the checklist from ordinary programming. A `while` loop terminates when t
A runaway loop is just a loop missing one of these — usually the first. The agent is *doing things*, tokens are flowing, avatars are walking around, and nothing external is changing. Motion without progress.
+{% img "note-1" %}
+
## The outer-loop toolbox
Here's the toolbox as it actually exists in [Munder Difflin](/), where the design constraint is blunt: a floor of CLI agents has to run for days without a human babysitting it, and without melting.
@@ -66,6 +68,8 @@ Here's the toolbox as it actually exists in [Munder Difflin](/), where the desig
**Human gates as loop exits.** The final exit isn't a dead process; it's a person. Spend, scope changes, and destructive operations escalate into an approvals queue rather than resolving inside the loop — the human is a designed exit condition, not an interrupt handler. That's the heart of [human-in-the-loop agent design](/blog/human-in-the-loop-approving-ai-agents/).
+{% img "note-2" %}
+
## The bottom line
The model gives you the inner loop; the outer loop is the product. Verified stop conditions, drain loops with anti-recursion guards, backoff, scheduled compaction, a breaker ladder, progress tripwires, budget bounds, and human exits — stacked together, they're why a floor of agents can run for days and converge on finished work instead of a bill.
diff --git a/blog/src/posts/manage-multiple-claude-code-sessions.md b/blog/src/posts/manage-multiple-claude-code-sessions.md
index ad2fb4d2..7ce95497 100644
--- a/blog/src/posts/manage-multiple-claude-code-sessions.md
+++ b/blog/src/posts/manage-multiple-claude-code-sessions.md
@@ -52,6 +52,8 @@ is for at a glance, and it constrains the session so it doesn't wander into anot
Scope follows naming. A session called `reviewer` reviews; it doesn't start refactoring. The tighter
the scope, the less the sessions overlap, which directly defuses failure mode #2.
+{% img "note-1" %}
+
## Habit 2 — Isolate context on purpose
Each `claude` session has its own context window, and that's a feature: it keeps one task's noise out
@@ -81,6 +83,8 @@ Plain markdown is enough to start. Once the notes pile up, you add a semantic in
recall the few relevant notes by meaning instead of re-reading everything — the full version of this
is [long-term memory for Claude Code](/blog/give-claude-code-long-term-memory/).
+{% img "note-2" %}
+
## Habit 4 — Give shared work a single coordination rule
Failure mode #2 — collisions — is the one pure discipline can't fully solve, because two well-behaved
diff --git a/blog/src/posts/markdown-first-agent-memory.md b/blog/src/posts/markdown-first-agent-memory.md
index 247453f6..8a110117 100644
--- a/blog/src/posts/markdown-first-agent-memory.md
+++ b/blog/src/posts/markdown-first-agent-memory.md
@@ -78,6 +78,8 @@ is an upgrade, not a dependency. Contrast a database that won't open: it takes t
markdown-first, the floor never falls out from under the agent; the worst case is slower recall, not
lost knowledge.
+{% img "note-1" %}
+
## Why not a vector database or a memory framework?
Vector DBs and dedicated memory frameworks are real tools with real uses. They're the wrong default
@@ -107,6 +109,8 @@ It's the same single-writer discipline that keeps
[multi-agent git safe](/blog/single-committer-git-pattern/) — applied to memory. Co-edited memory files
would tear; per-agent files plus a read-only shared index don't.
+{% img "note-2" %}
+
## When markdown-first is the right call
This approach shines when:
diff --git a/blog/src/posts/mcp-and-skills-in-a-hive.md b/blog/src/posts/mcp-and-skills-in-a-hive.md
index 4e58382f..e6529289 100644
--- a/blog/src/posts/mcp-and-skills-in-a-hive.md
+++ b/blog/src/posts/mcp-and-skills-in-a-hive.md
@@ -77,6 +77,8 @@ configuration rather than replacing it. Your repo isn't modified to make an agen
no stray settings diff to commit or gitignore. (The hook mechanics are covered in
[Claude Code hooks, explained](/blog/claude-code-hooks-explained/).)
+{% img "note-1" %}
+
## A note on the harness's own memory
Here's a deliberate design choice worth calling out: the hive's **semantic memory doesn't consume an
@@ -116,6 +118,8 @@ Because agents are real sessions, Claude Code's own configuration applies — pe
permission controls govern what a session in that directory can do. You're not learning a parallel,
harness-specific permission system; you're using the one you already know, per directory, per agent.
+{% img "note-2" %}
+
## A practical setup
Putting it together, a tooled-up hive might look like this:
diff --git a/blog/src/posts/mcp-security-tool-poisoning.md b/blog/src/posts/mcp-security-tool-poisoning.md
index 8d7d992a..4f0301d8 100644
--- a/blog/src/posts/mcp-security-tool-poisoning.md
+++ b/blog/src/posts/mcp-security-tool-poisoning.md
@@ -56,6 +56,8 @@ following instructions it was handed by something it was told to trust.
The mitigation starts with a mindset shift: **tool descriptions are untrusted model input, not
documentation.** Treat them the way you'd treat any string from the internet that reaches your prompt.
+{% img "note-1" %}
+
## The rug pull: poisoning on a delay
Approving a server once isn't enough, because descriptions can change. In a **rug pull**, a server is
@@ -87,6 +89,8 @@ ahead of clever injection chains. The flashy attack gets the write-ups; the cred
the damage. If you do one thing, make it **least privilege**: scope every tool's token so it can only
touch the data it explicitly needs.
+{% img "note-2" %}
+
## Defenses, layered
No single control is enough; MCP security is defense in depth.
diff --git a/blog/src/posts/multi-agent-orchestration-patterns.md b/blog/src/posts/multi-agent-orchestration-patterns.md
index c216a103..b2b71ceb 100644
--- a/blog/src/posts/multi-agent-orchestration-patterns.md
+++ b/blog/src/posts/multi-agent-orchestration-patterns.md
@@ -65,6 +65,8 @@ You can get most of the way with three rules:
3. **Start simple.** Most teams over-architect. Reach for more agents only when a single agent genuinely
can't hold the task.
+{% img "note-1" %}
+
## Patterns compose
Real systems rarely use one pattern in isolation — they nest. A supervisor's workers might each run a
@@ -94,6 +96,8 @@ The corollary: the value isn't "more agents," it's **the right topology plus the
its failure mode** — hop caps, idempotent handling, isolation. (We wrote up those mechanics in
[recovering from agent failures](/blog/recovering-from-agent-failures/).)
+{% img "note-2" %}
+
## The 2026 framework landscape
If you're building this on a framework, the control-vs-simplicity tension hasn't converged — they differ
diff --git a/blog/src/posts/munder-difflin-faq.md b/blog/src/posts/munder-difflin-faq.md
index 02f88cbf..f600c117 100644
--- a/blog/src/posts/munder-difflin-faq.md
+++ b/blog/src/posts/munder-difflin-faq.md
@@ -58,6 +58,8 @@ takes the agents you already run and makes them act like one team — they messa
long-term memory, and are routed by a coordinator you talk to in plain language, all visualized as a
live office floor on your own machine.
+{% img "note-1" %}
+
## Still deciding?
If you're comparing options, these go deeper than an FAQ can:
diff --git a/blog/src/posts/munder-difflin-v0-2-4-feature-walkthrough.md b/blog/src/posts/munder-difflin-v0-2-4-feature-walkthrough.md
index a2ab502e..7957767c 100644
--- a/blog/src/posts/munder-difflin-v0-2-4-feature-walkthrough.md
+++ b/blog/src/posts/munder-difflin-v0-2-4-feature-walkthrough.md
@@ -62,6 +62,8 @@ The practical result:
Codex is no longer the third provider with an asterisk. It's a full hive participant.
+{% img "note-1" %}
+
## Terminal work orders: the WORK ORDER FROM HIVE pattern
Both Antigravity and Codex now have full hook bridges. But the multi-provider work raised a broader question: what should happen when a future provider has *no* inbox-drain path at all — no hook bridge, no idle-wake nudge — and you still need to get hive mail to it?
@@ -92,6 +94,8 @@ The fix is straightforward: the heartbeat checks for unread actionable inbox ite
The GOD orchestrator now opens with the Terminal sidebar visible from the start. You've always been able to open it — now you don't have to remember to. For most workflows, seeing god's terminal output immediately is the right default.
+{% img "note-2" %}
+
## Slack + webhook: tunnelmole replaces localtunnel
The Slack and webhook ingress paths used `localtunnel` / `loca.lt` to expose the local server to the public internet. This allowed Slack's URL verification handshake to succeed and kept incoming webhook deliveries working.
diff --git a/blog/src/posts/node-pty-electron-real-terminals.md b/blog/src/posts/node-pty-electron-real-terminals.md
index 6d3b7e24..03dbfd61 100644
--- a/blog/src/posts/node-pty-electron-real-terminals.md
+++ b/blog/src/posts/node-pty-electron-real-terminals.md
@@ -97,6 +97,8 @@ The `-w node-pty` scopes the rebuild to just that module (faster than rebuilding
forces it. After this runs, the addon loads cleanly inside Electron. Forget it, and the app crashes on
launch with an ABI error that looks scarier than it is.
+{% img "note-1" %}
+
## Gotcha 2 — The macOS PATH trap
You ship the app, double-click it, and your terminal can't find `claude` — or `node`, or `git`, or
@@ -173,6 +175,8 @@ function safeSend(channel: string, payload: unknown) {
Route every PTY-to-renderer message through that, and quitting the app is clean instead of a crash
report.
+{% img "note-2" %}
+
## Managing many sessions
A real app runs more than one terminal, so wrap all of this in a manager keyed by session id —
diff --git a/blog/src/posts/number-five-on-product-hunt.md b/blog/src/posts/number-five-on-product-hunt.md
new file mode 100644
index 00000000..e808b828
--- /dev/null
+++ b/blog/src/posts/number-five-on-product-hunt.md
@@ -0,0 +1,104 @@
+---
+title: "Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers"
+description: "Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek's harness launch that day. Here's what actually happened: the numbers, the people who showed up, and the two pieces of feedback we're already shipping fixes for."
+date: 2026-08-19
+category: story
+categoryLabel: Story
+type: Non-technical
+primaryKeyword: "munder difflin product hunt"
+secondaryKeywords: ["product hunt launch retrospective", "product of the day", "ai agent harness launch", "launching a dev tool on product hunt"]
+tags: ["Story", "Launch", "Product Hunt", "Open Source"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "How did Munder Difflin do on Product Hunt?"
+ a: "It finished #5 Product of the Day on 2026-08-14 with 195 upvotes (177 on launch day itself), 326 followers, and #35 for the week — ahead of DeepSeek's harness, which launched the same day. It was a first launch, self-hunted, with no hunter network behind it."
+ - q: "Did Product Hunt drive a lot of traffic?"
+ a: "Honestly, no. The badge brought credibility, not crowds — roughly one site visitor per eight upvotes. What it did bring was a small number of unusually serious evaluators, including a CEO who ran it on a real multi-day task and reviewed it in detail. For a developer tool, that trade is worth knowing about before you launch."
+ - q: "What feedback came out of the launch?"
+ a: "Two things, both already acted on: first-run engine selection could trap you if you picked an engine you didn't have access to (fixed territory in v0.4.4's onboarding work), and people want a visible flag for 'this decision needs your eyes' so they can tell an agent that paused from one that decided on its own. That second one is now on the roadmap."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>On August 14 we launched Munder Difflin
+on Product Hunt for the first time. It finished <strong>#5 Product of the Day</strong> — ahead of
+DeepSeek's harness, which launched the same day — with 195 upvotes and 326 followers. The honest
+retro: Product Hunt bought us credibility, not traffic, and the ten people who actually commented
+gave us better product feedback than a thousand upvotes would have.</p></div>
+
+We had never launched on Product Hunt before. No hunter with a following, no launch agency, no
+upvote pod — I hunted it myself, scheduled it for August 14, and went to bed nervous.
+
+## The scoreboard
+
+- **#5 Product of the Day**, August 14, 2026 — the same day DeepSeek launched
+ [their harness](/blog/what-is-harness-engineering/) with tech-press coverage behind it; the
+ [day's leaderboard](https://www.producthunt.com/leaderboard/daily/2026/8/14) has them at #6,
+ one spot behind us, which still feels surreal to type
+- **195 upvotes** as of August 18 (177 on the day itself; the rest drifted in over the week)
+- **326 followers**, **#35 product of the week**, **#74 of the month**
+- **27 comments** — 15 of them mine, because I answered everything
+- **One review**: 4.0 overall, with value-for-money and customization at 5/5
+
+That last line deserves context. The review came from Gal Dayan, co-founder and CEO of Dial, who
+didn't skim the landing page — he ran Munder Difflin against his own Claude subscription on a
+multi-day task before writing a five-dimension review. His build-vs-buy verdict was the sentence
+I'd been trying to write for months, in someone else's words:
+
+> "I looked at rolling my own orchestration on tmux plus Claude Code directly. Wasn't worth
+> reinventing the mailbox and lifecycle tracking myself when this already handles worker handoffs,
+> and it's fully local so none of my code leaves my machine."
+
+That's the whole pitch. The [mailboxes](/blog/atomic-file-mailboxes-for-agents/), the lifecycle
+tracking, the [local-first design](/blog/why-local-first-matters-for-ai-agents/) — the boring
+plumbing is the product.
+
+{% img "note-1", "First launch, self-hunted, no upvote pod — and the badge came home anyway." %}
+
+## Who actually showed up
+
+Product Hunt gets described as a hype machine, and maybe it is for consumer apps. What showed up
+on our page was ten people, and the ratio of substance was unusually high: a CEO who ran a
+multi-day evaluation, an engineer who instruments his own agent spend down to the dollar, a
+builder who runs his own orchestration system and benchmarked ours against it, a product manager
+who uses it at work, and someone asking whether a hive could build a company's tender-management
+system end to end.
+
+Small crowd, serious questions. The exact opposite of [our Reddit
+launch](/blog/what-reddit-told-us-about-munder-difflin/), which was a stadium.
+
+## The two pieces of feedback that mattered
+
+**1. First-run engine selection could strand you.** One commenter picked Claude Code during setup
+without having Claude Code access, couldn't change the selection afterwards, and uninstalled
+twice in frustration. Another hit a Windows + Codex startup failure that killed his three-agent
+benchmark. Two people out of ten, blocked by the same class of problem: the non-Claude-Code path
+got less love than it deserved. The Windows side of this is exactly what
+[v0.4.4 fixed](/blog/launching-munder-difflin-v0-4-4/), and onboarding now validates your setup
+at step one instead of failing after step four.
+
+**2. Nobody can tell a finished agent from a stuck one — or a paused one from a self-directed
+one.** The two most technically serious people on the page independently asked for the same
+missing primitive. One measured that 64.9% of a day's agent spend landed in an "abandoned"
+bucket and wants to trust unattended runs. The other put it perfectly: the office view already
+tells you *who's stuck versus who's actually working* at a glance, but it doesn't tell you
+whether a clone paused for your input or made a judgment call on its own. A visible
+**"this decision needs your eyes"** flag is the ask, and it's the best feature request we've
+received on any channel. It's on the roadmap.
+
+{% img "note-2", "The best feature request of the launch: a flag that says 'this decision needs your eyes' — asked for twice, independently." %}
+
+## What Product Hunt is actually for
+
+Here's the number nobody puts in their launch thread: those 195 upvotes referred roughly 25
+unique visitors to our site. One visitor per eight upvotes. If you're launching a developer tool
+and expecting Product Hunt to be a traffic channel, adjust that expectation now.
+
+What it *is*: a credibility artifact (the badge now lives on [munderdiffl.in](https://munderdiffl.in)),
+and a filter that surfaces a handful of unusually serious evaluators. The questions those
+evaluators asked — about trust, about unattended runs, about
+[what runs where](/blog/why-local-first-matters-for-ai-agents/) — were the enterprise questions,
+and getting them this early is a gift.
+
+Would we launch there again? Yes — but as one channel in a week, not the week itself. The stadium
+was elsewhere, and that's [the next post](/blog/what-reddit-told-us-about-munder-difflin/).
diff --git a/blog/src/posts/observability-for-agent-fleets.md b/blog/src/posts/observability-for-agent-fleets.md
index fe03c881..582fc250 100644
--- a/blog/src/posts/observability-for-agent-fleets.md
+++ b/blog/src/posts/observability-for-agent-fleets.md
@@ -61,6 +61,8 @@ into the main process in real time, so the picture is live rather than a periodi
[orchestrator](/blog/how-the-god-orchestrator-works/) that routes work reads this feed to keep its
situational awareness current.
+{% img "note-1" %}
+
## Token and cost telemetry, per agent
This is the part teams skip and regret. Autonomous agents spend money on their own, so **cost is a
@@ -87,6 +89,8 @@ Actions and cost tell you *what's happening*; state tells you *why*.
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.
+{% img "note-2" %}
+
## Observability vs debugging
These are different jobs. [Debugging a multi-agent system](/blog/debugging-multi-agent-systems/) is
diff --git a/blog/src/posts/one-prompt-automated-pr-review.md b/blog/src/posts/one-prompt-automated-pr-review.md
index b777b032..95ae9598 100644
--- a/blog/src/posts/one-prompt-automated-pr-review.md
+++ b/blog/src/posts/one-prompt-automated-pr-review.md
@@ -47,6 +47,8 @@ A few examples, grounded in what's actually on GitHub:
Five reviews. One prompt. The reviews were posted so close together (all within seconds, around `2026-06-07T01:47`) that they clearly came from a single agent run. The whole batch took a few minutes I spent doing something else.
+{% img "note-1" %}
+
## The recurring part
The review run was half of what I asked for. The other half was the hourly mission.
@@ -79,6 +81,8 @@ A few things are true at once here, and they're worth separating.
**Third, what "automation" means here.** The hourly PR reviewer isn't a GitHub Actions workflow. It's not a webhook. It's a local agent that wakes up on a schedule, reads the repo state, and does the work — with the same intelligence, tone, and judgment a human reviewer would bring, because it *is* a Claude agent. The automation is just a timer that refills an agent's inbox.
+{% img "note-2" %}
+
## The limit worth naming
ScheduledMissions are local-first: the timers live in the desktop app's process. The PR reviewer only fires while Munder Difflin is open. That's a deliberate trade — this is a tool you run on your own machine, not a cloud cron — and `lastFiredAt` softens it by catching up on any overdue ticks at the next launch. But if you need PR reviews while the laptop is shut, that's genuinely a cloud job's territory.
diff --git a/blog/src/posts/open-source-ai-tools-on-purpose.md b/blog/src/posts/open-source-ai-tools-on-purpose.md
index ed3ded2a..eeee9909 100644
--- a/blog/src/posts/open-source-ai-tools-on-purpose.md
+++ b/blog/src/posts/open-source-ai-tools-on-purpose.md
@@ -65,6 +65,8 @@ what you can do as a user:
- **Longevity.** Open code outlives the company or the moment. The work you build on top of it is safe
in a way that a closed SaaS can't promise.
+{% img "note-1" %}
+
## Open *and* local-first — the combination is the point
"Open source" alone can still be hollow if the useful half lives in someone else's cloud. The version
@@ -89,6 +91,8 @@ It also lowers the bar to contribute. When the code and the thinking are both pu
rough edge can read the relevant file, understand it, and propose a fix — instead of filing a ticket into
a void and hoping.
+{% img "note-2" %}
+
## The honest tradeoffs
Open source isn't free of cost, and pretending otherwise would be exactly the kind of marketing this post
diff --git a/blog/src/posts/orca-vs-munder-difflin.md b/blog/src/posts/orca-vs-munder-difflin.md
index 9ecd9c53..98fd5ad5 100644
--- a/blog/src/posts/orca-vs-munder-difflin.md
+++ b/blog/src/posts/orca-vs-munder-difflin.md
@@ -48,6 +48,8 @@ That mobile companion and the editor-centric review flow are genuinely ahead of
Notice, though, what the workflow assumes: **you**. You send the prompts. You compare the results. You annotate the diffs. You steer. Orca's own docs describe an interactive loop, and there's no orchestrator, scheduler, or external trigger in it. That's not a flaw — it's the product. An IDE is a place you sit.
+{% img "note-1" %}
+
## What Munder Difflin actually is
Munder Difflin starts from the opposite question: what if you *don't* sit there?
@@ -61,6 +63,8 @@ It's a local-first Electron app that turns the same agent CLIs — Claude Code,
v0.3.3 did add a built-in Monaco IDE — file tree, tabs, side-by-side diffs vs HEAD — but let's be honest about what it's for: it's a **review surface for what your agents changed**, not a place you live. Orca's editing experience is deeper. Munder Difflin's bet is that you'll spend less time in an editor at all, because the office handles the routing, memory, and follow-through that would otherwise pull you back to the keyboard.
+{% img "note-2" %}
+
## The boundary, drawn plainly
| | **Orca** | **Munder Difflin** |
diff --git a/blog/src/posts/overnight-ai-coding-realistic-expectations.md b/blog/src/posts/overnight-ai-coding-realistic-expectations.md
index 93cbf337..03494dcc 100644
--- a/blog/src/posts/overnight-ai-coding-realistic-expectations.md
+++ b/blog/src/posts/overnight-ai-coding-realistic-expectations.md
@@ -70,6 +70,8 @@ The failure modes are just as predictable. Overnight agents struggle when:
Notice the pattern: the failures aren't about raw capability. They're about **scope and judgment**. The
fix isn't a smarter model; it's a better setup.
+{% img "note-1" %}
+
## The guardrails that make overnight work safe
Unattended doesn't have to mean ungoverned. The difference between "wake up to progress" and "wake up
@@ -109,6 +111,8 @@ If you want to try it tonight, here's the honest checklist:
5. **Leave breadcrumbs for morning-you.** Make sure there's a log and a short status per task. You're
optimizing your *review time*, not just the agents' run time.
+{% img "note-2" %}
+
## What still needs you in the morning
This is the part the slogans skip. Overnight agents change *when* the work happens, not *whether you're
diff --git a/blog/src/posts/prompt-caching-for-ai-agents.md b/blog/src/posts/prompt-caching-for-ai-agents.md
index ae497eb2..995195bc 100644
--- a/blog/src/posts/prompt-caching-for-ai-agents.md
+++ b/blog/src/posts/prompt-caching-for-ai-agents.md
@@ -70,6 +70,8 @@ turn. For a one-shot call that never repeats, caching isn't worth the write prem
which repeats the same prefix constantly — it's close to a no-brainer. The break-even is usually just
two or three reuses, and agents reuse far more than that.
+{% img "note-1" %}
+
## The one rule: stable first, volatile last
Caches match on an **exact prefix**. The provider walks your prompt from the start and reuses the cache
@@ -111,6 +113,8 @@ The practical implications:
[human-in-the-loop checkpoints](/blog/human-in-the-loop-ai-agents/) should be rare and high-signal,
not sprinkled everywhere.
+{% img "note-2" %}
+
## The multi-agent angle
In a single agent, caching is a per-session win. In a [hive](/blog/coordinating-ai-coding-agents/) it
diff --git a/blog/src/posts/qm-vs-munder-difflin.md b/blog/src/posts/qm-vs-munder-difflin.md
index 640c6c6a..e5fcfea2 100644
--- a/blog/src/posts/qm-vs-munder-difflin.md
+++ b/blog/src/posts/qm-vs-munder-difflin.md
@@ -68,6 +68,8 @@ If you map the concepts across, most of qm's vocabulary has a Munder Difflin cou
| Isolation | Isolated workspaces per employee | Isolated git worktrees per agent |
| License | MIT | MIT |
+{% img "note-1" %}
+
## What each has that the other doesn't
**qm's edge is multiplayer.** One shared harness, unified identity, org-level admin,
@@ -91,6 +93,8 @@ Slack, that's qm's home turf, and Munder Difflin doesn't try to be that.
- **A longer release train.** Public releases since v0.2.0, now at v0.3.5, with the
reliability work battle-tested by a growing contributor community.
+{% img "note-2" %}
+
## Which should you use?
- **Your whole team wants one shared fleet with org-level control → qm.** That's what
diff --git a/blog/src/posts/recovering-from-agent-failures.md b/blog/src/posts/recovering-from-agent-failures.md
index b7fddfe6..4d14247a 100644
--- a/blog/src/posts/recovering-from-agent-failures.md
+++ b/blog/src/posts/recovering-from-agent-failures.md
@@ -70,6 +70,8 @@ wedge the repo forever. And **graceful give-up:** a non-lock error doesn't throw
because the *next* mutation will stage and commit the same pending changes anyway. Nothing is lost by
bailing early.
+{% img "note-1" %}
+
## Don't choke on a poison message
A file-based mailbox will eventually contain a half-written or malformed JSON file. The naive router
@@ -106,6 +108,8 @@ It's deliberately blunt: it guarantees the conversation terminates. And because
runaway leaves a breadcrumb instead of a silent hang — you can read the log and see exactly which thread
ran away.
+{% img "note-2" %}
+
## Idempotent by construction
The cheapest way to survive duplicates and replays is to make re-handling a no-op. In the hive, an agent
diff --git a/blog/src/posts/rendering-many-live-terminals-performance.md b/blog/src/posts/rendering-many-live-terminals-performance.md
index 833454e4..376b0003 100644
--- a/blog/src/posts/rendering-many-live-terminals-performance.md
+++ b/blog/src/posts/rendering-many-live-terminals-performance.md
@@ -69,6 +69,8 @@ This single change fixes both naive problems: no per-switch teardown (no thrash)
(no blank pane). It's the structural decision everything else builds on — the same pool pattern at the
center of [building a terminal UI with xterm.js and node-pty](/blog/building-a-terminal-ui-xterm-node-pty/).
+{% img "note-1" %}
+
## Technique 2 — Render only what's visible
A pool keeps every session's *buffer* current, but you don't need to *paint* every terminal every
@@ -107,6 +109,8 @@ lives) over IPC. A few habits keep that path cheap:
These come straight from how the [node-pty terminal plane](/blog/node-pty-electron-real-terminals/)
streams to the UI.
+{% img "note-2" %}
+
## Technique 5 — Reach for an accelerated renderer when needed
xterm's default DOM renderer is fine for a handful of terminals. When you're rendering many
diff --git a/blog/src/posts/review-agent-work-where-it-happens.md b/blog/src/posts/review-agent-work-where-it-happens.md
index fbe46f69..247fd328 100644
--- a/blog/src/posts/review-agent-work-where-it-happens.md
+++ b/blog/src/posts/review-agent-work-where-it-happens.md
@@ -40,6 +40,8 @@ When you supervise agents, you're running a loop: watch the floor, read an escal
Multiply that by every agent, every task, all day. The cost isn't the seconds per switch; it's that switching makes review feel expensive, so you do less of it, so agent work merges less verified than it should. The bottleneck doesn't just slow you down — it degrades the quality of the supervision itself.
+{% img "note-1" %}
+
## Review-in-place: the IDE comes to the floor
This is the problem the v0.3.3 built-in IDE exists to solve. A title-bar **IDE** button opens a full-window **Monaco** editor — the same editor engine VS Code runs on, fully self-hosted with no CDN — as an overlay on the office floor. The floor, the terminals, and everything else stay untouched underneath; you toggle in, review, toggle out.
@@ -54,6 +56,8 @@ The workspace root snapshots from the selected agent's cwd (falling back to the
One architectural note that matters more than it sounds: **the renderer holds no filesystem or git access.** Every read, diff, and save is brokered through the Electron main process over IPC. The pretty editor window is just a view; the privileged operations happen in one audited place. And a v0.3.3 fix hardened the save path so keystrokes typed while a save is still writing are never silently dropped — a small thing, exactly the kind of small thing that erodes trust in an in-app editor if it's wrong.
+{% img "note-2" %}
+
## The diff is only trustworthy because of how it was made
A side-by-side diff vs HEAD is only useful if HEAD means something. In a naive multi-agent setup — several agents committing to one repo — it doesn't: histories interleave, `index.lock` collisions corrupt state, and "what did agent B change" has no clean answer.
diff --git a/blog/src/posts/run-a-mixed-engine-office.md b/blog/src/posts/run-a-mixed-engine-office.md
index 07e95386..13a65341 100644
--- a/blog/src/posts/run-a-mixed-engine-office.md
+++ b/blog/src/posts/run-a-mixed-engine-office.md
@@ -44,6 +44,8 @@ Seven engines can sit on one floor today, and they're not interchangeable — th
One honest caveat up front: Copilot's print mode exits per turn and has no hook bridge, so its workers can't drain hive inbox mail — routed mail bounces to the orchestrator instead of disappearing. That's by design, and it tells you exactly where Copilot desks belong.
+{% img "note-1" %}
+
## The layout that works
**Michael's office: Claude Code.** The orchestrator reads every request, adjudicates traffic, scribes the blackboard, and escalates only critical items to you. That's sustained, stateful, judgment-heavy work — give it the engine with native hooks and the tightest harness integration. (Michael's engine is swappable from onboarding or the change-engine flow if you want to experiment; OpenCode, Crush, and pi.dev are all god-eligible, backstopped by a provider-agnostic idle fallback.)
@@ -64,6 +66,8 @@ Then hire. In Add Agent, choosing a local-capable engine surfaces **OSS-model qu
The full local-model walkthrough is in [run Munder Difflin on open models](/blog/run-munder-difflin-on-open-models/).
+{% img "note-2" %}
+
## Keeping the mixed floor affordable and sane
A mixed floor is a cost instrument, but only if you can see and cap what each desk spends. Munder Difflin gives every agent a **token budget** with live fleet monitoring, real token and cost telemetry per agent per session, and a **circuit breaker** that steers, constrains, then stops any agent that loops or blows its budget. The expensive Claude Code desks carry tight scopes; the local desks can grind all night for electricity. The routing logic — which work deserves which price — is the whole subject of [the multi-agent cost playbook](/blog/the-multi-agent-cost-playbook/).
diff --git a/blog/src/posts/run-a-release-train-with-agents.md b/blog/src/posts/run-a-release-train-with-agents.md
new file mode 100644
index 00000000..d6061e66
--- /dev/null
+++ b/blog/src/posts/run-a-release-train-with-agents.md
@@ -0,0 +1,99 @@
+---
+title: "Run a Release Train with Agents"
+description: "Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week."
+date: 2026-08-19
+category: use-cases
+categoryLabel: Use Cases
+type: Non-technical
+primaryKeyword: "automate releases with ai agents"
+secondaryKeywords: ["release automation workflow", "ai changelog generation", "release notes automation", "ship faster open source", "munder difflin workflow"]
+tags: ["Use Cases", "Release", "Workflow", "Automation", "Multi-Agent"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "What release chores can agents take over?"
+ a: "The synchronization work: bumping versions everywhere they appear, writing the changelog entry from the actual merged diffs, drafting human-readable release notes, updating the website's version strings and download links, and checking that every link and version reference agrees. Humans stay on the judgment calls — what ships, and whether the notes tell the truth."
+ - q: "How do you stop version references drifting apart?"
+ a: "Two layers: an agent whose checklist includes every known surface (changelog, README badge, site, llms.txt, release page), and a guard script in CI that fails the build when a reference drifts. The script exists because an agent-run audit found our llms.txt advertising a version two releases stale — automation found it, a test now prevents it."
+ - q: "Does this replace release engineering?"
+ a: "No — it replaces release chores. The decisions (what's in, what's blocked, when to cut) stay human. What the agents remove is the hour of mechanical synchronization per release that otherwise gets skipped, which is exactly how version drift and stale notes happen."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>A release is one decision and forty
+chores. During our <a href="/blog/seven-releases-in-eight-days/">seven-releases-in-eight-days
+week</a>, the chores — version bumps, changelog prose, release notes, site updates, link
+checks — ran as a repeatable agent workflow. The decision stayed human. That's the whole
+trick, and here's the train schedule.</p></div>
+
+Everyone's release process degrades the same way. Release one: meticulous. Release five: the
+changelog says "misc fixes." Release nine: the README badge is two versions behind and the
+website's FAQ names a plan that doesn't exist. Not because anyone stopped caring — because
+synchronization chores scale linearly with surfaces, and humans under deadline cut exactly
+those corners.
+
+We shipped seven releases in eight days without (we think) shipping that decay, and the reason
+is that the chores are a train the [hive](/blog/what-is-a-multi-agent-harness/) runs on rails.
+
+## The train, car by car
+
+**Car 1: the changelog entry, from evidence.** An agent reads the actual merged commits and
+PRs since the last tag — not a memory of them — and drafts the changelog entry with a hard
+rule we stole from our own postmortems: *every entry says what was broken from the user's point
+of view, not which function changed.* "Agents booted, looked healthy, and had no idea they
+could message anyone" survives to [the published
+changelog](/blog/launching-munder-difflin-v0-4-4/) because the draft started from the diff and
+the issue thread, where that sentence was earned.
+
+{% img "note-1", "The changelog agent works from merged diffs and issue threads — not from anyone's memory of the week." %}
+
+**Car 2: version references, everywhere.** The version string lives in more places than you
+think: package manifest, changelog header, README badge, the website, the release page,
+`llms.txt`. One agent's checklist is simply: find every reference, update every reference,
+*then list where it looked* so omissions are visible. This car exists because an audit found
+our `llms.txt` advertising a version two releases stale — nobody had ever put it on a mental
+checklist.
+
+**Car 3: release notes for humans.** The changelog is the record; the release notes are the
+story. A second pass rewrites the entry in plain language — what you'll notice, what you need
+to do (usually nothing, [the app updates itself](/blog/why-our-auto-update-never-ran/)) — and
+since 0.4.4 can even ship as a designed page rendered inside the app. **This is also where
+contributors get credited by name, every release, without fail** — @gts-47's eight PRs and
+@baziyer's rendering fix headline the 0.4.4 thanks because an agent's checklist said *find
+every community PR in this release and name its author*, and checklists don't get shy.
+
+**Car 4: the guard rail.** The best part of agent-run chores: when an agent finds a drift
+class once, you make it impossible instead of remembered. A small link-and-version checker now
+runs in CI and fails the build if any known surface disagrees about the current version. The
+train doesn't rely on the conductor's attention anymore.
+
+{% img "note-2", "Find the drift once, then make it a failing test. The train stops relying on anyone's attention." %}
+
+## Why agents fit this shape of work
+
+Release chores are the ideal agent workload for three reasons. They're **evidence-based** — the
+truth is in the diff, the tag, and the file, so [verification is
+mechanical](/blog/how-ai-agents-verify-their-own-work/). They're **checklist-shaped** — the same
+surfaces every time, which agents execute with the enthusiasm humans reserve for release one.
+And they're **interruptible** — each car produces reviewable artifacts (a draft entry, a list
+of touched files), so the human can inspect the train at any station.
+
+Note what's *not* on the train: deciding what ships, judging whether a fix is real, choosing
+what the headline is. During our eight-day week those calls happened in minutes precisely
+because the chores weren't competing for the same attention.
+
+## Set up your own
+
+The portable version, whatever your stack:
+
+1. **Write the checklist down once** — every file that mentions a version, every step between
+ tag and announcement. This document *is* the agent brief.
+2. **Point agents at evidence** — diffs, merged PRs, closed issues. Ban writing from memory.
+3. **Route it through one dispatcher** so the cars run in order —
+ [that's what an orchestrator is for](/blog/how-to-talk-to-your-orchestrator/).
+4. **Convert discoveries into CI guards.** An agent finding drift is good; a test that makes
+ the drift impossible is the actual win.
+
+Our cadence didn't come from typing faster. It came from making releases cost one decision
+instead of one afternoon — and from a train that [runs on
+schedule](/blog/scheduling-autonomous-agent-missions/) even when the humans are asleep.
diff --git a/blog/src/posts/run-ai-agent-hive-from-slack-setup.md b/blog/src/posts/run-ai-agent-hive-from-slack-setup.md
index 16f9fc05..7a4b723c 100644
--- a/blog/src/posts/run-ai-agent-hive-from-slack-setup.md
+++ b/blog/src/posts/run-ai-agent-hive-from-slack-setup.md
@@ -93,6 +93,8 @@ the signing secret, it stays in the app's main process and is never logged.
> Keep both values handy. You'll paste them into Munder Difflin next, then come back to finish Event
> Subscriptions.
+{% img "note-1" %}
+
## Part 2 — Configure Munder Difflin
Open Munder Difflin and go to **Settings**. In the Slack section:
@@ -149,6 +151,8 @@ The message lands in the queue, GOD routes it, and an agent picks it up. Keep th
replying in that same thread — the hive is still listening. When the task is done, a summary appears
right there in the thread.
+{% img "note-2" %}
+
## Troubleshooting: the Request URL rotates on restart
Here's the one quirk worth tattooing on the back of your hand. **The public Request URL comes from an
diff --git a/blog/src/posts/run-an-office-of-ai-agents.md b/blog/src/posts/run-an-office-of-ai-agents.md
index af41ba88..c575304f 100644
--- a/blog/src/posts/run-an-office-of-ai-agents.md
+++ b/blog/src/posts/run-an-office-of-ai-agents.md
@@ -34,6 +34,8 @@ close the laptop and check the morning's progress over coffee.
That's not a metaphor for Munder Difflin — it's literally [the office floor](/#how). But the picture
only works because of what's underneath it.
+{% img "note-1" %}
+
## What makes it actually work
A self-running office isn't "point agents at a repo and hope." Four pieces carry the weight:
@@ -57,6 +59,8 @@ This is the part the fantasy skips. Unattended agents need a [human-in-the-loop]
work proceeds, but the risky stuff — spending real money, destructive operations, big scope changes —
queues for your approval. You wake up to *progress*, not surprises.
+{% img "note-2" %}
+
## What's realistic (and what isn't)
Honesty matters here, because over-promising is how people get burned:
diff --git a/blog/src/posts/run-munder-difflin-on-a-mac-mini.md b/blog/src/posts/run-munder-difflin-on-a-mac-mini.md
index eb809e3a..22ac2364 100644
--- a/blog/src/posts/run-munder-difflin-on-a-mac-mini.md
+++ b/blog/src/posts/run-munder-difflin-on-a-mac-mini.md
@@ -106,6 +106,8 @@ open-source-model provider (OpenRouter, Groq, DeepInfra, and friends) with an AP
<a href="/blog/run-munder-difflin-on-open-models/">open-models guide</a>. For a genuinely local GLM,
<code>glm-4.7-flash</code> (~30B) is the Mac-friendly member of the family.</p></div>
+{% img "note-1" %}
+
## Step 2 — Install a local model server
You have two solid options. Both expose an **OpenAI-compatible HTTP endpoint**, which is exactly what
@@ -195,6 +197,8 @@ points at a third-party <code>provider/model</code> slug instead, per the note a
every tier live in the <a href="/blog/run-munder-difflin-on-open-models/">open-source model catalog</a>,
kept in one place so they don't drift.</p></div>
+{% img "note-2" %}
+
## Step 4 — Run the hive offline
With a model served locally and the engines pointed at it, the rest of Munder Difflin is already
diff --git a/blog/src/posts/run-munder-difflin-on-open-models.md b/blog/src/posts/run-munder-difflin-on-open-models.md
index 741b6a92..20ff0048 100644
--- a/blog/src/posts/run-munder-difflin-on-open-models.md
+++ b/blog/src/posts/run-munder-difflin-on-open-models.md
@@ -60,6 +60,8 @@ The *local* route differs slightly by engine — same id, different prefix and w
Default endpoints are the usual ones: Ollama `http://localhost:11434/v1`, LM Studio `http://127.0.0.1:1234/v1`, vLLM whatever you exposed (often `:8000/v1`). You set these in the app — no shell exports required.
+{% img "note-1" %}
+
## Path A — fully local (Ollama / LM Studio / vLLM)
Three steps: pull a model, tell Munder Difflin where it lives, pick it for an agent.
@@ -116,6 +118,8 @@ Same open weights, hosted on someone else's GPUs, billed to your own key. This i
Prefer a model maker's own API? Those work too: DeepSeek (`deepseek/deepseek-v4-flash`, `DEEPSEEK_API_KEY`), Mistral (`mistral/...`, `MISTRAL_API_KEY`), Z.ai for GLM, Moonshot for Kimi. A couple of moving targets worth knowing as of mid-2026: DeepSeek's `deepseek-chat` / `deepseek-reasoner` aliases retire on 2026-07-24 (wire `deepseek-v4-flash` directly), and Groq is sunsetting Llama 4 — so on Groq stick to gpt-oss and `llama-3.3-70b-versatile`. The full slug-by-slug table, with citations and verify-live caveats, lives in the project's open-model catalog (the single source of truth this post and the Mac Mini guide both cite).
+{% img "note-2" %}
+
## Per-engine cheat-sheet
You rarely touch these directly — the AI Engines panel writes them — but here's what each engine does under the hood, so the model field makes sense.
diff --git a/blog/src/posts/scheduling-autonomous-agent-missions.md b/blog/src/posts/scheduling-autonomous-agent-missions.md
index 11c4d5d5..83f1b19a 100644
--- a/blog/src/posts/scheduling-autonomous-agent-missions.md
+++ b/blog/src/posts/scheduling-autonomous-agent-missions.md
@@ -80,6 +80,8 @@ This very post is proof. It exists because an **"Hourly Standup" mission** fired
`scheduler`, broadcast to every agent, asking each to report status and pick up work. No one typed that
prompt this hour. The schedule did.
+{% img "note-1" %}
+
## Why `lastFiredAt` matters
The one piece of cleverness worth understanding is `lastFiredAt`. A naive scheduler would restart every
@@ -119,6 +121,8 @@ A scheduler that fires the same instruction forever rewards a particular style o
- **Pause with `enabled`, don't delete.** Flip `enabled: false` to stop a mission while keeping its
history and `lastFiredAt`. You can switch it back on later and the cadence picks up cleanly.
+{% img "note-2" %}
+
## Pitfalls to avoid
- **Flooding the hive.** The scheduler will fire as often as you tell it to — restraint is on you. A
diff --git a/blog/src/posts/security-for-ai-coding-agents.md b/blog/src/posts/security-for-ai-coding-agents.md
index 9f84a166..86a00523 100644
--- a/blog/src/posts/security-for-ai-coding-agents.md
+++ b/blog/src/posts/security-for-ai-coding-agents.md
@@ -66,6 +66,8 @@ agent that only needs to read shouldn't hold write tokens; one that builds shoul
Least privilege also makes review tractable. A tightly-scoped change is one a human (or a peer agent) can
actually check. A sprawling one is where mistakes hide.
+{% img "note-1" %}
+
## Treat everything an agent reads as untrusted
This is the part teams miss. An agent reads constantly — files, web pages, issue comments, command output,
@@ -99,6 +101,8 @@ genuinely dangerous moves pay the cost of a confirmation. Pair this with agents
[verify their own work](/blog/how-ai-agents-verify-their-own-work/) and re-verify each other's, and you get
a funnel: cheap automated checks first, scarce human attention last, on the decisions that carry real risk.
+{% img "note-2" %}
+
## Keep the sensitive stuff local
Every time an agent sends content to an external service, that content may be cached, logged, or indexed —
diff --git a/blog/src/posts/semantic-memory-for-ai-agents.md b/blog/src/posts/semantic-memory-for-ai-agents.md
index 41e86971..058610ab 100644
--- a/blog/src/posts/semantic-memory-for-ai-agents.md
+++ b/blog/src/posts/semantic-memory-for-ai-agents.md
@@ -61,6 +61,8 @@ note entirely.
The payoff compounds: recall stays **near-instant** and the context window stays **small** even as the
note collection grows into the hundreds. You inject the few notes that matter, not the whole archive.
+{% img "note-1" %}
+
## Why markdown-first beats a heavyweight DB
There's a strong temptation to reach for a dedicated vector database or a full agent-memory framework.
@@ -126,6 +128,8 @@ If the semantic layer isn't installed at all, none of this errors — it's a no-
to reading their markdown directly. The fast path is an upgrade, not a dependency. That's the
markdown-first principle paying off: the floor never falls out from under the team.
+{% img "note-2" %}
+
## How fast is "fast"?
The "milliseconds" promise is about the *experience*, and it's worth being precise. Recall feels
diff --git a/blog/src/posts/seven-releases-in-eight-days.md b/blog/src/posts/seven-releases-in-eight-days.md
new file mode 100644
index 00000000..085db22e
--- /dev/null
+++ b/blog/src/posts/seven-releases-in-eight-days.md
@@ -0,0 +1,103 @@
+---
+title: "Seven Releases in Eight Days: 0.3.8 → 0.4.4"
+description: "Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour."
+date: 2026-08-19
+category: story
+categoryLabel: Story
+type: Non-technical
+primaryKeyword: "munder difflin releases"
+secondaryKeywords: ["munder difflin changelog", "shipping velocity open source", "release cadence dev tools", "munder difflin 0.4"]
+tags: ["Story", "Release", "Open Source", "Changelog"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "What shipped in the 0.4.x wave of Munder Difflin?"
+ a: "0.3.8 made memory condensation actually work; 0.3.9 added a check-for-updates panel; 0.4.0 rebuilt the brand and landing page with real screenshots; 0.4.1 renamed the GOD agent to your clone and named all ten engines; 0.4.2 added anonymous, opt-out telemetry with a public contract; 0.4.3 made Michael's portrait the logo; and 0.4.4 fixed agent messaging on Windows and added the skills catalog."
+ - q: "Why release so often?"
+ a: "Launch week. Thousands of new people hit the product at once and found things a small user base never would — Windows messaging, onboarding dead-ends, unreadable dark mode. When feedback arrives that fast, batching fixes into a monthly release just means people churn while the fix sits on a branch."
+ - q: "Is telemetry in Munder Difflin opt-out or opt-in?"
+ a: "Opt-out, anonymous, and governed by a public contract: TELEMETRY.md lists every event and property, the code enforces that list as a hard allowlist, DO_NOT_TRACK is respected unconditionally, and building from source or forking produces a build with no key — the analytics module becomes a no-op."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>August 11 to August 18: <strong>seven
+releases</strong>. A memory system that had been silently reading an empty directory, fixed. An
+update checker. A new face for the whole product. A public telemetry contract. Honest engine
+naming. And the big one — Windows agents that can finally hear each other. Here's the whole
+train, car by car.</p></div>
+
+Launch week compresses a year of feedback into days. Thousands of people hit first-run at once,
+on machines and configs we'd never seen, and the bug reports came in faster than any roadmap
+could dignify. So the roadmap lost. For eight days we just shipped.
+
+{% img "note-1", "Seven releases, eight days. The kanban wall did not enjoy it as much as we did." %}
+
+## 0.3.8 — memory condensation works for the first time
+
+The most embarrassing entry, so it goes first. The harness had been reading Claude Code
+transcripts from a directory that hasn't existed for months. Nothing errored — an absent
+directory reads exactly like "no transcripts yet" — so [the
+summarizer](/blog/compressing-agent-memory/) sat there proudly summarizing nothing. 0.3.8
+pointed it at reality, and stopped compaction firing on two schedules at once while it was in
+there. If your agents' memories seemed thinner than advertised before mid-August: they were.
+
+## 0.3.9 — "am I up to date?" gets an answer
+
+Settings → General now names your version, says whether it's the latest, and offers one button
+that does what it says: **Check for updates → Download → Restart to update**. It shares its
+state machine with the toolbar chip so the two can never disagree. Shipped fast for one reason:
+0.3.8 needed to reach people who'd already installed 0.3.7.
+
+## 0.4.0 and 0.4.3 — the brand grew up
+
+0.4.0 rebuilt munderdiffl.in around the real app — actual screenshots, a live demo loop in the
+hero — and unified the icon across every platform. Then 0.4.3 went further: the logo is now
+**Michael's pixel-art portrait on the brand yellow**, authored as a single vector, with every
+raster — site, app, all three platform icons — generated from that one source by a script. The
+icons can no longer drift apart, because none of them is hand-made anymore.
+
+{% img "note-2", "One vector, every icon. The logo is now the character the product is about." %}
+
+## 0.4.1 — the app says what the site says
+
+Small release, honest release. The site called Michael a clone of you; the app still said "GOD
+agent." Now [he's your clone everywhere](/blog/how-the-god-orchestrator-works/), his card says
+**BOSS**, and the engine card names all ten engines — it had been advertising three since before
+the other seven shipped. Words-only releases feel trivial until you count how many people meet
+your product through exactly those words.
+
+## 0.4.2 — telemetry, with the contract in writing
+
+We had zero insight into whether anyone even launched the app. 0.4.2 adds anonymous usage
+events — and we did it the only way a [local-first](/blog/why-local-first-matters-for-ai-agents/)
+project credibly can: **TELEMETRY.md** publicly lists every event and property, the code
+enforces that list as a hard allowlist, no prompts or paths or repo names ever leave your
+machine, `DO_NOT_TRACK` is respected unconditionally, and a fork built from source has no key —
+the entire module becomes a no-op. The toggle is right in onboarding.
+
+It's also why this post can contain honest numbers instead of adjectives. As of August 19:
+**2,929 installs, 1,695 people have run at least one agent, and 12,430 agents have been
+spawned.** (Installs, not "users" — download counters lie, install events mostly don't.)
+
+## 0.4.4 — the one Windows was owed
+
+The finale, and it gets [its own post](/blog/launching-munder-difflin-v0-4-4/): agent-to-agent
+messaging on Windows had been silently broken by a cmd.exe newline quirk, first runs never
+started their own hive services, and dark mode was measurably unreadable. All fixed — plus a
+227-skill catalog, a Prerequisites page, and designed release-note pages. It's also the release
+where community contributors show up in force: nine PRs from
+[@gts-47](https://github.com/gts-47) and [@baziyer](https://github.com/baziyer).
+
+{% img "note-3", "The 0.4.4 finale: Windows agents finally get the whole memo, not just its first line." %}
+
+## What the week taught us
+
+Two things. First: **silent failure is the enemy**, not bugs. Almost everything in this train —
+the phantom transcripts, the truncated protocol, the never-started services — failed without a
+single error message. We now treat "nothing errored" as a claim requiring evidence, and we wrote
+[a whole post on why our auto-update never ran](/blog/why-our-auto-update-never-ran/) in the
+same spirit.
+
+Second: release cadence is a form of respect. When someone reports a bug that's blocking them
+and the fix exists on a branch, every day it doesn't ship is a day they're deciding whether to
+uninstall. Seven releases in eight days wasn't heroics. It was queue processing.
diff --git a/blog/src/posts/shareable-agent-roles.md b/blog/src/posts/shareable-agent-roles.md
index 34639015..ae444a6e 100644
--- a/blog/src/posts/shareable-agent-roles.md
+++ b/blog/src/posts/shareable-agent-roles.md
@@ -73,6 +73,8 @@ Here's an *illustrative* manifest (realistic fields, but don't copy-paste it as
Read it top to bottom and it tells you everything: *who* (Jim, the PR reviewer), *what runs it* (Claude Code on a mid-tier model), *how it behaves* (plan mode, so it proposes before acting), *what it's for* (the goal), *what it's good at* (the tags), and *how much it's allowed to spend* (the budget). That's the entire role, and it fits in a screenshot. The point of the format is exactly that legibility: a role you can read, diff, and reason about — not a black box.
+{% img "note-1" %}
+
## Two ways to hire, one pipeline
There are two front doors, and they both lead to the same place.
@@ -88,6 +90,8 @@ This is the heart of the UX, and it's a single, load-bearing rule: **importing a
A few properties make that guarantee real rather than aspirational: there's **no executable in the format** — a manifest names a provider preset, and the actual binary always comes from your own local install, never the file (`provider: "custom"` is rejected outright). The import is **validated and bounded**, so a malformed or oversized manifest is refused, not trusted. The mechanics of treating a downloaded manifest as untrusted input — the validation, the bounds, the threat model — get their own [security deep-dive](/blog/hire-manifest-untrusted-input/); here the takeaway is the principle. **Portability and safety aren't in tension** as long as import is data-only and a human owns the spawn. You can share a role freely *because* sharing it can't, by construction, run anything.
+{% img "note-2" %}
+
## The Hiring Fair: a gallery of ready-made roles
Portable roles are more fun when there's somewhere to get them. **The Hiring Fair** is a static community gallery at [munderdiffl.in/hires](https://munderdiffl.in/hires/) — no login, no trackers, MIT-licensed — stocked with roles from the cast:
diff --git a/blog/src/posts/single-committer-git-pattern.md b/blog/src/posts/single-committer-git-pattern.md
index 85b3c6fd..6a6b9ab3 100644
--- a/blog/src/posts/single-committer-git-pattern.md
+++ b/blog/src/posts/single-committer-git-pattern.md
@@ -72,6 +72,8 @@ git.** Everything else is downstream of that rule.
This collapses a hard concurrency problem into a trivial one. The repo has many *readers* and exactly
one *writer*, which is the configuration git is perfectly happy with.
+{% img "note-1" %}
+
## Making the single committer bulletproof
"One committer" removes contention between agents, but the committer still has to handle the messy
@@ -128,6 +130,8 @@ That pairs naturally with the messaging layer: agents coordinate through files (
those file changes as they happen. The same single-writer discipline runs through both — it's the
backbone of [coordinating AI coding agents](/blog/coordinating-ai-coding-agents/) without collisions.
+{% img "note-2" %}
+
## What about the user's own repo?
A fair question: if agents are editing your *actual* code repository, who commits *that*? The
diff --git a/blog/src/posts/small-team-ai-agents-playbook.md b/blog/src/posts/small-team-ai-agents-playbook.md
index 29ef44e2..8b360054 100644
--- a/blog/src/posts/small-team-ai-agents-playbook.md
+++ b/blog/src/posts/small-team-ai-agents-playbook.md
@@ -51,6 +51,8 @@ problems while they're cheap. Add an agent only when a real bottleneck asks for
orchestrator [coordinate the work](/blog/coordinating-ai-coding-agents/) rather than having agents
free-lance.
+{% img "note-1" %}
+
## Cadence: predictable handoffs beat constant chatter
Agents coordinate best the same way a remote team does — asynchronously, in writing, on a rhythm.
@@ -96,6 +98,8 @@ expensive. The trick is to make the *safe* action the path of least resistance.
None of these slow a good agent down. They just make the failure modes shallow and recoverable, which is
the whole game when you're not watching every keystroke.
+{% img "note-2" %}
+
## A realistic first week
You don't need all of this on day one. A sane rollout:
diff --git a/blog/src/posts/the-clone-army-trap-mixed-swarm-vs-identical-agents.md b/blog/src/posts/the-clone-army-trap-mixed-swarm-vs-identical-agents.md
index a6cd4f98..17994868 100644
--- a/blog/src/posts/the-clone-army-trap-mixed-swarm-vs-identical-agents.md
+++ b/blog/src/posts/the-clone-army-trap-mixed-swarm-vs-identical-agents.md
@@ -82,6 +82,8 @@ efficient: the ability to spend big where it matters and small where it doesn't.
So the clone army's bill isn't "10× one agent." It's 10× *plus* re-derivation *plus* collision-cleanup —
for a result that a smaller, better-organized team would have produced with less drama.
+{% img "note-1" %}
+
## What a mixed swarm does differently
A mixed-capability swarm isn't "the same idea, but cheaper agents." It's a different *structure*, and the
@@ -126,6 +128,8 @@ quality drops the moment you route a genuinely hard subtask to a model that can'
*routing* mistake, not a swarm one. Default lean, escalate the hard minority on signal, and the capability
gap to an all-premium fleet closes to roughly nothing — at a fraction of the tokens.
+{% img "note-2" %}
+
## What "fraction of the tokens" actually means
We won't fabricate a benchmark number, but the direction is not subtle, and it comes from three
diff --git a/blog/src/posts/the-hook-shim-pattern.md b/blog/src/posts/the-hook-shim-pattern.md
index ebcb01b8..f85b4e21 100644
--- a/blog/src/posts/the-hook-shim-pattern.md
+++ b/blog/src/posts/the-hook-shim-pattern.md
@@ -79,6 +79,8 @@ Notice what it does *not* do: no decisions, no disk, no state. It tags the paylo
line of JSON, and relays whatever comes back. And notice the guards — missing socket, connection error,
and a 5-second timeout all `exit(0)`. **The shim can never crash the agent's turn.** That's the contract.
+{% img "note-1" %}
+
## All the logic lives in one process
On the other end, the app's main process listens on that socket and holds everything:
@@ -119,6 +121,8 @@ The danger with any "keep going" mechanism is an infinite loop, so the payload c
flag: if a previous Stop already blocked this turn, the process lets the agent stop. Re-engage once, never
forever. A genuine stop with an empty inbox falls through to a desktop "idle" notification.
+{% img "note-2" %}
+
## Why this pattern is worth copying
If you're wiring agent lifecycle hooks into anything stateful, the shim pattern gives you four things at
diff --git a/blog/src/posts/the-lethal-trifecta-for-coding-agents.md b/blog/src/posts/the-lethal-trifecta-for-coding-agents.md
index fc47856c..f77f25f5 100644
--- a/blog/src/posts/the-lethal-trifecta-for-coding-agents.md
+++ b/blog/src/posts/the-lethal-trifecta-for-coding-agents.md
@@ -72,6 +72,8 @@ Put plainly: **a useful coding agent is, almost by definition, the lethal trifec
to panic — it's a reason to design deliberately, because the thing that makes a coding agent powerful is
exactly the thing that makes it dangerous.
+{% img "note-1" %}
+
## The attack, concretely
You point your agent at a task. Somewhere in what it reads — a dependency's README, a GitHub issue, a doc
@@ -102,6 +104,8 @@ data, can change state or communicate externally}. If a task genuinely needs all
autonomously — it should run with a **human in the loop**. It's the same insight as the trifecta, turned
into a rule you can actually enforce.
+{% img "note-2" %}
+
## Where a hive helps
This is one place a well-built harness earns its keep. Keeping work **local-first** means private data
diff --git a/blog/src/posts/the-multi-agent-cost-playbook.md b/blog/src/posts/the-multi-agent-cost-playbook.md
index 8f298322..35e12052 100644
--- a/blog/src/posts/the-multi-agent-cost-playbook.md
+++ b/blog/src/posts/the-multi-agent-cost-playbook.md
@@ -63,6 +63,8 @@ isn't latency-sensitive at all: overnight reviews, bulk file analysis, [schedule
audits](/blog/scheduling-autonomous-agent-missions/). That work is batchable by design. Caching and
batching together stack on eligible workloads for a large combined discount.
+{% img "note-1" %}
+
## Lever 3 — Model tiering: cheap workers, premium orchestrator
This is the structural multi-agent win. The price spread between a small model and a frontier model is
@@ -95,6 +97,8 @@ that with an in-app usage view ([observability](/blog/observability-for-agent-fl
the bill climb in real time and apply levers 1–4 exactly where they bite. Predictable, attributable cost
is part of the local-first case.
+{% img "note-2" %}
+
## They compound — that's the whole point
These aren't five alternatives; they're five multipliers you apply at once. Cache the stable prefix,
diff --git a/blog/src/posts/the-newline-that-silenced-windows-agents.md b/blog/src/posts/the-newline-that-silenced-windows-agents.md
new file mode 100644
index 00000000..b16dfd2b
--- /dev/null
+++ b/blog/src/posts/the-newline-that-silenced-windows-agents.md
@@ -0,0 +1,107 @@
+---
+title: "The Newline That Silenced Every Windows Agent"
+description: "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."
+date: 2026-08-19
+category: internals
+categoryLabel: Internals
+type: Technical
+primaryKeyword: "cmd.exe newline argument truncation"
+secondaryKeywords: ["windows spawn npm cmd shim", "createprocess cmd.exe", "node spawn windows newline", "electron child_process windows", "npm shim decode"]
+tags: ["Internals", "Windows", "Debugging", "node-pty", "Postmortem"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "Why did agent messaging fail only on Windows?"
+ a: "On macOS and Linux, the multi-line hive protocol passes to the engine binary as one argv entry, newlines intact. On Windows, npm installs CLIs as .cmd shims, which can't go directly to CreateProcess — so the spawn ran through cmd.exe, and cmd.exe cuts an argument at its first newline. The agent got line one of its job description and nothing else."
+ - q: "Why didn't anything error?"
+ a: "Because nothing failed by any definition the code knew. The process spawned, the engine started, the agent answered prompts. The only casualty was the text after the first newline — which happened to contain everything about inboxes, outboxes, and memory. Truncation isn't an error; it's just less."
+ - q: "How was it fixed?"
+ a: "The spawner now reads the .cmd shim, extracts the real interpreter and script it points at, and launches that directly with an argv array — no cmd.exe in the path. A follow-up handled npm's interpreter-less shims for compiled binaries like OpenCode's. Anything undecodable falls back to the old path, but now logs what it couldn't decode."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>Windows agents booted, rendered, and
+answered prompts — while never sending or receiving a single message. The cause: npm installs
+CLIs as <code>.cmd</code> shims, <code>.cmd</code> files must run through <code>cmd.exe</code>,
+and <strong>cmd.exe truncates an argument at its first newline</strong>. Our startup protocol is
+multi-line. Every Windows agent got line one and lost the rest. Here's the full anatomy, because
+this bug class is hiding in more codebases than ours.</p></div>
+
+Half of our downloads are Windows. For an uncomfortably long time, the core of the product —
+[agents talking to each other](/blog/can-claude-code-agents-talk-to-each-other/) — did not work
+for those users, and neither they nor we could tell. This is the autopsy.
+
+## The setup
+
+When Munder Difflin spawns an agent, it passes the **hive protocol** as a command-line argument
+to the engine CLI: a multi-line block that names the agent, points at its `inbox/` and
+`outbox/` folders, explains the [file-mailbox rules](/blog/atomic-file-mailboxes-for-agents/),
+and tells it where its memory lives. One argument, many lines. On POSIX systems this is
+completely unremarkable — argv entries can contain any byte except NUL, and newlines ride along
+happily.
+
+## The three-layer trap
+
+**Layer one: npm shims.** On Windows, `npm install -g` doesn't put a real executable on your
+PATH. It writes a `.cmd` batch shim that locates node and runs the actual JS entry point.
+
+**Layer two: CreateProcess.** A `.cmd` is not a PE executable, so it can't be the target of
+`CreateProcess` directly. Node's `child_process` (and everything built on it) handles this by
+silently rewriting your spawn into `cmd.exe /d /s /c "your command here"`.
+
+**Layer three: cmd.exe.** And cmd.exe, parsing that command string with rules essentially
+unchanged since DOS, **stops at the first newline**. Everything after it isn't escaped or
+mangled — it's simply gone.
+
+{% img "note-1", "Three layers deep: npm's .cmd shim forces cmd.exe into the spawn path, and cmd.exe stops reading at the first newline." %}
+
+Stack the layers and you get: a multi-line protocol enters the spawn, and a one-line protocol
+arrives at the agent. Deterministically. On every Windows machine. With zero errors.
+
+## Why it was invisible
+
+Here's what made this bug expensive: **every observable signal said healthy.**
+
+The process spawned — exit code irrelevant, it's a long-running CLI. The agent's terminal
+rendered in the app and responded to typing. The engine received *a* prompt (line one:
+something like "You are an autonomous agent in a collaborating hive"), which is coherent enough
+that the agent behaved plausibly. It just never mentioned inboxes, because it had never heard
+of them.
+
+From the floor's perspective, Windows agents were simply... quiet. And "the agent didn't happen
+to send mail" is indistinguishable from "the agent cannot send mail" unless you go looking. No
+log line existed to catch, because truncation isn't a failure — cmd.exe was working as
+documented. The documentation is just from 1987.
+
+{% img "note-2", "Every signal read healthy: process up, terminal live, prompts answered. The agent just never knew it had a mailbox." %}
+
+## The fix: refuse the middleman
+
+The fix is conceptually simple: **never let a prompt-carrying spawn touch cmd.exe.** The spawner
+now opens the `.cmd` shim, decodes what it actually points at — npm shims are formulaic — and
+launches the real interpreter directly: `node.exe C:\...\cli.js --args`, passed as an argv
+array, which goes through `CreateProcess` with the multi-line argument intact.
+
+Then reality added a second chapter, as it does. OpenCode's npm package ships a *compiled
+binary*, so npm writes an interpreter-less shim the decoder didn't model — it returned null for
+every Windows OpenCode install and fell back to the truncating path. That's the
+[0.4.4](/blog/launching-munder-difflin-v0-4-4/) follow-up: direct-executable shims are handled,
+and — the real lesson — **the fallback is no longer silent.** If the decoder meets a shim it
+can't parse, it logs exactly what it couldn't decode. The next variant of this bug will
+announce itself.
+
+## The takeaways we actually wrote down
+
+- **A fallback that doesn't log is a bug with a delay timer.** The first fix's silent fallback
+ is why the OpenCode variant survived a release.
+- **"Nothing errored" is a claim, not evidence.** The failure mode of dropping *part* of an
+ input is nastier than crashing, because every health check you own passes. Our
+ [auto-update postmortem](/blog/why-our-auto-update-never-ran/) is the same lesson wearing a
+ different coat.
+- **Test the platform's spawn path, not your code's intent.** Our protocol handling was
+ correct on every platform. The three layers underneath it were not ours — and the user
+ doesn't care whose layer it was.
+
+If you're building anything that passes structured prompts to CLIs on Windows —
+[hooks](/blog/the-hook-shim-pattern/), harnesses, wrappers — go check what your spawns do when
+the target is a `.cmd`. We'll wait. It's probably ten minutes and one very bad surprise.
diff --git a/blog/src/posts/the-office-parody-behind-munder-difflin.md b/blog/src/posts/the-office-parody-behind-munder-difflin.md
index 90e55141..acb54126 100644
--- a/blog/src/posts/the-office-parody-behind-munder-difflin.md
+++ b/blog/src/posts/the-office-parody-behind-munder-difflin.md
@@ -46,6 +46,8 @@ aesthetic with a Dunder-Mifflin-maroon-and-gold coat of paint. (To be clear up f
It would be easy to read all of that as set dressing. It isn't. The metaphor was chosen because it
*teaches*.
+{% img "note-1" %}
+
## Why an office is the right metaphor for a hive
Here's the quiet insight: humanity has spent a century refining an answer to the question "how do a
@@ -86,6 +88,8 @@ The parody isn't skin-deep; it's wired through the real software:
gold. None of it is required to run agents — all of it makes running them feel like managing a team
instead of babysitting a script.
+{% img "note-2" %}
+
## Why playful beats po-faced here
There's a real argument that the humor is a *feature*, not a distraction:
diff --git a/blog/src/posts/tmux-and-scripts-vs-an-agent-harness.md b/blog/src/posts/tmux-and-scripts-vs-an-agent-harness.md
index 9458b050..ba93405a 100644
--- a/blog/src/posts/tmux-and-scripts-vs-an-agent-harness.md
+++ b/blog/src/posts/tmux-and-scripts-vs-an-agent-harness.md
@@ -50,6 +50,8 @@ If you're running two agents on two branches and reviewing everything yourself,
None of these are tmux's fault. tmux is a terminal multiplexer, and it's excellent at multiplexing terminals. Everything above is a *coordination* problem, and coordination is a different program — one you end up writing yourself, script by script, incident by incident.
+{% img "note-1" %}
+
## What a harness automates
This is the layer [Munder Difflin](/) is. Our landing page has a [full comparison table](/#compare), but it maps almost one-to-one onto the breakage list:
@@ -63,6 +65,8 @@ This is the layer [Munder Difflin](/) is. Our landing page has a [full compariso
Crucially, the terminals are still terminals. Every agent is the real CLI — Claude Code, Codex, Copilot CLI, and four others — running in a real pseudo-terminal you can pop open and type into, exactly like the pane you left behind.
+{% img "note-2" %}
+
## The honest framing
The DIY path isn't wrong; it's version one. Every feature above started life as somebody's shell script, and if you kept iterating on your tmux setup — add a router script, a memory file, a budget checker, a Slack bridge, a recovery script — you'd converge on a harness. Munder Difflin is that convergence, already built, MIT-licensed, and local-first, so the six months of scripting goes into your actual work instead.
diff --git a/blog/src/posts/trigger-ai-agents-from-github-webhook.md b/blog/src/posts/trigger-ai-agents-from-github-webhook.md
index e242b3c5..edc5c7a6 100644
--- a/blog/src/posts/trigger-ai-agents-from-github-webhook.md
+++ b/blog/src/posts/trigger-ai-agents-from-github-webhook.md
@@ -70,6 +70,8 @@ but unguarded. The tunnel is a doorbell; it is not what keeps strangers out.
Copy the public URL. You'll paste it into GitHub next.
+{% img "note-1" %}
+
## Step 2 — Point GitHub at it
You have two clean ways to do this, depending on how literal you want to be.
@@ -148,6 +150,8 @@ exactly like work that arrives through [the hive's normal message
routing](/blog/coordinating-ai-coding-agents/). A reviewer agent might read the PR; a writer might draft the
issue response. The webhook doesn't pick the agent — it just gets the work onto the board.
+{% img "note-2" %}
+
## Security, in one breath
A public endpoint that can enqueue work for autonomous agents is exactly what you don't want strangers poking,
diff --git a/blog/src/posts/trigger-ai-agents-from-slack.md b/blog/src/posts/trigger-ai-agents-from-slack.md
index 2b59398a..c709187d 100644
--- a/blog/src/posts/trigger-ai-agents-from-slack.md
+++ b/blog/src/posts/trigger-ai-agents-from-slack.md
@@ -58,6 +58,8 @@ Subscriptions → Request URL*. That tunnel is just a doorbell: it forwards Slac
port. If it can't be established, the local handler stays up anyway — the tunnel is a convenience, not
the security boundary.
+{% img "note-1" %}
+
## Security: verify everything before you trust it
A webhook that can enqueue work for autonomous agents is exactly the kind of endpoint you don't want
@@ -88,6 +90,8 @@ You can scope what counts, too. An optional **channel filter** means only messag
channel are accepted; events from anywhere else are dropped before they ever reach the queue. That
keeps a noisy workspace from turning into a noisy hive.
+{% img "note-2" %}
+
## Setting it up
The moving parts are minimal. In the app you enable Slack and paste your **signing secret** (from your
diff --git a/blog/src/posts/turn-feedback-into-a-backlog-with-agents.md b/blog/src/posts/turn-feedback-into-a-backlog-with-agents.md
new file mode 100644
index 00000000..505b0e06
--- /dev/null
+++ b/blog/src/posts/turn-feedback-into-a-backlog-with-agents.md
@@ -0,0 +1,94 @@
+---
+title: "Turn a Firehose of Feedback into a Backlog with Agents"
+description: "516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts."
+date: 2026-08-19
+category: use-cases
+categoryLabel: Use Cases
+type: Non-technical
+primaryKeyword: "ai agents process user feedback"
+secondaryKeywords: ["feedback triage automation", "turn comments into backlog", "user feedback analysis ai", "product feedback workflow", "munder difflin use case"]
+tags: ["Use Cases", "Feedback", "Workflow", "Product", "Multi-Agent"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "How do agents turn raw comments into a backlog?"
+ a: "Three passes: bucket every comment (bug, feature ask, objection, praise) with quotes and links preserved; merge duplicates across channels so five phrasings of one problem become one item with five receipts; then rank by evidence — how many distinct people, how serious, how blocked. The output is kanban cards whose descriptions cite the actual users."
+ - q: "What's the advantage over just reading the comments yourself?"
+ a: "Coverage and honesty. A human skims, remembers the loudest five comments, and calls it the community's opinion. An agent instructed to account for every comment can't skip the boring middle — and the resulting backlog item carries links to every person who reported it, which also gives you a list of exactly who to tell when it ships."
+ - q: "Did this actually change what Munder Difflin shipped?"
+ a: "Directly. The launch-week backlog put the Windows messaging failure and onboarding dead-ends at the top on evidence volume, and both headline v0.4.4. The 'this decision needs your eyes' flag — asked for independently by two users on two different channels — is on the roadmap because cross-channel merging revealed it was one request, not two."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>Feedback is an asset with a
+half-life: unprocessed, it decays into a vibe. After launch week handed us <strong>516 Reddit
+comments, a Product Hunt thread, and a swelling issue tracker</strong>, agents turned all of it
+into a ranked backlog where every card cites the real humans who asked. Two of the top three
+cards shipped in v0.4.4. The workflow, start to finish.</p></div>
+
+Launch-week feedback has a cruel shape: it arrives all at once, from five channels, in wildly
+mixed quality, precisely when you have the least attention to spare. Read it casually and
+you'll remember the funniest insult and the nicest compliment, then confidently misbuild your
+roadmap around them both.
+
+The fix isn't discipline. It's admitting this is a data-processing job and
+[staffing it accordingly](/blog/small-team-ai-agents-playbook/).
+
+## Pass one: account for everything
+
+The first pass is deliberately dumb: every comment, from every channel, gets bucketed —
+**bug report, feature ask, objection, praise, question** — with the quote, the author, and the
+permalink preserved. The brief's key sentence is *account for every comment*, because that's
+the sentence a tired human violates. Ours came back with counts we still quote in arguments:
+utility skepticism, 12 distinct commenters; token-cost concern, 11.
+
+The receipts matter more than the counts. "Users are worried about cost" starts a debate;
+eleven linked quotes end one.
+
+## Pass two: merge across channels
+
+{% img "note-1", "Five phrasings, two platforms, one problem. Cross-channel merging is where the signal actually lives." %}
+
+The pass most teams never do, because it requires holding everything at once. The same problem
+arrives dressed differently per platform: a Product Hunt commenter politely reports being
+unable to switch engines after setup; a Redditor says the onboarding dead-ended; a GitHub
+issue titles it precisely. One agent with all three corpora merges them into **one backlog
+item with five receipts** — and suddenly it's not three small complaints, it's one bug class
+blocking a fifth of new evaluators.
+
+This pass produced our best roadmap insight of the year: our two most sophisticated users — on
+*different platforms, in different words* — asked for the same missing primitive, a visible
+"this decision needs your eyes" flag on agents. Read channel by channel, that's two mild
+comments. Merged, it's the [clearest feature signal we've ever
+received](/blog/human-in-the-loop-ai-agents/).
+
+## Pass three: rank on evidence, file as work
+
+The final pass turns merged items into kanban cards, ranked by things you can defend: how many
+distinct people, how blocked they were, whether they're the kind of user you're building for.
+The card's description carries the quotes and links, so whoever picks it up — human or
+[agent](/blog/deploy-automated-pr-reviewer-agent/) — starts from the actual reports rather
+than a paraphrase.
+
+Then the backlog met reality: the top cards became
+[v0.4.4's headline fixes](/blog/launching-munder-difflin-v0-4-4/). And because every card
+carried its reporters, "tell the people who reported it" was a checklist item, not archaeology.
+One blocked user from launch week had said, verbatim, that he'd re-test when the fix shipped.
+The card knew his name. That follow-up is worth more than a week of marketing.
+
+{% img "note-2", "The card remembers who reported it — so shipping the fix comes with a list of exactly who to tell." %}
+
+## The compounding part
+
+Do this once and it's a great retro. The compounding version is a **standing intake**: the
+same bucketing agent runs on whatever accumulated overnight — new issues, Discord threads,
+stray mentions — and appends to the same backlog under the same merge rules, on a
+[schedule](/blog/scheduling-autonomous-agent-missions/). Feedback stops being an event and
+becomes a pipeline, and the backlog stays ranked by evidence instead of by whoever shouted
+most recently.
+
+The uncomfortable, useful truth we took from ours:
+[the community's](/blog/what-reddit-told-us-about-munder-difflin/) most upvoted praise and its
+sharpest criticism pointed at the same place — people love *watching* agents work and want
+more *control* over what they see. A backlog built on receipts forces you to hear both halves.
+That tension is now the roadmap's spine, and we can cite our sources.
diff --git a/blog/src/posts/vibe-kanban-alternative.md b/blog/src/posts/vibe-kanban-alternative.md
index e217f4fc..652518de 100644
--- a/blog/src/posts/vibe-kanban-alternative.md
+++ b/blog/src/posts/vibe-kanban-alternative.md
@@ -39,6 +39,8 @@ cards, assign them to agents, and move them through columns from to-do to in-pro
If you think in tasks and want a project-management surface over your agents, vibe-kanban fits
naturally. The reason to look elsewhere is about *who does the routing*.
+{% img "note-1" %}
+
## Where a board leaves the work to you
A kanban board is something a human drives. That's its strength and its ceiling:
@@ -57,6 +59,8 @@ doesn't compound.
Coordination between cards goes through you and the board, not agent-to-agent. There's no mailbox for
one agent to hand a finding directly to another.
+{% img "note-2" %}
+
## What a self-routing hive does instead
The alternative flips the model: instead of *you* working a board, you describe intent and the system
diff --git a/blog/src/posts/visualizing-ai-agents-pixijs.md b/blog/src/posts/visualizing-ai-agents-pixijs.md
index 09ba6f18..524e6447 100644
--- a/blog/src/posts/visualizing-ai-agents-pixijs.md
+++ b/blog/src/posts/visualizing-ai-agents-pixijs.md
@@ -69,6 +69,8 @@ One more structural choice: a **single shared ticker** drives all animation. Eve
hands out a delta-time and each live thing (avatars, envelopes, camera) advances by `dt`. One loop,
not dozens of timers — which keeps motion synchronized and the frame budget predictable.
+{% img "note-1" %}
+
## The floor is a Tiled map
The office isn't hand-coded geometry; it's a **Tiled** map (`.tmj`) — the same format 2D game
@@ -99,6 +101,8 @@ distinguishable at a glance.
But the sprites are just the *body*. What makes them meaningful is what drives them.
+{% img "note-2" %}
+
## The honest part: real events, not a script
This is the design principle that matters most. The avatars are **not** playing a canned animation —
diff --git a/blog/src/posts/voice-as-a-control-plane-for-agent-fleets.md b/blog/src/posts/voice-as-a-control-plane-for-agent-fleets.md
index 5a93d469..1928333f 100644
--- a/blog/src/posts/voice-as-a-control-plane-for-agent-fleets.md
+++ b/blog/src/posts/voice-as-a-control-plane-for-agent-fleets.md
@@ -46,6 +46,8 @@ Each of these is a sentence. Each fans out into minutes or hours of high-bandwid
The other half of the fit: orchestration is naturally *ambient*. You're across the room while an overnight mission grinds. A status question shouldn't cost you a walk to the desk, and a completion shouldn't wait until you happen to glance at a terminal.
+{% img "note-1" %}
+
## Case study: Talk mode
Munder Difflin shipped this thesis as a feature in v0.3.2 (the [launch post](/blog/launching-munder-difflin-v0-3-2/) has the full tour). Press **Talk** and you get a low-latency voice channel — OpenAI Realtime API over WebRTC, bring-your-own key — to Michael, the GOD orchestrator, running *alongside* the async terminal floor, not replacing it.
@@ -54,6 +56,8 @@ Michael listens, answers, and acts. The read side covers the hive: tasks, board,
And the loop closes in both directions. Voice-dispatched work reports back on its own: a completion watcher detects when a task lands and pushes the event into the live session so **Michael speaks it unprompted** — "respond when done" as a first-class behavior, with an on-screen toast, and a queue-to-notification path if the session is already closed. That's the ambient half delivered: you delegated by sentence, and the result comes back as a sentence.
+{% img "note-2" %}
+
## A control plane needs guardrails, not vibes
Here's where "control plane" stops being a metaphor and starts being an engineering standard. A microphone is a noisy, spoofable, mishearable input device wired to verbs like *kill*. If you treat that casually, you've built a gimmick with a blast radius. Talk mode's guardrails are the interesting part:
diff --git a/blog/src/posts/we-opened-a-discord.md b/blog/src/posts/we-opened-a-discord.md
new file mode 100644
index 00000000..7254e3c6
--- /dev/null
+++ b/blog/src/posts/we-opened-a-discord.md
@@ -0,0 +1,85 @@
+---
+title: "We Opened a Discord (Merge a PR, Become Employee of the Month)"
+description: "Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source."
+date: 2026-08-19
+category: story
+categoryLabel: Story
+type: Non-technical
+primaryKeyword: "munder difflin discord"
+secondaryKeywords: ["munder difflin community", "open source discord server", "contribute to munder difflin", "claude code community"]
+tags: ["Story", "Community", "Discord", "Open Source"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "Where is the Munder Difflin Discord?"
+ a: "discord.gg/SEDzP5ZPk5 — also linked from the site nav, the footer, and the README. It's free, it's where release news lands first, and it's the fastest way to get help with a setup problem or show off what your floor is doing."
+ - q: "What is the employee of the month role?"
+ a: "Merge a pull request into Munder Difflin and a GitHub workflow automatically grants you the 'employee of the month' role in the Discord. There's an optional Discord field in the PR template so the bot knows who to promote. It's a joke that's also completely sincere."
+ - q: "Why a Discord and not GitHub Discussions?"
+ a: "GitHub stays the home for issues and PRs — bugs belong where the code is. What launch week showed is that people also want a lower-stakes room: quick setup questions, sharing screenshots of their office floor, and hearing what's shipping before it ships. That's chat-shaped, not issue-shaped."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>Munder Difflin has a Discord:
+<a href="https://discord.gg/SEDzP5ZPk5">discord.gg/SEDzP5ZPk5</a>. Release news first, setup
+help fastest, floor screenshots welcome. And a workflow now watches the repo: <strong>merge a
+PR, and you're automatically granted the <em>employee of the month</em> role.</strong> We
+regret nothing about this feature and never will.</p></div>
+
+For a product that's an office homage, we were weirdly hard to hang out with. Feedback lived
+in GitHub issues, launch threads on
+[Reddit](/blog/what-reddit-told-us-about-munder-difflin/) and
+[Product Hunt](/blog/number-five-on-product-hunt/), and an inbox we won't discuss. Launch week
+made the gap obvious: between "formal bug report" and "shouting into a Reddit thread" there
+was nowhere to just… ask a quick question. Or post a screenshot of nine agents pulling an
+all-nighter.
+
+So: **[discord.gg/SEDzP5ZPk5](https://discord.gg/SEDzP5ZPk5)**. The lobby is open.
+
+## What it's for
+
+**Release news, first.** We just shipped
+[seven releases in eight days](/blog/seven-releases-in-eight-days/); Discord is where drops
+get announced the moment they're tagged, and where we'll be honest about what's still rough.
+
+**Setup help, fast.** A meaningful share of launch-week frustration was
+[first-run problems](/blog/launching-munder-difflin-v0-4-4/) that a two-minute conversation
+would have solved. If onboarding fights you, come fight back in a channel where someone's
+awake — the community spans enough timezones now that someone usually is.
+
+**Show your floor.** The screenshots people posted during launch week — offices mid-swarm,
+agents [working through the night](/blog/claude-code-automation-while-you-sleep/) — were the
+best part of the whole launch. They deserve a wall. This is the wall.
+
+{% img "note-1", "Between 'formal bug report' and 'Reddit thread' there was nowhere to just ask. Now there's a lobby." %}
+
+## Employee of the month
+
+Here's the part we're irrationally proud of. Contributing to Munder Difflin now comes with a
+title: **merge a pull request, and a GitHub workflow automatically grants you the *employee of
+the month* role in the Discord.** The PR template has an optional `Discord:` field so the bot
+knows who to celebrate. No nomination committee, no monthly limit, no plaque in a hallway —
+just a workflow that fires on merge, because in this office, recognition is automated too.
+
+The inaugural class earned it properly:
+[v0.4.4 carries nine community PRs](/blog/launching-munder-difflin-v0-4-4/) —
+[@gts-47](https://github.com/gts-47) with eight, from atomic task-ledger writes to un-silencing
+an agent's wake nudge, and [@baziyer](https://github.com/baziyer) with the fix that stops the
+office floor rendering when nobody's watching it. If you've been thinking about a first
+contribution, the [good-first-issue path](https://github.com/chaitanyagiri/munder-difflin)
+now ends with a job title.
+
+{% img "note-2", "Merge a PR, get the role. Recognition is a workflow now, like everything else around here." %}
+
+## The rules of the room
+
+Short version: GitHub remains the source of truth — bugs and feature requests belong in
+issues, where they [get triaged into real work](/blog/turn-feedback-into-a-backlog-with-agents/)
+rather than scrolling away. The Discord is for everything that's conversation-shaped. Be kind,
+assume good faith, and if you built something weird with your hive, we absolutely want to see
+it.
+
+The product has always been a bet that work is better with
+[a floor full of colleagues you can see](/blog/building-an-ai-office-floor/). It was overdue
+that the humans got a floor too. Come say hi:
+**[discord.gg/SEDzP5ZPk5](https://discord.gg/SEDzP5ZPk5)**.
diff --git a/blog/src/posts/what-are-claude-code-agents.md b/blog/src/posts/what-are-claude-code-agents.md
index a1fba9c7..476c3171 100644
--- a/blog/src/posts/what-are-claude-code-agents.md
+++ b/blog/src/posts/what-are-claude-code-agents.md
@@ -41,6 +41,8 @@ That's it. Every terminal where you start a `claude` session is an agent: one go
window, one loop. The magic isn't the word "agent" — it's that the loop can use tools and keep going
until the job's done.
+{% img "note-1" %}
+
## Agents vs. subagents
These two get conflated constantly, so let's separate them:
@@ -73,6 +75,8 @@ That's the wall every multi-agent setup hits. The fix isn't more agents — it's
the practical playbook in [how to run multiple Claude Code
agents](/blog/how-to-run-multiple-claude-code-agents/).
+{% img "note-2" %}
+
## What turns agents into a team
Three additions turn parallel sessions into something that behaves like a team:
diff --git a/blog/src/posts/what-is-a-multi-agent-harness.md b/blog/src/posts/what-is-a-multi-agent-harness.md
index 9e7c0152..66176ece 100644
--- a/blog/src/posts/what-is-a-multi-agent-harness.md
+++ b/blog/src/posts/what-is-a-multi-agent-harness.md
@@ -36,6 +36,8 @@ alt-tabbing between windows. A **multi-agent harness** is the software that fixe
That's the whole idea. Everything else is detail about *how* the coordination happens.
+{% img "note-1" %}
+
## What it adds on top of a single agent
A single agent is a loop: read context, take an action, repeat. A harness wraps **many** of those
@@ -49,6 +51,8 @@ loops and adds the parts a lone agent doesn't have:
that's the [GOD orchestrator](https://munderdiffl.in/#how), an agent you talk to in plain language.
- **Visibility.** A way to *see* what the team is doing, so it's not a black box.
+{% img "note-2" %}
+
## Harness vs. framework vs. subagents
These three get conflated. The difference is what you bring to the table:
diff --git a/blog/src/posts/what-is-aeo-for-dev-tools.md b/blog/src/posts/what-is-aeo-for-dev-tools.md
index 86c5dacc..ac24d604 100644
--- a/blog/src/posts/what-is-aeo-for-dev-tools.md
+++ b/blog/src/posts/what-is-aeo-for-dev-tools.md
@@ -57,6 +57,8 @@ The good news: you don't choose between them. AEO is mostly SEO done with a tigh
clearer answers, stronger structure, honest facts. A page that an LLM can confidently quote is also a
page Google's AI Overviews and traditional results reward.
+{% img "note-1" %}
+
## Why dev tools should care more than most
Developer tools sit at the perfect intersection for AEO:
@@ -180,6 +182,8 @@ README, and topics all feed the same entity. And keep content fresh — but **ho
`lastmod` dates and genuine updates help; faking freshness by bumping dates on unchanged pages is the
kind of manipulation that gets discounted. Update when you actually have something new.
+{% img "note-2" %}
+
## How to measure AEO (when there's no rank tracker)
AEO has no clean "position 3" metric, so measure it directly: **ask the engines.** On a monthly
diff --git a/blog/src/posts/what-is-an-agent-development-environment.md b/blog/src/posts/what-is-an-agent-development-environment.md
index a9233e78..8f15cd85 100644
--- a/blog/src/posts/what-is-an-agent-development-environment.md
+++ b/blog/src/posts/what-is-an-agent-development-environment.md
@@ -38,6 +38,8 @@ Then the coding-tools world borrowed the acronym for something adjacent but dist
Most people saying "ADE" in a dev-tools context mean the second sense. That's the sense this post maps.
+{% img "note-1" %}
+
## The 2026 landscape: four layers of delegation
The clean way to sort the tools is not by feature list but by **how much you hand over**.
@@ -50,6 +52,8 @@ The clean way to sort the tools is not by feature list but by **how much you han
**4. Agent harnesses / offices — the agents coordinate each other.** This is where **Munder Difflin** sits, and it's a different bet. Like an ADE, it runs real CLI agents (seven engines as of v0.3.3, including GitHub Copilot CLI) in isolated worktrees and real pseudo-terminals. Unlike an ADE, you don't dispatch to each agent yourself: a GOD orchestrator — Michael — routes work, agents message each other through mailboxes, share [long-term semantic memory](/blog/semantic-memory-for-ai-agents/), and get woken by triggers — typing, Slack, webhooks, schedules, even voice. Guardrails (approval gates, per-agent budgets, a circuit breaker, OTel observability) make it safe to leave running. The mental model isn't "my editor got agents" or "my agents got lanes" — it's *an office you supervise*. We've written a fuller definition in [what is a multi-agent harness](/blog/what-is-a-multi-agent-harness/).
+{% img "note-2" %}
+
## Where the categories blur
Nobody stays in their lane, and the direction of travel is telling.
diff --git a/blog/src/posts/what-is-harness-engineering.md b/blog/src/posts/what-is-harness-engineering.md
index 3aac818f..8299a6af 100644
--- a/blog/src/posts/what-is-harness-engineering.md
+++ b/blog/src/posts/what-is-harness-engineering.md
@@ -40,6 +40,8 @@ The broader discourse picked the term up fast, and a rough consensus formed: har
That's the whole thesis in one line: **the model is a commodity input; the harness is the differentiated system.** Frontier models leapfrog each other every quarter, and every serious agent product supports several of them interchangeably. What doesn't come off a shelf is the machinery that makes any of them dependable.
+{% img "note-1" %}
+
## What a harness actually contains
Strip the buzzwords and a production harness is a specific list of unglamorous subsystems:
@@ -55,6 +57,8 @@ Strip the buzzwords and a production harness is a specific list of unglamorous s
Notice what's absent: anything about making the model smarter. Harness engineering takes model capability as given and engineers everything else. (For how this differs from a single-agent wrapper, see [what a multi-agent harness is](/blog/what-is-a-multi-agent-harness/).)
+{% img "note-2" %}
+
## Four case studies from inside Munder Difflin
Munder Difflin is this discipline shipped as a product, so its internals make good worked examples.
diff --git a/blog/src/posts/what-reddit-told-us-about-munder-difflin.md b/blog/src/posts/what-reddit-told-us-about-munder-difflin.md
new file mode 100644
index 00000000..d992a449
--- /dev/null
+++ b/blog/src/posts/what-reddit-told-us-about-munder-difflin.md
@@ -0,0 +1,109 @@
+---
+title: "What 516 Reddit Comments Told Us About Munder Difflin"
+description: "We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it."
+date: 2026-08-19
+category: story
+categoryLabel: Story
+type: Non-technical
+primaryKeyword: "munder difflin reddit launch"
+secondaryKeywords: ["reddit launch retrospective", "launching dev tools on reddit", "r/ClaudeCode", "ai agent tool feedback"]
+tags: ["Story", "Launch", "Reddit", "Community", "Open Source"]
+author:
+ name: Chaitanya Giri
+ initials: CG
+faq:
+ - q: "How did the Munder Difflin Reddit launch go?"
+ a: "Ten posts across ten subreddits earned a combined score of 2,233 and 516 comments. r/ClaudeCode alone contributed 1,017 upvotes — almost half of everything — while r/OpenAI and r/selfhosted barely registered. The audience that already runs Claude Code all day understood the product instantly; everyone else needed more explaining than a screenshot can do."
+ - q: "What did Reddit criticize about Munder Difflin?"
+ a: "Three things, honestly: skepticism that a visual layer adds real utility over raw terminals, worry about token costs when running many agents, and fatigue with the orchestration-tool category in general. All three are fair, and two of them shaped what we shipped next — clearer budget controls and less theater, more control."
+ - q: "What did people like most?"
+ a: "Visibility. The most-upvoted comments were about glancing at the floor and knowing who's stuck versus who's working, watching envelopes move between agents' inboxes and outboxes, and the fact that the whole thing runs locally on files you can read yourself."
+---
+
+<div class="callout tldr"><span class="ic">TL;DR</span><p>Our Reddit launch: <strong>ten posts,
+2,233 combined upvotes, 516 comments</strong>. Nearly half the engagement came from one
+subreddit — r/ClaudeCode — and two communities ignored us entirely. We read all 516 comments,
+sorted them into what resonated, what got roasted, and what got fixed. This is that sorting,
+published.</p></div>
+
+Launch week, we posted Munder Difflin to ten subreddits over a few days. Not the same post ten
+times — each one angled for its community — and then the comments started, and did not stop for
+a week.
+
+## Where it landed, and where it didn't
+
+The distribution was brutal and informative. **r/ClaudeCode delivered 1,017 upvotes — 46% of
+all engagement from one community.** People who already run
+[multiple Claude Code sessions](/blog/how-to-run-multiple-claude-code-agents/) didn't need the
+pitch; they recognized the problem from the screenshot alone.
+
+The flops taught us just as much. r/OpenAI and r/selfhosted barely moved. In hindsight both make
+sense: r/OpenAI's crowd doesn't live in Claude Code, and r/selfhosted heard "Electron app that
+drives commercial AI subscriptions" and reasonably shrugged. A launch angle that works is mostly
+audience selection, not copywriting.
+
+{% img "note-1", "Ten subreddits, one clear winner: the people already drowning in Claude Code terminals didn't need the pitch." %}
+
+## What resonated
+
+Reading 516 comments in bulk, three themes kept earning upvotes:
+
+**Visibility.** The single most-upvoted non-post comment in the whole corpus was someone
+describing exactly the moment we built the office floor for: glancing at the screen and knowing
+the state of five working sessions without tailing five terminals. When people praised the
+product, they praised *knowing what's happening* — the floor, the envelopes physically traveling
+between desks, [the terminals you can pop open](/blog/building-a-terminal-ui-xterm-node-pty/) on
+any agent at any moment.
+
+**The mechanics being inspectable.** The [inbox/outbox file
+protocol](/blog/atomic-file-mailboxes-for-agents/) came up again and again, positively. Reddit's
+technical crowd trusts what it can `cat`. The fact that every message between agents is a JSON
+file on your own disk did more persuading than any diagram.
+
+**Local, on your own machine.** Everything runs where your code already lives, against the
+Claude plan you already have — no service in the middle. The what's-the-catch crowd could
+answer their own question by reading the source, and several did exactly that before saying
+anything nice.
+
+The best moment of the week wasn't a compliment, though. Another builder took a feature from his
+own rival project, **forked Munder Difflin, and sent us a pull request the same day**. That's
+the open-source version of a standing ovation.
+
+{% img "note-2", "The best compliment of launch week arrived as a pull request from a rival project, the same day." %}
+
+## What got roasted
+
+Publishing only the praise would be exactly the launch-retro genre we hate, so:
+
+**"Is this actually useful, or is it theater?"** The most common objection — a dozen distinct
+commenters. Watching pixel-art agents walk envelopes around is charming; charm is not utility.
+Our answer then and now: the simulation is deterministic and costs zero tokens, and the utility
+lives underneath it — routing, memory, lifecycle. But the burden of proof is ours, and it's why
+our sharpest users' asks are about *control* surfaces, not prettier sprites.
+
+**Token cost.** Eleven commenters worried that a floor full of agents burns money. Fair — which
+is why budgets and caps exist, and why we wrote
+[the multi-agent cost playbook](/blog/the-multi-agent-cost-playbook/) and keep
+[model routing](/blog/do-more-with-less-model-routing/) cheap by default: one strong
+orchestrator, inexpensive workers.
+
+**Category fatigue.** "Another Claude Code orchestrator" is a real sentiment in 2026, and some
+power users said plainly they want less theater and more control. We took that phrase seriously
+enough that it's become an internal design test.
+
+**And the bugs.** Windows users showed up, tried it, and hit real walls — which fed directly
+into [v0.4.4](/blog/launching-munder-difflin-v0-4-4/), the release where Windows agents can
+finally talk to each other. Several onboarding dead-ends reported in those threads are fixed in
+the same release. If you bounced off Munder Difflin in launch week on Windows: it's worth a
+second look now.
+
+## What we're taking away
+
+Reddit gave us the stadium; [Product Hunt](/blog/number-five-on-product-hunt/) gave us the
+panel interview. The stadium's verdict, compressed: **charm gets people in the door; visibility
+and control keep them.** The people who stayed cited watching state and steering it. The people
+who left cited theater and cost. Every roadmap argument we've had since launch week ends by
+re-reading one of those 516 comments.
+
+We didn't skim them. We [pointed agents at the threads](/blog/agents-ran-our-launch-week-analytics/)
+and made them account for every single comment — but that's its own story.
diff --git a/blog/src/posts/whats-new-in-agentic-ai-june-2026.md b/blog/src/posts/whats-new-in-agentic-ai-june-2026.md
index ab61aaa0..05ffa64f 100644
--- a/blog/src/posts/whats-new-in-agentic-ai-june-2026.md
+++ b/blog/src/posts/whats-new-in-agentic-ai-june-2026.md
@@ -71,6 +71,8 @@ frontier lab is now orchestrating subagents inside its own coding tool, the case
not weaker. (For the broader tool landscape, see our
[roundup of multi-agent Claude Code tools](/blog/best-claude-code-multi-agent-tools/).)
+{% img "note-1" %}
+
## Agent coordination is becoming a protocol layer
A year ago, every framework invented its own way for agents to reach tools and each other. That's
@@ -106,6 +108,8 @@ signal yet that **agentic coding is a metered resource**, priced like compute ra
core argument for [why local-first matters for AI agents](/blog/why-local-first-matters-for-ai-agents/): a
hive that runs on your machine and logs its own activity puts the meter where you can see it.
+{% img "note-2" %}
+
## Governance and identity grew up
The enterprise side of agents got its control plane.
diff --git a/blog/src/posts/whats-up-with-munder-difflin.md b/blog/src/posts/whats-up-with-munder-difflin.md
index 62cfe6a1..b5f8a087 100644
--- a/blog/src/posts/whats-up-with-munder-difflin.md
+++ b/blog/src/posts/whats-up-with-munder-difflin.md
@@ -73,6 +73,8 @@ prints in its terminal and it opens rendered. In the IDE, markdown files get a
code | split | preview switch that re-renders live. There's no raw-HTML pipeline anywhere in
it, which is the only way reading agent-generated files is safe by construction.
+{% img "note-1" %}
+
## Nine engines
**xAI Grok** and **Kimi Code** joined, bringing the roster to nine: Claude Code, OpenAI
@@ -129,6 +131,8 @@ didn't, agents died with a bare exit code and no explanation.
and Pixi reported nothing at all, so it just went blank until you restarted. It notices and
rebuilds itself now.
+{% img "note-2" %}
+
## And then: auto-update had never once worked
Here's the confession.
diff --git a/blog/src/posts/when-do-agents-need-an-agent-protocol.md b/blog/src/posts/when-do-agents-need-an-agent-protocol.md
index 610562e5..1e96dcee 100644
--- a/blog/src/posts/when-do-agents-need-an-agent-protocol.md
+++ b/blog/src/posts/when-do-agents-need-an-agent-protocol.md
@@ -68,6 +68,8 @@ a problem you've already solved. This is the same reason [coordinating co-locate
agents](/blog/coordinating-ai-coding-agents/) rarely starts with a protocol — it starts with a shared
directory.
+{% img "note-1" %}
+
## When you do need one: crossing a boundary
The calculus flips the moment your agents stop being a closed, owned set. A protocol earns its keep when
@@ -106,6 +108,8 @@ Most teams' first multi-agent system lives entirely on the "same side." Reach fo
only when, you actually cross over — and notice the two boundaries can differ: you might want MCP for
tools long before you ever need A2A for agents.
+{% img "note-2" %}
+
## Build so you can speak them later
None of this is an argument against the protocols — it's an argument against adopting them prematurely.
diff --git a/blog/src/posts/why-cli-agents-are-powerful.md b/blog/src/posts/why-cli-agents-are-powerful.md
index db9d32bd..42023b86 100644
--- a/blog/src/posts/why-cli-agents-are-powerful.md
+++ b/blog/src/posts/why-cli-agents-are-powerful.md
@@ -72,6 +72,8 @@ So the headline isn't "CLI agents can type commands." It's that **a terminal tur
worker** — something that can act, observe the consequence, and correct, in a tight loop, without a human
shuttling output back and forth across the glass.
+{% img "note-1" %}
+
## Local is what makes the access *real*
Here's the catch people miss. Terminal-level access is only as powerful as the machine the terminal is
@@ -141,6 +143,8 @@ caps the total, and routing keeps frontier prices off routine work. (For the ful
— it's that a hive is only worth running if it's *engineered* to be affordable, and these are the
mechanics that make it so.
+{% img "note-2" %}
+
## The bottom line
CLI agents are powerful because a terminal turns a model from a thing that *talks about* work into a
diff --git a/blog/src/posts/why-local-first-matters-for-ai-agents.md b/blog/src/posts/why-local-first-matters-for-ai-agents.md
index 29fb553a..eecf4939 100644
--- a/blog/src/posts/why-local-first-matters-for-ai-agents.md
+++ b/blog/src/posts/why-local-first-matters-for-ai-agents.md
@@ -42,6 +42,8 @@ Anthropic the same way your editor's does. Local-first is about *where the rest
In a [local-first setup](/#why), all of that stays on your machine. In a cloud platform, much of it
lives on someone else's servers. Same agents, very different trust model.
+{% img "note-1" %}
+
## Three reasons it matters
### 1. Control — it's your machine, your rules
@@ -71,6 +73,8 @@ But for an individual developer or a small team running agents against their own
convenience rarely outweighs handing over control, privacy, and predictable cost. You can have the
coordination *and* keep it local.
+{% img "note-2" %}
+
## Local-first doesn't mean uncoordinated
The old assumption was that local meant primitive — a few terminals, no shared brain. That's no longer
diff --git a/blog/src/posts/why-our-auto-update-never-ran.md b/blog/src/posts/why-our-auto-update-never-ran.md
index bab58e8c..a5d8ec53 100644
--- a/blog/src/posts/why-our-auto-update-never-ran.md
+++ b/blog/src/posts/why-our-auto-update-never-ran.md
@@ -78,6 +78,8 @@ swallowing for three releases:
TypeError: Cannot set properties of undefined (setting 'autoDownload')
```
+{% img "note-1" %}
+
## One line, three releases
Here is the code that shipped in v0.3.4:
@@ -142,6 +144,8 @@ So v0.3.7 changes three things beyond the interop fix:
plain module with no Electron imports, with unit tests covering the rule that bit us — a
re-check must never wipe out an update you already have staged.
+{% img "note-2" %}
+
## The version number is now a button
The other half of the report was that nothing in the app told the user what was happening.
diff --git a/blog/src/posts/why-we-built-munder-difflin.md b/blog/src/posts/why-we-built-munder-difflin.md
index d95350c1..e676acea 100644
--- a/blog/src/posts/why-we-built-munder-difflin.md
+++ b/blog/src/posts/why-we-built-munder-difflin.md
@@ -39,6 +39,8 @@ Three frustrations kept recurring, the same ones [everyone hits](/blog/from-one-
The agents weren't the bottleneck anymore. *I* was — the message bus, the conflict resolver, and the
project's only long-term memory.
+{% img "note-1" %}
+
## The realization
The instinct is to reach for a better terminal multiplexer. But the problem wasn't *running* agents in
@@ -68,6 +70,8 @@ And the joke that became the name: *the world's best agents, the world's worst p
office metaphor isn't decoration — it turned out to be the clearest way to think about (and watch) a
team of coordinating agents.
+{% img "note-2" %}
+
## Why local, why open source
Two decisions were never really in question. **Local-first**, because agents that touch your whole
diff --git a/blog/src/posts/your-first-hour-with-munder-difflin.md b/blog/src/posts/your-first-hour-with-munder-difflin.md
index 483ada08..1c2d7786 100644
--- a/blog/src/posts/your-first-hour-with-munder-difflin.md
+++ b/blog/src/posts/your-first-hour-with-munder-difflin.md
@@ -53,6 +53,8 @@ First launch drops you into a short wizard, and the four choices it asks for are
Finish the wizard and you land on the floor: a pixel-art office, empty except for Michael, who seats himself in his office automatically.
+{% img "note-1" %}
+
## Minute 10 — Your first brief to Michael
You don't manage the workers. You talk to one agent — the GOD orchestrator — and he runs the floor. Click into Michael's terminal and type a brief the way you'd brief a colleague: what you want, which repo, what "done" looks like.
@@ -69,6 +71,8 @@ Now the part that makes the product legible: the floor is not a decoration, it's
Click any agent and you get their desk: the live terminal (you can type back into it), a sandboxed file browser, and a git tab with status, log, and commit graph. This is the moment the abstraction clicks — that avatar is a real `claude` process, and you're reading its actual stdout.
+{% img "note-2" %}
+
## Minute 40 — Your first approval, and the diff
Sometime in the first hour, something lands in the approvals queue — a spend threshold, a destructive operation, a scope change. This is by design: Michael resolves routine requests himself and escalates only critical items, so the queue stays short and every item in it deserves your attention. (The philosophy behind that gate: [approving AI agents without babysitting them](/blog/human-in-the-loop-approving-ai-agents/).)
diff --git a/docs/blog/agent-security-and-sandboxing/index.html b/docs/blog/agent-security-and-sandboxing/index.html
index c5f15a46..aff34641 100644
--- a/docs/blog/agent-security-and-sandboxing/index.html
+++ b/docs/blog/agent-security-and-sandboxing/index.html
@@ -181,6 +181,7 @@ foot-gun on production repos.</p>
<p>That honesty is the right framing. Bypass mode isn’t reckless — it’s the <em>correct</em> default for an
unattended control room. But it removes the last interactive gate, so the safety has to live somewhere
else. The rest of this post is “somewhere else.”</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/agent-security-and-sandboxing/note-1.png" alt="Hand-drawn sketch from “Running AI Agents Safely: Permission Modes and Sandboxing”" loading="lazy" decoding="async" /></figure>
<h2 id="when-the-prompt-is-off-structure-is-your-safety" tabindex="-1">When the prompt is off, structure is your safety <a class="anchor" href="#when-the-prompt-is-off-structure-is-your-safety" aria-hidden="true">#</a></h2>
<p>If you can’t rely on a human clicking “approve,” you make the dangerous things structurally hard to
reach. Five layers do most of the work.</p>
@@ -211,6 +212,7 @@ log</a> records every action in order, so “what did the agent do at
2 a.m.?” has a precise, timestamped answer — and the genuinely critical calls can still pause for a human
through <a href="/blog/human-in-the-loop-approving-ai-agents/">native approvals</a>. Bypass mode and a human gate
aren’t mutually exclusive: most actions flow, the few that matter still wait.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/agent-security-and-sandboxing/note-2.png" alt="Hand-drawn sketch from “Running AI Agents Safely: Permission Modes and Sandboxing”" loading="lazy" decoding="async" /></figure>
<h2 id="what-to-gate-vs-what-to-allow" tabindex="-1">What to gate vs. what to allow <a class="anchor" href="#what-to-gate-vs-what-to-allow" aria-hidden="true">#</a></h2>
<p>Security theater is gating everything until the human rubber-stamps a hundred prompts and stops reading.
The goal is a <em>narrow</em> gate. A reasonable default policy:</p>
diff --git a/docs/blog/agents-ran-our-launch-week-analytics/index.html b/docs/blog/agents-ran-our-launch-week-analytics/index.html
new file mode 100644
index 00000000..e43f3316
--- /dev/null
+++ b/docs/blog/agents-ran-our-launch-week-analytics/index.html
@@ -0,0 +1,390 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Our Agents Ran Our Launch-Week Analytics — Munder Difflin Blog</title>
+<meta name="description" content="Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch." />
+<link rel="canonical" href="https://munderdiffl.in/blog/agents-ran-our-launch-week-analytics/" />
+
+<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="Our Agents Ran Our Launch-Week Analytics — Munder Difflin Blog" />
+<meta property="og:description" content="Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch." />
+<meta property="og:url" content="https://munderdiffl.in/blog/agents-ran-our-launch-week-analytics/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Use Cases" />
+<meta property="article:tag" content="Research" />
+<meta property="article:tag" content="Launch" />
+<meta property="article:tag" content="Workflow" />
+<meta property="article:tag" content="Multi-Agent" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Our Agents Ran Our Launch-Week Analytics — Munder Difflin Blog" />
+<meta name="twitter:description" content="Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "Our Agents Ran Our Launch-Week Analytics",
+ "description": "Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/agents-ran-our-launch-week-analytics/" },
+ "keywords": "ai agents launch analytics, analyze reddit comments with ai, multi-agent research workflow, launch retrospective automation, product hunt analysis ai, munder difflin use case",
+ "articleSection": "Use Cases",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/agents-ran-our-launch-week-analytics/"
+}
+</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": "Our Agents Ran Our Launch-Week Analytics", "item": "https://munderdiffl.in/blog/agents-ran-our-launch-week-analytics/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "What did the agents actually analyze?", "acceptedAnswer": { "@type": "Answer", "text": "Four channels in parallel: ten Reddit launch threads (501 comments including every nested reply), the full Product Hunt page (27 comments plus the page's own data), GitHub traffic, and PostHog funnels. Each agent produced a structured report — a readable markdown brief plus a JSON file — and the orchestrator synthesized them into one picture." } },
+ { "@type": "Question", "name": "Why use multiple agents instead of one long session?", "acceptedAnswer": { "@type": "Answer", "text": "Each channel is a full context window of raw material on its own. One agent per channel means each report is written by something that actually read every comment, not a skim. The orchestrator then works from the four distilled reports — which is exactly the fan-out-then-synthesize pattern hives are good at." } },
+ { "@type": "Question", "name": "Can I run this on my own launch?", "acceptedAnswer": { "@type": "Answer", "text": "Yes — the recipe is at the end of the post. You need the raw threads saved locally (Reddit's JSON endpoints work), one agent per channel with a clear brief, a shared folder for reports, and one synthesis pass at the end. A weekend launch produces an evening of agent work." } }
+
+ ]
+}
+</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,
+ 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-use-cases">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/use-cases/">Use Cases</a>
+ </nav>
+ <h1>Our Agents Ran Our Launch-Week Analytics</h1>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>3 min read</span>
+ <span class="tag kind">Use Cases</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png" alt="Illustration: Our Agents Ran Our Launch-Week Analytics" 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>After launch week we had ten Reddit
+threads, 516 comments, a Product Hunt page, and analytics dashboards — far more than any human
+was going to read honestly. So we didn't. <strong>A hive of agents read all of it</strong>: one
+agent per channel, structured briefs in, markdown + JSON reports out, one synthesis at the end.
+Every launch decision we've made since traces to those reports. Here's the workflow.</p></div>
+<p>There’s a specific kind of lying founders do after a launch: they remember the five most
+emotional comments and call it “what the community said.” We had 516 comments across ten
+subreddits. Nobody’s memory survives that honestly.</p>
+<p>But we make a tool whose whole job is
+<a href="/blog/run-an-office-of-ai-agents/">coordinating agents on real work</a>. Launch analytics turned
+out to be the best dogfood we’ve ever had.</p>
+<h2 id="the-floor-plan" tabindex="-1">The floor plan <a class="anchor" href="#the-floor-plan" aria-hidden="true">#</a></h2>
+<p>Four agents, one channel each, spawned with a written brief:</p>
+<ul>
+<li><strong>Reddit agent</strong> — the big one. Ten launch threads saved as raw JSON, 501 comments including
+every nested reply. Brief: account for <em>every</em> comment — bucket objections, praise,
+feature asks, and pricing signals, with quotes and usernames preserved.</li>
+<li><strong>Product Hunt agent</strong> — the launch page: all 27 comments, the review, and the page’s own
+embedded data, read straight from the source rather than eyeballing rendered numbers.</li>
+<li><strong>GitHub agent</strong> — stars, traffic, referrers, clones: which channel actually moved the repo.</li>
+<li><strong>Analytics agent</strong> — PostHog funnels: installs, first runs, and where new users stalled.</li>
+</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/note-1.png" alt="Hand-drawn sketch from “Our Agents Ran Our Launch-Week Analytics”" loading="lazy" decoding="async" /><figcaption>One channel per agent: Reddit, Product Hunt, GitHub, PostHog. Each reads everything, each files a report.</figcaption></figure>
+<p>Each agent wrote two artifacts into a shared research folder: a <strong>markdown brief</strong> a human
+actually wants to read, and a <strong>JSON file</strong> with the counted, bucketed data so later questions
+don’t require re-reading anything. Then the orchestrator synthesized the four into one picture.</p>
+<h2 id="why-the-fan-out-matters" tabindex="-1">Why the fan-out matters <a class="anchor" href="#why-the-fan-out-matters" aria-hidden="true">#</a></h2>
+<p>The naive version of this is pasting comments into one chat session until it fills up. The
+problem isn’t just context size — it’s that a model skimming its 400th comment gets exactly as
+lazy as a human does. One agent per channel keeps each report grounded in a full, careful read,
+and the <a href="/blog/how-the-god-orchestrator-works/">orchestrator</a> works from four distilled reports
+instead of raw sludge. Fan out, then synthesize. It’s the same
+<a href="/blog/multi-agent-orchestration-patterns/">pattern</a> that works for code.</p>
+<p>The other thing a hive gets you is <strong>iteration without re-reading</strong>. Days later we came back
+with sharper questions — “split willingness-to-pay by supporter motive versus buyer motive,”
+“which commenters were blocked from even running it?” — and dispatched them to the same agent,
+which still had <a href="/blog/how-agents-remember-semantic-memory/">its memory</a> of the corpus. Each
+pass appended to the same reports. The research got <em>thicker</em> instead of starting over.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/note-2.png" alt="Hand-drawn sketch from “Our Agents Ran Our Launch-Week Analytics”" loading="lazy" decoding="async" /><figcaption>Sharper question, same agent, same corpus — the reports grow instead of restarting.</figcaption></figure>
+<h2 id="what-fell-out-of-it" tabindex="-1">What fell out of it <a class="anchor" href="#what-fell-out-of-it" aria-hidden="true">#</a></h2>
+<p>Findings we would have missed by skimming, all of which changed real decisions:</p>
+<ul>
+<li><strong>46% of all engagement came from one subreddit.</strong> r/ClaudeCode delivered 1,017 of 2,233
+combined upvotes. Two other communities flatlined. That’s next launch’s channel budget,
+decided.</li>
+<li><strong>Product Hunt sent 195 upvotes and ~25 visitors.</strong> Credibility channel, not traffic channel.
+We’d have guessed wrong.</li>
+<li><strong>The two most serious evaluators asked for the same missing feature</strong> — a visible
+“this decision needs your eyes” flag — in different words on different platforms. Only
+cross-channel synthesis caught that they were the same request.</li>
+<li><strong>Every blocked-user story on two channels traced to the same bug class</strong> (the non-Claude-Code
+path on Windows), which moved it to the top of
+<a href="/blog/launching-munder-difflin-v0-4-4/">0.4.4</a>.</li>
+</ul>
+<p>The Reddit and Product Hunt halves of this analysis became
+<a href="/blog/what-reddit-told-us-about-munder-difflin/">their</a>
+<a href="/blog/number-five-on-product-hunt/">own</a> posts — both written <em>from the agents’ reports</em>, which
+is why they have real numbers in them instead of vibes.</p>
+<h2 id="run-it-on-your-launch" tabindex="-1">Run it on your launch <a class="anchor" href="#run-it-on-your-launch" aria-hidden="true">#</a></h2>
+<p>The recipe, portable to any hive setup:</p>
+<ol>
+<li><strong>Capture raw sources locally first.</strong> Reddit threads have JSON endpoints; save them to
+disk so agents parse structure instead of scraping rendered pages.</li>
+<li><strong>One agent per channel, written briefs.</strong> The brief that worked: <em>account for every
+comment; bucket, count, and quote; write both a human brief and a JSON dataset; flag what
+you couldn’t verify.</em> That last clause matters — our Reddit agent correctly flagged that
+view counts are null in public JSON rather than inventing them.</li>
+<li><strong>A shared research folder</strong> all agents write into, so reports reference each other.</li>
+<li><strong>One synthesis pass</strong> at the end — and keep the agents around, because your best questions
+arrive three days later.</li>
+</ol>
+<p>An evening of agent work, and launch week stops being a feeling and becomes a dataset. The
+<a href="/blog/claude-code-automation-while-you-sleep/">overnight version</a> works too — we know, because
+half of this ran while we slept off the launch.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">What did the agents actually analyze?</p>
+ <p class="a">Four channels in parallel: ten Reddit launch threads (501 comments including every nested reply), the full Product Hunt page (27 comments plus the page&#39;s own data), GitHub traffic, and PostHog funnels. Each agent produced a structured report — a readable markdown brief plus a JSON file — and the orchestrator synthesized them into one picture.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Why use multiple agents instead of one long session?</p>
+ <p class="a">Each channel is a full context window of raw material on its own. One agent per channel means each report is written by something that actually read every comment, not a skim. The orchestrator then works from the four distilled reports — which is exactly the fan-out-then-synthesize pattern hives are good at.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Can I run this on my own launch?</p>
+ <p class="a">Yes — the recipe is at the end of the post. You need the raw threads saved locally (Reddit&#39;s JSON endpoints work), one agent per channel with a clear brief, a shared folder for reports, and one synthesis pass at the end. A weekend launch produces an evening of agent work.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/use-cases/">Use Cases</a><a class="tag" href="/blog/tags/research/">Research</a><a class="tag" href="/blog/tags/launch/">Launch</a><a class="tag" href="/blog/tags/workflow/">Workflow</a><a class="tag" href="/blog/tags/multi-agent/">Multi-Agent</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-floor-plan">The floor plan</a></li><li class="lvl-2"><a href="#why-the-fan-out-matters">Why the fan-out matters</a></li><li class="lvl-2"><a href="#what-fell-out-of-it">What fell out of it</a></li><li class="lvl-2"><a href="#run-it-on-your-launch">Run it on your launch</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/an-agent-redesigned-this-blog/"><span class="k">← Older</span><span class="t">An Agent Redesigned the Blog You&#39;re Reading</span></a>
+ <span></span>
+ </div>
+ <section class="related">
+ <h2>Related in Use Cases</h2>
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/agents-rule-of-two/index.html b/docs/blog/agents-rule-of-two/index.html
index 2a81c50e..04cf6329 100644
--- a/docs/blog/agents-rule-of-two/index.html
+++ b/docs/blog/agents-rule-of-two/index.html
@@ -193,6 +193,7 @@ private data, nothing worth stealing. No way to communicate out, nowhere to send
just that observation made actionable: stay at two legs and the worst case is off the table. (Meta
credits both Willison’s framing and the older Chromium “Rule of 2” as
inspiration.)</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/agents-rule-of-two/note-1.png" alt="Hand-drawn sketch from “The Agents Rule of Two: A Simple Safety Rule for Coding Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="a-coding-agent-wants-all-three-by-default" tabindex="-1">A coding agent wants all three by default <a class="anchor" href="#a-coding-agent-wants-all-three-by-default" aria-hidden="true">#</a></h2>
<p>Here’s the uncomfortable part for our domain: a capable coding agent is <em>born</em> at the full trifecta.</p>
<ul>
@@ -219,6 +220,7 @@ reads as potentially hostile rather than as instructions to obey.</li>
</ul>
<p>In practice you rarely remove a leg entirely — you weaken it enough that a single compromised session
can’t complete the chain.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/agents-rule-of-two/note-2.png" alt="Hand-drawn sketch from “The Agents Rule of Two: A Simple Safety Rule for Coding Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="when-you-genuinely-need-all-three-supervise" tabindex="-1">When you genuinely need all three: supervise <a class="anchor" href="#when-you-genuinely-need-all-three-supervise" aria-hidden="true">#</a></h2>
<p>Sometimes the task really does want the full <a href="/blog/the-lethal-trifecta-for-coding-agents/">trifecta</a> — read an untrusted issue, touch private code,
and open a PR. Meta’s escape hatch is the right one: don’t run that autonomously. Route the risky step
diff --git a/docs/blog/ai-agent-glossary/index.html b/docs/blog/ai-agent-glossary/index.html
index 80bf92da..3324aa15 100644
--- a/docs/blog/ai-agent-glossary/index.html
+++ b/docs/blog/ai-agent-glossary/index.html
@@ -175,6 +175,7 @@ Great for parallelism within one task; it doesn’t persist or share memory acro
<h3 id="tool" tabindex="-1">Tool <a class="anchor" href="#tool" aria-hidden="true">#</a></h3>
<p><strong>A tool is a capability an agent can call — read a file, run a command, search the web.</strong> Tools are
what let an agent <em>do</em> things instead of just talk.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/ai-agent-glossary/note-1.png" alt="Hand-drawn sketch from “The AI Coding Agent Glossary: Harness, Orchestrator, Hive, Subagent”" loading="lazy" decoding="async" /></figure>
<h2 id="the-coordination-layer" tabindex="-1">The coordination layer <a class="anchor" href="#the-coordination-layer" aria-hidden="true">#</a></h2>
<h3 id="harness" tabindex="-1">Harness <a class="anchor" href="#harness" aria-hidden="true">#</a></h3>
<p><strong>A harness is the software that wraps the agents you already run and coordinates them — roles,
@@ -201,6 +202,7 @@ fetch the few most relevant.</strong> It’s what keeps recall instant as the kn
<h3 id="mailbox-inter-agent-messaging" tabindex="-1">Mailbox / inter-agent messaging <a class="anchor" href="#mailbox-inter-agent-messaging" aria-hidden="true">#</a></h3>
<p><strong>A mailbox lets one agent hand a message or result to another directly, instead of routing through
you.</strong> It’s how a hive coordinates without a human courier.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/ai-agent-glossary/note-2.png" alt="Hand-drawn sketch from “The AI Coding Agent Glossary: Harness, Orchestrator, Hive, Subagent”" loading="lazy" decoding="async" /></figure>
<h2 id="workflow-patterns" tabindex="-1">Workflow patterns <a class="anchor" href="#workflow-patterns" aria-hidden="true">#</a></h2>
<h3 id="git-worktree" tabindex="-1">Git worktree <a class="anchor" href="#git-worktree" aria-hidden="true">#</a></h3>
<p><strong>A git worktree is a separate working copy of one repo, so parallel agents edit isolated checkouts
diff --git a/docs/blog/an-agent-redesigned-this-blog/index.html b/docs/blog/an-agent-redesigned-this-blog/index.html
new file mode 100644
index 00000000..7db8f5cf
--- /dev/null
+++ b/docs/blog/an-agent-redesigned-this-blog/index.html
@@ -0,0 +1,377 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>An Agent Redesigned the Blog You&#39;re Reading — Munder Difflin Blog</title>
+<meta name="description" content="Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of." />
+<link rel="canonical" href="https://munderdiffl.in/blog/an-agent-redesigned-this-blog/" />
+
+<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="An Agent Redesigned the Blog You&#39;re Reading — Munder Difflin Blog" />
+<meta property="og:description" content="Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of." />
+<meta property="og:url" content="https://munderdiffl.in/blog/an-agent-redesigned-this-blog/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Use Cases" />
+<meta property="article:tag" content="Design" />
+<meta property="article:tag" content="Eleventy" />
+<meta property="article:tag" content="Workflow" />
+<meta property="article:tag" content="Meta" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="An Agent Redesigned the Blog You&#39;re Reading — Munder Difflin Blog" />
+<meta name="twitter:description" content="Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "An Agent Redesigned the Blog You're Reading",
+ "description": "Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/an-agent-redesigned-this-blog/" },
+ "keywords": "ai agent website redesign, eleventy blog redesign, svg illustrations generated by code, claude code design workflow, ai generated blog images alternative, munder difflin blog",
+ "articleSection": "Use Cases",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/an-agent-redesigned-this-blog/"
+}
+</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": "An Agent Redesigned the Blog You're Reading", "item": "https://munderdiffl.in/blog/an-agent-redesigned-this-blog/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "Who designed the new Munder Difflin blog?", "acceptedAnswer": { "@type": "Answer", "text": "A single agent, working in Claude Code, over one long session with founder feedback in the loop. It proposed two complete themes, and after one was chosen, it restyled the whole site, drew a hero illustration for all 119 posts, and shipped the result through CI to production." } },
+ { "@type": "Question", "name": "How were 119 hero images made for $0?", "acceptedAnswer": { "@type": "Answer", "text": "They're not AI-generated bitmaps — they're drawn as code. A small SVG parts library (a character, desks, terminals, envelopes, a kanban wall) plus 16 composition archetypes and a per-post spec file produce each scene; a headless browser screenshots them at 1600×900. Editing an image means editing a line of JavaScript, and regenerating costs nothing." } },
+ { "@type": "Question", "name": "What's the character in the illustrations?", "acceptedAnswer": { "@type": "Answer", "text": "An adaptation of Xiaohei, an open-source (MIT) illustration character we found through a starred repo — recolored to our brand yellow and put to work at tiny desks and terminals across every post. Credit to the original ian-xiaohei-illustrations project." } }
+
+ ]
+}
+</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,
+ 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-use-cases">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/use-cases/">Use Cases</a>
+ </nav>
+ <h1>An Agent Redesigned the Blog You&#39;re Reading</h1>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>3 min read</span>
+ <span class="tag kind">Use Cases</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/an-agent-redesigned-this-blog/hero.png" alt="Illustration: An Agent Redesigned the Blog You're Reading" 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>The redesign you're looking at —
+the fonts, the yellow, the little hand-drawn scenes on every post — was shipped end to end by
+one agent after Reddit told us the old blog read like AI slop. The part worth stealing:
+<strong>all 119 hero illustrations are drawn as code</strong> — an SVG parts library, 16
+composition archetypes, one spec file — and rendered by screenshotting a browser.
+Image-API bill: $0.</p></div>
+<p>During <a href="/blog/what-reddit-told-us-about-munder-difflin/">launch week</a>, among the feedback about
+the product, there was a quieter thread of feedback about this blog. It was not kind. The old
+design was the marketing site’s mono-font brutalism stretched over long-form text, there wasn’t
+a single image on any post, and more than one person used the phrase “AI-written.”</p>
+<p>Fair. So we handed the problem to an agent, with a brief instead of a mockup: <em>make it readable,
+make it human, give every post images, and don’t you dare use red.</em></p>
+<h2 id="two-themes-one-survivor" tabindex="-1">Two themes, one survivor <a class="anchor" href="#two-themes-one-survivor" aria-hidden="true">#</a></h2>
+<p>The agent’s first deliverable was two complete, buildable themes — not moodboards, actual
+switchable CSS behind an environment flag, previewable side by side. One warm and bookish, one
+editorial-magazine. The magazine won: serif headlines with real weight, a reading column set in
+a proper text face, the app’s own cream-paper palette, and the website’s yellow as the single
+accent — always as a highlighter fill, never as colored text.</p>
+<p>The founder’s role in this phase was one sentence at a time: <em>use the app’s colors. The accent
+is yellow, not red. No red anywhere.</em> Each note came back applied across every template within
+minutes. That loop — human taste, agent hands — is the whole
+<a href="/blog/why-we-built-munder-difflin/">reason this product exists</a>.</p>
+<h2 id="the-image-problem-and-the-0-answer" tabindex="-1">The image problem, and the $0 answer <a class="anchor" href="#the-image-problem-and-the-0-answer" aria-hidden="true">#</a></h2>
+<p>Then the hard part: 119 posts needed images, and AI image generation was the obvious move — and
+the wrong one. Quotes came out between $5 and $20 in API costs, every regeneration would cost
+again, and the results would have exactly the generic sheen the redesign was trying to escape.</p>
+<p>The agent proposed something better: <strong>draw them as code.</strong></p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/an-agent-redesigned-this-blog/note-1.png" alt="Hand-drawn sketch from “An Agent Redesigned the Blog You're Reading”" loading="lazy" decoding="async" /><figcaption>A parts library, 16 archetypes, and one spec file — that's the entire illustration system behind 119 unique heroes.</figcaption></figure>
+<p>The system has three layers, all plain JavaScript and SVG:</p>
+<ul>
+<li><strong>A parts library</strong> — one small character (an adaptation of the MIT-licensed <em>Xiaohei</em>,
+recolored to our brand yellow), desks, terminals, envelopes, a kanban wall, clocks, shields,
+coffee. A hand-drawn wobble comes from an SVG turbulence filter, seeded per post so no two
+images wobble identically.</li>
+<li><strong>16 composition archetypes</strong> — “agents talking,” “night shift,” “versus,” “the routing
+desk” — each a function that arranges parts into a scene.</li>
+<li><strong>One spec file</strong> — a line per post choosing an archetype and the handwritten annotations:
+the blue mechanism labels and the orange punchline you see in the corners.</li>
+</ul>
+<p>A headless browser opens each scene at 1600×900 and screenshots it into the post’s media
+folder. All 119 rendered in three batches. Total image-API spend: <strong>zero</strong>. And when one scene
+looked wrong — a sleeping character whose eyes were open, which is nightmare material — the fix
+was editing a function, not re-prompting a diffusion model and praying.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/an-agent-redesigned-this-blog/note-2.png" alt="Hand-drawn sketch from “An Agent Redesigned the Blog You're Reading”" loading="lazy" decoding="async" /><figcaption>When a drawing is code, 'his eyes should be closed' is a one-line fix — not a re-roll.</figcaption></figure>
+<h2 id="one-manifest-to-rule-the-media" tabindex="-1">One manifest to rule the media <a class="anchor" href="#one-manifest-to-rule-the-media" aria-hidden="true">#</a></h2>
+<p>Under the hood, a single <code>media.json</code> drives every image, inline figure, and video embed on the
+blog — per-post entries with a file path, alt text, and a status flag. Templates render a
+designed placeholder until an entry flips to <code>ready</code>, so the site never shows a broken image,
+and adding <a href="/blog/deploy-a-blog-writer-agent/">this very image pipeline</a> to a new post is one
+JSON entry. YouTube embeds got the same treatment: click-to-load, privacy-friendly, with a
+placeholder state for videos that don’t exist yet.</p>
+<h2 id="the-making-of-honestly" tabindex="-1">The making-of, honestly <a class="anchor" href="#the-making-of-honestly" aria-hidden="true">#</a></h2>
+<p>The parts nobody puts in the case study: the agent got the category badge black-on-black on the
+first pass and fixed it when told. It got told “I do not want any red things” <em>after</em> it had
+already picked a coral topic color, and remapped the entire palette. The founder’s browser
+cached the old build twice, producing two rounds of “you haven’t changed anything” that were
+resolved by an agent-written no-cache dev server. Real work looks like this.</p>
+<p>But the scoreboard at the end: a full editorial redesign, 119 bespoke illustrations, a media
+pipeline, and CI deployment to production — one agent, one extended session, zero image-API
+dollars. The blog you’re reading is the artifact. If it still reads like AI slop, at least now
+it’s <em>hand-drawn</em> AI slop.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">Who designed the new Munder Difflin blog?</p>
+ <p class="a">A single agent, working in Claude Code, over one long session with founder feedback in the loop. It proposed two complete themes, and after one was chosen, it restyled the whole site, drew a hero illustration for all 119 posts, and shipped the result through CI to production.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">How were 119 hero images made for $0?</p>
+ <p class="a">They&#39;re not AI-generated bitmaps — they&#39;re drawn as code. A small SVG parts library (a character, desks, terminals, envelopes, a kanban wall) plus 16 composition archetypes and a per-post spec file produce each scene; a headless browser screenshots them at 1600×900. Editing an image means editing a line of JavaScript, and regenerating costs nothing.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">What&#39;s the character in the illustrations?</p>
+ <p class="a">An adaptation of Xiaohei, an open-source (MIT) illustration character we found through a starred repo — recolored to our brand yellow and put to work at tiny desks and terminals across every post. Credit to the original ian-xiaohei-illustrations project.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/use-cases/">Use Cases</a><a class="tag" href="/blog/tags/design/">Design</a><a class="tag" href="/blog/tags/eleventy/">Eleventy</a><a class="tag" href="/blog/tags/workflow/">Workflow</a><a class="tag" href="/blog/tags/meta/">Meta</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="#two-themes-one-survivor">Two themes, one survivor</a></li><li class="lvl-2"><a href="#the-image-problem-and-the-0-answer">The image problem, and the $0 answer</a></li><li class="lvl-2"><a href="#one-manifest-to-rule-the-media">One manifest to rule the media</a></li><li class="lvl-2"><a href="#the-making-of-honestly">The making-of, honestly</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/launching-munder-difflin-v0-4-4/"><span class="k">← Older</span><span class="t">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</span></a>
+ <a class="pn next" href="/blog/agents-ran-our-launch-week-analytics/"><span class="k">Newer →</span><span class="t">Our Agents Ran Our Launch-Week Analytics</span></a>
+ </div>
+ <section class="related">
+ <h2>Related in Use Cases</h2>
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/append-only-event-log-agents/index.html b/docs/blog/append-only-event-log-agents/index.html
index d27bd4dd..23ce05d4 100644
--- a/docs/blog/append-only-event-log-agents/index.html
+++ b/docs/blog/append-only-event-log-agents/index.html
@@ -195,6 +195,7 @@ picks up new lines from there. Multiple consumers, no coordination.</li>
</ul>
<p>A database would give you indexes and queries you mostly don’t need here, at the cost of a schema and a
server. For an audit/observability log, plain JSONL is the right amount of technology.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/append-only-event-log-agents/note-1.png" alt="Hand-drawn sketch from “An Append-Only Event Log for a Hive of Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="what-to-record-per-event" tabindex="-1">What to record per event <a class="anchor" href="#what-to-record-per-event" aria-hidden="true">#</a></h2>
<p>The art is choosing events that are <strong>small, typed, and factual.</strong> Each line carries a <code>ts</code>
(timestamp) and a <code>kind</code>, plus only the fields that matter for that kind. In a hive, the events worth
@@ -218,6 +219,7 @@ resolves approvals, and it’s the only thing that writes the file. That keeps t
interleaved, half-written lines, and it pairs with the
<a href="/blog/single-committer-git-pattern/">single-committer git pattern</a>: each batch of coordination is
both appended to the log <em>and</em> committed, so the log’s history and git’s history line up.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/append-only-event-log-agents/note-2.png" alt="Hand-drawn sketch from “An Append-Only Event Log for a Hive of Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="replay-and-debugging" tabindex="-1">Replay and debugging <a class="anchor" href="#replay-and-debugging" aria-hidden="true">#</a></h2>
<p>Here’s where the log earns its keep. Because it’s an ordered, immutable record, you can <strong>replay</strong> the
system’s history:</p>
@@ -310,6 +312,22 @@ it’s free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -341,22 +359,6 @@ it’s free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/architecture-two-planes-one-renderer/index.html b/docs/blog/architecture-two-planes-one-renderer/index.html
index a9abe6d0..dadabfc8 100644
--- a/docs/blog/architecture-two-planes-one-renderer/index.html
+++ b/docs/blog/architecture-two-planes-one-renderer/index.html
@@ -198,6 +198,7 @@ behind <a href="/blog/rendering-many-live-terminals-performance/">rendering many
<p>What the terminal plane gives you: the unfiltered truth of what each agent did. What it <em>can’t</em> easily
give you: a reliable “which tool is running right now?” without scraping and guessing at output. That’s
the other plane’s job.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/architecture-two-planes-one-renderer/note-1.png" alt="Hand-drawn sketch from “Munder Difflin's Architecture: Two Data Planes, One Renderer”" loading="lazy" decoding="async" /></figure>
<h2 id="the-event-plane-hooks-hive" tabindex="-1">The event plane (hooks + hive) <a class="anchor" href="#the-event-plane-hooks-hive" aria-hidden="true">#</a></h2>
<p>The event plane is about <em>structure</em>. It has two sources, both feeding the main process:</p>
<p><strong>Claude Code hooks.</strong> Each agent is launched with lifecycle hooks wired through a tiny shim that
@@ -222,6 +223,7 @@ you’d see bytes but have to guess at meaning.</li>
<p>Together they’re complementary: the office floor is <strong>event-driven</strong> (precise, structured, cheap to
render), and the terminal view is <strong>byte-for-byte authentic</strong> (the full detail when you want it). Two
planes, two questions, both answered well.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/architecture-two-planes-one-renderer/note-2.png" alt="Hand-drawn sketch from “Munder Difflin's Architecture: Two Data Planes, One Renderer”" loading="lazy" decoding="async" /></figure>
<h2 id="one-renderer-convergence" tabindex="-1">One renderer convergence <a class="anchor" href="#one-renderer-convergence" aria-hidden="true">#</a></h2>
<p>Both planes terminate in a single Electron renderer running React and Pixi.js:</p>
<ul>
@@ -313,6 +315,22 @@ free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -344,22 +362,6 @@ free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/assets/blog-press.css b/docs/blog/assets/blog-press.css
index 1773bf75..2b2eed3e 100644
--- a/docs/blog/assets/blog-press.css
+++ b/docs/blog/assets/blog-press.css
@@ -182,9 +182,12 @@ a.tag:hover { background: var(--ink); color: var(--paper); }
.ph-art { text-align: center; display: grid; gap: 8px; }
.ph-art .ph-glyph { font-size: 46px; color: var(--c, var(--accent)); }
.ph-art .ph-note { font-family: var(--grot); font-weight: 700; font-size: 12px; letter-spacing: 0.24em; text-transform: uppercase; color: var(--ink-soft); }
-.fig-inline { margin: 38px 0; }
-.fig-inline img { border: 3px solid var(--rule); }
-.fig-inline.fig-placeholder { aspect-ratio: 2/1; }
+.fig-inline { margin: 42px auto; max-width: 620px; }
+.fig-inline img { display: block; width: 100%; border: 3px solid var(--rule); border-radius: 6px; background: #fff; }
+.fig-inline figcaption { text-align: center; }
+.fig-inline:nth-of-type(odd) img { transform: rotate(-0.4deg); }
+.fig-inline:nth-of-type(even) img { transform: rotate(0.35deg); }
+.fig-inline.fig-placeholder { aspect-ratio: 15/7; }
/* post body layout */
.post-wrap { display: grid; grid-template-columns: minmax(0, 1fr) 240px; gap: 56px; padding-top: 44px; max-width: 1120px; }
diff --git a/docs/blog/assets/media/agent-security-and-sandboxing/note-1.png b/docs/blog/assets/media/agent-security-and-sandboxing/note-1.png
new file mode 100644
index 00000000..adcb8566
Binary files /dev/null and b/docs/blog/assets/media/agent-security-and-sandboxing/note-1.png differ
diff --git a/docs/blog/assets/media/agent-security-and-sandboxing/note-2.png b/docs/blog/assets/media/agent-security-and-sandboxing/note-2.png
new file mode 100644
index 00000000..21327235
Binary files /dev/null and b/docs/blog/assets/media/agent-security-and-sandboxing/note-2.png differ
diff --git a/docs/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png b/docs/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png
new file mode 100644
index 00000000..62dfc607
Binary files /dev/null and b/docs/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png differ
diff --git a/docs/blog/assets/media/agents-ran-our-launch-week-analytics/note-1.png b/docs/blog/assets/media/agents-ran-our-launch-week-analytics/note-1.png
new file mode 100644
index 00000000..e2ebf3c5
Binary files /dev/null and b/docs/blog/assets/media/agents-ran-our-launch-week-analytics/note-1.png differ
diff --git a/docs/blog/assets/media/agents-ran-our-launch-week-analytics/note-2.png b/docs/blog/assets/media/agents-ran-our-launch-week-analytics/note-2.png
new file mode 100644
index 00000000..004b88a2
Binary files /dev/null and b/docs/blog/assets/media/agents-ran-our-launch-week-analytics/note-2.png differ
diff --git a/docs/blog/assets/media/agents-rule-of-two/note-1.png b/docs/blog/assets/media/agents-rule-of-two/note-1.png
new file mode 100644
index 00000000..924a09d2
Binary files /dev/null and b/docs/blog/assets/media/agents-rule-of-two/note-1.png differ
diff --git a/docs/blog/assets/media/agents-rule-of-two/note-2.png b/docs/blog/assets/media/agents-rule-of-two/note-2.png
new file mode 100644
index 00000000..43d215e9
Binary files /dev/null and b/docs/blog/assets/media/agents-rule-of-two/note-2.png differ
diff --git a/docs/blog/assets/media/ai-agent-glossary/note-1.png b/docs/blog/assets/media/ai-agent-glossary/note-1.png
new file mode 100644
index 00000000..b47a17e0
Binary files /dev/null and b/docs/blog/assets/media/ai-agent-glossary/note-1.png differ
diff --git a/docs/blog/assets/media/ai-agent-glossary/note-2.png b/docs/blog/assets/media/ai-agent-glossary/note-2.png
new file mode 100644
index 00000000..1b4b8fdd
Binary files /dev/null and b/docs/blog/assets/media/ai-agent-glossary/note-2.png differ
diff --git a/docs/blog/assets/media/an-agent-redesigned-this-blog/hero.png b/docs/blog/assets/media/an-agent-redesigned-this-blog/hero.png
new file mode 100644
index 00000000..bd8bbcde
Binary files /dev/null and b/docs/blog/assets/media/an-agent-redesigned-this-blog/hero.png differ
diff --git a/docs/blog/assets/media/an-agent-redesigned-this-blog/note-1.png b/docs/blog/assets/media/an-agent-redesigned-this-blog/note-1.png
new file mode 100644
index 00000000..da5caa17
Binary files /dev/null and b/docs/blog/assets/media/an-agent-redesigned-this-blog/note-1.png differ
diff --git a/docs/blog/assets/media/an-agent-redesigned-this-blog/note-2.png b/docs/blog/assets/media/an-agent-redesigned-this-blog/note-2.png
new file mode 100644
index 00000000..25ab43f4
Binary files /dev/null and b/docs/blog/assets/media/an-agent-redesigned-this-blog/note-2.png differ
diff --git a/docs/blog/assets/media/append-only-event-log-agents/note-1.png b/docs/blog/assets/media/append-only-event-log-agents/note-1.png
new file mode 100644
index 00000000..38acd856
Binary files /dev/null and b/docs/blog/assets/media/append-only-event-log-agents/note-1.png differ
diff --git a/docs/blog/assets/media/append-only-event-log-agents/note-2.png b/docs/blog/assets/media/append-only-event-log-agents/note-2.png
new file mode 100644
index 00000000..1b6ccc21
Binary files /dev/null and b/docs/blog/assets/media/append-only-event-log-agents/note-2.png differ
diff --git a/docs/blog/assets/media/architecture-two-planes-one-renderer/note-1.png b/docs/blog/assets/media/architecture-two-planes-one-renderer/note-1.png
new file mode 100644
index 00000000..21518af5
Binary files /dev/null and b/docs/blog/assets/media/architecture-two-planes-one-renderer/note-1.png differ
diff --git a/docs/blog/assets/media/architecture-two-planes-one-renderer/note-2.png b/docs/blog/assets/media/architecture-two-planes-one-renderer/note-2.png
new file mode 100644
index 00000000..0f8e70de
Binary files /dev/null and b/docs/blog/assets/media/architecture-two-planes-one-renderer/note-2.png differ
diff --git a/docs/blog/assets/media/atomic-file-mailboxes-for-agents/note-1.png b/docs/blog/assets/media/atomic-file-mailboxes-for-agents/note-1.png
new file mode 100644
index 00000000..1d11ed60
Binary files /dev/null and b/docs/blog/assets/media/atomic-file-mailboxes-for-agents/note-1.png differ
diff --git a/docs/blog/assets/media/atomic-file-mailboxes-for-agents/note-2.png b/docs/blog/assets/media/atomic-file-mailboxes-for-agents/note-2.png
new file mode 100644
index 00000000..6ebb8726
Binary files /dev/null and b/docs/blog/assets/media/atomic-file-mailboxes-for-agents/note-2.png differ
diff --git a/docs/blog/assets/media/best-ai-coding-agents/note-1.png b/docs/blog/assets/media/best-ai-coding-agents/note-1.png
new file mode 100644
index 00000000..5f41f0de
Binary files /dev/null and b/docs/blog/assets/media/best-ai-coding-agents/note-1.png differ
diff --git a/docs/blog/assets/media/best-ai-coding-agents/note-2.png b/docs/blog/assets/media/best-ai-coding-agents/note-2.png
new file mode 100644
index 00000000..d9fb4f13
Binary files /dev/null and b/docs/blog/assets/media/best-ai-coding-agents/note-2.png differ
diff --git a/docs/blog/assets/media/best-claude-code-multi-agent-tools/note-1.png b/docs/blog/assets/media/best-claude-code-multi-agent-tools/note-1.png
new file mode 100644
index 00000000..352823b2
Binary files /dev/null and b/docs/blog/assets/media/best-claude-code-multi-agent-tools/note-1.png differ
diff --git a/docs/blog/assets/media/best-claude-code-multi-agent-tools/note-2.png b/docs/blog/assets/media/best-claude-code-multi-agent-tools/note-2.png
new file mode 100644
index 00000000..9ac66b29
Binary files /dev/null and b/docs/blog/assets/media/best-claude-code-multi-agent-tools/note-2.png differ
diff --git a/docs/blog/assets/media/building-a-terminal-ui-xterm-node-pty/note-1.png b/docs/blog/assets/media/building-a-terminal-ui-xterm-node-pty/note-1.png
new file mode 100644
index 00000000..37dfd9c4
Binary files /dev/null and b/docs/blog/assets/media/building-a-terminal-ui-xterm-node-pty/note-1.png differ
diff --git a/docs/blog/assets/media/building-a-terminal-ui-xterm-node-pty/note-2.png b/docs/blog/assets/media/building-a-terminal-ui-xterm-node-pty/note-2.png
new file mode 100644
index 00000000..083b1949
Binary files /dev/null and b/docs/blog/assets/media/building-a-terminal-ui-xterm-node-pty/note-2.png differ
diff --git a/docs/blog/assets/media/building-an-ai-office-floor/note-1.png b/docs/blog/assets/media/building-an-ai-office-floor/note-1.png
new file mode 100644
index 00000000..d2cb5ee4
Binary files /dev/null and b/docs/blog/assets/media/building-an-ai-office-floor/note-1.png differ
diff --git a/docs/blog/assets/media/building-an-ai-office-floor/note-2.png b/docs/blog/assets/media/building-an-ai-office-floor/note-2.png
new file mode 100644
index 00000000..95c07312
Binary files /dev/null and b/docs/blog/assets/media/building-an-ai-office-floor/note-2.png differ
diff --git a/docs/blog/assets/media/building-reliable-ai-agents/note-1.png b/docs/blog/assets/media/building-reliable-ai-agents/note-1.png
new file mode 100644
index 00000000..5bd94ce8
Binary files /dev/null and b/docs/blog/assets/media/building-reliable-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/building-reliable-ai-agents/note-2.png b/docs/blog/assets/media/building-reliable-ai-agents/note-2.png
new file mode 100644
index 00000000..16f618ac
Binary files /dev/null and b/docs/blog/assets/media/building-reliable-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/can-claude-code-agents-talk-to-each-other/note-1.png b/docs/blog/assets/media/can-claude-code-agents-talk-to-each-other/note-1.png
new file mode 100644
index 00000000..9082074b
Binary files /dev/null and b/docs/blog/assets/media/can-claude-code-agents-talk-to-each-other/note-1.png differ
diff --git a/docs/blog/assets/media/can-claude-code-agents-talk-to-each-other/note-2.png b/docs/blog/assets/media/can-claude-code-agents-talk-to-each-other/note-2.png
new file mode 100644
index 00000000..48a04c23
Binary files /dev/null and b/docs/blog/assets/media/can-claude-code-agents-talk-to-each-other/note-2.png differ
diff --git a/docs/blog/assets/media/claude-code-automation-while-you-sleep/note-1.png b/docs/blog/assets/media/claude-code-automation-while-you-sleep/note-1.png
new file mode 100644
index 00000000..062f5895
Binary files /dev/null and b/docs/blog/assets/media/claude-code-automation-while-you-sleep/note-1.png differ
diff --git a/docs/blog/assets/media/claude-code-automation-while-you-sleep/note-2.png b/docs/blog/assets/media/claude-code-automation-while-you-sleep/note-2.png
new file mode 100644
index 00000000..8633ad2b
Binary files /dev/null and b/docs/blog/assets/media/claude-code-automation-while-you-sleep/note-2.png differ
diff --git a/docs/blog/assets/media/claude-code-git-worktrees-vs-hive/note-1.png b/docs/blog/assets/media/claude-code-git-worktrees-vs-hive/note-1.png
new file mode 100644
index 00000000..c4764b99
Binary files /dev/null and b/docs/blog/assets/media/claude-code-git-worktrees-vs-hive/note-1.png differ
diff --git a/docs/blog/assets/media/claude-code-git-worktrees-vs-hive/note-2.png b/docs/blog/assets/media/claude-code-git-worktrees-vs-hive/note-2.png
new file mode 100644
index 00000000..a0a83f3a
Binary files /dev/null and b/docs/blog/assets/media/claude-code-git-worktrees-vs-hive/note-2.png differ
diff --git a/docs/blog/assets/media/claude-code-hooks-explained/note-1.png b/docs/blog/assets/media/claude-code-hooks-explained/note-1.png
new file mode 100644
index 00000000..8eee8d4b
Binary files /dev/null and b/docs/blog/assets/media/claude-code-hooks-explained/note-1.png differ
diff --git a/docs/blog/assets/media/claude-code-hooks-explained/note-2.png b/docs/blog/assets/media/claude-code-hooks-explained/note-2.png
new file mode 100644
index 00000000..aec462f0
Binary files /dev/null and b/docs/blog/assets/media/claude-code-hooks-explained/note-2.png differ
diff --git a/docs/blog/assets/media/claude-code-multi-agent-setup-tutorial/note-1.png b/docs/blog/assets/media/claude-code-multi-agent-setup-tutorial/note-1.png
new file mode 100644
index 00000000..bc13df48
Binary files /dev/null and b/docs/blog/assets/media/claude-code-multi-agent-setup-tutorial/note-1.png differ
diff --git a/docs/blog/assets/media/claude-code-multi-agent-setup-tutorial/note-2.png b/docs/blog/assets/media/claude-code-multi-agent-setup-tutorial/note-2.png
new file mode 100644
index 00000000..f0ad2980
Binary files /dev/null and b/docs/blog/assets/media/claude-code-multi-agent-setup-tutorial/note-2.png differ
diff --git a/docs/blog/assets/media/claude-code-orchestration-guide/note-1.png b/docs/blog/assets/media/claude-code-orchestration-guide/note-1.png
new file mode 100644
index 00000000..37a55826
Binary files /dev/null and b/docs/blog/assets/media/claude-code-orchestration-guide/note-1.png differ
diff --git a/docs/blog/assets/media/claude-code-orchestration-guide/note-2.png b/docs/blog/assets/media/claude-code-orchestration-guide/note-2.png
new file mode 100644
index 00000000..e1dd5332
Binary files /dev/null and b/docs/blog/assets/media/claude-code-orchestration-guide/note-2.png differ
diff --git a/docs/blog/assets/media/claude-code-orchestration-tools-compared/note-1.png b/docs/blog/assets/media/claude-code-orchestration-tools-compared/note-1.png
new file mode 100644
index 00000000..554bf3b9
Binary files /dev/null and b/docs/blog/assets/media/claude-code-orchestration-tools-compared/note-1.png differ
diff --git a/docs/blog/assets/media/claude-code-orchestration-tools-compared/note-2.png b/docs/blog/assets/media/claude-code-orchestration-tools-compared/note-2.png
new file mode 100644
index 00000000..53b64897
Binary files /dev/null and b/docs/blog/assets/media/claude-code-orchestration-tools-compared/note-2.png differ
diff --git a/docs/blog/assets/media/claude-code-subagents-vs-multi-agent-harness/note-1.png b/docs/blog/assets/media/claude-code-subagents-vs-multi-agent-harness/note-1.png
new file mode 100644
index 00000000..9d56a5a9
Binary files /dev/null and b/docs/blog/assets/media/claude-code-subagents-vs-multi-agent-harness/note-1.png differ
diff --git a/docs/blog/assets/media/claude-code-subagents-vs-multi-agent-harness/note-2.png b/docs/blog/assets/media/claude-code-subagents-vs-multi-agent-harness/note-2.png
new file mode 100644
index 00000000..87c062a6
Binary files /dev/null and b/docs/blog/assets/media/claude-code-subagents-vs-multi-agent-harness/note-2.png differ
diff --git a/docs/blog/assets/media/claude-squad-alternative/note-1.png b/docs/blog/assets/media/claude-squad-alternative/note-1.png
new file mode 100644
index 00000000..64c7bb30
Binary files /dev/null and b/docs/blog/assets/media/claude-squad-alternative/note-1.png differ
diff --git a/docs/blog/assets/media/claude-squad-alternative/note-2.png b/docs/blog/assets/media/claude-squad-alternative/note-2.png
new file mode 100644
index 00000000..46025211
Binary files /dev/null and b/docs/blog/assets/media/claude-squad-alternative/note-2.png differ
diff --git a/docs/blog/assets/media/claude-squad-vs-munder-difflin/note-1.png b/docs/blog/assets/media/claude-squad-vs-munder-difflin/note-1.png
new file mode 100644
index 00000000..5f7c322a
Binary files /dev/null and b/docs/blog/assets/media/claude-squad-vs-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/claude-squad-vs-munder-difflin/note-2.png b/docs/blog/assets/media/claude-squad-vs-munder-difflin/note-2.png
new file mode 100644
index 00000000..817ac478
Binary files /dev/null and b/docs/blog/assets/media/claude-squad-vs-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/cline-vs-munder-difflin/note-1.png b/docs/blog/assets/media/cline-vs-munder-difflin/note-1.png
new file mode 100644
index 00000000..2f6b4403
Binary files /dev/null and b/docs/blog/assets/media/cline-vs-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/cline-vs-munder-difflin/note-2.png b/docs/blog/assets/media/cline-vs-munder-difflin/note-2.png
new file mode 100644
index 00000000..faf1300c
Binary files /dev/null and b/docs/blog/assets/media/cline-vs-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/command-center-guide/note-1.png b/docs/blog/assets/media/command-center-guide/note-1.png
new file mode 100644
index 00000000..45c20adf
Binary files /dev/null and b/docs/blog/assets/media/command-center-guide/note-1.png differ
diff --git a/docs/blog/assets/media/command-center-guide/note-2.png b/docs/blog/assets/media/command-center-guide/note-2.png
new file mode 100644
index 00000000..7262351a
Binary files /dev/null and b/docs/blog/assets/media/command-center-guide/note-2.png differ
diff --git a/docs/blog/assets/media/compressing-agent-memory/note-1.png b/docs/blog/assets/media/compressing-agent-memory/note-1.png
new file mode 100644
index 00000000..317a7161
Binary files /dev/null and b/docs/blog/assets/media/compressing-agent-memory/note-1.png differ
diff --git a/docs/blog/assets/media/compressing-agent-memory/note-2.png b/docs/blog/assets/media/compressing-agent-memory/note-2.png
new file mode 100644
index 00000000..561f01f8
Binary files /dev/null and b/docs/blog/assets/media/compressing-agent-memory/note-2.png differ
diff --git a/docs/blog/assets/media/conductor-claude-code-alternative/note-1.png b/docs/blog/assets/media/conductor-claude-code-alternative/note-1.png
new file mode 100644
index 00000000..2b5650ef
Binary files /dev/null and b/docs/blog/assets/media/conductor-claude-code-alternative/note-1.png differ
diff --git a/docs/blog/assets/media/conductor-claude-code-alternative/note-2.png b/docs/blog/assets/media/conductor-claude-code-alternative/note-2.png
new file mode 100644
index 00000000..9d7ef0b3
Binary files /dev/null and b/docs/blog/assets/media/conductor-claude-code-alternative/note-2.png differ
diff --git a/docs/blog/assets/media/context-engineering-for-ai-agents/note-1.png b/docs/blog/assets/media/context-engineering-for-ai-agents/note-1.png
new file mode 100644
index 00000000..db033df5
Binary files /dev/null and b/docs/blog/assets/media/context-engineering-for-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/context-engineering-for-ai-agents/note-2.png b/docs/blog/assets/media/context-engineering-for-ai-agents/note-2.png
new file mode 100644
index 00000000..8848bad4
Binary files /dev/null and b/docs/blog/assets/media/context-engineering-for-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/coordinating-ai-coding-agents/note-1.png b/docs/blog/assets/media/coordinating-ai-coding-agents/note-1.png
new file mode 100644
index 00000000..0eba121d
Binary files /dev/null and b/docs/blog/assets/media/coordinating-ai-coding-agents/note-1.png differ
diff --git a/docs/blog/assets/media/coordinating-ai-coding-agents/note-2.png b/docs/blog/assets/media/coordinating-ai-coding-agents/note-2.png
new file mode 100644
index 00000000..44daa838
Binary files /dev/null and b/docs/blog/assets/media/coordinating-ai-coding-agents/note-2.png differ
diff --git a/docs/blog/assets/media/crewai-autogen-vs-a-local-agent-harness/note-1.png b/docs/blog/assets/media/crewai-autogen-vs-a-local-agent-harness/note-1.png
new file mode 100644
index 00000000..2c2130e4
Binary files /dev/null and b/docs/blog/assets/media/crewai-autogen-vs-a-local-agent-harness/note-1.png differ
diff --git a/docs/blog/assets/media/crewai-autogen-vs-a-local-agent-harness/note-2.png b/docs/blog/assets/media/crewai-autogen-vs-a-local-agent-harness/note-2.png
new file mode 100644
index 00000000..ef4ce841
Binary files /dev/null and b/docs/blog/assets/media/crewai-autogen-vs-a-local-agent-harness/note-2.png differ
diff --git a/docs/blog/assets/media/crystal-claude-code-alternative/note-1.png b/docs/blog/assets/media/crystal-claude-code-alternative/note-1.png
new file mode 100644
index 00000000..bc4e4c9f
Binary files /dev/null and b/docs/blog/assets/media/crystal-claude-code-alternative/note-1.png differ
diff --git a/docs/blog/assets/media/crystal-claude-code-alternative/note-2.png b/docs/blog/assets/media/crystal-claude-code-alternative/note-2.png
new file mode 100644
index 00000000..70a47f77
Binary files /dev/null and b/docs/blog/assets/media/crystal-claude-code-alternative/note-2.png differ
diff --git a/docs/blog/assets/media/debugging-multi-agent-systems/note-1.png b/docs/blog/assets/media/debugging-multi-agent-systems/note-1.png
new file mode 100644
index 00000000..54d7bf43
Binary files /dev/null and b/docs/blog/assets/media/debugging-multi-agent-systems/note-1.png differ
diff --git a/docs/blog/assets/media/debugging-multi-agent-systems/note-2.png b/docs/blog/assets/media/debugging-multi-agent-systems/note-2.png
new file mode 100644
index 00000000..4b7f4747
Binary files /dev/null and b/docs/blog/assets/media/debugging-multi-agent-systems/note-2.png differ
diff --git a/docs/blog/assets/media/deploy-a-blog-writer-agent/note-1.png b/docs/blog/assets/media/deploy-a-blog-writer-agent/note-1.png
new file mode 100644
index 00000000..d7faecc4
Binary files /dev/null and b/docs/blog/assets/media/deploy-a-blog-writer-agent/note-1.png differ
diff --git a/docs/blog/assets/media/deploy-a-blog-writer-agent/note-2.png b/docs/blog/assets/media/deploy-a-blog-writer-agent/note-2.png
new file mode 100644
index 00000000..f3f4c1e7
Binary files /dev/null and b/docs/blog/assets/media/deploy-a-blog-writer-agent/note-2.png differ
diff --git a/docs/blog/assets/media/deploy-automated-pr-reviewer-agent/note-1.png b/docs/blog/assets/media/deploy-automated-pr-reviewer-agent/note-1.png
new file mode 100644
index 00000000..738806fc
Binary files /dev/null and b/docs/blog/assets/media/deploy-automated-pr-reviewer-agent/note-1.png differ
diff --git a/docs/blog/assets/media/deploy-automated-pr-reviewer-agent/note-2.png b/docs/blog/assets/media/deploy-automated-pr-reviewer-agent/note-2.png
new file mode 100644
index 00000000..6dafa86e
Binary files /dev/null and b/docs/blog/assets/media/deploy-automated-pr-reviewer-agent/note-2.png differ
diff --git a/docs/blog/assets/media/do-more-with-less-model-routing/note-1.png b/docs/blog/assets/media/do-more-with-less-model-routing/note-1.png
new file mode 100644
index 00000000..25c04638
Binary files /dev/null and b/docs/blog/assets/media/do-more-with-less-model-routing/note-1.png differ
diff --git a/docs/blog/assets/media/do-more-with-less-model-routing/note-2.png b/docs/blog/assets/media/do-more-with-less-model-routing/note-2.png
new file mode 100644
index 00000000..2bd3e113
Binary files /dev/null and b/docs/blog/assets/media/do-more-with-less-model-routing/note-2.png differ
diff --git a/docs/blog/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-1.png b/docs/blog/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-1.png
new file mode 100644
index 00000000..4d87ccae
Binary files /dev/null and b/docs/blog/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-2.png b/docs/blog/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-2.png
new file mode 100644
index 00000000..152ddc8c
Binary files /dev/null and b/docs/blog/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/evaluating-ai-agent-reliability/note-1.png b/docs/blog/assets/media/evaluating-ai-agent-reliability/note-1.png
new file mode 100644
index 00000000..ff888d5d
Binary files /dev/null and b/docs/blog/assets/media/evaluating-ai-agent-reliability/note-1.png differ
diff --git a/docs/blog/assets/media/evaluating-ai-agent-reliability/note-2.png b/docs/blog/assets/media/evaluating-ai-agent-reliability/note-2.png
new file mode 100644
index 00000000..aa9fe574
Binary files /dev/null and b/docs/blog/assets/media/evaluating-ai-agent-reliability/note-2.png differ
diff --git a/docs/blog/assets/media/file-based-coordination-vs-message-queues/note-1.png b/docs/blog/assets/media/file-based-coordination-vs-message-queues/note-1.png
new file mode 100644
index 00000000..edff9817
Binary files /dev/null and b/docs/blog/assets/media/file-based-coordination-vs-message-queues/note-1.png differ
diff --git a/docs/blog/assets/media/file-based-coordination-vs-message-queues/note-2.png b/docs/blog/assets/media/file-based-coordination-vs-message-queues/note-2.png
new file mode 100644
index 00000000..2d016f2e
Binary files /dev/null and b/docs/blog/assets/media/file-based-coordination-vs-message-queues/note-2.png differ
diff --git a/docs/blog/assets/media/from-one-terminal-to-a-team/note-1.png b/docs/blog/assets/media/from-one-terminal-to-a-team/note-1.png
new file mode 100644
index 00000000..10c5cf99
Binary files /dev/null and b/docs/blog/assets/media/from-one-terminal-to-a-team/note-1.png differ
diff --git a/docs/blog/assets/media/from-one-terminal-to-a-team/note-2.png b/docs/blog/assets/media/from-one-terminal-to-a-team/note-2.png
new file mode 100644
index 00000000..2fece6fc
Binary files /dev/null and b/docs/blog/assets/media/from-one-terminal-to-a-team/note-2.png differ
diff --git a/docs/blog/assets/media/generative-engine-optimization-techniques/note-1.png b/docs/blog/assets/media/generative-engine-optimization-techniques/note-1.png
new file mode 100644
index 00000000..67073a07
Binary files /dev/null and b/docs/blog/assets/media/generative-engine-optimization-techniques/note-1.png differ
diff --git a/docs/blog/assets/media/generative-engine-optimization-techniques/note-2.png b/docs/blog/assets/media/generative-engine-optimization-techniques/note-2.png
new file mode 100644
index 00000000..6f5888dc
Binary files /dev/null and b/docs/blog/assets/media/generative-engine-optimization-techniques/note-2.png differ
diff --git a/docs/blog/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-1.png b/docs/blog/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-1.png
new file mode 100644
index 00000000..c2e94da5
Binary files /dev/null and b/docs/blog/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-1.png differ
diff --git a/docs/blog/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-2.png b/docs/blog/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-2.png
new file mode 100644
index 00000000..0256cf19
Binary files /dev/null and b/docs/blog/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-2.png differ
diff --git a/docs/blog/assets/media/give-claude-code-long-term-memory/note-1.png b/docs/blog/assets/media/give-claude-code-long-term-memory/note-1.png
new file mode 100644
index 00000000..da291474
Binary files /dev/null and b/docs/blog/assets/media/give-claude-code-long-term-memory/note-1.png differ
diff --git a/docs/blog/assets/media/give-claude-code-long-term-memory/note-2.png b/docs/blog/assets/media/give-claude-code-long-term-memory/note-2.png
new file mode 100644
index 00000000..e11a0d28
Binary files /dev/null and b/docs/blog/assets/media/give-claude-code-long-term-memory/note-2.png differ
diff --git a/docs/blog/assets/media/hire-manifest-untrusted-input/note-1.png b/docs/blog/assets/media/hire-manifest-untrusted-input/note-1.png
new file mode 100644
index 00000000..22309b54
Binary files /dev/null and b/docs/blog/assets/media/hire-manifest-untrusted-input/note-1.png differ
diff --git a/docs/blog/assets/media/hire-manifest-untrusted-input/note-2.png b/docs/blog/assets/media/hire-manifest-untrusted-input/note-2.png
new file mode 100644
index 00000000..dbea7f7e
Binary files /dev/null and b/docs/blog/assets/media/hire-manifest-untrusted-input/note-2.png differ
diff --git a/docs/blog/assets/media/how-agents-remember-semantic-memory/note-1.png b/docs/blog/assets/media/how-agents-remember-semantic-memory/note-1.png
new file mode 100644
index 00000000..d1e0c619
Binary files /dev/null and b/docs/blog/assets/media/how-agents-remember-semantic-memory/note-1.png differ
diff --git a/docs/blog/assets/media/how-agents-remember-semantic-memory/note-2.png b/docs/blog/assets/media/how-agents-remember-semantic-memory/note-2.png
new file mode 100644
index 00000000..92282a81
Binary files /dev/null and b/docs/blog/assets/media/how-agents-remember-semantic-memory/note-2.png differ
diff --git a/docs/blog/assets/media/how-ai-agents-verify-their-own-work/note-1.png b/docs/blog/assets/media/how-ai-agents-verify-their-own-work/note-1.png
new file mode 100644
index 00000000..d50b3362
Binary files /dev/null and b/docs/blog/assets/media/how-ai-agents-verify-their-own-work/note-1.png differ
diff --git a/docs/blog/assets/media/how-ai-agents-verify-their-own-work/note-2.png b/docs/blog/assets/media/how-ai-agents-verify-their-own-work/note-2.png
new file mode 100644
index 00000000..03965ca0
Binary files /dev/null and b/docs/blog/assets/media/how-ai-agents-verify-their-own-work/note-2.png differ
diff --git a/docs/blog/assets/media/how-ai-answer-engines-choose-sources/note-1.png b/docs/blog/assets/media/how-ai-answer-engines-choose-sources/note-1.png
new file mode 100644
index 00000000..6a67fc79
Binary files /dev/null and b/docs/blog/assets/media/how-ai-answer-engines-choose-sources/note-1.png differ
diff --git a/docs/blog/assets/media/how-ai-answer-engines-choose-sources/note-2.png b/docs/blog/assets/media/how-ai-answer-engines-choose-sources/note-2.png
new file mode 100644
index 00000000..30ba4898
Binary files /dev/null and b/docs/blog/assets/media/how-ai-answer-engines-choose-sources/note-2.png differ
diff --git a/docs/blog/assets/media/how-the-god-orchestrator-works/note-1.png b/docs/blog/assets/media/how-the-god-orchestrator-works/note-1.png
new file mode 100644
index 00000000..a3295b30
Binary files /dev/null and b/docs/blog/assets/media/how-the-god-orchestrator-works/note-1.png differ
diff --git a/docs/blog/assets/media/how-the-god-orchestrator-works/note-2.png b/docs/blog/assets/media/how-the-god-orchestrator-works/note-2.png
new file mode 100644
index 00000000..d0e28303
Binary files /dev/null and b/docs/blog/assets/media/how-the-god-orchestrator-works/note-2.png differ
diff --git a/docs/blog/assets/media/how-to-add-a-github-copilot-cli-agent/note-1.png b/docs/blog/assets/media/how-to-add-a-github-copilot-cli-agent/note-1.png
new file mode 100644
index 00000000..eb8fd28b
Binary files /dev/null and b/docs/blog/assets/media/how-to-add-a-github-copilot-cli-agent/note-1.png differ
diff --git a/docs/blog/assets/media/how-to-add-a-github-copilot-cli-agent/note-2.png b/docs/blog/assets/media/how-to-add-a-github-copilot-cli-agent/note-2.png
new file mode 100644
index 00000000..725bd5d8
Binary files /dev/null and b/docs/blog/assets/media/how-to-add-a-github-copilot-cli-agent/note-2.png differ
diff --git a/docs/blog/assets/media/how-to-choose-a-multi-agent-tool/note-1.png b/docs/blog/assets/media/how-to-choose-a-multi-agent-tool/note-1.png
new file mode 100644
index 00000000..67b1f86b
Binary files /dev/null and b/docs/blog/assets/media/how-to-choose-a-multi-agent-tool/note-1.png differ
diff --git a/docs/blog/assets/media/how-to-choose-a-multi-agent-tool/note-2.png b/docs/blog/assets/media/how-to-choose-a-multi-agent-tool/note-2.png
new file mode 100644
index 00000000..6c1f1923
Binary files /dev/null and b/docs/blog/assets/media/how-to-choose-a-multi-agent-tool/note-2.png differ
diff --git a/docs/blog/assets/media/how-to-hire-from-the-agent-gallery/note-1.png b/docs/blog/assets/media/how-to-hire-from-the-agent-gallery/note-1.png
new file mode 100644
index 00000000..601446e6
Binary files /dev/null and b/docs/blog/assets/media/how-to-hire-from-the-agent-gallery/note-1.png differ
diff --git a/docs/blog/assets/media/how-to-hire-from-the-agent-gallery/note-2.png b/docs/blog/assets/media/how-to-hire-from-the-agent-gallery/note-2.png
new file mode 100644
index 00000000..b04d572f
Binary files /dev/null and b/docs/blog/assets/media/how-to-hire-from-the-agent-gallery/note-2.png differ
diff --git a/docs/blog/assets/media/how-to-install-and-use-munder-difflin/note-1.png b/docs/blog/assets/media/how-to-install-and-use-munder-difflin/note-1.png
new file mode 100644
index 00000000..81d7bfb7
Binary files /dev/null and b/docs/blog/assets/media/how-to-install-and-use-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/how-to-install-and-use-munder-difflin/note-2.png b/docs/blog/assets/media/how-to-install-and-use-munder-difflin/note-2.png
new file mode 100644
index 00000000..758755e2
Binary files /dev/null and b/docs/blog/assets/media/how-to-install-and-use-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/how-to-run-multiple-claude-code-agents/note-1.png b/docs/blog/assets/media/how-to-run-multiple-claude-code-agents/note-1.png
new file mode 100644
index 00000000..f3e4e360
Binary files /dev/null and b/docs/blog/assets/media/how-to-run-multiple-claude-code-agents/note-1.png differ
diff --git a/docs/blog/assets/media/how-to-run-multiple-claude-code-agents/note-2.png b/docs/blog/assets/media/how-to-run-multiple-claude-code-agents/note-2.png
new file mode 100644
index 00000000..9f0f0396
Binary files /dev/null and b/docs/blog/assets/media/how-to-run-multiple-claude-code-agents/note-2.png differ
diff --git a/docs/blog/assets/media/how-to-talk-to-your-orchestrator/note-1.png b/docs/blog/assets/media/how-to-talk-to-your-orchestrator/note-1.png
new file mode 100644
index 00000000..eeb39ecb
Binary files /dev/null and b/docs/blog/assets/media/how-to-talk-to-your-orchestrator/note-1.png differ
diff --git a/docs/blog/assets/media/how-to-talk-to-your-orchestrator/note-2.png b/docs/blog/assets/media/how-to-talk-to-your-orchestrator/note-2.png
new file mode 100644
index 00000000..41f90b1f
Binary files /dev/null and b/docs/blog/assets/media/how-to-talk-to-your-orchestrator/note-2.png differ
diff --git a/docs/blog/assets/media/how-to-use-the-built-in-monaco-ide/note-1.png b/docs/blog/assets/media/how-to-use-the-built-in-monaco-ide/note-1.png
new file mode 100644
index 00000000..cc12e699
Binary files /dev/null and b/docs/blog/assets/media/how-to-use-the-built-in-monaco-ide/note-1.png differ
diff --git a/docs/blog/assets/media/how-to-use-the-built-in-monaco-ide/note-2.png b/docs/blog/assets/media/how-to-use-the-built-in-monaco-ide/note-2.png
new file mode 100644
index 00000000..98b19878
Binary files /dev/null and b/docs/blog/assets/media/how-to-use-the-built-in-monaco-ide/note-2.png differ
diff --git a/docs/blog/assets/media/human-in-the-loop-ai-agents/note-1.png b/docs/blog/assets/media/human-in-the-loop-ai-agents/note-1.png
new file mode 100644
index 00000000..1db28186
Binary files /dev/null and b/docs/blog/assets/media/human-in-the-loop-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/human-in-the-loop-ai-agents/note-2.png b/docs/blog/assets/media/human-in-the-loop-ai-agents/note-2.png
new file mode 100644
index 00000000..d02e3bb6
Binary files /dev/null and b/docs/blog/assets/media/human-in-the-loop-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/human-in-the-loop-approving-ai-agents/note-1.png b/docs/blog/assets/media/human-in-the-loop-approving-ai-agents/note-1.png
new file mode 100644
index 00000000..cff78e5e
Binary files /dev/null and b/docs/blog/assets/media/human-in-the-loop-approving-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/human-in-the-loop-approving-ai-agents/note-2.png b/docs/blog/assets/media/human-in-the-loop-approving-ai-agents/note-2.png
new file mode 100644
index 00000000..ad521fa1
Binary files /dev/null and b/docs/blog/assets/media/human-in-the-loop-approving-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/keep-agent-semantic-memory-clean/note-1.png b/docs/blog/assets/media/keep-agent-semantic-memory-clean/note-1.png
new file mode 100644
index 00000000..ac496b7a
Binary files /dev/null and b/docs/blog/assets/media/keep-agent-semantic-memory-clean/note-1.png differ
diff --git a/docs/blog/assets/media/keep-agent-semantic-memory-clean/note-2.png b/docs/blog/assets/media/keep-agent-semantic-memory-clean/note-2.png
new file mode 100644
index 00000000..6279a843
Binary files /dev/null and b/docs/blog/assets/media/keep-agent-semantic-memory-clean/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-2-0/note-1.png b/docs/blog/assets/media/launching-munder-difflin-v0-2-0/note-1.png
new file mode 100644
index 00000000..28558a1c
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-2-0/note-1.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-2-0/note-2.png b/docs/blog/assets/media/launching-munder-difflin-v0-2-0/note-2.png
new file mode 100644
index 00000000..70b39933
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-2-0/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-2-4/note-1.png b/docs/blog/assets/media/launching-munder-difflin-v0-2-4/note-1.png
new file mode 100644
index 00000000..ed0f8dd1
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-2-4/note-1.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-2-4/note-2.png b/docs/blog/assets/media/launching-munder-difflin-v0-2-4/note-2.png
new file mode 100644
index 00000000..78f7ca23
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-2-4/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-2-8/note-1.png b/docs/blog/assets/media/launching-munder-difflin-v0-2-8/note-1.png
new file mode 100644
index 00000000..b2984c64
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-2-8/note-1.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-2-8/note-2.png b/docs/blog/assets/media/launching-munder-difflin-v0-2-8/note-2.png
new file mode 100644
index 00000000..8b55b423
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-2-8/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-3-0/note-1.png b/docs/blog/assets/media/launching-munder-difflin-v0-3-0/note-1.png
new file mode 100644
index 00000000..15345b74
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-3-0/note-1.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-3-0/note-2.png b/docs/blog/assets/media/launching-munder-difflin-v0-3-0/note-2.png
new file mode 100644
index 00000000..7bae6983
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-3-0/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-3-2/note-1.png b/docs/blog/assets/media/launching-munder-difflin-v0-3-2/note-1.png
new file mode 100644
index 00000000..cc4b2944
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-3-2/note-1.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-3-2/note-2.png b/docs/blog/assets/media/launching-munder-difflin-v0-3-2/note-2.png
new file mode 100644
index 00000000..0c72f561
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-3-2/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-3-3/note-1.png b/docs/blog/assets/media/launching-munder-difflin-v0-3-3/note-1.png
new file mode 100644
index 00000000..6fe67f5c
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-3-3/note-1.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-3-3/note-2.png b/docs/blog/assets/media/launching-munder-difflin-v0-3-3/note-2.png
new file mode 100644
index 00000000..faced389
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-3-3/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-3-5/note-1.png b/docs/blog/assets/media/launching-munder-difflin-v0-3-5/note-1.png
new file mode 100644
index 00000000..cec4fc39
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-3-5/note-1.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-3-5/note-2.png b/docs/blog/assets/media/launching-munder-difflin-v0-3-5/note-2.png
new file mode 100644
index 00000000..e21408b3
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-3-5/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png b/docs/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png
new file mode 100644
index 00000000..90bf6507
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-1.png b/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-1.png
new file mode 100644
index 00000000..dd54baa0
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-1.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-2.png b/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-2.png
new file mode 100644
index 00000000..e20d3db8
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-2.png differ
diff --git a/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-3.png b/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-3.png
new file mode 100644
index 00000000..4da97143
Binary files /dev/null and b/docs/blog/assets/media/launching-munder-difflin-v0-4-4/note-3.png differ
diff --git a/docs/blog/assets/media/local-first-ai-agent-orchestration/note-1.png b/docs/blog/assets/media/local-first-ai-agent-orchestration/note-1.png
new file mode 100644
index 00000000..4befc9eb
Binary files /dev/null and b/docs/blog/assets/media/local-first-ai-agent-orchestration/note-1.png differ
diff --git a/docs/blog/assets/media/local-first-ai-agent-orchestration/note-2.png b/docs/blog/assets/media/local-first-ai-agent-orchestration/note-2.png
new file mode 100644
index 00000000..1c4d7696
Binary files /dev/null and b/docs/blog/assets/media/local-first-ai-agent-orchestration/note-2.png differ
diff --git a/docs/blog/assets/media/local-first-vs-cloud-agent-sdks/note-1.png b/docs/blog/assets/media/local-first-vs-cloud-agent-sdks/note-1.png
new file mode 100644
index 00000000..e50056d3
Binary files /dev/null and b/docs/blog/assets/media/local-first-vs-cloud-agent-sdks/note-1.png differ
diff --git a/docs/blog/assets/media/local-first-vs-cloud-agent-sdks/note-2.png b/docs/blog/assets/media/local-first-vs-cloud-agent-sdks/note-2.png
new file mode 100644
index 00000000..6b0928cf
Binary files /dev/null and b/docs/blog/assets/media/local-first-vs-cloud-agent-sdks/note-2.png differ
diff --git a/docs/blog/assets/media/long-running-agents-the-2026-shift/note-1.png b/docs/blog/assets/media/long-running-agents-the-2026-shift/note-1.png
new file mode 100644
index 00000000..b4ac9164
Binary files /dev/null and b/docs/blog/assets/media/long-running-agents-the-2026-shift/note-1.png differ
diff --git a/docs/blog/assets/media/long-running-agents-the-2026-shift/note-2.png b/docs/blog/assets/media/long-running-agents-the-2026-shift/note-2.png
new file mode 100644
index 00000000..875cb4d5
Binary files /dev/null and b/docs/blog/assets/media/long-running-agents-the-2026-shift/note-2.png differ
diff --git a/docs/blog/assets/media/loop-engineering-for-ai-agents/note-1.png b/docs/blog/assets/media/loop-engineering-for-ai-agents/note-1.png
new file mode 100644
index 00000000..89c0e187
Binary files /dev/null and b/docs/blog/assets/media/loop-engineering-for-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/loop-engineering-for-ai-agents/note-2.png b/docs/blog/assets/media/loop-engineering-for-ai-agents/note-2.png
new file mode 100644
index 00000000..e34f4caa
Binary files /dev/null and b/docs/blog/assets/media/loop-engineering-for-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/manage-multiple-claude-code-sessions/note-1.png b/docs/blog/assets/media/manage-multiple-claude-code-sessions/note-1.png
new file mode 100644
index 00000000..8f055b85
Binary files /dev/null and b/docs/blog/assets/media/manage-multiple-claude-code-sessions/note-1.png differ
diff --git a/docs/blog/assets/media/manage-multiple-claude-code-sessions/note-2.png b/docs/blog/assets/media/manage-multiple-claude-code-sessions/note-2.png
new file mode 100644
index 00000000..2251d235
Binary files /dev/null and b/docs/blog/assets/media/manage-multiple-claude-code-sessions/note-2.png differ
diff --git a/docs/blog/assets/media/markdown-first-agent-memory/note-1.png b/docs/blog/assets/media/markdown-first-agent-memory/note-1.png
new file mode 100644
index 00000000..6651136d
Binary files /dev/null and b/docs/blog/assets/media/markdown-first-agent-memory/note-1.png differ
diff --git a/docs/blog/assets/media/markdown-first-agent-memory/note-2.png b/docs/blog/assets/media/markdown-first-agent-memory/note-2.png
new file mode 100644
index 00000000..9020ba66
Binary files /dev/null and b/docs/blog/assets/media/markdown-first-agent-memory/note-2.png differ
diff --git a/docs/blog/assets/media/mcp-and-skills-in-a-hive/note-1.png b/docs/blog/assets/media/mcp-and-skills-in-a-hive/note-1.png
new file mode 100644
index 00000000..4ff5db92
Binary files /dev/null and b/docs/blog/assets/media/mcp-and-skills-in-a-hive/note-1.png differ
diff --git a/docs/blog/assets/media/mcp-and-skills-in-a-hive/note-2.png b/docs/blog/assets/media/mcp-and-skills-in-a-hive/note-2.png
new file mode 100644
index 00000000..08633f63
Binary files /dev/null and b/docs/blog/assets/media/mcp-and-skills-in-a-hive/note-2.png differ
diff --git a/docs/blog/assets/media/mcp-security-tool-poisoning/note-1.png b/docs/blog/assets/media/mcp-security-tool-poisoning/note-1.png
new file mode 100644
index 00000000..d09e8303
Binary files /dev/null and b/docs/blog/assets/media/mcp-security-tool-poisoning/note-1.png differ
diff --git a/docs/blog/assets/media/mcp-security-tool-poisoning/note-2.png b/docs/blog/assets/media/mcp-security-tool-poisoning/note-2.png
new file mode 100644
index 00000000..43d8a9f3
Binary files /dev/null and b/docs/blog/assets/media/mcp-security-tool-poisoning/note-2.png differ
diff --git a/docs/blog/assets/media/multi-agent-orchestration-patterns/note-1.png b/docs/blog/assets/media/multi-agent-orchestration-patterns/note-1.png
new file mode 100644
index 00000000..c95bd7e3
Binary files /dev/null and b/docs/blog/assets/media/multi-agent-orchestration-patterns/note-1.png differ
diff --git a/docs/blog/assets/media/multi-agent-orchestration-patterns/note-2.png b/docs/blog/assets/media/multi-agent-orchestration-patterns/note-2.png
new file mode 100644
index 00000000..ca18f41a
Binary files /dev/null and b/docs/blog/assets/media/multi-agent-orchestration-patterns/note-2.png differ
diff --git a/docs/blog/assets/media/munder-difflin-faq/note-1.png b/docs/blog/assets/media/munder-difflin-faq/note-1.png
new file mode 100644
index 00000000..adcbea65
Binary files /dev/null and b/docs/blog/assets/media/munder-difflin-faq/note-1.png differ
diff --git a/docs/blog/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-1.png b/docs/blog/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-1.png
new file mode 100644
index 00000000..601446e6
Binary files /dev/null and b/docs/blog/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-1.png differ
diff --git a/docs/blog/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-2.png b/docs/blog/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-2.png
new file mode 100644
index 00000000..2f4c9f42
Binary files /dev/null and b/docs/blog/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-2.png differ
diff --git a/docs/blog/assets/media/node-pty-electron-real-terminals/note-1.png b/docs/blog/assets/media/node-pty-electron-real-terminals/note-1.png
new file mode 100644
index 00000000..047b6bfe
Binary files /dev/null and b/docs/blog/assets/media/node-pty-electron-real-terminals/note-1.png differ
diff --git a/docs/blog/assets/media/node-pty-electron-real-terminals/note-2.png b/docs/blog/assets/media/node-pty-electron-real-terminals/note-2.png
new file mode 100644
index 00000000..9f00b037
Binary files /dev/null and b/docs/blog/assets/media/node-pty-electron-real-terminals/note-2.png differ
diff --git a/docs/blog/assets/media/number-five-on-product-hunt/hero.png b/docs/blog/assets/media/number-five-on-product-hunt/hero.png
new file mode 100644
index 00000000..be23a966
Binary files /dev/null and b/docs/blog/assets/media/number-five-on-product-hunt/hero.png differ
diff --git a/docs/blog/assets/media/number-five-on-product-hunt/note-1.png b/docs/blog/assets/media/number-five-on-product-hunt/note-1.png
new file mode 100644
index 00000000..3c184ac0
Binary files /dev/null and b/docs/blog/assets/media/number-five-on-product-hunt/note-1.png differ
diff --git a/docs/blog/assets/media/number-five-on-product-hunt/note-2.png b/docs/blog/assets/media/number-five-on-product-hunt/note-2.png
new file mode 100644
index 00000000..b6d0e6c1
Binary files /dev/null and b/docs/blog/assets/media/number-five-on-product-hunt/note-2.png differ
diff --git a/docs/blog/assets/media/observability-for-agent-fleets/note-1.png b/docs/blog/assets/media/observability-for-agent-fleets/note-1.png
new file mode 100644
index 00000000..09e8f326
Binary files /dev/null and b/docs/blog/assets/media/observability-for-agent-fleets/note-1.png differ
diff --git a/docs/blog/assets/media/observability-for-agent-fleets/note-2.png b/docs/blog/assets/media/observability-for-agent-fleets/note-2.png
new file mode 100644
index 00000000..8367a2a4
Binary files /dev/null and b/docs/blog/assets/media/observability-for-agent-fleets/note-2.png differ
diff --git a/docs/blog/assets/media/one-prompt-automated-pr-review/note-1.png b/docs/blog/assets/media/one-prompt-automated-pr-review/note-1.png
new file mode 100644
index 00000000..f5ebf957
Binary files /dev/null and b/docs/blog/assets/media/one-prompt-automated-pr-review/note-1.png differ
diff --git a/docs/blog/assets/media/one-prompt-automated-pr-review/note-2.png b/docs/blog/assets/media/one-prompt-automated-pr-review/note-2.png
new file mode 100644
index 00000000..e6e6a3e1
Binary files /dev/null and b/docs/blog/assets/media/one-prompt-automated-pr-review/note-2.png differ
diff --git a/docs/blog/assets/media/open-source-ai-tools-on-purpose/note-1.png b/docs/blog/assets/media/open-source-ai-tools-on-purpose/note-1.png
new file mode 100644
index 00000000..806dd622
Binary files /dev/null and b/docs/blog/assets/media/open-source-ai-tools-on-purpose/note-1.png differ
diff --git a/docs/blog/assets/media/open-source-ai-tools-on-purpose/note-2.png b/docs/blog/assets/media/open-source-ai-tools-on-purpose/note-2.png
new file mode 100644
index 00000000..9ac66b29
Binary files /dev/null and b/docs/blog/assets/media/open-source-ai-tools-on-purpose/note-2.png differ
diff --git a/docs/blog/assets/media/orca-vs-munder-difflin/note-1.png b/docs/blog/assets/media/orca-vs-munder-difflin/note-1.png
new file mode 100644
index 00000000..51c6c574
Binary files /dev/null and b/docs/blog/assets/media/orca-vs-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/orca-vs-munder-difflin/note-2.png b/docs/blog/assets/media/orca-vs-munder-difflin/note-2.png
new file mode 100644
index 00000000..80e94d6c
Binary files /dev/null and b/docs/blog/assets/media/orca-vs-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/overnight-ai-coding-realistic-expectations/note-1.png b/docs/blog/assets/media/overnight-ai-coding-realistic-expectations/note-1.png
new file mode 100644
index 00000000..ed437891
Binary files /dev/null and b/docs/blog/assets/media/overnight-ai-coding-realistic-expectations/note-1.png differ
diff --git a/docs/blog/assets/media/overnight-ai-coding-realistic-expectations/note-2.png b/docs/blog/assets/media/overnight-ai-coding-realistic-expectations/note-2.png
new file mode 100644
index 00000000..47e84bdb
Binary files /dev/null and b/docs/blog/assets/media/overnight-ai-coding-realistic-expectations/note-2.png differ
diff --git a/docs/blog/assets/media/prompt-caching-for-ai-agents/note-1.png b/docs/blog/assets/media/prompt-caching-for-ai-agents/note-1.png
new file mode 100644
index 00000000..f077c2f6
Binary files /dev/null and b/docs/blog/assets/media/prompt-caching-for-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/prompt-caching-for-ai-agents/note-2.png b/docs/blog/assets/media/prompt-caching-for-ai-agents/note-2.png
new file mode 100644
index 00000000..739cf531
Binary files /dev/null and b/docs/blog/assets/media/prompt-caching-for-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/qm-vs-munder-difflin/note-1.png b/docs/blog/assets/media/qm-vs-munder-difflin/note-1.png
new file mode 100644
index 00000000..f27f9b81
Binary files /dev/null and b/docs/blog/assets/media/qm-vs-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/qm-vs-munder-difflin/note-2.png b/docs/blog/assets/media/qm-vs-munder-difflin/note-2.png
new file mode 100644
index 00000000..10e03b1c
Binary files /dev/null and b/docs/blog/assets/media/qm-vs-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/recovering-from-agent-failures/note-1.png b/docs/blog/assets/media/recovering-from-agent-failures/note-1.png
new file mode 100644
index 00000000..e5e4cf44
Binary files /dev/null and b/docs/blog/assets/media/recovering-from-agent-failures/note-1.png differ
diff --git a/docs/blog/assets/media/recovering-from-agent-failures/note-2.png b/docs/blog/assets/media/recovering-from-agent-failures/note-2.png
new file mode 100644
index 00000000..75fab1fa
Binary files /dev/null and b/docs/blog/assets/media/recovering-from-agent-failures/note-2.png differ
diff --git a/docs/blog/assets/media/rendering-many-live-terminals-performance/note-1.png b/docs/blog/assets/media/rendering-many-live-terminals-performance/note-1.png
new file mode 100644
index 00000000..b616c37a
Binary files /dev/null and b/docs/blog/assets/media/rendering-many-live-terminals-performance/note-1.png differ
diff --git a/docs/blog/assets/media/rendering-many-live-terminals-performance/note-2.png b/docs/blog/assets/media/rendering-many-live-terminals-performance/note-2.png
new file mode 100644
index 00000000..0b36f667
Binary files /dev/null and b/docs/blog/assets/media/rendering-many-live-terminals-performance/note-2.png differ
diff --git a/docs/blog/assets/media/review-agent-work-where-it-happens/note-1.png b/docs/blog/assets/media/review-agent-work-where-it-happens/note-1.png
new file mode 100644
index 00000000..61586a7b
Binary files /dev/null and b/docs/blog/assets/media/review-agent-work-where-it-happens/note-1.png differ
diff --git a/docs/blog/assets/media/review-agent-work-where-it-happens/note-2.png b/docs/blog/assets/media/review-agent-work-where-it-happens/note-2.png
new file mode 100644
index 00000000..31881a8c
Binary files /dev/null and b/docs/blog/assets/media/review-agent-work-where-it-happens/note-2.png differ
diff --git a/docs/blog/assets/media/run-a-mixed-engine-office/note-1.png b/docs/blog/assets/media/run-a-mixed-engine-office/note-1.png
new file mode 100644
index 00000000..b701b328
Binary files /dev/null and b/docs/blog/assets/media/run-a-mixed-engine-office/note-1.png differ
diff --git a/docs/blog/assets/media/run-a-mixed-engine-office/note-2.png b/docs/blog/assets/media/run-a-mixed-engine-office/note-2.png
new file mode 100644
index 00000000..d566f023
Binary files /dev/null and b/docs/blog/assets/media/run-a-mixed-engine-office/note-2.png differ
diff --git a/docs/blog/assets/media/run-a-release-train-with-agents/hero.png b/docs/blog/assets/media/run-a-release-train-with-agents/hero.png
new file mode 100644
index 00000000..46b5b9f1
Binary files /dev/null and b/docs/blog/assets/media/run-a-release-train-with-agents/hero.png differ
diff --git a/docs/blog/assets/media/run-a-release-train-with-agents/note-1.png b/docs/blog/assets/media/run-a-release-train-with-agents/note-1.png
new file mode 100644
index 00000000..76d00f49
Binary files /dev/null and b/docs/blog/assets/media/run-a-release-train-with-agents/note-1.png differ
diff --git a/docs/blog/assets/media/run-a-release-train-with-agents/note-2.png b/docs/blog/assets/media/run-a-release-train-with-agents/note-2.png
new file mode 100644
index 00000000..2211c106
Binary files /dev/null and b/docs/blog/assets/media/run-a-release-train-with-agents/note-2.png differ
diff --git a/docs/blog/assets/media/run-ai-agent-hive-from-slack-setup/note-1.png b/docs/blog/assets/media/run-ai-agent-hive-from-slack-setup/note-1.png
new file mode 100644
index 00000000..e3e51b1a
Binary files /dev/null and b/docs/blog/assets/media/run-ai-agent-hive-from-slack-setup/note-1.png differ
diff --git a/docs/blog/assets/media/run-ai-agent-hive-from-slack-setup/note-2.png b/docs/blog/assets/media/run-ai-agent-hive-from-slack-setup/note-2.png
new file mode 100644
index 00000000..280a68c5
Binary files /dev/null and b/docs/blog/assets/media/run-ai-agent-hive-from-slack-setup/note-2.png differ
diff --git a/docs/blog/assets/media/run-an-office-of-ai-agents/note-1.png b/docs/blog/assets/media/run-an-office-of-ai-agents/note-1.png
new file mode 100644
index 00000000..7719cccc
Binary files /dev/null and b/docs/blog/assets/media/run-an-office-of-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/run-an-office-of-ai-agents/note-2.png b/docs/blog/assets/media/run-an-office-of-ai-agents/note-2.png
new file mode 100644
index 00000000..014f1f67
Binary files /dev/null and b/docs/blog/assets/media/run-an-office-of-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/run-munder-difflin-on-a-mac-mini/note-1.png b/docs/blog/assets/media/run-munder-difflin-on-a-mac-mini/note-1.png
new file mode 100644
index 00000000..a6dee762
Binary files /dev/null and b/docs/blog/assets/media/run-munder-difflin-on-a-mac-mini/note-1.png differ
diff --git a/docs/blog/assets/media/run-munder-difflin-on-a-mac-mini/note-2.png b/docs/blog/assets/media/run-munder-difflin-on-a-mac-mini/note-2.png
new file mode 100644
index 00000000..fc3b628f
Binary files /dev/null and b/docs/blog/assets/media/run-munder-difflin-on-a-mac-mini/note-2.png differ
diff --git a/docs/blog/assets/media/run-munder-difflin-on-open-models/note-1.png b/docs/blog/assets/media/run-munder-difflin-on-open-models/note-1.png
new file mode 100644
index 00000000..2939e3ec
Binary files /dev/null and b/docs/blog/assets/media/run-munder-difflin-on-open-models/note-1.png differ
diff --git a/docs/blog/assets/media/run-munder-difflin-on-open-models/note-2.png b/docs/blog/assets/media/run-munder-difflin-on-open-models/note-2.png
new file mode 100644
index 00000000..2e66282e
Binary files /dev/null and b/docs/blog/assets/media/run-munder-difflin-on-open-models/note-2.png differ
diff --git a/docs/blog/assets/media/scheduling-autonomous-agent-missions/note-1.png b/docs/blog/assets/media/scheduling-autonomous-agent-missions/note-1.png
new file mode 100644
index 00000000..701b5d8d
Binary files /dev/null and b/docs/blog/assets/media/scheduling-autonomous-agent-missions/note-1.png differ
diff --git a/docs/blog/assets/media/scheduling-autonomous-agent-missions/note-2.png b/docs/blog/assets/media/scheduling-autonomous-agent-missions/note-2.png
new file mode 100644
index 00000000..31a16615
Binary files /dev/null and b/docs/blog/assets/media/scheduling-autonomous-agent-missions/note-2.png differ
diff --git a/docs/blog/assets/media/security-for-ai-coding-agents/note-1.png b/docs/blog/assets/media/security-for-ai-coding-agents/note-1.png
new file mode 100644
index 00000000..3537f52b
Binary files /dev/null and b/docs/blog/assets/media/security-for-ai-coding-agents/note-1.png differ
diff --git a/docs/blog/assets/media/security-for-ai-coding-agents/note-2.png b/docs/blog/assets/media/security-for-ai-coding-agents/note-2.png
new file mode 100644
index 00000000..4848b307
Binary files /dev/null and b/docs/blog/assets/media/security-for-ai-coding-agents/note-2.png differ
diff --git a/docs/blog/assets/media/semantic-memory-for-ai-agents/note-1.png b/docs/blog/assets/media/semantic-memory-for-ai-agents/note-1.png
new file mode 100644
index 00000000..c3601515
Binary files /dev/null and b/docs/blog/assets/media/semantic-memory-for-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/semantic-memory-for-ai-agents/note-2.png b/docs/blog/assets/media/semantic-memory-for-ai-agents/note-2.png
new file mode 100644
index 00000000..e79db157
Binary files /dev/null and b/docs/blog/assets/media/semantic-memory-for-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/seven-releases-in-eight-days/hero.png b/docs/blog/assets/media/seven-releases-in-eight-days/hero.png
new file mode 100644
index 00000000..624dc0cb
Binary files /dev/null and b/docs/blog/assets/media/seven-releases-in-eight-days/hero.png differ
diff --git a/docs/blog/assets/media/seven-releases-in-eight-days/note-1.png b/docs/blog/assets/media/seven-releases-in-eight-days/note-1.png
new file mode 100644
index 00000000..199aafca
Binary files /dev/null and b/docs/blog/assets/media/seven-releases-in-eight-days/note-1.png differ
diff --git a/docs/blog/assets/media/seven-releases-in-eight-days/note-2.png b/docs/blog/assets/media/seven-releases-in-eight-days/note-2.png
new file mode 100644
index 00000000..3b4ae830
Binary files /dev/null and b/docs/blog/assets/media/seven-releases-in-eight-days/note-2.png differ
diff --git a/docs/blog/assets/media/seven-releases-in-eight-days/note-3.png b/docs/blog/assets/media/seven-releases-in-eight-days/note-3.png
new file mode 100644
index 00000000..02e0b1e4
Binary files /dev/null and b/docs/blog/assets/media/seven-releases-in-eight-days/note-3.png differ
diff --git a/docs/blog/assets/media/shareable-agent-roles/note-1.png b/docs/blog/assets/media/shareable-agent-roles/note-1.png
new file mode 100644
index 00000000..c712933d
Binary files /dev/null and b/docs/blog/assets/media/shareable-agent-roles/note-1.png differ
diff --git a/docs/blog/assets/media/shareable-agent-roles/note-2.png b/docs/blog/assets/media/shareable-agent-roles/note-2.png
new file mode 100644
index 00000000..25e618f2
Binary files /dev/null and b/docs/blog/assets/media/shareable-agent-roles/note-2.png differ
diff --git a/docs/blog/assets/media/single-committer-git-pattern/note-1.png b/docs/blog/assets/media/single-committer-git-pattern/note-1.png
new file mode 100644
index 00000000..3e2d623e
Binary files /dev/null and b/docs/blog/assets/media/single-committer-git-pattern/note-1.png differ
diff --git a/docs/blog/assets/media/single-committer-git-pattern/note-2.png b/docs/blog/assets/media/single-committer-git-pattern/note-2.png
new file mode 100644
index 00000000..9aed84e6
Binary files /dev/null and b/docs/blog/assets/media/single-committer-git-pattern/note-2.png differ
diff --git a/docs/blog/assets/media/small-team-ai-agents-playbook/note-1.png b/docs/blog/assets/media/small-team-ai-agents-playbook/note-1.png
new file mode 100644
index 00000000..f047fff9
Binary files /dev/null and b/docs/blog/assets/media/small-team-ai-agents-playbook/note-1.png differ
diff --git a/docs/blog/assets/media/small-team-ai-agents-playbook/note-2.png b/docs/blog/assets/media/small-team-ai-agents-playbook/note-2.png
new file mode 100644
index 00000000..36ab55dc
Binary files /dev/null and b/docs/blog/assets/media/small-team-ai-agents-playbook/note-2.png differ
diff --git a/docs/blog/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-1.png b/docs/blog/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-1.png
new file mode 100644
index 00000000..61983efe
Binary files /dev/null and b/docs/blog/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-1.png differ
diff --git a/docs/blog/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-2.png b/docs/blog/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-2.png
new file mode 100644
index 00000000..c0e2ddb1
Binary files /dev/null and b/docs/blog/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-2.png differ
diff --git a/docs/blog/assets/media/the-hook-shim-pattern/note-1.png b/docs/blog/assets/media/the-hook-shim-pattern/note-1.png
new file mode 100644
index 00000000..d06b9c8e
Binary files /dev/null and b/docs/blog/assets/media/the-hook-shim-pattern/note-1.png differ
diff --git a/docs/blog/assets/media/the-hook-shim-pattern/note-2.png b/docs/blog/assets/media/the-hook-shim-pattern/note-2.png
new file mode 100644
index 00000000..818ede31
Binary files /dev/null and b/docs/blog/assets/media/the-hook-shim-pattern/note-2.png differ
diff --git a/docs/blog/assets/media/the-lethal-trifecta-for-coding-agents/note-1.png b/docs/blog/assets/media/the-lethal-trifecta-for-coding-agents/note-1.png
new file mode 100644
index 00000000..881b4ada
Binary files /dev/null and b/docs/blog/assets/media/the-lethal-trifecta-for-coding-agents/note-1.png differ
diff --git a/docs/blog/assets/media/the-lethal-trifecta-for-coding-agents/note-2.png b/docs/blog/assets/media/the-lethal-trifecta-for-coding-agents/note-2.png
new file mode 100644
index 00000000..cdc599a5
Binary files /dev/null and b/docs/blog/assets/media/the-lethal-trifecta-for-coding-agents/note-2.png differ
diff --git a/docs/blog/assets/media/the-multi-agent-cost-playbook/note-1.png b/docs/blog/assets/media/the-multi-agent-cost-playbook/note-1.png
new file mode 100644
index 00000000..d659683c
Binary files /dev/null and b/docs/blog/assets/media/the-multi-agent-cost-playbook/note-1.png differ
diff --git a/docs/blog/assets/media/the-multi-agent-cost-playbook/note-2.png b/docs/blog/assets/media/the-multi-agent-cost-playbook/note-2.png
new file mode 100644
index 00000000..21b6e13e
Binary files /dev/null and b/docs/blog/assets/media/the-multi-agent-cost-playbook/note-2.png differ
diff --git a/docs/blog/assets/media/the-newline-that-silenced-windows-agents/hero.png b/docs/blog/assets/media/the-newline-that-silenced-windows-agents/hero.png
new file mode 100644
index 00000000..5af951ed
Binary files /dev/null and b/docs/blog/assets/media/the-newline-that-silenced-windows-agents/hero.png differ
diff --git a/docs/blog/assets/media/the-newline-that-silenced-windows-agents/note-1.png b/docs/blog/assets/media/the-newline-that-silenced-windows-agents/note-1.png
new file mode 100644
index 00000000..486dc9ac
Binary files /dev/null and b/docs/blog/assets/media/the-newline-that-silenced-windows-agents/note-1.png differ
diff --git a/docs/blog/assets/media/the-newline-that-silenced-windows-agents/note-2.png b/docs/blog/assets/media/the-newline-that-silenced-windows-agents/note-2.png
new file mode 100644
index 00000000..e67ebddd
Binary files /dev/null and b/docs/blog/assets/media/the-newline-that-silenced-windows-agents/note-2.png differ
diff --git a/docs/blog/assets/media/the-office-parody-behind-munder-difflin/note-1.png b/docs/blog/assets/media/the-office-parody-behind-munder-difflin/note-1.png
new file mode 100644
index 00000000..6f15d3e3
Binary files /dev/null and b/docs/blog/assets/media/the-office-parody-behind-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/the-office-parody-behind-munder-difflin/note-2.png b/docs/blog/assets/media/the-office-parody-behind-munder-difflin/note-2.png
new file mode 100644
index 00000000..33786821
Binary files /dev/null and b/docs/blog/assets/media/the-office-parody-behind-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/tmux-and-scripts-vs-an-agent-harness/note-1.png b/docs/blog/assets/media/tmux-and-scripts-vs-an-agent-harness/note-1.png
new file mode 100644
index 00000000..f7d00ea9
Binary files /dev/null and b/docs/blog/assets/media/tmux-and-scripts-vs-an-agent-harness/note-1.png differ
diff --git a/docs/blog/assets/media/tmux-and-scripts-vs-an-agent-harness/note-2.png b/docs/blog/assets/media/tmux-and-scripts-vs-an-agent-harness/note-2.png
new file mode 100644
index 00000000..69c8d032
Binary files /dev/null and b/docs/blog/assets/media/tmux-and-scripts-vs-an-agent-harness/note-2.png differ
diff --git a/docs/blog/assets/media/trigger-ai-agents-from-github-webhook/note-1.png b/docs/blog/assets/media/trigger-ai-agents-from-github-webhook/note-1.png
new file mode 100644
index 00000000..4358e59e
Binary files /dev/null and b/docs/blog/assets/media/trigger-ai-agents-from-github-webhook/note-1.png differ
diff --git a/docs/blog/assets/media/trigger-ai-agents-from-github-webhook/note-2.png b/docs/blog/assets/media/trigger-ai-agents-from-github-webhook/note-2.png
new file mode 100644
index 00000000..f798482d
Binary files /dev/null and b/docs/blog/assets/media/trigger-ai-agents-from-github-webhook/note-2.png differ
diff --git a/docs/blog/assets/media/trigger-ai-agents-from-slack/note-1.png b/docs/blog/assets/media/trigger-ai-agents-from-slack/note-1.png
new file mode 100644
index 00000000..6bc65b5f
Binary files /dev/null and b/docs/blog/assets/media/trigger-ai-agents-from-slack/note-1.png differ
diff --git a/docs/blog/assets/media/trigger-ai-agents-from-slack/note-2.png b/docs/blog/assets/media/trigger-ai-agents-from-slack/note-2.png
new file mode 100644
index 00000000..7d35aa76
Binary files /dev/null and b/docs/blog/assets/media/trigger-ai-agents-from-slack/note-2.png differ
diff --git a/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/hero.png b/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/hero.png
new file mode 100644
index 00000000..b1293ae1
Binary files /dev/null and b/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/hero.png differ
diff --git a/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/note-1.png b/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/note-1.png
new file mode 100644
index 00000000..1703a5e8
Binary files /dev/null and b/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/note-1.png differ
diff --git a/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/note-2.png b/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/note-2.png
new file mode 100644
index 00000000..978d5748
Binary files /dev/null and b/docs/blog/assets/media/turn-feedback-into-a-backlog-with-agents/note-2.png differ
diff --git a/docs/blog/assets/media/vibe-kanban-alternative/note-1.png b/docs/blog/assets/media/vibe-kanban-alternative/note-1.png
new file mode 100644
index 00000000..8e1e9155
Binary files /dev/null and b/docs/blog/assets/media/vibe-kanban-alternative/note-1.png differ
diff --git a/docs/blog/assets/media/vibe-kanban-alternative/note-2.png b/docs/blog/assets/media/vibe-kanban-alternative/note-2.png
new file mode 100644
index 00000000..cde99706
Binary files /dev/null and b/docs/blog/assets/media/vibe-kanban-alternative/note-2.png differ
diff --git a/docs/blog/assets/media/visualizing-ai-agents-pixijs/note-1.png b/docs/blog/assets/media/visualizing-ai-agents-pixijs/note-1.png
new file mode 100644
index 00000000..c741379d
Binary files /dev/null and b/docs/blog/assets/media/visualizing-ai-agents-pixijs/note-1.png differ
diff --git a/docs/blog/assets/media/visualizing-ai-agents-pixijs/note-2.png b/docs/blog/assets/media/visualizing-ai-agents-pixijs/note-2.png
new file mode 100644
index 00000000..e7ad845f
Binary files /dev/null and b/docs/blog/assets/media/visualizing-ai-agents-pixijs/note-2.png differ
diff --git a/docs/blog/assets/media/voice-as-a-control-plane-for-agent-fleets/note-1.png b/docs/blog/assets/media/voice-as-a-control-plane-for-agent-fleets/note-1.png
new file mode 100644
index 00000000..b526ba88
Binary files /dev/null and b/docs/blog/assets/media/voice-as-a-control-plane-for-agent-fleets/note-1.png differ
diff --git a/docs/blog/assets/media/voice-as-a-control-plane-for-agent-fleets/note-2.png b/docs/blog/assets/media/voice-as-a-control-plane-for-agent-fleets/note-2.png
new file mode 100644
index 00000000..dc960b85
Binary files /dev/null and b/docs/blog/assets/media/voice-as-a-control-plane-for-agent-fleets/note-2.png differ
diff --git a/docs/blog/assets/media/we-opened-a-discord/hero.png b/docs/blog/assets/media/we-opened-a-discord/hero.png
new file mode 100644
index 00000000..ebca5d82
Binary files /dev/null and b/docs/blog/assets/media/we-opened-a-discord/hero.png differ
diff --git a/docs/blog/assets/media/we-opened-a-discord/note-1.png b/docs/blog/assets/media/we-opened-a-discord/note-1.png
new file mode 100644
index 00000000..d6de30ee
Binary files /dev/null and b/docs/blog/assets/media/we-opened-a-discord/note-1.png differ
diff --git a/docs/blog/assets/media/we-opened-a-discord/note-2.png b/docs/blog/assets/media/we-opened-a-discord/note-2.png
new file mode 100644
index 00000000..06628136
Binary files /dev/null and b/docs/blog/assets/media/we-opened-a-discord/note-2.png differ
diff --git a/docs/blog/assets/media/what-are-claude-code-agents/note-1.png b/docs/blog/assets/media/what-are-claude-code-agents/note-1.png
new file mode 100644
index 00000000..a0943a9a
Binary files /dev/null and b/docs/blog/assets/media/what-are-claude-code-agents/note-1.png differ
diff --git a/docs/blog/assets/media/what-are-claude-code-agents/note-2.png b/docs/blog/assets/media/what-are-claude-code-agents/note-2.png
new file mode 100644
index 00000000..f7d36213
Binary files /dev/null and b/docs/blog/assets/media/what-are-claude-code-agents/note-2.png differ
diff --git a/docs/blog/assets/media/what-is-a-multi-agent-harness/note-1.png b/docs/blog/assets/media/what-is-a-multi-agent-harness/note-1.png
new file mode 100644
index 00000000..bb3c415b
Binary files /dev/null and b/docs/blog/assets/media/what-is-a-multi-agent-harness/note-1.png differ
diff --git a/docs/blog/assets/media/what-is-a-multi-agent-harness/note-2.png b/docs/blog/assets/media/what-is-a-multi-agent-harness/note-2.png
new file mode 100644
index 00000000..77a27a9e
Binary files /dev/null and b/docs/blog/assets/media/what-is-a-multi-agent-harness/note-2.png differ
diff --git a/docs/blog/assets/media/what-is-aeo-for-dev-tools/note-1.png b/docs/blog/assets/media/what-is-aeo-for-dev-tools/note-1.png
new file mode 100644
index 00000000..68eda8d8
Binary files /dev/null and b/docs/blog/assets/media/what-is-aeo-for-dev-tools/note-1.png differ
diff --git a/docs/blog/assets/media/what-is-aeo-for-dev-tools/note-2.png b/docs/blog/assets/media/what-is-aeo-for-dev-tools/note-2.png
new file mode 100644
index 00000000..9d215c17
Binary files /dev/null and b/docs/blog/assets/media/what-is-aeo-for-dev-tools/note-2.png differ
diff --git a/docs/blog/assets/media/what-is-an-agent-development-environment/note-1.png b/docs/blog/assets/media/what-is-an-agent-development-environment/note-1.png
new file mode 100644
index 00000000..cbd0b93e
Binary files /dev/null and b/docs/blog/assets/media/what-is-an-agent-development-environment/note-1.png differ
diff --git a/docs/blog/assets/media/what-is-an-agent-development-environment/note-2.png b/docs/blog/assets/media/what-is-an-agent-development-environment/note-2.png
new file mode 100644
index 00000000..a3344d01
Binary files /dev/null and b/docs/blog/assets/media/what-is-an-agent-development-environment/note-2.png differ
diff --git a/docs/blog/assets/media/what-is-harness-engineering/note-1.png b/docs/blog/assets/media/what-is-harness-engineering/note-1.png
new file mode 100644
index 00000000..fa42660b
Binary files /dev/null and b/docs/blog/assets/media/what-is-harness-engineering/note-1.png differ
diff --git a/docs/blog/assets/media/what-is-harness-engineering/note-2.png b/docs/blog/assets/media/what-is-harness-engineering/note-2.png
new file mode 100644
index 00000000..e3caa6f1
Binary files /dev/null and b/docs/blog/assets/media/what-is-harness-engineering/note-2.png differ
diff --git a/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/hero.png b/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/hero.png
new file mode 100644
index 00000000..69edea31
Binary files /dev/null and b/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/hero.png differ
diff --git a/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/note-1.png b/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/note-1.png
new file mode 100644
index 00000000..a1dd4017
Binary files /dev/null and b/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/note-2.png b/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/note-2.png
new file mode 100644
index 00000000..6f7f300b
Binary files /dev/null and b/docs/blog/assets/media/what-reddit-told-us-about-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/whats-new-in-agentic-ai-june-2026/note-1.png b/docs/blog/assets/media/whats-new-in-agentic-ai-june-2026/note-1.png
new file mode 100644
index 00000000..f16921d0
Binary files /dev/null and b/docs/blog/assets/media/whats-new-in-agentic-ai-june-2026/note-1.png differ
diff --git a/docs/blog/assets/media/whats-new-in-agentic-ai-june-2026/note-2.png b/docs/blog/assets/media/whats-new-in-agentic-ai-june-2026/note-2.png
new file mode 100644
index 00000000..6b798e6d
Binary files /dev/null and b/docs/blog/assets/media/whats-new-in-agentic-ai-june-2026/note-2.png differ
diff --git a/docs/blog/assets/media/whats-up-with-munder-difflin/note-1.png b/docs/blog/assets/media/whats-up-with-munder-difflin/note-1.png
new file mode 100644
index 00000000..cc9c7e9b
Binary files /dev/null and b/docs/blog/assets/media/whats-up-with-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/whats-up-with-munder-difflin/note-2.png b/docs/blog/assets/media/whats-up-with-munder-difflin/note-2.png
new file mode 100644
index 00000000..341ce65f
Binary files /dev/null and b/docs/blog/assets/media/whats-up-with-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/when-do-agents-need-an-agent-protocol/note-1.png b/docs/blog/assets/media/when-do-agents-need-an-agent-protocol/note-1.png
new file mode 100644
index 00000000..ed5755e8
Binary files /dev/null and b/docs/blog/assets/media/when-do-agents-need-an-agent-protocol/note-1.png differ
diff --git a/docs/blog/assets/media/when-do-agents-need-an-agent-protocol/note-2.png b/docs/blog/assets/media/when-do-agents-need-an-agent-protocol/note-2.png
new file mode 100644
index 00000000..910f78e3
Binary files /dev/null and b/docs/blog/assets/media/when-do-agents-need-an-agent-protocol/note-2.png differ
diff --git a/docs/blog/assets/media/why-cli-agents-are-powerful/note-1.png b/docs/blog/assets/media/why-cli-agents-are-powerful/note-1.png
new file mode 100644
index 00000000..295b42ee
Binary files /dev/null and b/docs/blog/assets/media/why-cli-agents-are-powerful/note-1.png differ
diff --git a/docs/blog/assets/media/why-cli-agents-are-powerful/note-2.png b/docs/blog/assets/media/why-cli-agents-are-powerful/note-2.png
new file mode 100644
index 00000000..9788f649
Binary files /dev/null and b/docs/blog/assets/media/why-cli-agents-are-powerful/note-2.png differ
diff --git a/docs/blog/assets/media/why-local-first-matters-for-ai-agents/note-1.png b/docs/blog/assets/media/why-local-first-matters-for-ai-agents/note-1.png
new file mode 100644
index 00000000..c498ea9f
Binary files /dev/null and b/docs/blog/assets/media/why-local-first-matters-for-ai-agents/note-1.png differ
diff --git a/docs/blog/assets/media/why-local-first-matters-for-ai-agents/note-2.png b/docs/blog/assets/media/why-local-first-matters-for-ai-agents/note-2.png
new file mode 100644
index 00000000..e8eee765
Binary files /dev/null and b/docs/blog/assets/media/why-local-first-matters-for-ai-agents/note-2.png differ
diff --git a/docs/blog/assets/media/why-our-auto-update-never-ran/note-1.png b/docs/blog/assets/media/why-our-auto-update-never-ran/note-1.png
new file mode 100644
index 00000000..67f12b89
Binary files /dev/null and b/docs/blog/assets/media/why-our-auto-update-never-ran/note-1.png differ
diff --git a/docs/blog/assets/media/why-our-auto-update-never-ran/note-2.png b/docs/blog/assets/media/why-our-auto-update-never-ran/note-2.png
new file mode 100644
index 00000000..228c8e31
Binary files /dev/null and b/docs/blog/assets/media/why-our-auto-update-never-ran/note-2.png differ
diff --git a/docs/blog/assets/media/why-we-built-munder-difflin/note-1.png b/docs/blog/assets/media/why-we-built-munder-difflin/note-1.png
new file mode 100644
index 00000000..cbe1357b
Binary files /dev/null and b/docs/blog/assets/media/why-we-built-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/why-we-built-munder-difflin/note-2.png b/docs/blog/assets/media/why-we-built-munder-difflin/note-2.png
new file mode 100644
index 00000000..92f855a4
Binary files /dev/null and b/docs/blog/assets/media/why-we-built-munder-difflin/note-2.png differ
diff --git a/docs/blog/assets/media/your-first-hour-with-munder-difflin/note-1.png b/docs/blog/assets/media/your-first-hour-with-munder-difflin/note-1.png
new file mode 100644
index 00000000..1800b639
Binary files /dev/null and b/docs/blog/assets/media/your-first-hour-with-munder-difflin/note-1.png differ
diff --git a/docs/blog/assets/media/your-first-hour-with-munder-difflin/note-2.png b/docs/blog/assets/media/your-first-hour-with-munder-difflin/note-2.png
new file mode 100644
index 00000000..9c648739
Binary files /dev/null and b/docs/blog/assets/media/your-first-hour-with-munder-difflin/note-2.png differ
diff --git a/docs/blog/atomic-file-mailboxes-for-agents/index.html b/docs/blog/atomic-file-mailboxes-for-agents/index.html
index 3da37ed4..04f2957a 100644
--- a/docs/blog/atomic-file-mailboxes-for-agents/index.html
+++ b/docs/blog/atomic-file-mailboxes-for-agents/index.html
@@ -202,6 +202,7 @@ rename inbox/&lt;id&gt;.json.tmp-9f3a → inbox/&lt;id&gt;.json ← appears at
</code></pre>
<p>This one trick is why files beat a naive shared log. A log every agent appends to is a multi-writer
race; a directory of atomically-renamed files is conflict-free by construction.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/atomic-file-mailboxes-for-agents/note-1.png" alt="Hand-drawn sketch from “Atomic File Mailboxes: How Agents Message Each Other”" loading="lazy" decoding="async" /></figure>
<h2 id="the-message-itself-speech-acts-not-free-text" tabindex="-1">The message itself: speech acts, not free text <a class="anchor" href="#the-message-itself-speech-acts-not-free-text" aria-hidden="true">#</a></h2>
<p>A message isn’t just a blob of text — it carries intent. The design borrows the one genuinely useful
idea from decades of agent-communication research, the <strong>speech act</strong>, and drops the rest:</p>
@@ -239,6 +240,7 @@ re-seeing a message is a no-op. Combined with moving handled messages to <code>i
can’t accidentally act on the same request twice.</li>
</ul>
<p>These are small rules with a big payoff: the messaging layer can be busy and still provably converge.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/atomic-file-mailboxes-for-agents/note-2.png" alt="Hand-drawn sketch from “Atomic File Mailboxes: How Agents Message Each Other”" loading="lazy" decoding="async" /></figure>
<h2 id="broadcast-and-escalation" tabindex="-1">Broadcast and escalation <a class="anchor" href="#broadcast-and-escalation" aria-hidden="true">#</a></h2>
<p>Two special addresses round out the system:</p>
<ul>
@@ -325,6 +327,22 @@ the office floor; it’s free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -356,22 +374,6 @@ the office floor; it’s free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/best-ai-coding-agents/index.html b/docs/blog/best-ai-coding-agents/index.html
index 4a2cdbcd..e0b11375 100644
--- a/docs/blog/best-ai-coding-agents/index.html
+++ b/docs/blog/best-ai-coding-agents/index.html
@@ -238,6 +238,7 @@ shipping bigger work. The “one tool wins everything” framing is over.</p>
</tr>
</tbody>
</table>
+<figure class="fig fig-inline"><img src="/blog/assets/media/best-ai-coding-agents/note-1.png" alt="Hand-drawn sketch from “The Best AI Coding Agents in 2026: A Field Guide”" loading="lazy" decoding="async" /></figure>
<h2 id="the-tools-fairly" tabindex="-1">The tools, fairly <a class="anchor" href="#the-tools-fairly" aria-hidden="true">#</a></h2>
<p><strong>Cursor</strong> — a dedicated AI-first IDE that leads on in-editor agent ergonomics; reference pricing runs
<a href="https://www.developersdigest.tech/blog/ai-coding-tools-pricing-2026">~$20 (Pro) to $200 (Ultra)/mo</a>
@@ -267,6 +268,7 @@ human-approves-each-step philosophy. Best if your team already lives in GitHub.<
enough. If that’s your need specifically with Claude Code, the
<a href="/blog/best-claude-code-multi-agent-tools/">multi-agent tools roundup</a> goes deeper, and
<a href="/blog/local-first-vs-cloud-agent-sdks/">local-first vs cloud agent SDKs</a> covers the build-vs-buy angle.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/best-ai-coding-agents/note-2.png" alt="Hand-drawn sketch from “The Best AI Coding Agents in 2026: A Field Guide”" loading="lazy" decoding="async" /></figure>
<h2 id="how-to-choose" tabindex="-1">How to choose <a class="anchor" href="#how-to-choose" aria-hidden="true">#</a></h2>
<ul>
<li><strong>You live in an editor</strong> → Cursor (polished IDE) or Cline (local/BYOK in VS Code).</li>
diff --git a/docs/blog/best-claude-code-multi-agent-tools/index.html b/docs/blog/best-claude-code-multi-agent-tools/index.html
index a80e8f33..dd8737d8 100644
--- a/docs/blog/best-claude-code-multi-agent-tools/index.html
+++ b/docs/blog/best-claude-code-multi-agent-tools/index.html
@@ -244,6 +244,7 @@ harness</a> idea.</li>
</table>
<p>The single row that most separates the field is <strong>shared memory + orchestrator</strong>: that’s the jump
from “running agents in parallel” to “running a team.”</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/best-claude-code-multi-agent-tools/note-1.png" alt="Hand-drawn sketch from “The Best Tools to Run Multiple Claude Code Agents (2026)”" loading="lazy" decoding="async" /></figure>
<h2 id="claude-squad-the-lean-terminal-option" tabindex="-1">Claude Squad — the lean terminal option <a class="anchor" href="#claude-squad-the-lean-terminal-option" aria-hidden="true">#</a></h2>
<p><a href="https://github.com/smtg-ai/claude-squad">Claude Squad</a> is a terminal UI that manages multiple AI
coding agents — Claude Code among them — each in its own tmux session, with git worktrees keeping
@@ -282,6 +283,7 @@ pool memory or talk to each other, and there’s no orchestrator routing work be
</ul>
<p>Best for: developers who want an open, visual, worktree-based parallel workflow without the terminal.
More on the trade-offs in <a href="/blog/crystal-claude-code-alternative/">a Crystal alternative</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/best-claude-code-multi-agent-tools/note-2.png" alt="Hand-drawn sketch from “The Best Tools to Run Multiple Claude Code Agents (2026)”" loading="lazy" decoding="async" /></figure>
<h2 id="vibe-kanban-the-task-board-for-agents" tabindex="-1">vibe-kanban — the task board for agents <a class="anchor" href="#vibe-kanban-the-task-board-for-agents" aria-hidden="true">#</a></h2>
<p><a href="https://github.com/BloopAI/vibe-kanban">vibe-kanban</a> takes a different angle: a kanban board where
you create tasks as cards, assign them to coding agents (it’s agent-agnostic — Claude Code, Gemini,
diff --git a/docs/blog/building-a-terminal-ui-xterm-node-pty/index.html b/docs/blog/building-a-terminal-ui-xterm-node-pty/index.html
index d7bedde4..223d9f05 100644
--- a/docs/blog/building-a-terminal-ui-xterm-node-pty/index.html
+++ b/docs/blog/building-a-terminal-ui-xterm-node-pty/index.html
@@ -210,6 +210,7 @@ window<span class="token punctuation">.</span>cth<span class="token punctuation"
<p><code>term.write()</code> takes the raw bytes including escape sequences — you do <strong>not</strong> strip ANSI; that’s
xterm’s whole job. Writing a dim “process exited” line on <code>onExit</code> is a nice touch so a dead terminal
doesn’t just freeze silently.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/building-a-terminal-ui-xterm-node-pty/note-1.png" alt="Hand-drawn sketch from “Building a Terminal UI with xterm.js and node-pty”" loading="lazy" decoding="async" /></figure>
<h2 id="step-3-send-keystrokes-back" tabindex="-1">Step 3 — Send keystrokes back <a class="anchor" href="#step-3-send-keystrokes-back" aria-hidden="true">#</a></h2>
<p><code>term.onData</code> fires for every keystroke (already encoded as the bytes a terminal would send — arrow
keys as escape sequences, Enter as <code>\r</code>, and so on). Forward them straight to the PTY:</p>
@@ -284,6 +285,7 @@ element — instant, no repaint required.</li>
<span class="token punctuation">}</span></code></pre>
<p>Switching agents becomes a DOM move, not a teardown. The terminal is always populated and always
visible immediately — which is what you need when a user is flicking between a dozen live sessions.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/building-a-terminal-ui-xterm-node-pty/note-2.png" alt="Hand-drawn sketch from “Building a Terminal UI with xterm.js and node-pty”" loading="lazy" decoding="async" /></figure>
<h2 id="performance-notes-for-dozens-of-terminals" tabindex="-1">Performance notes for dozens of terminals <a class="anchor" href="#performance-notes-for-dozens-of-terminals" aria-hidden="true">#</a></h2>
<p>A pool keeps correctness; a few habits keep it fast:</p>
<ul>
@@ -368,6 +370,22 @@ to watch many real terminals at once; it’s free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -399,22 +417,6 @@ to watch many real terminals at once; it’s free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/building-an-ai-office-floor/index.html b/docs/blog/building-an-ai-office-floor/index.html
index 8bd5b990..5bf563db 100644
--- a/docs/blog/building-an-ai-office-floor/index.html
+++ b/docs/blog/building-an-ai-office-floor/index.html
@@ -205,6 +205,7 @@ map’s walkability grid — four-directional, no diagonals:</p>
<p>On an unweighted grid, BFS returns the shortest path for free — no heuristic, no priority queue, no A*
needed at office scale. It’s a dozen lines and it’s correct, which is the right trade for a map this
size.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/building-an-ai-office-floor/note-1.png" alt="Hand-drawn sketch from “Building an AI \&quot;Office Floor\&quot;: Avatars, Pathfinding, Envelopes”" loading="lazy" decoding="async" /></figure>
<h2 id="avatars-one-sheet-many-people" tabindex="-1">Avatars: one sheet, many people <a class="anchor" href="#avatars-one-sheet-many-people" aria-hidden="true">#</a></h2>
<p>Drawing fifteen unique characters by hand would be a slog. Instead, avatars start from a shared
<strong>character walk sheet</strong> and are made distinct by <em>recoloring</em>:</p>
@@ -239,6 +240,7 @@ refusals red, and an escalation to the human a distinct color. So you don’t ju
moved — you see <em>who asked whom, and what kind of ask it was</em>, at a glance.</p>
<p>That envelope is pure presentation riding on real data: it only flies because the
<a href="/blog/atomic-file-mailboxes-for-agents/">message router</a> actually delivered something.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/building-an-ai-office-floor/note-2.png" alt="Hand-drawn sketch from “Building an AI \&quot;Office Floor\&quot;: Avatars, Pathfinding, Envelopes”" loading="lazy" decoding="async" /></figure>
<h2 id="keeping-it-lightweight" tabindex="-1">Keeping it lightweight <a class="anchor" href="#keeping-it-lightweight" aria-hidden="true">#</a></h2>
<p>The whole point is that this is <em>game tech in a dev tool</em>, not a game. So the implementation stays
lean: pixel-art settings (no antialias, nearest-neighbor scaling, integer positions), a single shared
@@ -313,6 +315,22 @@ techniques — the hard part is wiring them to <em>real</em> agent events, not t
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -344,22 +362,6 @@ techniques — the hard part is wiring them to <em>real</em> agent events, not t
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/building-reliable-ai-agents/index.html b/docs/blog/building-reliable-ai-agents/index.html
index 4802c0c7..4d128b50 100644
--- a/docs/blog/building-reliable-ai-agents/index.html
+++ b/docs/blog/building-reliable-ai-agents/index.html
@@ -197,6 +197,7 @@ a different approach, or hand it to a human.</li>
</ol>
<p>An unbounded retry is the single most common way a “resilient” agent turns into a money fire. The retry
<em>budget</em> is what makes retrying a feature instead of a hazard.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/building-reliable-ai-agents/note-1.png" alt="Hand-drawn sketch from “Building Reliable AI Agents: Failure Is the Default”" loading="lazy" decoding="async" /></figure>
<h2 id="catch-bad-output-before-it-spreads" tabindex="-1">Catch bad output before it spreads <a class="anchor" href="#catch-bad-output-before-it-spreads" aria-hidden="true">#</a></h2>
<p>The sneakiest failure is the one that looks like success. A model returns confident nonsense, or JSON
that’s almost-but-not-quite valid, and the agent acts on it. The defense is to <strong>validate at the
@@ -233,6 +234,7 @@ agent crashes, hangs, or goes off the rails, the others don’t even notice —
mailboxes are untouched, and the orchestrator can restart or reassign the failed work without a
system-wide reset.</p>
<p>Contain the blast radius and a single failure stays a single failure, instead of becoming an outage.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/building-reliable-ai-agents/note-2.png" alt="Hand-drawn sketch from “Building Reliable AI Agents: Failure Is the Default”" loading="lazy" decoding="async" /></figure>
<h2 id="a-reliability-checklist" tabindex="-1">A reliability checklist <a class="anchor" href="#a-reliability-checklist" aria-hidden="true">#</a></h2>
<p>When an agent run dies and takes its progress with it, it usually skipped one of these:</p>
<ol>
diff --git a/docs/blog/can-claude-code-agents-talk-to-each-other/index.html b/docs/blog/can-claude-code-agents-talk-to-each-other/index.html
index efa0d140..e3629740 100644
--- a/docs/blog/can-claude-code-agents-talk-to-each-other/index.html
+++ b/docs/blog/can-claude-code-agents-talk-to-each-other/index.html
@@ -200,6 +200,7 @@ busy at the same time without locks or races.</li>
<p>The one rule that keeps it clean: <strong>never write into another agent’s folder.</strong> You only ever write to
your own outbox; the router does the routing. Single-writer-per-file is what makes the whole thing
safe under concurrency.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/can-claude-code-agents-talk-to-each-other/note-1.png" alt="Hand-drawn sketch from “Can Claude Code Agents Talk to Each Other?”" loading="lazy" decoding="async" /></figure>
<h2 id="whats-actually-in-a-message" tabindex="-1">What’s actually in a message <a class="anchor" href="#whats-actually-in-a-message" aria-hidden="true">#</a></h2>
<p>A message isn’t just free text — it carries a little structure so the receiving agent knows what’s
expected of it. In practice each message names:</p>
@@ -227,6 +228,7 @@ router diverts it to an approvals queue for a person to answer, and the answer c
message. That’s how an agent reaches a human for the genuinely critical calls without anyone having to
watch a terminal, the same loop we describe in
<a href="/blog/human-in-the-loop-ai-agents/">keeping a human in the loop</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/can-claude-code-agents-talk-to-each-other/note-2.png" alt="Hand-drawn sketch from “Can Claude Code Agents Talk to Each Other?”" loading="lazy" decoding="async" /></figure>
<h2 id="memory-is-a-slower-kind-of-talking" tabindex="-1">Memory is a slower kind of talking <a class="anchor" href="#memory-is-a-slower-kind-of-talking" aria-hidden="true">#</a></h2>
<p>There’s one more channel that’s easy to miss: <strong>shared memory.</strong> Messages are how agents coordinate in
the moment; memory is how they coordinate across time. When each agent writes durable facts to a notes
diff --git a/docs/blog/claude-code-automation-while-you-sleep/index.html b/docs/blog/claude-code-automation-while-you-sleep/index.html
index f92c62b9..da9feed3 100644
--- a/docs/blog/claude-code-automation-while-you-sleep/index.html
+++ b/docs/blog/claude-code-automation-while-you-sleep/index.html
@@ -188,6 +188,7 @@ exact command in the spawn dialog, so there’s no mystery about what’s being
<p>The important word is <strong>deliberately.</strong> Bypassing approvals is a real grant of authority, so you pair
it with the boundaries below. Turn it off when you want to confirm each action; turn it on when you’ve
scoped the work and you trust the guardrails.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-automation-while-you-sleep/note-1.png" alt="Hand-drawn sketch from “Claude Code Automation: Let Agents Build While You Sleep”" loading="lazy" decoding="async" /></figure>
<h2 id="ingredient-2-the-autonomous-loop" tabindex="-1">Ingredient 2 — The autonomous loop <a class="anchor" href="#ingredient-2-the-autonomous-loop" aria-hidden="true">#</a></h2>
<p>The second ingredient is the loop that keeps an agent moving from one task to the next without you
handing it each one. The elegant way to build it is on Claude Code’s <strong>Stop hook</strong> — the hook that
@@ -236,6 +237,7 @@ up, “what happened while I was out?” has a precise answer, not a guess.</p>
<p>Run a 30-minute unattended session before you run an 8-hour one. Watch what the agents do with the
autonomy you’ve granted, tighten the escalation policy where they overstepped, and only then extend the
duration. Trust is earned by observation, not assumed.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-automation-while-you-sleep/note-2.png" alt="Hand-drawn sketch from “Claude Code Automation: Let Agents Build While You Sleep”" loading="lazy" decoding="async" /></figure>
<h2 id="a-realistic-overnight-setup" tabindex="-1">A realistic overnight setup <a class="anchor" href="#a-realistic-overnight-setup" aria-hidden="true">#</a></h2>
<p>Putting it together, a sane overnight automation looks like this:</p>
<ol>
diff --git a/docs/blog/claude-code-git-worktrees-vs-hive/index.html b/docs/blog/claude-code-git-worktrees-vs-hive/index.html
index d105460e..26dea0de 100644
--- a/docs/blog/claude-code-git-worktrees-vs-hive/index.html
+++ b/docs/blog/claude-code-git-worktrees-vs-hive/index.html
@@ -203,6 +203,7 @@ roster, no single place to see what the team is collectively doing.</li>
</ul>
<p>In other words, worktrees make parallel agents <em>safe to run</em>, not <em>able to cooperate</em>. That’s a real
and useful guarantee — it’s just not the same as a team.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-git-worktrees-vs-hive/note-1.png" alt="Hand-drawn sketch from “Git Worktrees vs a Hive: Two Ways to Parallelize Claude Code”" loading="lazy" decoding="async" /></figure>
<h2 id="what-a-hive-gives-you" tabindex="-1">What a hive gives you <a class="anchor" href="#what-a-hive-gives-you" aria-hidden="true">#</a></h2>
<p>A <strong>hive</strong> is the coordination layer worktrees lack. It wraps several long-lived agents and adds:</p>
<ul>
@@ -231,6 +232,7 @@ hive ───────┼─ worktree: agent-b (branch agent-b) ─┼──
<p>The layers don’t conflict; they stack. Worktrees are a git feature for workspace isolation. A hive is a
coordination feature for teamwork. Asking which to use is like asking whether to use seatbelts or a
steering wheel.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-git-worktrees-vs-hive/note-2.png" alt="Hand-drawn sketch from “Git Worktrees vs a Hive: Two Ways to Parallelize Claude Code”" loading="lazy" decoding="async" /></figure>
<h2 id="a-decision-guide" tabindex="-1">A decision guide <a class="anchor" href="#a-decision-guide" aria-hidden="true">#</a></h2>
<p>Pick based on how <em>interdependent</em> your parallel work is:</p>
<p><strong>Just worktrees</strong> are enough when:</p>
diff --git a/docs/blog/claude-code-hooks-explained/index.html b/docs/blog/claude-code-hooks-explained/index.html
index 959dc5b2..6a5ec911 100644
--- a/docs/blog/claude-code-hooks-explained/index.html
+++ b/docs/blog/claude-code-hooks-explained/index.html
@@ -183,6 +183,7 @@ Claude’s next move.</p>
}</code></pre>
<p>The <code>matcher</code> (for tool events) lets you scope a hook to specific tools — <code>*</code> means “every tool.” Tool
events carry that matcher; lifecycle events like <code>Stop</code> don’t need one.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-hooks-explained/note-1.png" alt="Hand-drawn sketch from “Claude Code Hooks, Explained (PreToolUse, PostToolUse, Stop)”" loading="lazy" decoding="async" /></figure>
<h2 id="the-lifecycle-events-that-matter" tabindex="-1">The lifecycle events that matter <a class="anchor" href="#the-lifecycle-events-that-matter" aria-hidden="true">#</a></h2>
<p>There are several hook events; these are the ones you’ll reach for most.</p>
<h3 id="pretooluse" tabindex="-1">PreToolUse <a class="anchor" href="#pretooluse" aria-hidden="true">#</a></h3>
@@ -253,6 +254,7 @@ to the agent exactly once. No message is re-delivered, and the loop can’t spin
nothing left — the foundation of <a href="/blog/claude-code-automation-while-you-sleep/">letting agents build while you sleep</a>.
It’s also how the <a href="/blog/how-the-god-orchestrator-works/">GOD orchestrator</a> keeps the whole floor
moving: route a task into an agent’s inbox, and its next Stop hook picks it up automatically.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-hooks-explained/note-2.png" alt="Hand-drawn sketch from “Claude Code Hooks, Explained (PreToolUse, PostToolUse, Stop)”" loading="lazy" decoding="async" /></figure>
<h2 id="writing-your-own-hooks-practical-tips" tabindex="-1">Writing your own hooks: practical tips <a class="anchor" href="#writing-your-own-hooks-practical-tips" aria-hidden="true">#</a></h2>
<p>If you’re building with hooks directly, a few lessons that save pain:</p>
<ul>
@@ -327,6 +329,22 @@ free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -358,22 +376,6 @@ free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/claude-code-multi-agent-setup-tutorial/index.html b/docs/blog/claude-code-multi-agent-setup-tutorial/index.html
index af6473ab..565fb257 100644
--- a/docs/blog/claude-code-multi-agent-setup-tutorial/index.html
+++ b/docs/blog/claude-code-multi-agent-setup-tutorial/index.html
@@ -190,6 +190,7 @@ It’s the right default for a watch-it-work demo; turn it off if you want to co
<p>Onboarding also sets a <strong>harness home</strong> — a folder where the harness keeps its own state: the hive
git repo, each agent’s memory, and the shared semantic memory palace. You never edit it by hand; it’s
just where coordination lives.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-multi-agent-setup-tutorial/note-1.png" alt="Hand-drawn sketch from “Set Up a Claude Code Multi-Agent Workflow in 10 Minutes”" loading="lazy" decoding="async" /></figure>
<h2 id="step-2-meet-the-god-orchestrator-1-minute" tabindex="-1">Step 2 — Meet the GOD orchestrator (1 minute) <a class="anchor" href="#step-2-meet-the-god-orchestrator-1-minute" aria-hidden="true">#</a></h2>
<p>When the hive comes up, one agent is already there: the <strong>GOD orchestrator</strong>, seated in the corner
office. It’s an ordinary <code>claude</code> process with one extra job — it runs the floor. You talk to <em>it</em> in
@@ -231,6 +232,7 @@ actual tool calls, not a simulation. Envelopes fly desk-to-desk when messages ro
audit trail of who said what.</li>
</ol>
<p>You’ve gone from a blank app to a coordinated team acting on one sentence. That’s the setup.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-multi-agent-setup-tutorial/note-2.png" alt="Hand-drawn sketch from “Set Up a Claude Code Multi-Agent Workflow in 10 Minutes”" loading="lazy" decoding="async" /></figure>
<h2 id="what-you-just-avoided" tabindex="-1">What you just avoided <a class="anchor" href="#what-you-just-avoided" aria-hidden="true">#</a></h2>
<p>Doing this by hand means you become the message bus: copy-pasting findings between windows, manually
deciding who edits which file, and resolving <code>index.lock</code> errors when two agents commit at once. The
diff --git a/docs/blog/claude-code-orchestration-guide/index.html b/docs/blog/claude-code-orchestration-guide/index.html
index 9e3bf72e..c3a5d4b8 100644
--- a/docs/blog/claude-code-orchestration-guide/index.html
+++ b/docs/blog/claude-code-orchestration-guide/index.html
@@ -196,6 +196,7 @@ as the orchestrator, seated in the corner office. Because the orchestrator is a
codebase, you tune <em>how</em> it routes and <em>what</em> it considers critical by editing its instructions, not
by redeploying. That’s the practical heart of
<a href="/blog/how-the-god-orchestrator-works/">how the GOD orchestrator works</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-orchestration-guide/note-1.png" alt="Hand-drawn sketch from “Orchestrating Claude Code Agents: A Practical Guide”" loading="lazy" decoding="async" /></figure>
<h2 id="how-a-request-flows-through-the-orchestrator" tabindex="-1">How a request flows through the orchestrator <a class="anchor" href="#how-a-request-flows-through-the-orchestrator" aria-hidden="true">#</a></h2>
<p>Here’s the path a single instruction takes, end to end:</p>
<h3 id="1-you-describe-a-goal-to-the-orchestrator" tabindex="-1">1. You describe a goal to the orchestrator <a class="anchor" href="#1-you-describe-a-goal-to-the-orchestrator" aria-hidden="true">#</a></h3>
@@ -240,6 +241,7 @@ code itself. An orchestrator that starts doing the tasks is a bottleneck wearing
when the team goes sideways you can replay what happened. For the broader patterns here, see
<a href="/blog/coordinating-ai-coding-agents/">the best way to coordinate AI coding agents</a>.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-orchestration-guide/note-2.png" alt="Hand-drawn sketch from “Orchestrating Claude Code Agents: A Practical Guide”" loading="lazy" decoding="async" /></figure>
<h2 id="when-you-actually-need-an-orchestrator" tabindex="-1">When you actually need an orchestrator <a class="anchor" href="#when-you-actually-need-an-orchestrator" aria-hidden="true">#</a></h2>
<p>You don’t need orchestration for one agent, or even for two or three independent tasks you’re happy to
assign by hand. You need it when:</p>
diff --git a/docs/blog/claude-code-orchestration-tools-compared/index.html b/docs/blog/claude-code-orchestration-tools-compared/index.html
index 6b668192..22c92671 100644
--- a/docs/blog/claude-code-orchestration-tools-compared/index.html
+++ b/docs/blog/claude-code-orchestration-tools-compared/index.html
@@ -165,6 +165,7 @@ orchestrator is more leverage.</li>
</ol>
<p>A sixth practical factor — <strong>footprint</strong> — decides whether a tool is overkill for your workload.
We’ll fold it into the verdict.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-orchestration-tools-compared/note-1.png" alt="Hand-drawn sketch from “Claude Code Orchestration Tools, Compared”" loading="lazy" decoding="async" /></figure>
<h2 id="the-comparison" tabindex="-1">The comparison <a class="anchor" href="#the-comparison" aria-hidden="true">#</a></h2>
<p>Scored as ●●● strong · ●●○ partial · ●○○ minimal, to the best of our knowledge at the time of writing.
Tools evolve — verify against each project’s current docs.</p>
@@ -233,6 +234,7 @@ Tools evolve — verify against each project’s current docs.</p>
<p>Read the table as a fit, not a scoreboard. The tools clustered on the left optimize for <strong>control and
simplicity</strong>; Munder Difflin optimizes for <strong>coordination</strong> (memory + messaging + a routing
orchestrator). Both are legitimate.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-orchestration-tools-compared/note-2.png" alt="Hand-drawn sketch from “Claude Code Orchestration Tools, Compared”" loading="lazy" decoding="async" /></figure>
<h2 id="how-to-read-each-criterion" tabindex="-1">How to read each criterion <a class="anchor" href="#how-to-read-each-criterion" aria-hidden="true">#</a></h2>
<h3 id="shared-memory-is-the-real-divider" tabindex="-1">Shared memory is the real divider <a class="anchor" href="#shared-memory-is-the-real-divider" aria-hidden="true">#</a></h3>
<p>This is where the field genuinely splits. Session managers and worktree apps (Claude Squad, Conductor,
diff --git a/docs/blog/claude-code-subagents-vs-multi-agent-harness/index.html b/docs/blog/claude-code-subagents-vs-multi-agent-harness/index.html
index 975f50a7..b3f22de1 100644
--- a/docs/blog/claude-code-subagents-vs-multi-agent-harness/index.html
+++ b/docs/blog/claude-code-subagents-vs-multi-agent-harness/index.html
@@ -192,6 +192,7 @@ teammates across tasks; you have helpers conjured for one job.</li>
</ul>
<p>None of this is a flaw — it’s the scope. Subagents are an <em>intra-agent</em> concurrency primitive. They
were never meant to be a standing team.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-subagents-vs-multi-agent-harness/note-1.png" alt="Hand-drawn sketch from “Claude Code Subagents vs a Multi-Agent Harness”" loading="lazy" decoding="async" /></figure>
<h2 id="what-a-harness-adds" tabindex="-1">What a harness adds <a class="anchor" href="#what-a-harness-adds" aria-hidden="true">#</a></h2>
<p>A <a href="https://munderdiffl.in/#what">multi-agent harness</a> wraps agents you already run — full Claude Code
sessions — and adds the layer subagents structurally can’t provide:</p>
@@ -252,6 +253,7 @@ and escalates only the critical calls to you. The parent-as-bottleneck problem g
</tbody>
</table>
<p>The table isn’t a scoreboard — it’s a map. Each column wins its own territory.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-code-subagents-vs-multi-agent-harness/note-2.png" alt="Hand-drawn sketch from “Claude Code Subagents vs a Multi-Agent Harness”" loading="lazy" decoding="async" /></figure>
<h2 id="theyre-better-together" tabindex="-1">They’re better together <a class="anchor" href="#theyre-better-together" aria-hidden="true">#</a></h2>
<p>The framing that trips people up is “subagents <em>or</em> a harness.” In practice it’s both:</p>
<ul>
diff --git a/docs/blog/claude-squad-alternative/index.html b/docs/blog/claude-squad-alternative/index.html
index 0469cb45..af0768f9 100644
--- a/docs/blog/claude-squad-alternative/index.html
+++ b/docs/blog/claude-squad-alternative/index.html
@@ -165,6 +165,7 @@ other’s files.</li>
</ul>
<p>If your need is “run a few independent Claude Code tasks in parallel from the terminal,” Claude Squad
may be all you ever want. Switching costs you simplicity — so switch only for a real reason.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-squad-alternative/note-1.png" alt="Hand-drawn sketch from “Looking for a Claude Squad Alternative?”" loading="lazy" decoding="async" /></figure>
<h2 id="where-a-session-manager-stops" tabindex="-1">Where a session manager stops <a class="anchor" href="#where-a-session-manager-stops" aria-hidden="true">#</a></h2>
<p>A session manager parallelizes agents; it doesn’t <em>coordinate</em> them. Three things stay your job:</p>
<h3 id="1-agents-dont-share-what-they-learn" tabindex="-1">1. Agents don’t share what they learn <a class="anchor" href="#1-agents-dont-share-what-they-learn" aria-hidden="true">#</a></h3>
@@ -179,6 +180,7 @@ the message bus, relaying findings between sessions.</p>
becomes the bottleneck — and there’s no orchestrator to take it off your plate.</p>
<p>None of these are bugs — they’re simply outside a session manager’s scope. They’re also exactly the
things people go looking for an alternative to solve.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-squad-alternative/note-2.png" alt="Hand-drawn sketch from “Looking for a Claude Squad Alternative?”" loading="lazy" decoding="async" /></figure>
<h2 id="what-a-coordinated-hive-adds" tabindex="-1">What a coordinated hive adds <a class="anchor" href="#what-a-coordinated-hive-adds" aria-hidden="true">#</a></h2>
<p>The alternative isn’t “a fancier terminal.” It’s a different <em>shape</em>: a <a href="/#what">multi-agent harness</a>
that wraps the agents you already run and adds the coordination layer on top.</p>
diff --git a/docs/blog/claude-squad-vs-munder-difflin/index.html b/docs/blog/claude-squad-vs-munder-difflin/index.html
index ea6ee1bf..43b94870 100644
--- a/docs/blog/claude-squad-vs-munder-difflin/index.html
+++ b/docs/blog/claude-squad-vs-munder-difflin/index.html
@@ -169,6 +169,7 @@ head-to-head: where each is genuinely better, and how to decide.</p>
<li><strong>Munder Difflin</strong> runs agents <em>as a team</em>. It’s a <a href="/#what">multi-agent harness</a>.</li>
</ul>
<p>Everything below is detail on that distinction.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-squad-vs-munder-difflin/note-1.png" alt="Hand-drawn sketch from “Claude Squad vs Munder Difflin: Which Should You Use?”" loading="lazy" decoding="async" /></figure>
<h2 id="feature-comparison" tabindex="-1">Feature comparison <a class="anchor" href="#feature-comparison" aria-hidden="true">#</a></h2>
<table>
<thead>
@@ -244,6 +245,7 @@ or an orchestrator — they need isolation, which Claude Squad gives you cleanly
</ul>
<p>If that’s you, Claude Squad is the right tool and the visual floor would just be overhead. Be honest
about your workload before you reach for more.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/claude-squad-vs-munder-difflin/note-2.png" alt="Hand-drawn sketch from “Claude Squad vs Munder Difflin: Which Should You Use?”" loading="lazy" decoding="async" /></figure>
<h2 id="where-munder-difflin-is-the-better-pick" tabindex="-1">Where Munder Difflin is the better pick <a class="anchor" href="#where-munder-difflin-is-the-better-pick" aria-hidden="true">#</a></h2>
<ul>
<li><strong>Your agents need to share what they learn.</strong> <a href="/blog/give-claude-code-long-term-memory/">Long-term
diff --git a/docs/blog/cline-vs-munder-difflin/index.html b/docs/blog/cline-vs-munder-difflin/index.html
index 7bb5c91a..a3d87745 100644
--- a/docs/blog/cline-vs-munder-difflin/index.html
+++ b/docs/blog/cline-vs-munder-difflin/index.html
@@ -193,6 +193,7 @@ your own Claude Code sessions calling the API you already use.</li>
</ul>
<p>So if your priority is “keep it on my machine, on my models,” both qualify. The decision is about
<em>scope</em>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/cline-vs-munder-difflin/note-1.png" alt="Hand-drawn sketch from “Cline vs Munder Difflin: In-Editor Agent or Local Hive?”" loading="lazy" decoding="async" /></figure>
<h2 id="where-cline-wins" tabindex="-1">Where Cline wins <a class="anchor" href="#where-cline-wins" aria-hidden="true">#</a></h2>
<ul>
<li><strong>In-editor ergonomics.</strong> If you live in VS Code and want an agent right there — reading the file you
@@ -216,6 +217,7 @@ several agents run at once.</li>
</ul>
<p>If your problem is “I want a coordinated team of agents working a goal,” that’s Munder Difflin’s lane,
not an editor extension’s.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/cline-vs-munder-difflin/note-2.png" alt="Hand-drawn sketch from “Cline vs Munder Difflin: In-Editor Agent or Local Hive?”" loading="lazy" decoding="async" /></figure>
<h2 id="how-to-choose" tabindex="-1">How to choose <a class="anchor" href="#how-to-choose" aria-hidden="true">#</a></h2>
<table>
<thead>
diff --git a/docs/blog/command-center-guide/index.html b/docs/blog/command-center-guide/index.html
index bd0752c5..02d7cf7b 100644
--- a/docs/blog/command-center-guide/index.html
+++ b/docs/blog/command-center-guide/index.html
@@ -181,6 +181,7 @@
<p>The Tasks tab is a <strong>dependency-aware kanban board</strong>. Tasks move across four columns — todo, doing, blocked, done — and each task is assigned to a specific agent.</p>
<p>The load-bearing word is <em>dependency-aware</em>. Real work has ordering: the refactor has to land before the tests get updated; the schema migration comes before the endpoint. On the board you wire those dependencies explicitly, and downstream tasks wait until their prerequisites finish. You’re not the sequencer anymore — the board is.</p>
<p>Work gets onto the board a few ways: you create tasks yourself, Michael creates and assigns them as he routes requests, and you can <strong>pull open GitHub issues from any registered repo</strong> (via the <code>gh</code> CLI) and assign them to agents with one click. Issue in, task tracked, agent dispatched — and when the work ships, the <strong>CI status watcher</strong> in the Activity tab shows live pass/fail/in-progress for the repo’s GitHub Actions runs. The loop closes in the same window it opened in.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/command-center-guide/note-1.png" alt="Hand-drawn sketch from “The Command Center: Kanban, Fleet, and Budgets in One Place”" loading="lazy" decoding="async" /></figure>
<h2 id="fleet-status-the-roster-at-a-glance" tabindex="-1">Fleet status: the roster at a glance <a class="anchor" href="#fleet-status-the-roster-at-a-glance" aria-hidden="true">#</a></h2>
<p>The Floor tab is where the fleet stops being a set of individual terminals and becomes a roster. Each agent card shows what that agent is up to, and the card’s progress bar doubles as a <strong>context-window gauge</strong> — a glanceable read on how much of the model’s context each agent has burned. An agent near the top of its gauge is an agent about to compact or slow down; you can see it coming instead of discovering it.</p>
<p>Dispatch also lives here: pick an agent, pick a model (the <strong>per-agent model selector</strong> means your cheap-tier worker and your frontier-tier reviewer are one dropdown apart), and send work. Routine tasks go to the cheap tier; the frontier tier is reserved for the reasoning that needs it.</p>
@@ -189,6 +190,7 @@
<p><strong>Per-agent token budgets.</strong> You set a budget per agent, and live fleet monitoring tracks consumption across the whole roster against it. Budgets pair with the <strong>circuit breaker</strong>, which handles the runaway case on a ladder: <em>steer</em> (nudge the agent), then <em>constrain</em>, then <em>stop</em>. An agent that loops, storms errors, or blows through its cap gets caught by machinery, not by you noticing the bill.</p>
<p><strong>Real telemetry.</strong> The Activity tab doesn’t estimate from message counts — it reads the JSONL transcripts Claude Code writes to <code>~/.claude/projects/</code> and surfaces <strong>actual token counts and estimated USD cost per agent, per session</strong>, backed by a <strong>durable cost ledger</strong> that survives app restarts. Yesterday’s spend is still there this morning, attributed to the agent that spent it.</p>
<p><strong>Observability.</strong> Also in Activity: a live <strong>OpenTelemetry collector</strong> with per-model cost attribution, a fleet grid, and a <strong>per-agent tool-span waterfall</strong> — the “what exactly is this agent doing, step by step, and what does each step cost” view. It’s the same discipline we covered in <a href="/blog/observability-for-agent-fleets/">observability for agent fleets</a>, built into the harness instead of bolted on.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/command-center-guide/note-2.png" alt="Hand-drawn sketch from “The Command Center: Kanban, Fleet, and Budgets in One Place”" loading="lazy" decoding="async" /></figure>
<h2 id="triggers-the-boards-fourth-dimension" tabindex="-1">Triggers: the board’s fourth dimension <a class="anchor" href="#triggers-the-boards-fourth-dimension" aria-hidden="true">#</a></h2>
<p>The kanban answers “what’s in flight.” The <strong>Triggers tab</strong> answers “what happens next without me” — every way the hive wakes up when you aren’t typing. <strong>Schedules</strong> are the first and oldest of them: recurring missions carry a label, an interval, a target agent, and a body, and the tab shows last-fired and next-fired times, so drift is visible. A scheduler <strong>heartbeat</strong> re-engages the floor when it goes quiet. Together with the board, it turns the hive from something you drive into something you supervise — the full pattern is in <a href="/blog/scheduling-autonomous-agent-missions/">scheduling autonomous agent missions</a>.</p>
<h2 id="floor-or-board-a-simple-rule" tabindex="-1">Floor or board? A simple rule <a class="anchor" href="#floor-or-board-a-simple-rule" aria-hidden="true">#</a></h2>
diff --git a/docs/blog/compressing-agent-memory/index.html b/docs/blog/compressing-agent-memory/index.html
index dce80509..b823e908 100644
--- a/docs/blog/compressing-agent-memory/index.html
+++ b/docs/blog/compressing-agent-memory/index.html
@@ -195,6 +195,7 @@ around 80% are reported) so a long session keeps running.</li>
on engineering conversations, and purpose-built memory dialects claim far higher.</li>
</ul>
<p>These differ in where they run, but they share one goal: fewer tokens, same meaning.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/compressing-agent-memory/note-1.png" alt="Hand-drawn sketch from “Compressing Agent Memory Without Losing the Original”" loading="lazy" decoding="async" /></figure>
<h2 id="the-trap-lossy-in-ways-you-cant-predict" tabindex="-1">The trap: lossy in ways you can’t predict <a class="anchor" href="#the-trap-lossy-in-ways-you-cant-predict" aria-hidden="true">#</a></h2>
<p>Compression is not deterministically lossy — it can drop <em>exactly the wrong thing</em>. A revenue definition
is simple until it includes “except for multi-year prepayment contracts”; summarize the exception away and
@@ -222,6 +223,7 @@ shared palace; recall is a <code>search</code> or a <code>wake-up</code> away. T
compressed index is an accelerator built on top of it — never instead of it. That ordering is the whole
trick: <strong>compression buys speed; the preserved original buys correctness.</strong> You get the small wake-up
digest without ever betting your only copy on a summary.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/compressing-agent-memory/note-2.png" alt="Hand-drawn sketch from “Compressing Agent Memory Without Losing the Original”" loading="lazy" decoding="async" /></figure>
<h2 id="when-not-to-compress" tabindex="-1">When not to compress <a class="anchor" href="#when-not-to-compress" aria-hidden="true">#</a></h2>
<p>Compression is a tradeoff, not a default. Skip it (or always keep the original alongside) when the working
set already fits comfortably — compressing tiny context adds latency and lossy risk for no gain; when the
@@ -295,6 +297,22 @@ without forgetting; it’s free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -326,22 +344,6 @@ without forgetting; it’s free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/architecture-two-planes-one-renderer/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/architecture-two-planes-one-renderer/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-04">Jun 4, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/architecture-two-planes-one-renderer/">Munder Difflin&#39;s Architecture: Two Data Planes, One Renderer</a></h3>
- <p class="dek">A walkthrough of the multi-agent harness architecture: a node-pty terminal plane and a hooks/hive event plane feeding one React + Pixi.js renderer.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/architecture-two-planes-one-renderer/" aria-label="Read: Munder Difflin&#39;s Architecture: Two Data Planes, One Renderer">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/conductor-claude-code-alternative/index.html b/docs/blog/conductor-claude-code-alternative/index.html
index 70e70c9c..0e15450c 100644
--- a/docs/blog/conductor-claude-code-alternative/index.html
+++ b/docs/blog/conductor-claude-code-alternative/index.html
@@ -163,6 +163,7 @@ smooth.</li>
</ul>
<p>If you’re a Mac user whose workflow is “spin up N parallel attempts and review the diffs,” Conductor
is a strong fit. The reasons to look elsewhere are specific.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/conductor-claude-code-alternative/note-1.png" alt="Hand-drawn sketch from “A Conductor Alternative for Orchestrating Claude Code”" loading="lazy" decoding="async" /></figure>
<h2 id="where-youd-want-an-alternative" tabindex="-1">Where you’d want an alternative <a class="anchor" href="#where-youd-want-an-alternative" aria-hidden="true">#</a></h2>
<h3 id="its-macos-only" tabindex="-1">It’s macOS-only <a class="anchor" href="#its-macos-only" aria-hidden="true">#</a></h3>
<p>If you’re on Windows or Linux — or you bounce between machines — a Mac-only app is a hard stop. A
@@ -176,6 +177,7 @@ ferrying context between worktrees.</p>
<h3 id="its-closed-source" tabindex="-1">It’s closed-source <a class="anchor" href="#its-closed-source" aria-hidden="true">#</a></h3>
<p>You can’t read the internals, self-host changes, or extend it. For some teams that’s fine; for others
— especially open-source-minded ones — it’s a dealbreaker.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/conductor-claude-code-alternative/note-2.png" alt="Hand-drawn sketch from “A Conductor Alternative for Orchestrating Claude Code”" loading="lazy" decoding="async" /></figure>
<h2 id="what-orchestration-actually-means" tabindex="-1">What “orchestration” actually means <a class="anchor" href="#what-orchestration-actually-means" aria-hidden="true">#</a></h2>
<p>The word <em>conductor</em> implies coordination, so it’s worth being precise about what full
<a href="/#how">orchestration</a> looks like for coding agents:</p>
diff --git a/docs/blog/context-engineering-for-ai-agents/index.html b/docs/blog/context-engineering-for-ai-agents/index.html
index b94fefde..0dc0be51 100644
--- a/docs/blog/context-engineering-for-ai-agents/index.html
+++ b/docs/blog/context-engineering-for-ai-agents/index.html
@@ -195,6 +195,7 @@ feature) nudges the model off course.</li>
</ul>
<p>Notice that three of the four get <em>worse</em> as you add tokens. That’s the whole argument for treating
context as something to curate, not accumulate.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/context-engineering-for-ai-agents/note-1.png" alt="Hand-drawn sketch from “Context Engineering for AI Agents: Budgeting the Window”" loading="lazy" decoding="async" /></figure>
<h2 id="multi-agent-makes-it-sharper" tabindex="-1">Multi-agent makes it sharper <a class="anchor" href="#multi-agent-makes-it-sharper" aria-hidden="true">#</a></h2>
<p>In a single-agent setup you can sometimes get away with a messy window. In a hive you can’t. Every
agent has its own window, and they have to coordinate. The naive design — one giant shared context that
@@ -250,6 +251,7 @@ next in a few lines, and that digest — not the raw hour of work — is what pr
stays on disk for anyone who needs to replay it; the <em>summary</em> is what travels. Whether it’s a single
agent compacting its own session or a team compacting into a standup, the move is the same: trade fidelity
you no longer need for window you do.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/context-engineering-for-ai-agents/note-2.png" alt="Hand-drawn sketch from “Context Engineering for AI Agents: Budgeting the Window”" loading="lazy" decoding="async" /></figure>
<h2 id="a-practical-checklist" tabindex="-1">A practical checklist <a class="anchor" href="#a-practical-checklist" aria-hidden="true">#</a></h2>
<p>When an agent underperforms, resist the urge to rewrite its prompt first. Audit its window instead:</p>
<ol>
diff --git a/docs/blog/coordinating-ai-coding-agents/index.html b/docs/blog/coordinating-ai-coding-agents/index.html
index f98b281c..4410d0cd 100644
--- a/docs/blog/coordinating-ai-coding-agents/index.html
+++ b/docs/blog/coordinating-ai-coding-agents/index.html
@@ -189,6 +189,7 @@ into place — so a reader never sees a half-written message.</li>
that every agent appends to (that file is just a multi-writer conflict by another name). The full
design — speech acts, hop caps to prevent ping-pong, idempotent delivery — is in
<a href="/blog/atomic-file-mailboxes-for-agents/">atomic file mailboxes for agents</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/coordinating-ai-coding-agents/note-1.png" alt="Hand-drawn sketch from “The Best Way to Coordinate AI Coding Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="rule-3-one-committer-for-git" tabindex="-1">Rule 3 — One committer for git <a class="anchor" href="#rule-3-one-committer-for-git" aria-hidden="true">#</a></h2>
<p>Here’s the rule people learn the hard way. Git is not safe to drive from many processes at once. The
moment two agents run <code>git add</code>/<code>git commit</code> concurrently, they race on <code>.git/index.lock</code> and you get
@@ -207,6 +208,7 @@ if they do.</p>
<strong>writes</strong> it. Other agents <em>propose</em> changes; the scribe — typically the orchestrator — incorporates
them. The plan stays coherent because it has one author, and it stays current because everyone can
suggest edits. Same single-writer principle, applied to the one genuinely co-owned artifact.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/coordinating-ai-coding-agents/note-2.png" alt="Hand-drawn sketch from “The Best Way to Coordinate AI Coding Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="rule-5-an-orchestrator-to-route-and-break-ties" tabindex="-1">Rule 5 — An orchestrator to route and break ties <a class="anchor" href="#rule-5-an-orchestrator-to-route-and-break-ties" aria-hidden="true">#</a></h2>
<p>The first four rules make collisions impossible. The fifth makes the team <em>productive</em>: someone has to
decide who does what and settle disputes.</p>
diff --git a/docs/blog/crewai-autogen-vs-a-local-agent-harness/index.html b/docs/blog/crewai-autogen-vs-a-local-agent-harness/index.html
index d5b6b5c8..96b011e5 100644
--- a/docs/blog/crewai-autogen-vs-a-local-agent-harness/index.html
+++ b/docs/blog/crewai-autogen-vs-a-local-agent-harness/index.html
@@ -168,6 +168,7 @@
<p><strong>AutoGen</strong> — the Microsoft research project that popularized conversational multi-agent patterns — has been merged with Semantic Kernel into the <strong>Microsoft Agent Framework</strong>, which shipped its production-ready 1.0 in April 2026 for Python and .NET. AutoGen and Semantic Kernel themselves are in maintenance mode; Agent Framework carries the torch, combining AutoGen’s agent abstractions with Semantic Kernel’s enterprise plumbing (state management, middleware, telemetry) plus graph-based workflows. If you’re on Azure and building agents into a product, it’s the obvious pick.</p>
<p><strong>LangGraph</strong> hit a stable 1.0 in late 2025 and is used in production at companies like Klarna, LinkedIn, Uber, and Replit. It models agent workflows as graphs with cycles — loop, retry, reflect — with checkpointing and a first-class <code>interrupt()</code> primitive for human-in-the-loop. For complex stateful pipelines where you want explicit control over every branch, it’s the default answer.</p>
<p>Notice what all three have in common. They’re <strong>libraries</strong>. <code>pip install</code>, import, write Python. That’s not a criticism — it’s the point. A framework’s job is to give a developer building blocks.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/crewai-autogen-vs-a-local-agent-harness/note-1.png" alt="Hand-drawn sketch from “CrewAI and AutoGen vs a Local Agent Harness: Framework or App?”" loading="lazy" decoding="async" /></figure>
<h2 id="what-a-framework-doesnt-give-you" tabindex="-1">What a framework doesn’t give you <a class="anchor" href="#what-a-framework-doesnt-give-you" aria-hidden="true">#</a></h2>
<p>Here’s the part the comparison charts skip: when you pick a framework, <strong>you’ve signed up to build the harness yourself.</strong> The agent loop is maybe a fifth of a working multi-agent system. Around it you still need:</p>
<ul>
@@ -182,6 +183,7 @@
<p>A <a href="/blog/what-is-a-multi-agent-harness/">multi-agent harness</a> is the other answer: the system, already assembled, as an app. Munder Difflin is a free, MIT-licensed, local-first desktop app (macOS/Windows/Linux) where every agent is a <strong>real CLI process</strong> — Claude Code, OpenAI Codex, Antigravity, OpenCode, Crush, pi.dev, GitHub Copilot CLI — running in its own pseudo-terminal and its own isolated git worktree. A <a href="/blog/how-the-god-orchestrator-works/">GOD orchestrator</a> routes work between them; agents share long-term memory; triggers include typing, Slack, webhooks, schedules, and voice.</p>
<p>The pieces you’d have built around a framework are already there: <a href="/blog/human-in-the-loop-approving-ai-agents/">human approval gates</a> on spend, scope, and destructive ops; a circuit breaker with a steer → constrain → stop ladder; per-agent token budgets; OpenTelemetry observability; a Command Center with a kanban board and live fleet monitoring. And because it drives CLIs rather than calling model APIs, it rides the <strong>subscriptions you already pay for</strong> — no mandatory API key, with BYO keys and local LLMs as options.</p>
<p>The honest flip side: you can’t <code>import</code> Munder Difflin into your SaaS. It won’t run your custom document pipeline inside your product. It’s an app for a specific job — a team of agents working your repositories, visible on one screen — not a toolkit for arbitrary agent systems.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/crewai-autogen-vs-a-local-agent-harness/note-2.png" alt="Hand-drawn sketch from “CrewAI and AutoGen vs a Local Agent Harness: Framework or App?”" loading="lazy" decoding="async" /></figure>
<h2 id="the-honest-decision-rule" tabindex="-1">The honest decision rule <a class="anchor" href="#the-honest-decision-rule" aria-hidden="true">#</a></h2>
<p><strong>Choose a framework (CrewAI, Agent Framework, LangGraph) when:</strong></p>
<ul>
diff --git a/docs/blog/crystal-claude-code-alternative/index.html b/docs/blog/crystal-claude-code-alternative/index.html
index ad211676..0043fcad 100644
--- a/docs/blog/crystal-claude-code-alternative/index.html
+++ b/docs/blog/crystal-claude-code-alternative/index.html
@@ -165,6 +165,7 @@ juggling.</li>
</ul>
<p>For “run a few variations in parallel and pick the best diff,” Crystal is a good answer. The reason to
look further is usually one word: <em>memory</em>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/crystal-claude-code-alternative/note-1.png" alt="Hand-drawn sketch from “A Crystal Alternative: Multi-Agent Claude Code with Memory”" loading="lazy" decoding="async" /></figure>
<h2 id="where-parallel-sessions-hit-a-ceiling" tabindex="-1">Where parallel sessions hit a ceiling <a class="anchor" href="#where-parallel-sessions-hit-a-ceiling" aria-hidden="true">#</a></h2>
<p>Crystal, like other parallel-worktree apps, runs agents <em>beside</em> each other. What it doesn’t add is a
coordination layer:</p>
@@ -178,6 +179,7 @@ the same context.</p>
<h3 id="theres-no-orchestrator" tabindex="-1">There’s no orchestrator <a class="anchor" href="#theres-no-orchestrator" aria-hidden="true">#</a></h3>
<p>You launch and assign each session. Nothing decomposes a goal and routes the pieces across the team
for you.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/crystal-claude-code-alternative/note-2.png" alt="Hand-drawn sketch from “A Crystal Alternative: Multi-Agent Claude Code with Memory”" loading="lazy" decoding="async" /></figure>
<h2 id="what-memory-changes-day-to-day" tabindex="-1">What memory changes, day to day <a class="anchor" href="#what-memory-changes-day-to-day" aria-hidden="true">#</a></h2>
<p>Adding a shared brain to a team of agents is a bigger shift than it sounds:</p>
<ul>
diff --git a/docs/blog/debugging-multi-agent-systems/index.html b/docs/blog/debugging-multi-agent-systems/index.html
index 2c8856e6..694350b7 100644
--- a/docs/blog/debugging-multi-agent-systems/index.html
+++ b/docs/blog/debugging-multi-agent-systems/index.html
@@ -196,6 +196,7 @@ replying to a <code>request</code> and leaving a peer stuck.</li>
<p>Reading the trail answers the relational question: did A actually ask B what you think it did, and did
B get it? Half of “the hive stalled” bugs resolve right here — a message that was malformed, misrouted,
or never sent.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/debugging-multi-agent-systems/note-1.png" alt="Hand-drawn sketch from “How to Debug a Multi-Agent System”" loading="lazy" decoding="async" /></figure>
<h2 id="drop-into-the-agents-terminal" tabindex="-1">Drop into the agent’s terminal <a class="anchor" href="#drop-into-the-agents-terminal" aria-hidden="true">#</a></h2>
<p>Now — and only now — open the specific agent’s terminal. Because every agent runs in a real
pseudo-terminal, you have its byte-for-byte output, not a summary. With the log and the message trail
@@ -211,6 +212,7 @@ idle — often pointing you at the right terminal before you’ve even opened th
<strong>replayable</strong>: each coordination step is a commit, so you can walk the history and reconstruct exactly
what the hive knew at any point — the roster, the pending messages, the board. When “what state was the
system in when it broke?” matters, the git log answers it precisely instead of from memory.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/debugging-multi-agent-systems/note-2.png" alt="Hand-drawn sketch from “How to Debug a Multi-Agent System”" loading="lazy" decoding="async" /></figure>
<h2 id="check-the-usual-suspects" tabindex="-1">Check the usual suspects <a class="anchor" href="#check-the-usual-suspects" aria-hidden="true">#</a></h2>
<p>Some failure modes recur in multi-agent systems. When you’re stuck, check these directly:</p>
<ul>
diff --git a/docs/blog/deploy-a-blog-writer-agent/index.html b/docs/blog/deploy-a-blog-writer-agent/index.html
index f30b0339..88e3e54f 100644
--- a/docs/blog/deploy-a-blog-writer-agent/index.html
+++ b/docs/blog/deploy-a-blog-writer-agent/index.html
@@ -193,6 +193,7 @@ spare-time pace. When someone — or an AI answer engine — searches “single-
is how a one-person project publishes like a content team.</p>
<p>And crucially: it’s <em>largely hands-off</em>. The expensive part of blogging isn’t typing — it’s the discipline
to keep shipping. An agent has no problem with discipline.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/deploy-a-blog-writer-agent/note-1.png" alt="Hand-drawn sketch from “Deploy a Blog-Writer Agent: The One That Wrote This Post”" loading="lazy" decoding="async" /></figure>
<h2 id="the-pipeline-end-to-end" tabindex="-1">The pipeline, end to end <a class="anchor" href="#the-pipeline-end-to-end" aria-hidden="true">#</a></h2>
<p>The writer agent isn’t a magic monolith. It’s one role in a hive, and the post moves through the same
machinery any work does. Four stages:</p>
@@ -241,6 +242,7 @@ then put the <strong>deploy</strong> behind a human approval. Draft and integrat
the next backlog item each time. One prompt to the orchestrator stood up <a href="/blog/one-prompt-automated-pr-review/">an hourly PR
reviewer</a> for us the same way — automation that just keeps running.
Point that same scheduling at content and the blog writes itself on a timer.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/deploy-a-blog-writer-agent/note-2.png" alt="Hand-drawn sketch from “Deploy a Blog-Writer Agent: The One That Wrote This Post”" loading="lazy" decoding="async" /></figure>
<h2 id="the-meta-point" tabindex="-1">The meta-point <a class="anchor" href="#the-meta-point" aria-hidden="true">#</a></h2>
<p>A multi-agent hive isn’t only for code. Once you have a writer that drafts, an orchestrator that integrates
and commits, a build that publishes, and one human gate, you have a <strong>content function</strong> — not a one-off
@@ -317,50 +319,50 @@ floor; it’s free and open source.</p>
<h2>Related in Use Cases</h2>
<div class="post-grid">
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/overnight-ai-coding-realistic-expectations/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/overnight-ai-coding-realistic-expectations/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-04">Jun 4, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
+ <span>3 min</span>
</div>
- <h3><a href="/blog/overnight-ai-coding-realistic-expectations/">Overnight AI Coding: What&#39;s Realistic (and What&#39;s Not)</a></h3>
- <p class="dek">An honest look at letting AI coding agents run overnight — what works today, where guardrails matter, and what still needs a human in the morning.</p>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/overnight-ai-coding-realistic-expectations/" aria-label="Read: Overnight AI Coding: What&#39;s Realistic (and What&#39;s Not)">Read →</a>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/from-one-terminal-to-a-team/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/from-one-terminal-to-a-team/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-02">Jun 2, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>3 min</span>
</div>
- <h3><a href="/blog/from-one-terminal-to-a-team/">From One Terminal to a Team: Scaling Your Claude Code Workflow</a></h3>
- <p class="dek">The workflow shift from a single Claude Code session to a coordinated team of agents — what changes, where it breaks, and the concrete before-and-after.</p>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/from-one-terminal-to-a-team/" aria-label="Read: From One Terminal to a Team: Scaling Your Claude Code Workflow">Read →</a>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/run-an-office-of-ai-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-an-office-of-ai-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-02">Jun 2, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>3 min</span>
</div>
- <h3><a href="/blog/run-an-office-of-ai-agents/">Run an Office of AI Agents While You Sleep</a></h3>
- <p class="dek">What it takes to run a self-coordinating office of AI coding agents that keeps shipping after you log off — and the guardrails that keep it sane.</p>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/run-an-office-of-ai-agents/" aria-label="Read: Run an Office of AI Agents While You Sleep">Read →</a>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/deploy-automated-pr-reviewer-agent/index.html b/docs/blog/deploy-automated-pr-reviewer-agent/index.html
index 16e43372..afc1d540 100644
--- a/docs/blog/deploy-automated-pr-reviewer-agent/index.html
+++ b/docs/blog/deploy-automated-pr-reviewer-agent/index.html
@@ -169,6 +169,7 @@
<li><strong>It sees the whole backlog at once.</strong> Reading the full set of open issues plus shared hive memory, it can notice that issues #41, #43, and #47 are three faces of the same bug — rather than reviewing each in a vacuum.</li>
<li><strong>It escalates through the same inbox you use.</strong> A serious finding becomes a message to you, routed like any other hive mail. No separate alerting system.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/deploy-automated-pr-reviewer-agent/note-1.png" alt="Hand-drawn sketch from “Deploy a PR Reviewer That Never Sleeps — In About One Prompt”" loading="lazy" decoding="async" /></figure>
<h2 id="deploying-it-the-one-prompt-version" tabindex="-1">Deploying it: the one-prompt version <a class="anchor" href="#deploying-it-the-one-prompt-version" aria-hidden="true">#</a></h2>
<p>You don’t configure this. You brief it. Open Munder Difflin, select the GOD orchestrator, and describe the outcome the way you’d brief a coworker:</p>
<blockquote>
@@ -201,6 +202,7 @@
<h3 id="why-the-consolidation-is-the-real-win" tabindex="-1">Why the consolidation is the real win <a class="anchor" href="#why-the-consolidation-is-the-real-win" aria-hidden="true">#</a></h3>
<p>It’s tempting to frame this as “it reviewed PRs fast.” But the load-bearing part is the <strong>de-noising</strong>: 22 → 2. A reviewer that comments on everything just moves the triage burden into your inbox. A reviewer that reads the whole backlog, verifies against source, and collapses duplicates into root causes does the part of code review that’s actually hard — deciding <em>what’s true and what’s distinct</em> — and hands you the short list.</p>
<p>That’s the difference between an automated commenter and an automated <em>reviewer</em>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/deploy-automated-pr-reviewer-agent/note-2.png" alt="Hand-drawn sketch from “Deploy a PR Reviewer That Never Sleeps — In About One Prompt”" loading="lazy" decoding="async" /></figure>
<h2 id="what-to-be-honest-about" tabindex="-1">What to be honest about <a class="anchor" href="#what-to-be-honest-about" aria-hidden="true">#</a></h2>
<p>Two limits worth stating plainly, because overselling this helps no one:</p>
<ul>
diff --git a/docs/blog/do-more-with-less-model-routing/index.html b/docs/blog/do-more-with-less-model-routing/index.html
index 51ea7e23..f24f7a12 100644
--- a/docs/blog/do-more-with-less-model-routing/index.html
+++ b/docs/blog/do-more-with-less-model-routing/index.html
@@ -194,6 +194,7 @@ buys you something.</li>
<p>The third option typically cuts total spend by more than half while <em>keeping</em> quality, because you only
spend big where capability actually changes the outcome. “Do more with less” isn’t a slogan here; it’s
just what falls out of matching price to need.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/do-more-with-less-model-routing/note-1.png" alt="Hand-drawn sketch from “Do More With Less: Smart Model Routing Across Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="the-orchestrator-is-the-natural-router" tabindex="-1">The orchestrator is the natural router <a class="anchor" href="#the-orchestrator-is-the-natural-router" aria-hidden="true">#</a></h2>
<p>In a single-agent setup, routing is a manual choice you make per session. In a hive, you can do better,
because there’s already a component that sees every task before it’s handed out: the
@@ -226,6 +227,7 @@ retrying a too-small model is just paying twice for the same miss.</li>
model’s coherence over long runs.</li>
</ul>
<p>Everything that trips none of these — the bulk of the day — stays lean.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/do-more-with-less-model-routing/note-2.png" alt="Hand-drawn sketch from “Do More With Less: Smart Model Routing Across Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="you-cant-route-what-you-cant-see" tabindex="-1">You can’t route what you can’t see <a class="anchor" href="#you-cant-route-what-you-cant-see" aria-hidden="true">#</a></h2>
<p>The honest caveat: routing decisions are only as good as your visibility into cost. If you don’t know
which agents and tasks are burning the most tokens, you’re guessing. The teams that get the most out of
diff --git a/docs/blog/does-the-june-2026-agent-sdk-change-affect-munder-difflin/index.html b/docs/blog/does-the-june-2026-agent-sdk-change-affect-munder-difflin/index.html
index 112f170b..6706c221 100644
--- a/docs/blog/does-the-june-2026-agent-sdk-change-affect-munder-difflin/index.html
+++ b/docs/blog/does-the-june-2026-agent-sdk-change-affect-munder-difflin/index.html
@@ -197,6 +197,7 @@ of Claude. It’s what the June 15 update re-bills onto the separate credit.</li
<p>A useful test: if a tool <strong>embeds the SDK</strong> to run agents headlessly, it’s affected; if it <strong>drives the
Claude Code CLI</strong> the way you would by hand, it isn’t. Munder Difflin is firmly the latter — it’s a
<a href="/blog/claude-code-subagents-vs-multi-agent-harness/">harness around Claude Code, not a wrapper around the SDK</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-1.png" alt="Hand-drawn sketch from “Does the June 2026 Agent SDK Change Affect Munder Difflin?”" loading="lazy" decoding="async" /></figure>
<h2 id="why-this-doesnt-change-how-munder-difflin-runs" tabindex="-1">Why this doesn’t change how Munder Difflin runs <a class="anchor" href="#why-this-doesnt-change-how-munder-difflin-runs" aria-hidden="true">#</a></h2>
<p>Munder Difflin is a <a href="/#what">multi-agent harness</a> that orchestrates the <strong>native Claude Code CLI</strong>. Each
agent in the hive is spawned as a real <strong>interactive terminal session</strong> through <code>node-pty</code> — a genuine
@@ -220,6 +221,7 @@ it), and its usage is light enough to sit comfortably <strong>within the include
even with enrich turned on, you’re covered; with it off, the change is invisible to you.</p>
<p>That’s the honest shape of it: <strong>the agents are unaffected; the optional enrich assistant uses
<code>claude -p</code>, which the new credit covers.</strong> No “100% unaffected” hand-waving.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/does-the-june-2026-agent-sdk-change-affect-munder-difflin/note-2.png" alt="Hand-drawn sketch from “Does the June 2026 Agent SDK Change Affect Munder Difflin?”" loading="lazy" decoding="async" /></figure>
<h2 id="how-to-check-for-yourself" tabindex="-1">How to check for yourself <a class="anchor" href="#how-to-check-for-yourself" aria-hidden="true">#</a></h2>
<p>You don’t have to take our word for it. In Munder Difflin, every agent is a tab you can watch — a live
terminal running Claude Code, exactly the interactive usage the policy keeps on your subscription. The
diff --git a/docs/blog/evaluating-ai-agent-reliability/index.html b/docs/blog/evaluating-ai-agent-reliability/index.html
index 66655e51..0c98338d 100644
--- a/docs/blog/evaluating-ai-agent-reliability/index.html
+++ b/docs/blog/evaluating-ai-agent-reliability/index.html
@@ -190,6 +190,7 @@ weakly-tested codebase is the harder case the benchmark removed. As benchmark ro
a leaderboard score is a starting point, not a verdict — real-world reliability is consistently lower.</p>
<p>The takeaway isn’t “ignore benchmarks.” It’s: use them to <em>rank</em>, then re-measure on <em>your</em> work before
you trust anything.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/evaluating-ai-agent-reliability/note-1.png" alt="Hand-drawn sketch from “Evaluating AI Agent Reliability: How to Measure What You Can Trust”" loading="lazy" decoding="async" /></figure>
<h2 id="measure-the-things-that-actually-break" tabindex="-1">Measure the things that actually break <a class="anchor" href="#measure-the-things-that-actually-break" aria-hidden="true">#</a></h2>
<p>Final-answer accuracy hides the failure modes that matter for an autonomous agent. What predicts
real reliability is the stuff that compounds over a long run:</p>
@@ -225,6 +226,7 @@ overall pass.</li>
<li><strong>Human calibration on a sample.</strong> Have a person review 1–2% of cases and check the judge agrees;
when they diverge, fix the rubric. Automated eval scales; human eval keeps it honest.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/evaluating-ai-agent-reliability/note-2.png" alt="Hand-drawn sketch from “Evaluating AI Agent Reliability: How to Measure What You Can Trust”" loading="lazy" decoding="async" /></figure>
<h2 id="close-the-loop-with-observability" tabindex="-1">Close the loop with observability <a class="anchor" href="#close-the-loop-with-observability" aria-hidden="true">#</a></h2>
<p>A reliability number is only as good as the data behind it, and a <a href="/#what">multi-agent harness</a> is already
producing most of it. Munder Difflin records <strong>real token and cost telemetry</strong> from the agents’
diff --git a/docs/blog/feed.xml b/docs/blog/feed.xml
index 221425a3..0a76c1af 100644
--- a/docs/blog/feed.xml
+++ b/docs/blog/feed.xml
@@ -4,9 +4,89 @@
<subtitle>Guides, deep dives, and comparisons on running multi-agent Claude Code: orchestration, agent memory, automation, and the tooling landscape.</subtitle>
<link href="https://munderdiffl.in/blog/feed.xml" rel="self" />
<link href="https://munderdiffl.in/blog/" />
- <updated>2026-08-08T00:00:00.000Z</updated>
+ <updated>2026-08-19T00:00:00.000Z</updated>
<id>https://munderdiffl.in/blog/</id>
<author><name>Chaitanya Giri</name><uri>https://munderdiffl.in</uri></author>
+ <entry>
+ <title>Our Agents Ran Our Launch-Week Analytics</title>
+ <link href="https://munderdiffl.in/blog/agents-ran-our-launch-week-analytics/" />
+ <id>https://munderdiffl.in/blog/agents-ran-our-launch-week-analytics/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Use Cases" />
+ <summary>Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</summary>
+ </entry>
+ <entry>
+ <title>An Agent Redesigned the Blog You&#39;re Reading</title>
+ <link href="https://munderdiffl.in/blog/an-agent-redesigned-this-blog/" />
+ <id>https://munderdiffl.in/blog/an-agent-redesigned-this-blog/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Use Cases" />
+ <summary>Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</summary>
+ </entry>
+ <entry>
+ <title>Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</title>
+ <link href="https://munderdiffl.in/blog/launching-munder-difflin-v0-4-4/" />
+ <id>https://munderdiffl.in/blog/launching-munder-difflin-v0-4-4/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
+ <summary>v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</summary>
+ </entry>
+ <entry>
+ <title>Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</title>
+ <link href="https://munderdiffl.in/blog/number-five-on-product-hunt/" />
+ <id>https://munderdiffl.in/blog/number-five-on-product-hunt/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
+ <summary>Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</summary>
+ </entry>
+ <entry>
+ <title>Run a Release Train with Agents</title>
+ <link href="https://munderdiffl.in/blog/run-a-release-train-with-agents/" />
+ <id>https://munderdiffl.in/blog/run-a-release-train-with-agents/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Use Cases" />
+ <summary>Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</summary>
+ </entry>
+ <entry>
+ <title>Seven Releases in Eight Days: 0.3.8 → 0.4.4</title>
+ <link href="https://munderdiffl.in/blog/seven-releases-in-eight-days/" />
+ <id>https://munderdiffl.in/blog/seven-releases-in-eight-days/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
+ <summary>Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</summary>
+ </entry>
+ <entry>
+ <title>The Newline That Silenced Every Windows Agent</title>
+ <link href="https://munderdiffl.in/blog/the-newline-that-silenced-windows-agents/" />
+ <id>https://munderdiffl.in/blog/the-newline-that-silenced-windows-agents/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Internals" />
+ <summary>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.</summary>
+ </entry>
+ <entry>
+ <title>Turn a Firehose of Feedback into a Backlog with Agents</title>
+ <link href="https://munderdiffl.in/blog/turn-feedback-into-a-backlog-with-agents/" />
+ <id>https://munderdiffl.in/blog/turn-feedback-into-a-backlog-with-agents/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Use Cases" />
+ <summary>516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</summary>
+ </entry>
+ <entry>
+ <title>We Opened a Discord (Merge a PR, Become Employee of the Month)</title>
+ <link href="https://munderdiffl.in/blog/we-opened-a-discord/" />
+ <id>https://munderdiffl.in/blog/we-opened-a-discord/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
+ <summary>Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</summary>
+ </entry>
+ <entry>
+ <title>What 516 Reddit Comments Told Us About Munder Difflin</title>
+ <link href="https://munderdiffl.in/blog/what-reddit-told-us-about-munder-difflin/" />
+ <id>https://munderdiffl.in/blog/what-reddit-told-us-about-munder-difflin/</id>
+ <published>2026-08-19T00:00:00.000Z</published>
+ <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
+ <summary>We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</summary>
+ </entry>
<entry>
<title>What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</title>
<link href="https://munderdiffl.in/blog/whats-up-with-munder-difflin/" />
@@ -407,84 +487,4 @@
<updated>2026-06-04T00:00:00.000Z</updated><category term="Internals" />
<summary>A walkthrough of the multi-agent harness architecture: a node-pty terminal plane and a hooks/hive event plane feeding one React + Pixi.js renderer.</summary>
</entry>
- <entry>
- <title>The Best Tools to Run Multiple Claude Code Agents (2026)</title>
- <link href="https://munderdiffl.in/blog/best-claude-code-multi-agent-tools/" />
- <id>https://munderdiffl.in/blog/best-claude-code-multi-agent-tools/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Comparisons" />
- <summary>An honest 2026 roundup of tools to run multiple Claude Code agents — Claude Squad, Conductor, Crystal, vibe-kanban, and Munder Difflin — compared.</summary>
- </entry>
- <entry>
- <title>Building Reliable AI Agents: Failure Is the Default</title>
- <link href="https://munderdiffl.in/blog/building-reliable-ai-agents/" />
- <id>https://munderdiffl.in/blog/building-reliable-ai-agents/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Guides" />
- <summary>Agents fail constantly: tools error, steps stall, output goes wrong. Reliability isn&#39;t avoiding failure — it&#39;s making each one contained and recoverable.</summary>
- </entry>
- <entry>
- <title>Can Claude Code Agents Talk to Each Other?</title>
- <link href="https://munderdiffl.in/blog/can-claude-code-agents-talk-to-each-other/" />
- <id>https://munderdiffl.in/blog/can-claude-code-agents-talk-to-each-other/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Concepts" />
- <summary>Can Claude Code agents talk to each other? By default they report to their launcher — but a small coordination layer lets them message peer-to-peer.</summary>
- </entry>
- <entry>
- <title>Claude Code Automation: Let Agents Build While You Sleep</title>
- <link href="https://munderdiffl.in/blog/claude-code-automation-while-you-sleep/" />
- <id>https://munderdiffl.in/blog/claude-code-automation-while-you-sleep/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Guides" />
- <summary>Claude Code automation that runs overnight: an autonomous Stop-hook loop, safe permission bypass, and guardrails so you wake up to progress, not chaos.</summary>
- </entry>
- <entry>
- <title>Git Worktrees vs a Hive: Two Ways to Parallelize Claude Code</title>
- <link href="https://munderdiffl.in/blog/claude-code-git-worktrees-vs-hive/" />
- <id>https://munderdiffl.in/blog/claude-code-git-worktrees-vs-hive/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Orchestration" />
- <summary>Claude Code git worktrees vs a hive: when isolated worktrees suffice for parallel agents, and when you need memory, messaging, and an orchestrator on top.</summary>
- </entry>
- <entry>
- <title>Claude Code Orchestration Tools, Compared</title>
- <link href="https://munderdiffl.in/blog/claude-code-orchestration-tools-compared/" />
- <id>https://munderdiffl.in/blog/claude-code-orchestration-tools-compared/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Comparisons" />
- <summary>Claude Code orchestration tools compared on memory, messaging, visibility, control, and local-first — across Claude Squad, Conductor, Crystal, and more.</summary>
- </entry>
- <entry>
- <title>Claude Squad vs Munder Difflin: Which Should You Use?</title>
- <link href="https://munderdiffl.in/blog/claude-squad-vs-munder-difflin/" />
- <id>https://munderdiffl.in/blog/claude-squad-vs-munder-difflin/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Comparisons" />
- <summary>Claude Squad vs Munder Difflin: a lean terminal session manager against a memory-backed, orchestrated, visual hive. Feature table and an honest verdict.</summary>
- </entry>
- <entry>
- <title>Context Engineering for AI Agents: Budgeting the Window</title>
- <link href="https://munderdiffl.in/blog/context-engineering-for-ai-agents/" />
- <id>https://munderdiffl.in/blog/context-engineering-for-ai-agents/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Guides" />
- <summary>Why context engineering beats prompt wording for agents — and the tactics (isolation, retrieval, externalized state, compaction) that keep the window lean.</summary>
- </entry>
- <entry>
- <title>How to Debug a Multi-Agent System</title>
- <link href="https://munderdiffl.in/blog/debugging-multi-agent-systems/" />
- <id>https://munderdiffl.in/blog/debugging-multi-agent-systems/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Guides" />
- <summary>How to debug a multi-agent system: use the event log, per-agent terminals, message trails, and git history to find why a hive of AI agents went sideways.</summary>
- </entry>
- <entry>
- <title>Do More With Less: Smart Model Routing Across Agents</title>
- <link href="https://munderdiffl.in/blog/do-more-with-less-model-routing/" />
- <id>https://munderdiffl.in/blog/do-more-with-less-model-routing/</id>
- <published>2026-06-04T00:00:00.000Z</published>
- <updated>2026-06-04T00:00:00.000Z</updated><category term="Concepts" />
- <summary>Why a hive of agents shouldn&#39;t all run the biggest model — and how routing the right task to the right model cuts cost and latency without losing quality.</summary>
- </entry>
</feed>
diff --git a/docs/blog/file-based-coordination-vs-message-queues/index.html b/docs/blog/file-based-coordination-vs-message-queues/index.html
index a462d2a3..dbe035f7 100644
--- a/docs/blog/file-based-coordination-vs-message-queues/index.html
+++ b/docs/blog/file-based-coordination-vs-message-queues/index.html
@@ -181,6 +181,7 @@ honest look at where that choice runs out.</p>
a router moves each outbox file to its recipient. Shared plans live in one markdown
<a href="/blog/how-the-god-orchestrator-works/">board</a>. History is an <a href="/blog/append-only-event-log-agents/">append-only log</a>.
Nothing here is a database or a daemon — it’s files on disk, and that’s the point.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/file-based-coordination-vs-message-queues/note-1.png" alt="Hand-drawn sketch from “File-Based Coordination vs Message Queues for AI Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="why-files-beat-a-broker-for-a-hive" tabindex="-1">Why files beat a broker for a hive <a class="anchor" href="#why-files-beat-a-broker-for-a-hive" aria-hidden="true">#</a></h2>
<p><strong>You can read it.</strong> A message is a file you can <code>cat</code>. The whole system state is a directory you can
list. When something goes wrong, you debug by <em>looking</em> — no broker admin UI, no “drain the queue to see
@@ -210,6 +211,7 @@ for shared state like the board and the git history. Agents never contend; they
<li><strong>It doesn’t cross machines.</strong> Files coordinate processes on one host. The moment your agents live on
different boxes, you need something networked.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/file-based-coordination-vs-message-queues/note-2.png" alt="Hand-drawn sketch from “File-Based Coordination vs Message Queues for AI Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="when-to-actually-reach-for-a-queue" tabindex="-1">When to actually reach for a queue <a class="anchor" href="#when-to-actually-reach-for-a-queue" aria-hidden="true">#</a></h2>
<p>Use the decision, not the dogma. Files are right when your hive is <strong>local, supervised, and dozens of
agents</strong> — where debuggability, durability, and zero-ops dominate. Switch to a broker (Redis, RabbitMQ,
@@ -286,6 +288,22 @@ durable, git-versioned, and debuggable by just looking.
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -317,22 +335,6 @@ durable, git-versioned, and debuggable by just looking.
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/from-one-terminal-to-a-team/index.html b/docs/blog/from-one-terminal-to-a-team/index.html
index 7c413bdc..b831c285 100644
--- a/docs/blog/from-one-terminal-to-a-team/index.html
+++ b/docs/blog/from-one-terminal-to-a-team/index.html
@@ -157,6 +157,7 @@ need. The only ceiling is <em>throughput</em> — one agent does one thing at a
parallelism in the room.</p>
<p><strong>The pain that pushes you forward:</strong> you’re waiting on the agent while three other things you could
parallelize sit idle.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/from-one-terminal-to-a-team/note-1.png" alt="Hand-drawn sketch from “From One Terminal to a Team: Scaling Your Claude Code Workflow”" loading="lazy" decoding="async" /></figure>
<h2 id="stage-2-a-few-manual-terminals" tabindex="-1">Stage 2: A few manual terminals <a class="anchor" href="#stage-2-a-few-manual-terminals" aria-hidden="true">#</a></h2>
<p>So you open more terminals — a <a href="/blog/how-to-run-multiple-claude-code-agents/">classic move</a>. One
writes tests, one refactors, one updates docs. Throughput jumps. For two or three <em>independent</em> tasks,
@@ -183,6 +184,7 @@ instead of routing through you.</li>
</ul>
<p>That’s the leap from juggling <a href="/blog/what-are-claude-code-agents/">Claude Code agents</a> to running a
<a href="/#what">multi-agent harness</a>. It’s the stage where adding agents stops adding <em>overhead</em>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/from-one-terminal-to-a-team/note-2.png" alt="Hand-drawn sketch from “From One Terminal to a Team: Scaling Your Claude Code Workflow”" loading="lazy" decoding="async" /></figure>
<h2 id="the-before-and-after" tabindex="-1">The before-and-after <a class="anchor" href="#the-before-and-after" aria-hidden="true">#</a></h2>
<p>The same morning, two ways:</p>
<table>
@@ -273,50 +275,50 @@ jump; it’s free and open source.</p>
<h2>Related in Use Cases</h2>
<div class="post-grid">
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/deploy-a-blog-writer-agent/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deploy-a-blog-writer-agent/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-10">Jun 10, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>3 min</span>
</div>
- <h3><a href="/blog/deploy-a-blog-writer-agent/">Deploy a Blog-Writer Agent: The One That Wrote This Post</a></h3>
- <p class="dek">How Munder Difflin&#39;s blog is written by an automated writer agent in the hive — drafts in a worktree, single-committer integration, Eleventy build, human-gated deploy. Build your own.</p>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/deploy-a-blog-writer-agent/" aria-label="Read: Deploy a Blog-Writer Agent: The One That Wrote This Post">Read →</a>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/overnight-ai-coding-realistic-expectations/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/overnight-ai-coding-realistic-expectations/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-04">Jun 4, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
+ <span>3 min</span>
</div>
- <h3><a href="/blog/overnight-ai-coding-realistic-expectations/">Overnight AI Coding: What&#39;s Realistic (and What&#39;s Not)</a></h3>
- <p class="dek">An honest look at letting AI coding agents run overnight — what works today, where guardrails matter, and what still needs a human in the morning.</p>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/overnight-ai-coding-realistic-expectations/" aria-label="Read: Overnight AI Coding: What&#39;s Realistic (and What&#39;s Not)">Read →</a>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/run-an-office-of-ai-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-an-office-of-ai-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-02">Jun 2, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>3 min</span>
</div>
- <h3><a href="/blog/run-an-office-of-ai-agents/">Run an Office of AI Agents While You Sleep</a></h3>
- <p class="dek">What it takes to run a self-coordinating office of AI coding agents that keeps shipping after you log off — and the guardrails that keep it sane.</p>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/run-an-office-of-ai-agents/" aria-label="Read: Run an Office of AI Agents While You Sleep">Read →</a>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/generative-engine-optimization-techniques/index.html b/docs/blog/generative-engine-optimization-techniques/index.html
index 39501e45..1cc8f7af 100644
--- a/docs/blog/generative-engine-optimization-techniques/index.html
+++ b/docs/blog/generative-engine-optimization-techniques/index.html
@@ -203,6 +203,7 @@ amplified the gains rather than competing with them.</li>
<p>The through-line: generative engines reward content that is <em>quotable and evidenced</em>. A sentence with a
statistic, a citation, and a clear claim is exactly the kind of thing an LLM can lift into an answer
with confidence — which is the whole game.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/generative-engine-optimization-techniques/note-1.png" alt="Hand-drawn sketch from “Generative Engine Optimization: The Techniques the Research Backs”" loading="lazy" decoding="async" /></figure>
<h2 id="what-flopped-keyword-stuffing" tabindex="-1">What flopped: keyword stuffing <a class="anchor" href="#what-flopped-keyword-stuffing" aria-hidden="true">#</a></h2>
<p>Here’s the finding worth tattooing on the SEO reflex: <strong>keyword stuffing didn’t work.</strong> In the GEO
research, jamming target keywords in — a tactic that historically nudged classic search — failed to
@@ -224,6 +225,7 @@ engine, domain, or query type.</li>
</ul>
<p>None of that invalidates the core lesson; it just means you treat the study as strong evidence for a
<em>direction</em> and confirm with your own testing. Which is the scientific posture anyway.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/generative-engine-optimization-techniques/note-2.png" alt="Hand-drawn sketch from “Generative Engine Optimization: The Techniques the Research Backs”" loading="lazy" decoding="async" /></figure>
<h2 id="how-to-apply-it" tabindex="-1">How to apply it <a class="anchor" href="#how-to-apply-it" aria-hidden="true">#</a></h2>
<p>For a blog, docs, or a product page you want cited:</p>
<ul>
diff --git a/docs/blog/github-copilot-cli-vs-claude-code-for-hive-work/index.html b/docs/blog/github-copilot-cli-vs-claude-code-for-hive-work/index.html
index bb2adb7b..8913aa31 100644
--- a/docs/blog/github-copilot-cli-vs-claude-code-for-hive-work/index.html
+++ b/docs/blog/github-copilot-cli-vs-claude-code-for-hive-work/index.html
@@ -171,6 +171,7 @@
<li><strong>Can it be interrupted, steered, and fed new input mid-stream?</strong></li>
</ol>
<p>Claude Code and Copilot CLI give very different answers — and neither answer is wrong. They’re different shapes for different jobs.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-1.png" alt="Hand-drawn sketch from “GitHub Copilot CLI vs Claude Code as Hive Workers”" loading="lazy" decoding="async" /></figure>
<h2 id="claude-code-the-hive-aware-resident" tabindex="-1">Claude Code: the hive-aware resident <a class="anchor" href="#claude-code-the-hive-aware-resident" aria-hidden="true">#</a></h2>
<p>Claude Code runs as a persistent interactive session in its pseudo-terminal, and it exposes native hooks — external commands fired at lifecycle points. Munder Difflin leans on those hard:</p>
<ul>
@@ -191,6 +192,7 @@
</ul>
<p>The honest limitation: with no resident process between turns, there’s nothing to deliver inbox mail <em>to</em>. So in Munder Difflin, Copilot’s provider is registered non-hive-aware (<code>canReceiveInbox: false</code>), and routed mail <strong>bounces to the GOD orchestrator</strong> instead of silently dropping. The orchestrator can then re-dispatch it as a fresh Copilot task or hand it to a hive-aware worker.</p>
<p>To be fair to Copilot CLI: the tool itself is more extensible than the print-mode integration uses. GitHub ships its own hooks system (JSON files in <code>.github/hooks/</code> or <code>~/.copilot/hooks/</code>, with <code>sessionStart</code>/<code>sessionEnd</code> events), MCP server support, and custom instructions. A deeper bridge is conceivable; v0.3.3 ships the documented, honest version.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/github-copilot-cli-vs-claude-code-for-hive-work/note-2.png" alt="Hand-drawn sketch from “GitHub Copilot CLI vs Claude Code as Hive Workers”" loading="lazy" decoding="async" /></figure>
<h2 id="verdict-dont-pick-mix" tabindex="-1">Verdict: don’t pick — mix <a class="anchor" href="#verdict-dont-pick-mix" aria-hidden="true">#</a></h2>
<p>The comparison table writes itself once you frame it as lifecycle:</p>
<table>
diff --git a/docs/blog/give-claude-code-long-term-memory/index.html b/docs/blog/give-claude-code-long-term-memory/index.html
index 5f717900..55747ccd 100644
--- a/docs/blog/give-claude-code-long-term-memory/index.html
+++ b/docs/blog/give-claude-code-long-term-memory/index.html
@@ -156,6 +156,7 @@ core problem. Here’s how to fix it.</p>
Nothing it learned persists unless you <strong>write it somewhere the next session will read.</strong> That’s the
whole trick: long-term memory is just durable storage plus a habit of reading it on startup. This is
the foundation of <a href="https://munderdiffl.in/#how">agent long-term memory</a> in general.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/give-claude-code-long-term-memory/note-1.png" alt="Hand-drawn sketch from “How to Give Claude Code Long-Term Memory”" loading="lazy" decoding="async" /></figure>
<h2 id="step-1-write-durable-facts-to-markdown" tabindex="-1">Step 1: Write durable facts to markdown <a class="anchor" href="#step-1-write-durable-facts-to-markdown" aria-hidden="true">#</a></h2>
<p>Give each agent a <code>memory.md</code> and a rule: when you learn something durable — a decision, a
convention, a gotcha — append it. Keep entries small and atomic:</p>
@@ -186,6 +187,7 @@ from each agent’s markdown notes.</p>
<p>One trap: if several agents write the same memory file at once, you get torn writes. Give each agent
its <strong>own</strong> memory file and let a shared index aggregate them read-only. Same principle that keeps
multi-agent git safe — one writer per file.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/give-claude-code-long-term-memory/note-2.png" alt="Hand-drawn sketch from “How to Give Claude Code Long-Term Memory”" loading="lazy" decoding="async" /></figure>
<h2 id="step-3-make-reading-a-startup-ritual" tabindex="-1">Step 3: Make reading a startup ritual <a class="anchor" href="#step-3-make-reading-a-startup-ritual" aria-hidden="true">#</a></h2>
<p>Memory only helps if it’s read. Bake it into the agent’s startup: “before starting a task, recall
relevant notes; after finishing, append what you learned.” Once that loop is reliable, the briefs you
diff --git a/docs/blog/hire-manifest-untrusted-input/index.html b/docs/blog/hire-manifest-untrusted-input/index.html
index e1ed3dd5..12575015 100644
--- a/docs/blog/hire-manifest-untrusted-input/index.html
+++ b/docs/blog/hire-manifest-untrusted-input/index.html
@@ -185,6 +185,7 @@
<h2 id="no-executable-field" tabindex="-1">No executable field <a class="anchor" href="#no-executable-field" aria-hidden="true">#</a></h2>
<p>The second structural defense is an absence. <strong>There is no <code>command</code> or <code>executable</code> field in the schema.</strong> A manifest cannot name the program that runs. The binary always comes from the user’s <strong>locally configured provider preset</strong> — the <code>claude</code>, <code>agy</code>, or <code>codex</code> you installed and pointed the app at. <code>provider: &quot;custom&quot;</code> is rejected by the validator outright, precisely because a custom provider is a user-side escape hatch for naming an arbitrary binary, and we will not let a downloaded file reach through it.</p>
<p>So the worst a manifest can do on the “what runs” axis is <em>select among providers you already trust</em>. It picks <code>claude</code> or <code>codex</code>; it cannot introduce <code>curl</code> or <code>/bin/sh</code>. That shrinks the attack surface to the <em>arguments</em> passed to a binary you already chose to install — which is exactly where the interesting bug lived.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/hire-manifest-untrusted-input/note-1.png" alt="Hand-drawn sketch from “Treating a Hire Manifest as Untrusted Input”" loading="lazy" decoding="async" /></figure>
<h2 id="the-high-severity-bug-windows-command-injection-via-model" tabindex="-1">The HIGH-severity bug: Windows command injection via <code>model</code> <a class="anchor" href="#the-high-severity-bug-windows-command-injection-via-model" aria-hidden="true">#</a></h2>
<p>The first review found it. <code>commandFlags</code> were validated tightly from day one — but <code>model</code> was only <strong>length-capped</strong>, never <strong>shape-checked</strong>. And <code>model</code> is not inert: it flows onto the spawn command line as <code>--model &lt;model&gt;</code>, quoted only if it contained whitespace.</p>
<p>That “quoted only if it contained whitespace” is the whole bug. Consider this manifest field:</p>
@@ -208,6 +209,7 @@
<span class="token keyword">const</span> <span class="token constant">SAFE_FLAG_NAMES</span> <span class="token operator">=</span> <span class="token keyword">new</span> <span class="token class-name">Set</span><span class="token punctuation">(</span><span class="token punctuation">[</span> <span class="token comment">/* a small, curated set of known-harmless flags */</span> <span class="token punctuation">]</span><span class="token punctuation">)</span><span class="token punctuation">;</span></code></pre>
<p>A token must (a) match <code>FLAG_RE</code> — so no whitespace, no shell metacharacters, no <code>%</code> (which would invite <code>cmd.exe</code> environment expansion) — <strong>and</strong> (b) have a flag name that’s in <code>SAFE_FLAG_NAMES</code>. Nothing system-prompt-related, settings-related, MCP-related, or provider/base-URL-related is ever allowlisted, because those are the flags that change <em>what the agent trusts</em> or <em>where it talks to</em>. And the args, once validated, go to <code>node-pty</code> as an <strong>argv array</strong> — never concatenated into a shell string.</p>
<p>The general principle is worth stating plainly: <strong>for attacker-controlled input, an allowlist beats a denylist.</strong> A denylist is a bet that you enumerated every <em>bad</em> value — and that bet loses every time the world adds a new bad value you didn’t anticipate. An allowlist is a bet that you enumerated every <em>safe</em> value — and the safe set is small, well-understood, and changes slowly. When the input is hostile and the surface keeps growing, you want to be betting on the small stable set, not the unbounded one.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/hire-manifest-untrusted-input/note-2.png" alt="Hand-drawn sketch from “Treating a Hire Manifest as Untrusted Input”" loading="lazy" decoding="async" /></figure>
<h2 id="ssrf-safe-bounded-fetch" tabindex="-1">SSRF-safe, bounded fetch <a class="anchor" href="#ssrf-safe-bounded-fetch" aria-hidden="true">#</a></h2>
<p>The deep link <code>munderdifflin://hire?src=&lt;url&gt;</code> hands the app a URL it will fetch from the <strong>main</strong> process — which has the network and the OS at its disposal. A naive fetch here is a classic server-side request forgery (SSRF) primitive: a remote page tells <em>your</em> app to make a request <em>you</em> didn’t intend. The transport (<code>src/main/hire.ts</code>) is hardened on three axes, each of which started out wrong in the first cut.</p>
<h3 id="https-only-with-a-loopback-carve-out" tabindex="-1">https-only, with a loopback carve-out <a class="anchor" href="#https-only-with-a-loopback-carve-out" aria-hidden="true">#</a></h3>
@@ -311,50 +313,50 @@ for hop in 0..5: // cap at 5 hops
<h2>Related in Internals</h2>
<div class="post-grid">
<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>
+ <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-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
+ <span>4 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>
+ <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/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>
+ <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/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <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-06-05">Jun 5, 2026</time>
+ <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/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
+ <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/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
+ <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>
<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/architecture-two-planes-one-renderer/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/architecture-two-planes-one-renderer/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-04">Jun 4, 2026</time>
+ <time datetime="2026-06-05">Jun 5, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>5 min</span>
</div>
- <h3><a href="/blog/architecture-two-planes-one-renderer/">Munder Difflin&#39;s Architecture: Two Data Planes, One Renderer</a></h3>
- <p class="dek">A walkthrough of the multi-agent harness architecture: a node-pty terminal plane and a hooks/hive event plane feeding one React + Pixi.js renderer.</p>
+ <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
+ <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
<div class="foot">
<span class="tag kind">Internals</span>
- <a class="more" href="/blog/architecture-two-planes-one-renderer/" aria-label="Read: Munder Difflin&#39;s Architecture: Two Data Planes, One Renderer">Read →</a>
+ <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/how-agents-remember-semantic-memory/index.html b/docs/blog/how-agents-remember-semantic-memory/index.html
index 9481b862..c659a2c2 100644
--- a/docs/blog/how-agents-remember-semantic-memory/index.html
+++ b/docs/blog/how-agents-remember-semantic-memory/index.html
@@ -207,6 +207,7 @@ but it ends in an interactive <code>Mine now? [Y/n]</code> prompt that <code>--y
would hang on it indefinitely. The fix in <code>memory.ts</code> is to <strong>skip init entirely</strong> and let the first
<code>mempalace mine</code> lazily create the palace (downloading the local embedding model once, on first run).
One less moving part, and no hang.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-agents-remember-semantic-memory/note-1.png" alt="Hand-drawn sketch from “How AI Agents Remember: Semantic Memory in a Hive”" loading="lazy" decoding="async" /></figure>
<h2 id="recall-search-and-wake-up" tabindex="-1">Recall: <code>search</code> and <code>wake-up</code> <a class="anchor" href="#recall-search-and-wake-up" aria-hidden="true">#</a></h2>
<p>With notes mined, an agent recalls in two ways — both plain CLI calls it runs itself:</p>
<pre class="language-bash"><code class="language-bash">mempalace search <span class="token string">"how do we build the web bundle?"</span> <span class="token parameter variable">--results</span> <span class="token number">5</span>
@@ -235,6 +236,7 @@ markdown — never a single point of failure that takes the memory down with it.
<p>The embedding model is configurable (<code>minilm</code> by default for snappy local recall, <code>embeddinggemma</code>
when you want a heavier multilingual model). Everything runs locally — the palace, the model, the
mining — so memory stays <a href="/blog/why-local-first-matters-for-ai-agents/">local-first</a> and private.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-agents-remember-semantic-memory/note-2.png" alt="Hand-drawn sketch from “How AI Agents Remember: Semantic Memory in a Hive”" loading="lazy" decoding="async" /></figure>
<h2 id="why-this-matters-for-a-hive-not-just-one-agent" tabindex="-1">Why this matters for a hive (not just one agent) <a class="anchor" href="#why-this-matters-for-a-hive-not-just-one-agent" aria-hidden="true">#</a></h2>
<p>A single agent with memory is useful. A <em>hive</em> with shared memory compounds:</p>
<ul>
diff --git a/docs/blog/how-ai-agents-verify-their-own-work/index.html b/docs/blog/how-ai-agents-verify-their-own-work/index.html
index dff7d32c..7375b5cc 100644
--- a/docs/blog/how-ai-agents-verify-their-own-work/index.html
+++ b/docs/blog/how-ai-agents-verify-their-own-work/index.html
@@ -194,6 +194,7 @@ recreate. In a fresh worktree, make the dependencies real <em>before</em> claimi
<span class="token function">npm</span> run typecheck <span class="token comment"># now this is a claim you can stand behind</span>
<span class="token function">npm</span> run build <span class="token comment"># paste the result — green that reproduces is green</span></code></pre>
<p>“It works on my branch” is worthless if your branch is a state no one else can reach.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-ai-agents-verify-their-own-work/note-1.png" alt="Hand-drawn sketch from “How AI Agents Verify Their Own Work (Before Saying 'Done')”" loading="lazy" decoding="async" /></figure>
<h2 id="verify-the-fix-not-the-intent" tabindex="-1">Verify the fix, not the intent <a class="anchor" href="#verify-the-fix-not-the-intent" aria-hidden="true">#</a></h2>
<p>A subtler failure than skipping the check: running a check that doesn’t prove the thing you fixed. You
patched the cause, the code compiles, so you call it done — but you never confirmed the <em>symptom</em> is gone.</p>
@@ -219,6 +220,7 @@ the wrong file, ran in a dirty environment, misread output). In practice it look
naturally with <a href="/blog/human-in-the-loop-ai-agents/">human-in-the-loop gates</a>: the agent verifies, a peer
re-verifies, and the human approves what’s hard to reverse. Each layer assumes the one before it can be
wrong — which is why the chain holds.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-ai-agents-verify-their-own-work/note-2.png" alt="Hand-drawn sketch from “How AI Agents Verify Their Own Work (Before Saying 'Done')”" loading="lazy" decoding="async" /></figure>
<h2 id="a-self-verification-checklist" tabindex="-1">A self-verification checklist <a class="anchor" href="#a-self-verification-checklist" aria-hidden="true">#</a></h2>
<p>Before an agent writes “done,” it should answer yes to all of these:</p>
<ul>
diff --git a/docs/blog/how-ai-answer-engines-choose-sources/index.html b/docs/blog/how-ai-answer-engines-choose-sources/index.html
index 06cb38c5..7f53972e 100644
--- a/docs/blog/how-ai-answer-engines-choose-sources/index.html
+++ b/docs/blog/how-ai-answer-engines-choose-sources/index.html
@@ -181,6 +181,7 @@ authority</strong>. The unit that wins isn’t the page — it’s the quotable,
lifted a source’s visibility in AI answers by <a href="https://aithinkerlab.com/generative-engine-optimization-2026/">up to roughly 40%</a> —
with the biggest gains from <strong>adding statistics, citing sources, and including quotations</strong>. In other
words: specific, verifiable, quotable content is what gets pulled into answers.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-ai-answer-engines-choose-sources/note-1.png" alt="Hand-drawn sketch from “How AI Answer Engines Choose What to Cite”" loading="lazy" decoding="async" /></figure>
<h2 id="the-engines-dont-agree-a-per-engine-tour" tabindex="-1">The engines don’t agree — a per-engine tour <a class="anchor" href="#the-engines-dont-agree-a-per-engine-tour" aria-hidden="true">#</a></h2>
<p>Here’s the part most “AI SEO” advice glosses over: the major engines cite <em>strikingly different</em>
sources. Reported analyses (notably the <a href="https://www.prnewswire.com/news-releases/5w-releases-ai-platform-citation-source-index-2026-the-50-websites-that-now-decide-what-brands-are-visible-inside-chatgpt-claude-perplexity-gemini-and-google-ai-overviews-302759804.html">5W AI Platform Citation Source Index 2026</a>
@@ -217,6 +218,7 @@ parse what your content <em>is</em> — and Google AI Overviews weight it especi
</ul>
<p>None of this replaces good SEO — crawlable, fast, well-structured pages still matter. It layers a
second discipline on top, aimed at the quotable claim instead of the click.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-ai-answer-engines-choose-sources/note-2.png" alt="Hand-drawn sketch from “How AI Answer Engines Choose What to Cite”" loading="lazy" decoding="async" /></figure>
<h2 id="how-to-know-if-its-working" tabindex="-1">How to know if it’s working <a class="anchor" href="#how-to-know-if-its-working" aria-hidden="true">#</a></h2>
<p>AEO has no clean “position 3” metric, so measure it directly: each month, ask ChatGPT, Claude, and
Perplexity the questions your audience would ask, and check whether you’re named — and whether the
diff --git a/docs/blog/how-the-god-orchestrator-works/index.html b/docs/blog/how-the-god-orchestrator-works/index.html
index 94538bc3..42d1a389 100644
--- a/docs/blog/how-the-god-orchestrator-works/index.html
+++ b/docs/blog/how-the-god-orchestrator-works/index.html
@@ -207,6 +207,7 @@ the <strong>speech act</strong> — each message declares its intent:</p>
<p>The harness fills in the id, sender, hop count, and timestamps. A good task spec means the worker can
start without a follow-up question — which is the difference between routing that accelerates the team
and routing that just adds a hop.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-the-god-orchestrator-works/note-1.png" alt="Hand-drawn sketch from “Inside the GOD Orchestrator: Routing, Adjudication, Escalation”" loading="lazy" decoding="async" /></figure>
<h2 id="job-3-adjudicate-the-routine-traffic" tabindex="-1">Job 3 — Adjudicate the routine traffic <a class="anchor" href="#job-3-adjudicate-the-routine-traffic" aria-hidden="true">#</a></h2>
<p>This is the job that makes autonomy real. As agents work, they raise questions <em>for each other</em>: which
schema to validate against, whether a staging URL is current, a small change to the plan. If every one
@@ -259,6 +260,7 @@ moving.</li>
<li>Every step is committed to the hive’s git repo and written to an append-only log, so the whole
episode is auditable and replayable.</li>
</ol>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-the-god-orchestrator-works/note-2.png" alt="Hand-drawn sketch from “Inside the GOD Orchestrator: Routing, Adjudication, Escalation”" loading="lazy" decoding="async" /></figure>
<h2 id="what-makes-it-robust" tabindex="-1">What makes it robust <a class="anchor" href="#what-makes-it-robust" aria-hidden="true">#</a></h2>
<p>A few properties keep the orchestrator from being a single point of failure:</p>
<ul>
diff --git a/docs/blog/how-to-add-a-github-copilot-cli-agent/index.html b/docs/blog/how-to-add-a-github-copilot-cli-agent/index.html
index dfe28ce9..8d0bca13 100644
--- a/docs/blog/how-to-add-a-github-copilot-cli-agent/index.html
+++ b/docs/blog/how-to-add-a-github-copilot-cli-agent/index.html
@@ -170,6 +170,7 @@
<pre class="language-bash"><code class="language-bash"><span class="token function">npm</span> <span class="token function">install</span> <span class="token parameter variable">-g</span> @github/copilot</code></pre>
<p>Then log in once with your GitHub account if you haven’t (<code>copilot</code> walks you through it on first run). That’s the entire auth story: <strong>the engine uses your existing GitHub Copilot login, no new keys</strong>, nothing to paste into Settings → AI Engines.</p>
<p>You can also skip this step entirely. Munder Difflin has a self-healing installer for missing engine CLIs: if you pick Copilot in Add Agent and the <code>copilot</code> binary isn’t on your <code>PATH</code>, the harness offers the official <code>npm install -g @github/copilot</code>, runs it in the terminal, then auto restarts-and-continues into the freshly installed binary. No dead end, no manual retry.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-add-a-github-copilot-cli-agent/note-1.png" alt="Hand-drawn sketch from “How to Add a GitHub Copilot CLI Agent to Your Floor”" loading="lazy" decoding="async" /></figure>
<h2 id="step-2-add-agent-pick-copilot" tabindex="-1">Step 2: Add Agent, pick Copilot <a class="anchor" href="#step-2-add-agent-pick-copilot" aria-hidden="true">#</a></h2>
<p>Click <strong>Add Agent</strong> on the floor. The visual provider picker now lists GitHub Copilot CLI alongside the other six engines. Pick it, name your hire, choose a working directory — and if you flip the git-isolation toggle, the agent gets its own dedicated worktree so it never collides with other agents on branches (more on why that matters in <a href="/blog/claude-code-git-worktrees-vs-hive/">worktrees vs the hive</a>).</p>
<p>Here’s the whole hire flow in nineteen seconds:</p>
@@ -190,6 +191,7 @@
<pre class="language-bash"><code class="language-bash">copilot <span class="token parameter variable">-p</span> <span class="token string">"&lt;prompt>"</span> <span class="token parameter variable">-s</span> --allow-all-tools --no-ask-user <span class="token punctuation">[</span>--model <span class="token operator">&lt;</span>id<span class="token operator">></span><span class="token punctuation">]</span></code></pre>
<p>The auto-approval flags — <code>-s --allow-all-tools --no-ask-user</code> — are <strong>gated by the floor’s auto-mode toggle</strong>, exactly like every other engine. Auto-mode on: Copilot gets its documented allow-all flags and works without stopping to ask permission per tool call. Auto-mode off: the flags are omitted and the agent runs conservatively. The floor-level guardrails — <a href="/blog/human-in-the-loop-approving-ai-agents/">the approvals queue</a>, budgets, the circuit breaker — sit above all of that regardless of engine.</p>
<p>Session continuity is handled with <code>--resume</code> (best-effort): print mode exits after every turn, but the next turn reattaches the prior session, so follow-ups don’t start cold.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-add-a-github-copilot-cli-agent/note-2.png" alt="Hand-drawn sketch from “How to Add a GitHub Copilot CLI Agent to Your Floor”" loading="lazy" decoding="async" /></figure>
<h2 id="the-honest-inbox-caveat" tabindex="-1">The honest inbox caveat <a class="anchor" href="#the-honest-inbox-caveat" aria-hidden="true">#</a></h2>
<p>This is the part worth reading twice. Print mode <strong>exits per turn and exposes no hook bridge</strong>, which means a Copilot worker can’t do the thing hive-aware engines do: sit idle, notice mail in its inbox, and drain it. The engine is registered as non-hive-aware (<code>canReceiveInbox: false</code>) on purpose.</p>
<p>So what happens when another agent routes a message to your Copilot worker? It <strong>bounces to the GOD orchestrator</strong> instead of silently dropping. Michael sees the bounced mail and handles or re-routes it — the message survives, it just doesn’t land in a mailbox nobody is checking. (If you’re new to how Michael adjudicates traffic, <a href="/blog/how-the-god-orchestrator-works/">the GOD orchestrator post</a> explains the routing model.)</p>
diff --git a/docs/blog/how-to-choose-a-multi-agent-tool/index.html b/docs/blog/how-to-choose-a-multi-agent-tool/index.html
index 2bd02789..607f77f3 100644
--- a/docs/blog/how-to-choose-a-multi-agent-tool/index.html
+++ b/docs/blog/how-to-choose-a-multi-agent-tool/index.html
@@ -163,6 +163,7 @@ orchestrator.</li>
</ul>
<p>If you’re in the first camp, optimize for simplicity. If you’re in the second, the checklist below
will steer you toward heavier, more coordinated tools — and that’s correct.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-choose-a-multi-agent-tool/note-1.png" alt="Hand-drawn sketch from “How to Choose a Multi-Agent Coding Tool: A Buyer's Checklist”" loading="lazy" decoding="async" /></figure>
<h2 id="the-six-criteria" tabindex="-1">The six criteria <a class="anchor" href="#the-six-criteria" aria-hidden="true">#</a></h2>
<h3 id="1-memory" tabindex="-1">1. Memory <a class="anchor" href="#1-memory" aria-hidden="true">#</a></h3>
<p>Does the tool give agents a shared, durable <a href="/blog/give-claude-code-long-term-memory/">long-term
@@ -256,6 +257,7 @@ Multiply, sum, compare. A worked example for a team whose bottleneck is coordina
manager wins handily — that’s the point. The rubric encodes <em>your</em> priorities, so it gives <em>your</em>
answer. For a ready-made criteria breakdown across the real tools, see <a href="/blog/claude-code-orchestration-tools-compared/">Claude Code orchestration
tools, compared</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-choose-a-multi-agent-tool/note-2.png" alt="Hand-drawn sketch from “How to Choose a Multi-Agent Coding Tool: A Buyer's Checklist”" loading="lazy" decoding="async" /></figure>
<h2 id="three-traps-to-avoid" tabindex="-1">Three traps to avoid <a class="anchor" href="#three-traps-to-avoid" aria-hidden="true">#</a></h2>
<ul>
<li><strong>Buying for a workload you don’t have.</strong> A coordinated hive is overkill for two independent tasks;
diff --git a/docs/blog/how-to-hire-from-the-agent-gallery/index.html b/docs/blog/how-to-hire-from-the-agent-gallery/index.html
index 0ba1140f..bddd3060 100644
--- a/docs/blog/how-to-hire-from-the-agent-gallery/index.html
+++ b/docs/blog/how-to-hire-from-the-agent-gallery/index.html
@@ -166,6 +166,7 @@
<h2 id="step-1-browse-the-gallery" tabindex="-1">Step 1: Browse the gallery <a class="anchor" href="#step-1-browse-the-gallery" aria-hidden="true">#</a></h2>
<p>The gallery lives at <a href="https://munderdiffl.in/hires/">munderdiffl.in/hires</a> — a static page, no login, no trackers. It’s stocked with <strong>six off-the-shelf hires</strong>, each a complete role: a PR reviewer, a docs writer, a QA enforcer, a security auditor, a token-spend auditor, and a migrations grinder, each fronted by a pixel avatar from the app’s affectionate Office parody cast.</p>
<p>Every card tells you what you’re getting before you click anything: the role’s goal, its capability tags, and which provider it’s written for. Don’t overthink the choice — you’re picking a starting point, not signing a contract. Everything on the card is editable after import.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-hire-from-the-agent-gallery/note-1.png" alt="Hand-drawn sketch from “How to Hire From the Agent Gallery”" loading="lazy" decoding="async" /></figure>
<h2 id="step-2-import-the-hire" tabindex="-1">Step 2: Import the hire <a class="anchor" href="#step-2-import-the-hire" aria-hidden="true">#</a></h2>
<p>Two ways in, both landing in the same place:</p>
<ul>
@@ -181,6 +182,7 @@
<li><strong>Model and flags</strong> tell you what it costs to run and how it behaves. The allowlist keeps flags safe; it doesn’t make them right for you.</li>
<li><strong>Token budget</strong> is the spend ceiling the author suggested. Set it to what <em>you</em> are comfortable with — the harness enforces per-agent budgets with live fleet monitoring and a circuit breaker behind it.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-hire-from-the-agent-gallery/note-2.png" alt="Hand-drawn sketch from “How to Hire From the Agent Gallery”" loading="lazy" decoding="async" /></figure>
<h2 id="step-4-customize-the-four-things-that-matter" tabindex="-1">Step 4: Customize the four things that matter <a class="anchor" href="#step-4-customize-the-four-things-that-matter" aria-hidden="true">#</a></h2>
<p>A gallery hire is deliberately generic. Four edits turn it into <em>your</em> hire:</p>
<p><strong>Identity.</strong> Rename it and pick the avatar you want to see walking the floor. This sounds cosmetic; it isn’t. When six agents are working at once, you triage by face and name.</p>
diff --git a/docs/blog/how-to-install-and-use-munder-difflin/index.html b/docs/blog/how-to-install-and-use-munder-difflin/index.html
index f0b10903..78dfd466 100644
--- a/docs/blog/how-to-install-and-use-munder-difflin/index.html
+++ b/docs/blog/how-to-install-and-use-munder-difflin/index.html
@@ -243,6 +243,7 @@ adding your main project now saves a step.</li>
</ol>
<p>Finish the wizard and you land on the office floor. Michael — your orchestrator — boots into his
office automatically; give him a few seconds to clock in.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-install-and-use-munder-difflin/note-1.png" alt="Hand-drawn sketch from “How to Install and Use Munder Difflin”" loading="lazy" decoding="async" /></figure>
<h2 id="step-4-meet-michael-your-god-orchestrator" tabindex="-1">Step 4: Meet Michael, your GOD orchestrator <a class="anchor" href="#step-4-meet-michael-your-god-orchestrator" aria-hidden="true">#</a></h2>
<p>Michael is the <strong>GOD agent</strong>: he runs the floor, triages requests, assigns work, and escalates only
the critical calls to you. He’s the agent you talk to.</p>
@@ -311,6 +312,7 @@ you’re back; the GOD agent only interrupts you for the critical calls.</li>
the practical guardrails behind it are in <a href="/blog/claude-code-automation-while-you-sleep/">Claude Code automation while you
sleep</a>. Be honest with yourself about scope — bounded,
well-specified jobs go best.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-install-and-use-munder-difflin/note-2.png" alt="Hand-drawn sketch from “How to Install and Use Munder Difflin”" loading="lazy" decoding="async" /></figure>
<h2 id="step-8-use-michaels-command-center" tabindex="-1">Step 8: Use Michael’s Command Center <a class="anchor" href="#step-8-use-michaels-command-center" aria-hidden="true">#</a></h2>
<p>Select Michael on the floor and open his panel — it’s not a plain terminal. It’s a control surface
with six tabs:</p>
diff --git a/docs/blog/how-to-run-multiple-claude-code-agents/index.html b/docs/blog/how-to-run-multiple-claude-code-agents/index.html
index cb98f4fb..cd3a44f6 100644
--- a/docs/blog/how-to-run-multiple-claude-code-agents/index.html
+++ b/docs/blog/how-to-run-multiple-claude-code-agents/index.html
@@ -163,6 +163,7 @@ one per task:</p>
<span class="token comment"># terminal 3 — the refactorer</span>
<span class="token builtin class-name">cd</span> ~/project <span class="token operator">&amp;&amp;</span> claude</code></pre>
<p>This works for two or three <strong>independent</strong> tasks. The moment they overlap, three problems appear.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-run-multiple-claude-code-agents/note-1.png" alt="Hand-drawn sketch from “How to Run Multiple Claude Code Agents (Without Losing Track)”" loading="lazy" decoding="async" /></figure>
<h2 id="where-the-manual-approach-breaks" tabindex="-1">Where the manual approach breaks <a class="anchor" href="#where-the-manual-approach-breaks" aria-hidden="true">#</a></h2>
<h3 id="1-they-collide-on-files" tabindex="-1">1. They collide on files <a class="anchor" href="#1-they-collide-on-files" aria-hidden="true">#</a></h3>
<p>Two agents editing the same file race each other; in a git repo you get <code>index.lock</code> errors and
@@ -192,6 +193,7 @@ it in plain language and it assigns the agents.</p>
<p>Seeing the team work — who’s busy, who’s idle, what messages are flying — turns a black box into
something you can supervise. Visibility is what makes running many agents feel calm instead of
chaotic.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-run-multiple-claude-code-agents/note-2.png" alt="Hand-drawn sketch from “How to Run Multiple Claude Code Agents (Without Losing Track)”" loading="lazy" decoding="async" /></figure>
<h2 id="from-tabs-to-a-team" tabindex="-1">From tabs to a team <a class="anchor" href="#from-tabs-to-a-team" aria-hidden="true">#</a></h2>
<p>The progression is always the same: one session → a few manual tabs → a coordinated team. Once you
hit the tab-juggling stage, a harness automates exactly the three habits above so you stop being the
diff --git a/docs/blog/how-to-talk-to-your-orchestrator/index.html b/docs/blog/how-to-talk-to-your-orchestrator/index.html
index 248f0cda..0fbc9573 100644
--- a/docs/blog/how-to-talk-to-your-orchestrator/index.html
+++ b/docs/blog/how-to-talk-to-your-orchestrator/index.html
@@ -175,6 +175,7 @@
<p><strong>2. The constraints.</strong> What must not change, where the work lives, what conventions apply. Which repo (the floor works over your registered repos), which directories are off-limits, “follow the existing design tokens,” “don’t touch the migration history.” Constraints are cheap to write and expensive to omit — this is <a href="/blog/context-engineering-for-ai-agents/">context engineering</a> at the human layer.</p>
<p><strong>3. The budget.</strong> Munder Difflin supports per-agent token budgets with live fleet monitoring, backed by a circuit breaker that nudges, constrains, then stops runaways. Say what the work is worth: “keep this under N tokens total” or “this is an overnight job, not a sprint.” A budget in the brief becomes a budget on the floor.</p>
<p><strong>4. The deliverable.</strong> Name the artifact that proves completion: a PR against main, a green test suite, a markdown report, a rendered page. “Done” without an artifact is a vibe; agents ship vibes enthusiastically.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-talk-to-your-orchestrator/note-1.png" alt="Hand-drawn sketch from “How to Brief Your Orchestrator (So the Floor Actually Ships)”" loading="lazy" decoding="async" /></figure>
<h2 id="bad-brief-good-brief" tabindex="-1">Bad brief, good brief <a class="anchor" href="#bad-brief-good-brief" aria-hidden="true">#</a></h2>
<p><strong>Bad:</strong> “Fix the login bug.”
No goal state, no repro, no deliverable. Michael will staff <em>something</em>, and you’ll spend the review round discovering what he guessed.</p>
@@ -185,6 +186,7 @@ Three goals in a trench coat. Split them — the task board handles dependencies
<p>That last sentence is the pro move: telling the orchestrator what to do with <em>adjacent</em> discoveries, so scope stays fixed without discoveries getting lost.</p>
<h2 id="let-it-staff" tabindex="-1">Let it staff <a class="anchor" href="#let-it-staff" aria-hidden="true">#</a></h2>
<p>Don’t specify which agent does what unless you have a real reason. Michael assigns work across the roster, and each hire can run a different engine — Claude Code, Codex, Antigravity, OpenCode, Crush, pi.dev, or GitHub Copilot CLI — so routing is part of the value. If you <em>do</em> care (“use the cheap local-model worker for the boilerplate”), say it as a constraint, not by micromanaging assignments.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-talk-to-your-orchestrator/note-2.png" alt="Hand-drawn sketch from “How to Brief Your Orchestrator (So the Floor Actually Ships)”" loading="lazy" decoding="async" /></figure>
<h2 id="mid-run-steering-status-approvals" tabindex="-1">Mid-run: steering, status, approvals <a class="anchor" href="#mid-run-steering-status-approvals" aria-hidden="true">#</a></h2>
<p>A brief is not a launch-and-pray. Three controls matter while the floor runs:</p>
<p><strong>Steering.</strong> Munder Difflin has a mid-run steer and a graceful stop driven through Claude Code hook returns — you redirect an agent without killing its session. You can also type into any agent’s terminal directly, or message Michael to re-plan: “drop the docs task, the API changed.”</p>
diff --git a/docs/blog/how-to-use-the-built-in-monaco-ide/index.html b/docs/blog/how-to-use-the-built-in-monaco-ide/index.html
index a81c23ae..c923748b 100644
--- a/docs/blog/how-to-use-the-built-in-monaco-ide/index.html
+++ b/docs/blog/how-to-use-the-built-in-monaco-ide/index.html
@@ -169,6 +169,7 @@
<p>The left rail has two jobs, in priority order.</p>
<p><strong>The git CHANGES list</strong> is the headline. It shows every file with uncommitted changes in the workspace. Click one and you get a <strong>read-only side-by-side diff against HEAD</strong> — the agent’s version on one side, what was committed before on the other. This is the “what did my agent actually do” view, and it’s deliberately read-only: a diff is for reading, not for accidentally editing the wrong pane.</p>
<p><strong>The workspace file tree</strong> sits alongside it. Click any file there and it opens as a normal, <em>editable</em> Monaco tab. So the rail gives you both motions: <em>review</em> (CHANGES → diff) and <em>fix</em> (tree → edit).</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-use-the-built-in-monaco-ide/note-1.png" alt="Hand-drawn sketch from “How to Use the Built-in Monaco IDE”" loading="lazy" decoding="async" /></figure>
<h2 id="tabs-dirty-dots-and-cmdctrls" tabindex="-1">Tabs, dirty dots, and Cmd/Ctrl+S <a class="anchor" href="#tabs-dirty-dots-and-cmdctrls" aria-hidden="true">#</a></h2>
<p>Open files stack up as <strong>editor tabs</strong> on the right, each with a <strong>dirty-state dot</strong> when it has unsaved edits, plus save and close. <strong>Cmd/Ctrl+S</strong> saves the active tab.</p>
<p>One hardening detail worth knowing because it’s the kind of thing that silently eats work in lesser editors: saves are protected against the in-flight race. If you keep typing while a save is still writing to disk, those keystrokes are <strong>not</strong> dropped when the save completes. v0.3.3 fixed this explicitly.</p>
@@ -180,6 +181,7 @@
<li>otherwise the <strong>first agent’s</strong> cwd.</li>
</ol>
<p>Practical consequence: <strong>select the agent whose work you want to review, then click IDE.</strong> That drops you straight into its directory — which matters on a floor where <a href="/blog/claude-code-git-worktrees-vs-hive/">each agent can run in its own isolated git worktree</a>, so “the repo” isn’t one place.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/how-to-use-the-built-in-monaco-ide/note-2.png" alt="Hand-drawn sketch from “How to Use the Built-in Monaco IDE”" loading="lazy" decoding="async" /></figure>
<h2 id="the-security-posture-the-renderer-never-touches-disk" tabindex="-1">The security posture: the renderer never touches disk <a class="anchor" href="#the-security-posture-the-renderer-never-touches-disk" aria-hidden="true">#</a></h2>
<p>Everything the IDE does — listing the tree, reading files, writing saves, computing diffs — is <strong>brokered through main-process IPC</strong>. The diff view rides a <code>git:diff</code> IPC channel plus the preload bridge; the renderer process holds no filesystem or git access of its own. That’s the same architecture as the rest of the harness: the sandboxed renderer asks, the main process does, and the attack surface of “web content with disk access” simply doesn’t exist here.</p>
<h2 id="the-workflow-its-built-for-finish-diff-tweak-approve" tabindex="-1">The workflow it’s built for: finish → diff → tweak → approve <a class="anchor" href="#the-workflow-its-built-for-finish-diff-tweak-approve" aria-hidden="true">#</a></h2>
diff --git a/docs/blog/human-in-the-loop-ai-agents/index.html b/docs/blog/human-in-the-loop-ai-agents/index.html
index 770b6b42..cd5ca9c2 100644
--- a/docs/blog/human-in-the-loop-ai-agents/index.html
+++ b/docs/blog/human-in-the-loop-ai-agents/index.html
@@ -187,6 +187,7 @@ escalates to a human; everything else the agents handle. A solid default:</p>
interruptions? Tighten the list. Agents doing things that scare you? Loosen what they’re allowed to
decide alone. In a hive, this policy lives in the <a href="/blog/how-the-god-orchestrator-works/">orchestrator’s</a>
instructions — so you adjust behavior by editing a prompt, not by shipping code.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/human-in-the-loop-ai-agents/note-1.png" alt="Hand-drawn sketch from “Human-in-the-Loop AI Agents: Approvals That Don't Slow You Down”" loading="lazy" decoding="async" /></figure>
<h2 id="how-escalation-actually-works" tabindex="-1">How escalation actually works <a class="anchor" href="#how-escalation-actually-works" aria-hidden="true">#</a></h2>
<p>When an agent (or the orchestrator on its behalf) hits something critical, it doesn’t act. It addresses
a message to the human — or flags the item as needing human attention — and the coordinating process
@@ -217,6 +218,7 @@ better failure mode than “guess.”</li>
</ul>
<p>These mean the queue catches the things that <em>should</em> reach you even when the agents don’t explicitly
flag them.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/human-in-the-loop-ai-agents/note-2.png" alt="Hand-drawn sketch from “Human-in-the-Loop AI Agents: Approvals That Don't Slow You Down”" loading="lazy" decoding="async" /></figure>
<h2 id="why-this-beats-approve-everything-and-approve-nothing" tabindex="-1">Why this beats “approve everything” and “approve nothing” <a class="anchor" href="#why-this-beats-approve-everything-and-approve-nothing" aria-hidden="true">#</a></h2>
<ul>
<li><strong>vs. approve everything:</strong> you keep autonomy and your attention. The agents do the 95% that’s
diff --git a/docs/blog/human-in-the-loop-approving-ai-agents/index.html b/docs/blog/human-in-the-loop-approving-ai-agents/index.html
index 1288fe29..9c9f62ab 100644
--- a/docs/blog/human-in-the-loop-approving-ai-agents/index.html
+++ b/docs/blog/human-in-the-loop-approving-ai-agents/index.html
@@ -187,6 +187,7 @@ an approval re-routed the message back into the queue. The
<a href="https://github.com/chaitanyagiri/munder-difflin/blob/main/CHANGELOG.md">v0.1.7 release</a> notes it plainly:
“Moving to native HITL removes the panel and the bug.” Deleting the abstraction deleted the class of bug
with it.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/human-in-the-loop-approving-ai-agents/note-1.png" alt="Hand-drawn sketch from “Approving AI Agents: Human-in-the-Loop Without a Queue”" loading="lazy" decoding="async" /></figure>
<h2 id="the-native-approach-approve-where-the-work-happens" tabindex="-1">The native approach: approve where the work happens <a class="anchor" href="#the-native-approach-approve-where-the-work-happens" aria-hidden="true">#</a></h2>
<p>Here’s the shift. Coding agents <em>already have</em> a human-in-the-loop mechanism — the <strong>permission prompt</strong>.
Claude Code pauses before a sensitive tool call and asks, right there in the agent’s own terminal. That
@@ -217,6 +218,7 @@ critical calls. A <code>needsHuman</code> flag still rides along, but it’s <st
envelope on the office-floor visualization. As the code comments note, it’s “Cosmetic only — no queue
behind it.” The system even guards against a <code>god → &quot;human&quot;</code> message looping back to itself. One
recipient, one source of truth, no parallel inbox to babysit.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/human-in-the-loop-approving-ai-agents/note-2.png" alt="Hand-drawn sketch from “Approving AI Agents: Human-in-the-Loop Without a Queue”" loading="lazy" decoding="async" /></figure>
<h2 id="approve-from-anywhere" tabindex="-1">Approve from anywhere <a class="anchor" href="#approve-from-anywhere" aria-hidden="true">#</a></h2>
<p>A nice property falls out of doing it this way: because approval rides on the native session prompt,
<strong>you can approve from wherever you can reach the session.</strong> Munder Difflin’s <code>/remote-control</code> lets the
diff --git a/docs/blog/index.html b/docs/blog/index.html
index b2679738..02a6a3be 100644
--- a/docs/blog/index.html
+++ b/docs/blog/index.html
@@ -107,29 +107,195 @@
building a self-coordinating hive of agents with a GOD orchestrator you talk to.</p>
<div class="filters" role="navigation" aria-label="Topics">
- <a class="chip" aria-current="page">All<span class="ct">119</span></a>
+ <a class="chip" aria-current="page">All<span class="ct">129</span></a>
<a class="chip" href="/blog/topics/guides/">guides<span class="ct">34</span></a>
<a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
</div>
</header>
-<div class="wrap featured"><article class="card t-story">
+<div class="wrap featured"><article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+
+</div>
+
+
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">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-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/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>3 min</span>
+ </div>
+ <h3><a href="/blog/what-reddit-told-us-about-munder-difflin/">What 516 Reddit Comments Told Us About Munder Difflin</a></h3>
+ <p class="dek">We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-label="Read: What 516 Reddit Comments Told Us About Munder Difflin">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
<a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
@@ -145,13 +311,7 @@
</div>
</div>
</article>
-
-</div>
-
-
-<section class="wrap">
- <div class="post-grid">
- <article class="card t-internals">
+<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">
@@ -685,7 +845,7 @@
<div class="meta">
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>7 min</span>
</div>
<h3><a href="/blog/launching-munder-difflin-v0-2-4/">Launching Munder Difflin v0.2.4</a></h3>
<p class="dek">Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</p>
diff --git a/docs/blog/keep-agent-semantic-memory-clean/index.html b/docs/blog/keep-agent-semantic-memory-clean/index.html
index 80f7b931..600abe22 100644
--- a/docs/blog/keep-agent-semantic-memory-clean/index.html
+++ b/docs/blog/keep-agent-semantic-memory-clean/index.html
@@ -186,6 +186,7 @@ memories in ~600–900 tokens — its “what do I already know” digest.</p>
<p>The “essential story” was almost entirely a hooks configuration file, repeated across agents, with the
occasional real note wedged between the blobs. The most important context an agent could load was
being spent on JSON it would never need to recall.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/keep-agent-semantic-memory-clean/note-1.png" alt="Hand-drawn sketch from “Keep Your Agent's Semantic Memory Clean: Don't Index the Config”" loading="lazy" decoding="async" /></figure>
<h2 id="the-cause-the-index-ate-the-whole-directory" tabindex="-1">The cause: the index ate the whole directory <a class="anchor" href="#the-cause-the-index-ate-the-whole-directory" aria-hidden="true">#</a></h2>
<p>The miner does what most file-based indexers do — it walks the target directory and files every file it
finds. But an agent’s folder isn’t just <code>memory.md</code>. It also holds:</p>
@@ -218,6 +219,7 @@ rewrites a file that’s already correct, so it’s safe to call every cycle.</p
it.</strong> A <code>.gitignore</code> is a readable, version-controlled declaration of “these files are operational, not
knowledge.” That’s better than burying an exclude list inside the miner, where the next person has to go
read source code to find out why their config isn’t showing up in recall.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/keep-agent-semantic-memory-clean/note-2.png" alt="Hand-drawn sketch from “Keep Your Agent's Semantic Memory Clean: Don't Index the Config”" loading="lazy" decoding="async" /></figure>
<h2 id="the-fix-part-two-prune-whats-already-filed" tabindex="-1">The fix, part two: prune what’s already filed <a class="anchor" href="#the-fix-part-two-prune-whats-already-filed" aria-hidden="true">#</a></h2>
<p>Adding a <code>.gitignore</code> stops <em>future</em> noise. It does nothing about the thousands of config drawers
already sitting in the index, because mining is <strong>additive</strong> — it files new content and updates changed
diff --git a/docs/blog/launching-munder-difflin-v0-2-0/index.html b/docs/blog/launching-munder-difflin-v0-2-0/index.html
index 97d60fc0..e1f1ea3c 100644
--- a/docs/blog/launching-munder-difflin-v0-2-0/index.html
+++ b/docs/blog/launching-munder-difflin-v0-2-0/index.html
@@ -203,6 +203,7 @@ long.</li>
</ul>
<p>This is the layer we wrote about wanting in <a href="/blog/observability-for-agent-fleets/">observability for agent fleets</a>:
not a dashboard bolted on the side, but the live state of the team where you’re already looking.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-2-0/note-1.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.2.0”" loading="lazy" decoding="async" /></figure>
<h2 id="and-you-can-stay-in-control-of-it" tabindex="-1">…and you can stay in control of it <a class="anchor" href="#and-you-can-stay-in-control-of-it" aria-hidden="true">#</a></h2>
<p>Seeing is half of it. The other half is being able to <em>act</em> — gently or firmly — without killing everything.</p>
<ul>
@@ -237,6 +238,7 @@ choosing, with a safe move that relocates existing data.</li>
no more re-adding agents one by one. (Thanks @Gulum — #16.)</li>
<li><strong>Delete scheduled missions.</strong> Scheduled missions now have a delete button. (Thanks @Gulum — #9.)</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-2-0/note-2.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.2.0”" loading="lazy" decoding="async" /></figure>
<h2 id="legibility-and-cross-platform-fixes" tabindex="-1">Legibility and cross-platform fixes <a class="anchor" href="#legibility-and-cross-platform-fixes" aria-hidden="true">#</a></h2>
<p>A big chunk of v0.2.0 is the unglamorous, high-impact work of making the thing actually pleasant to read and
reliable to run everywhere — almost all of it community-driven.</p>
@@ -339,50 +341,50 @@ the next release is built the same way this one was.</p>
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/launching-munder-difflin-v0-2-4/index.html b/docs/blog/launching-munder-difflin-v0-2-4/index.html
index 32f740b2..35dbc1d5 100644
--- a/docs/blog/launching-munder-difflin-v0-2-4/index.html
+++ b/docs/blog/launching-munder-difflin-v0-2-4/index.html
@@ -152,7 +152,7 @@
<span class="dot" aria-hidden="true">·</span>
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true">·</span>
- <span>6 min read</span>
+ <span>7 min read</span>
<span class="tag kind">Story</span>
</div>
</header>
@@ -175,6 +175,7 @@
<li><strong>Codex</strong> — your OpenAI subscription. Codex’s coding focus, same hook bridge as everyone else.</li>
</ul>
<p>Drop the CLIs you want on your <code>PATH</code>, add them as workers, done. Mix and match however you like. The hive layer underneath is the same no matter who’s running.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-2-4/note-1.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.2.4”" loading="lazy" decoding="async" /></figure>
<h2 id="the-real-flex-automate-basically-anything-in-one-prompt" tabindex="-1">the real flex: automate basically anything in <em>one prompt</em> <a class="anchor" href="#the-real-flex-automate-basically-anything-in-one-prompt" aria-hidden="true">#</a></h2>
<p>Here’s where it stops being a tech demo and starts being a thing you actually use.</p>
<blockquote>
@@ -213,6 +214,7 @@
<p>This is the one people don’t believe until they see it. When agents are mid-turn and your machine tries to sleep or lock, Munder Difflin holds the line (it blocks app suspension while work is live) so a long mission doesn’t get guillotined the moment your screen dims. Start something big, walk away, come back to it done. <strong>Overnight runs are a feature, not a gamble.</strong></p>
<h3 id="-yes-it-really-looks-like-the-office" tabindex="-1">🏢 yes, it really looks like <em>The Office</em> <a class="anchor" href="#-yes-it-really-looks-like-the-office" aria-hidden="true">#</a></h3>
<p>The whole point of a floor is that you can <em>watch</em> it. Every agent is a real terminal under the hood — <code>claude</code>, <code>agy</code>, or <code>codex</code> — rendered as a little pixel coworker doing its thing. The cast is an affectionate <em>Office</em> parody (Michael runs the floor; the rest of the gang fills the desks), they take coffee breaks when idle, and you can see at a glance who’s working, who’s thinking, and who’s stuck. It’s genuinely fun to leave running on a second monitor. Identity theft is not a joke, Jim.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-2-4/note-2.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.2.4”" loading="lazy" decoding="async" /></figure>
<h2 id="also-new-in-024-the-quiet-reliability-glow-up" tabindex="-1">also new in 0.2.4 (the quiet reliability glow-up) <a class="anchor" href="#also-new-in-024-the-quiet-reliability-glow-up" aria-hidden="true">#</a></h2>
<p>The stuff that doesn’t get a headline but makes the floor feel solid:</p>
<ul>
@@ -220,6 +222,11 @@
<li><strong>God opens to its Terminal by default</strong> — selecting the orchestrator mounts straight to its terminal instead of reopening a stale “ASK ME” tab. (ASK ME is still one click away.)</li>
<li><strong>Tougher public ingress</strong> — the Slack/webhook tunnel no longer crashes at load, and a permanently-failing Slack reply (like a bot token missing a scope) gets logged once instead of retrying forever and spamming your console.</li>
</ul>
+<h2 id="credits" tabindex="-1">credits <a class="anchor" href="#credits" aria-hidden="true">#</a></h2>
+<p>A run of fixes in the 0.2.2 wave that this release builds on came from the community —
+<a href="https://github.com/Gulum">@Gulum</a> landed eight of them, from the Windows usage meter that
+always read $0.00 to un-black-holing mail sent to the prep assistant. First sustained outside
+contributor the project ever had. Thank you.</p>
<h2 id="get-v024" tabindex="-1">get v0.2.4 <a class="anchor" href="#get-v024" aria-hidden="true">#</a></h2>
<p>Munder Difflin is <strong>free, open source, and local-first</strong> on macOS, Windows, and Linux. No account. No cloud. Your machine, your subscriptions, your floor.</p>
<p><a href="https://github.com/chaitanyagiri/munder-difflin/releases/latest"><strong>Download v0.2.4</strong></a> — install the CLIs you want (<code>claude</code>, <code>agy</code>, and/or <code>codex</code>), add them to the floor, and brief your first GOD orchestrator.</p>
@@ -277,7 +284,7 @@
<aside class="toc-rail" aria-label="Table of contents">
<div class="tt">On this page</div>
<ol>
- <li class="lvl-2"><a href="#three-clis-one-hive-zero-second-class-citizens">three CLIs, one hive, zero second-class citizens</a></li><li class="lvl-2"><a href="#the-real-flex-automate-basically-anything-in-one-prompt">the real flex: automate basically anything in one prompt</a></li><li class="lvl-2"><a href="#the-whole-menu-every-feature-no-fluff">the whole menu (every feature, no fluff)</a></li><li class="lvl-3"><a href="#-your-office-reachable-from-your-phone">💬 your office, reachable from your phone</a></li><li class="lvl-3"><a href="#-set-it-and-forget-it">⏰ set it and forget it</a></li><li class="lvl-3"><a href="#-close-the-lid-it-keeps-working">🌙 close the lid, it keeps working</a></li><li class="lvl-3"><a href="#-yes-it-really-looks-like-the-office">🏢 yes, it really looks like The Office</a></li><li class="lvl-2"><a href="#also-new-in-024-the-quiet-reliability-glow-up">also new in 0.2.4 (the quiet reliability glow-up)</a></li><li class="lvl-2"><a href="#get-v024">get v0.2.4</a></li>
+ <li class="lvl-2"><a href="#three-clis-one-hive-zero-second-class-citizens">three CLIs, one hive, zero second-class citizens</a></li><li class="lvl-2"><a href="#the-real-flex-automate-basically-anything-in-one-prompt">the real flex: automate basically anything in one prompt</a></li><li class="lvl-2"><a href="#the-whole-menu-every-feature-no-fluff">the whole menu (every feature, no fluff)</a></li><li class="lvl-3"><a href="#-your-office-reachable-from-your-phone">💬 your office, reachable from your phone</a></li><li class="lvl-3"><a href="#-set-it-and-forget-it">⏰ set it and forget it</a></li><li class="lvl-3"><a href="#-close-the-lid-it-keeps-working">🌙 close the lid, it keeps working</a></li><li class="lvl-3"><a href="#-yes-it-really-looks-like-the-office">🏢 yes, it really looks like The Office</a></li><li class="lvl-2"><a href="#also-new-in-024-the-quiet-reliability-glow-up">also new in 0.2.4 (the quiet reliability glow-up)</a></li><li class="lvl-2"><a href="#credits">credits</a></li><li class="lvl-2"><a href="#get-v024">get v0.2.4</a></li>
</ol>
</aside>
@@ -291,50 +298,50 @@
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/launching-munder-difflin-v0-2-8/index.html b/docs/blog/launching-munder-difflin-v0-2-8/index.html
index 52efbf94..89349d5a 100644
--- a/docs/blog/launching-munder-difflin-v0-2-8/index.html
+++ b/docs/blog/launching-munder-difflin-v0-2-8/index.html
@@ -185,6 +185,7 @@
<h3 id="-the-file-import" tabindex="-1">📁 the file import <a class="anchor" href="#-the-file-import" aria-hidden="true">#</a></h3>
<p>prefer files? there’s an <strong>import hire…</strong> button right inside the Add-Agent modal. point it at a local <code>.hire.json</code> file and it reads it in. same destination: the modal, pre-filled.</p>
<p>both paths converge. link or file, you land in the same review screen.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-2-8/note-1.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.2.8: Shareable Hires”" loading="lazy" decoding="async" /></figure>
<h2 id="the-part-that-matters-import-never-spawns-anything" tabindex="-1">the part that matters: import never spawns anything <a class="anchor" href="#the-part-that-matters-import-never-spawns-anything" aria-hidden="true">#</a></h2>
<p>read this twice, because it’s the whole trust promise:</p>
<blockquote>
@@ -210,6 +211,7 @@
<p><strong>browse → click ⚡hire → review → spawn.</strong></p>
</blockquote>
<p>that’s it. that’s the whole onboarding. instead of “here’s an empty floor, good luck,” it’s “here’s Pam, want her to write your docs? yes? she’s at her desk now.”</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-2-8/note-2.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.2.8: Shareable Hires”" loading="lazy" decoding="async" /></figure>
<h2 id="why-this-is-secretly-a-growth-thing" tabindex="-1">why this is secretly a growth thing <a class="anchor" href="#why-this-is-secretly-a-growth-thing" aria-hidden="true">#</a></h2>
<p>here’s the bit we’re genuinely excited about. the hardest moment in any tool like this is the <strong>first five minutes</strong>. an empty office asks too much of a newcomer.</p>
<p>a hire collapses that. somebody who already runs a great floor can package up their best role and <strong>share the link</strong>. the recipient clicks it, reviews it, spawns it — and now they’ve got a working agent on their <em>first</em> try, before they’ve learned a single thing about orchestrator prompts. then <em>they</em> tweak it, build their own great role, and share <em>that</em>.</p>
@@ -301,50 +303,50 @@
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/launching-munder-difflin-v0-3-0/index.html b/docs/blog/launching-munder-difflin-v0-3-0/index.html
index 23f29154..1609b99d 100644
--- a/docs/blog/launching-munder-difflin-v0-3-0/index.html
+++ b/docs/blog/launching-munder-difflin-v0-3-0/index.html
@@ -184,6 +184,7 @@
<p><strong>secrets are write-only.</strong> you set a credential once. it’s reached only through a loopback broker. it is <em>never read back</em> into the renderer.</p>
</blockquote>
<p>so the UI can let you configure an integration without the secret ever round-tripping through the part of the app that draws windows. and the connectivity-<strong>test</strong> path — the “is this hooked up right?” button — is <strong>confined</strong>, so it can’t be bent into a secret-exfiltration or <a href="/blog/agent-security-and-sandboxing/">SSRF</a> trick. write-only in, brokered access out.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-3-0/note-1.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.3.0: Selectable Engines, Integrations & Slack-Spawned Workers”" loading="lazy" decoding="async" /></figure>
<h2 id="slack-spawn-reply-safe-teardown" tabindex="-1">Slack → spawn → reply → safe teardown <a class="anchor" href="#slack-spawn-reply-safe-teardown" aria-hidden="true">#</a></h2>
<p>the third headline is the one that feels like magic the first time: <strong>Michael can spawn a worker straight from Slack.</strong></p>
<p>here’s the loop. a request lands in Slack. Michael spins up an <strong>isolated, ephemeral worker</strong> to handle it. the worker does the job and <strong>posts its reply back into the thread itself</strong>. then — and this is the whole trick — it gets <strong>torn down safely</strong>.</p>
@@ -205,6 +206,7 @@
<li>🧭 <strong>feature-aware onboarding</strong> — first-run setup adapts to what you actually have available, with an explicit permissions &amp; reliability step.</li>
<li>🔧 <strong>a visible engine-CLI installer</strong> — if the engine binary for your chosen provider is missing, the installer runs <em>visibly</em> and self-heals instead of failing in silence.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-3-0/note-2.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.3.0: Selectable Engines, Integrations & Slack-Spawned Workers”" loading="lazy" decoding="async" /></figure>
<h2 id="reliability-the-floor-survives-a-closed-lid" tabindex="-1">reliability: the floor survives a closed lid <a class="anchor" href="#reliability-the-floor-survives-a-closed-lid" aria-hidden="true">#</a></h2>
<p>if you run agents overnight, two fixes are for you:</p>
<ul>
@@ -293,50 +295,50 @@
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/launching-munder-difflin-v0-3-2/index.html b/docs/blog/launching-munder-difflin-v0-3-2/index.html
index 04f95baa..280f9f0b 100644
--- a/docs/blog/launching-munder-difflin-v0-3-2/index.html
+++ b/docs/blog/launching-munder-difflin-v0-3-2/index.html
@@ -185,6 +185,7 @@
<p>a main-process <strong>completion watcher</strong> notices when the dispatched task actually finishes — the card flips to <em>done</em>, or a done reply lands in the inbox — and <strong>pushes that straight into the live session so Michael speaks it, unprompted</strong>. “Pam finished the changelog.” an on-screen <strong>toast</strong> shows it too, so it’s there whether or not you caught the audio.</p>
<p>and if you’ve already closed the session? the completion isn’t lost. it <strong>queues to a desktop notification</strong>, and the next time you connect, Michael <strong>warm-starts with the completions since you last talked</strong>. there’s also a <code>wait_for</code> tool for when you explicitly want him to block until a specific task lands.</p>
<p>fire-and-forget by default; tell-me-the-second-it’s-done without you asking. that’s the loop.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-3-2/note-1.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator”" loading="lazy" decoding="async" /></figure>
<h2 id="it-stays-on-a-budget" tabindex="-1">it stays on a budget <a class="anchor" href="#it-stays-on-a-budget" aria-hidden="true">#</a></h2>
<p>a live voice session is a meter running. so v0.3.2 keeps it honest:</p>
<ul>
@@ -201,6 +202,7 @@
</blockquote>
<p>the renderer’s content-security policy is opened <em>just</em> enough to let the WebRTC handshake reach <code>api.openai.com</code>, and nothing more. it’s the same write-only-secrets posture the <a href="/blog/launching-munder-difflin-v0-3-0/">integrations broker</a> uses, applied to voice. (local-first people: the audio goes to OpenAI’s Realtime API because that’s what’s doing the speech — everything else stays on your machine. that’s <a href="/blog/why-local-first-matters-for-ai-agents/">why local-first still matters</a> for the rest of the floor.)</p>
<p>the whole loop is <strong>human-verified end-to-end</strong> — connect, mic, answer, <em>and</em> the full spawn / kill / dispatch action path, exercised live on a real key.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-3-2/note-2.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator”" loading="lazy" decoding="async" /></figure>
<h2 id="the-smaller-things-that-add-up" tabindex="-1">the smaller things that add up <a class="anchor" href="#the-smaller-things-that-add-up" aria-hidden="true">#</a></h2>
<p>a release with a headline this big still has a tail of quality-of-life wins:</p>
<ul>
@@ -294,50 +296,50 @@
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/launching-munder-difflin-v0-3-3/index.html b/docs/blog/launching-munder-difflin-v0-3-3/index.html
index b4a9f881..a68092e4 100644
--- a/docs/blog/launching-munder-difflin-v0-3-3/index.html
+++ b/docs/blog/launching-munder-difflin-v0-3-3/index.html
@@ -183,6 +183,7 @@ call goes through the main process over the same audited IPC bridge the rest of
</ul>
<p>The workspace root snapshots from your selected agent (or the orchestrator), so the IDE opens
exactly where the work is happening.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/note-1.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support”" loading="lazy" decoding="async" /></figure>
<h2 id="github-copilot-cli-joins-the-hive" tabindex="-1">GitHub Copilot CLI joins the hive <a class="anchor" href="#github-copilot-cli-joins-the-hive" aria-hidden="true">#</a></h2>
<p>The engine roster grows to <strong>seven</strong>: Claude Code, OpenAI Codex, Antigravity (Gemini), OpenCode,
Crush, pi.dev — and now <strong>GitHub Copilot CLI</strong>.</p>
@@ -211,6 +212,7 @@ from <strong><a href="https://github.com/anxkhn">Anas Khan (@anxkhn)</a></strong
outside the project, complete with a registry test and live verification against the real CLI.
That’s exactly the kind of contribution the preset registry was designed for. Thank you, Anas. If
there’s a CLI agent you want on the floor, <a href="https://github.com/chaitanyagiri/munder-difflin/blob/main/CONTRIBUTING.md">the door is open</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/note-2.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support”" loading="lazy" decoding="async" /></figure>
<h2 id="get-it" tabindex="-1">Get it <a class="anchor" href="#get-it" aria-hidden="true">#</a></h2>
<p><strong><a href="https://github.com/chaitanyagiri/munder-difflin/releases/latest">Download v0.3.3</a></strong> for macOS,
Windows, or Linux — or clone and <code>npm run dev</code>. Free, MIT-licensed, local-first, and everything
@@ -285,50 +287,50 @@ help it reach more people.</p>
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-2/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-2/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-27">Jun 27, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-2/">Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator</a></h3>
- <p class="dek">Munder Difflin v0.3.2 adds Realtime Michael — a low-latency voice channel to the GOD orchestrator. Talk to Michael and he listens, answers, and acts: reading the hive and, behind spoken echo-back confirmation, dispatching, spawning, and steering the floor in real time.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-2/" aria-label="Read: Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/launching-munder-difflin-v0-3-5/index.html b/docs/blog/launching-munder-difflin-v0-3-5/index.html
index ee4c6321..ac432b8c 100644
--- a/docs/blog/launching-munder-difflin-v0-3-5/index.html
+++ b/docs/blog/launching-munder-difflin-v0-3-5/index.html
@@ -200,6 +200,7 @@ renders everywhere</strong>: a live <strong>code | split | preview</strong> swit
any <code>.md</code> path an agent prints in its terminal</strong> to open a rendered preview instantly.
Safe by construction: no raw-HTML pipeline exists, links never navigate the app, and remote
images are blocked by CSP.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/note-1.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself”" loading="lazy" decoding="async" /></figure>
<h2 id="a-queue-you-can-trust-and-escape" tabindex="-1">A queue you can trust — and escape <a class="anchor" href="#a-queue-you-can-trust-and-escape" aria-hidden="true">#</a></h2>
<p>The reliability heart of this wave is Vyapak’s work: <strong>one delivery gate for every
automatic writer</strong>. A single drain loop now owns the “is this terminal free?” decision, and
@@ -225,6 +226,7 @@ compact agent cards, and a <strong>full-app dark mode</strong> (not just the ter
“Restart to update” — installation is always your click. v0.3.5 is the first release
delivered this way; if you’re on 0.3.4, it’s probably already waiting for you.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/note-2.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself”" loading="lazy" decoding="async" /></figure>
<h2 id="where-this-fits" tabindex="-1">Where this fits <a class="anchor" href="#where-this-fits" aria-hidden="true">#</a></h2>
<p>If you’ve seen <a href="https://github.com/yc-software/qm">YC’s qm</a> — a multiplayer agent harness
for teams in Slack and the browser — Munder Difflin is the same idea grown from the other
@@ -305,50 +307,50 @@ to help it reach more people.</p>
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-2/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-2/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-27">Jun 27, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-2/">Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator</a></h3>
- <p class="dek">Munder Difflin v0.3.2 adds Realtime Michael — a low-latency voice channel to the GOD orchestrator. Talk to Michael and he listens, answers, and acts: reading the hive and, behind spoken echo-back confirmation, dispatching, spawning, and steering the floor in real time.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-2/" aria-label="Read: Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/launching-munder-difflin-v0-4-4/index.html b/docs/blog/launching-munder-difflin-v0-4-4/index.html
new file mode 100644
index 00000000..67979568
--- /dev/null
+++ b/docs/blog/launching-munder-difflin-v0-4-4/index.html
@@ -0,0 +1,390 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk — Munder Difflin Blog</title>
+<meta name="description" content="v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes." />
+<link rel="canonical" href="https://munderdiffl.in/blog/launching-munder-difflin-v0-4-4/" />
+
+<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="Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk — Munder Difflin Blog" />
+<meta property="og:description" content="v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes." />
+<meta property="og:url" content="https://munderdiffl.in/blog/launching-munder-difflin-v0-4-4/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Story" />
+<meta property="article:tag" content="Release" />
+<meta property="article:tag" content="Windows" />
+<meta property="article:tag" content="Skills" />
+<meta property="article:tag" content="Open Source" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk — Munder Difflin Blog" />
+<meta name="twitter:description" content="v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk",
+ "description": "v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/launching-munder-difflin-v0-4-4/" },
+ "keywords": "munder difflin v0.4.4, munder difflin release, claude code multi-agent windows, windows ai agents, skills catalog claude code, electron dark mode contrast",
+ "articleSection": "Story",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/launching-munder-difflin-v0-4-4/"
+}
+</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": "Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk", "item": "https://munderdiffl.in/blog/launching-munder-difflin-v0-4-4/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "What's the headline fix in Munder Difflin v0.4.4?", "acceptedAnswer": { "@type": "Answer", "text": "Agent-to-agent messaging now works on Windows. A cmd.exe quirk was silently cutting the hive protocol out of every agent's startup prompt, so Windows agents booted, looked healthy, and had no idea they could message anyone. v0.4.4 launches the real interpreter directly with a proper argument array, so the full protocol arrives intact." } },
+ { "@type": "Question", "name": "What's new besides the fixes?", "acceptedAnswer": { "@type": "Answer", "text": "A browsable catalog of 227 skills you can install across Claude Code, OpenCode and Codex; a Prerequisites page in Settings that shows live status for git, Node, uv, MemPalace and every engine; release notes that can carry their own designed page; an update toast that says what actually changed; and a rebuilt dark mode with readable contrast everywhere." } },
+ { "@type": "Question", "name": "Do I need to do anything to upgrade?", "acceptedAnswer": { "@type": "Answer", "text": "No. The app updates itself from GitHub releases — you'll get a toast that now tells you what's in the update, and installation happens only when you click Restart. Fresh installs additionally benefit from first-run fixes: hive services now start on a brand-new install, and onboarding validates your home folder at step one." } }
+
+ ]
+}
+</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,
+ 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-story">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/story/">Story</a>
+ </nav>
+ <h1>Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</h1>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>4 min read</span>
+ <span class="tag kind">Story</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="Illustration: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk" 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><strong>v0.4.4 is the release where
+Windows stops being a second-class citizen.</strong> Agent-to-agent messaging worked everywhere
+except the platform with roughly half our downloads — a cmd.exe quirk ate the hive protocol
+mid-prompt, silently. That's fixed, along with a first run that never started its own services,
+a setup wizard you couldn't finish, and a dark mode you couldn't read. Plus: a 227-skill catalog,
+a Prerequisites page, and release notes with their own designed pages.</p></div>
+<p>Some releases are about new toys. This one is about a hard truth we learned during
+<a href="/blog/what-reddit-told-us-about-munder-difflin/">launch week</a>: a lot of the people who bounced
+off Munder Difflin weren’t rejecting the idea — they were hitting bugs we couldn’t see from a
+Mac.</p>
+<h2 id="the-windows-bug-that-looked-like-nothing" tabindex="-1">The Windows bug that looked like nothing <a class="anchor" href="#the-windows-bug-that-looked-like-nothing" aria-hidden="true">#</a></h2>
+<p>Here’s the failure that headlines this release. When Munder Difflin spawns an agent, it hands it
+the hive protocol — a multi-line prompt that tells the agent where its <code>inbox/</code> and <code>outbox/</code>
+live, how to message other agents, where its memory is. On Windows, any engine installed as an
+npm <code>.cmd</code> shim can’t go straight to <code>CreateProcess</code>, so it ran via <code>cmd.exe /c &quot;…&quot;</code>. And cmd.exe
+cuts an argument at its first newline.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/note-1.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk”" loading="lazy" decoding="async" /><figcaption>cmd.exe kept the first line of the hive protocol and quietly dropped the rest — inbox, outbox, memory, everything.</figcaption></figure>
+<p>So Windows agents received exactly one line of their job description. They booted, rendered,
+answered prompts, looked completely healthy — and had no idea they could talk to anyone. No
+error, anywhere, because nothing <em>failed</em>. The floor just never came alive.</p>
+<p>v0.4.4 decodes the npm shim and launches its real interpreter with a proper argv array — no
+cmd.exe in the middle, no truncation. A second pass handles OpenCode’s compiled-binary shims,
+which the first fix didn’t model. The full autopsy is in
+<a href="/blog/the-newline-that-silenced-windows-agents/">its own post</a>, because bugs this quiet deserve
+a paper trail.</p>
+<h2 id="first-runs-that-actually-run" tabindex="-1">First runs that actually run <a class="anchor" href="#first-runs-that-actually-run" aria-hidden="true">#</a></h2>
+<p>Three more launch-week wounds, closed:</p>
+<ul>
+<li><strong>A fresh install never started its hive services.</strong> The message router, hook server, and
+mission scheduler all waited for a home folder that a first run doesn’t have yet — and nothing
+re-kicked them once onboarding set one. New installs now bootstrap the moment the home exists.</li>
+<li><strong>The setup wizard could not be finished</strong> if it suggested <code>~/HarnessAgents</code> — the <code>~</code> was
+taken literally and <code>mkdir</code> died. Onboarding now validates the folder at step one instead of
+failing after step four.</li>
+<li><strong>Dark mode was unreadable in a specific, measurable way.</strong> The structural border token
+measured under 2.1:1 contrast against every surface — 187 uses, 93 of them as 1px borders —
+so the whole UI read as flat grey. It’s rebuilt at 3.4–4.0:1 on a warmer ground.</li>
+</ul>
+<p>Did it matter? As of August 19, the share of fresh installs that go on to actually run an
+agent has moved from <strong>50.2% to 57.5%</strong> since these fixes shipped. That’s dozens of people a
+week who used to hit a wall and now hit an office floor.</p>
+<h2 id="the-new-toys-there-are-some" tabindex="-1">The new toys (there are some) <a class="anchor" href="#the-new-toys-there-are-some" aria-hidden="true">#</a></h2>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/note-2.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk”" loading="lazy" decoding="async" /><figcaption>227 skills, searchable and installable across Claude Code, OpenCode and Codex — with scope precedence handled for you.</figcaption></figure>
+<p><strong>Skills.</strong> A browsable catalog of 227 skills with search, category and publisher filters, and
+one-click install across Claude Code, OpenCode and Codex — with scope precedence handled, and
+uninstall guarded so it refuses anything that isn’t a real <code>SKILL.md</code> folder inside a managed
+root. If you’ve read <a href="/blog/mcp-and-skills-in-a-hive/">our take on MCP and skills in a hive</a>,
+this is that opinion, shipped.</p>
+<p><strong>Prerequisites.</strong> A Settings page that answers “why won’t this engine start?” before you ask:
+live status for uv, git, Node, MemPalace and every agent engine, real paths, platform-correct
+install commands — and a button that asks Michael to fill the gaps for you.</p>
+<p><strong>Release drops.</strong> A release can now carry its own authored HTML page, rendered in a fully
+sandboxed iframe. Release notes shouldn’t have to be bullet points forever.</p>
+<p>And smaller things you’ll notice: the update toast now says what’s actually in the update, the
+IDE previews images, fullscreen roster cards show model, project and a context gauge, and Grok
+4.6 joined the model picker.</p>
+<h2 id="credits-where-theyre-due" tabindex="-1">Credits where they’re due <a class="anchor" href="#credits-where-theyre-due" aria-hidden="true">#</a></h2>
+<p>This is the first release where community fixes are a <em>run</em>, not a cameo — and that deserves
+names, not a footnote. <strong><a href="https://github.com/gts-47">@gts-47</a> landed eight pull requests</strong> in
+this release (#129–#134, #143, #144): among them, terminal copy no longer drags the CLI’s quote
+rail along, agent terminals run in UTF-8, task-ledger writes are atomic, and one odd message id
+no longer silences an agent’s wake nudge. <strong><a href="https://github.com/baziyer">@baziyer</a></strong> fixed the
+office floor rendering when nobody’s looking at it (#142) — the politest possible performance
+win.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/note-3.png" alt="Hand-drawn sketch from “Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk”" loading="lazy" decoding="async" /><figcaption>Nine community PRs in one release. Contributors now get the 'employee of the month' role in Discord when their PR lands.</figcaption></figure>
+<p>Contributors now also get something small and silly for it: merge a PR and a workflow hands you
+the <strong>employee of the month</strong> role in <a href="/blog/we-opened-a-discord/">our new Discord</a>. It felt
+thematically required.</p>
+<h2 id="get-it" tabindex="-1">Get it <a class="anchor" href="#get-it" aria-hidden="true">#</a></h2>
+<p>If you’re already on 0.3.5 or later, do nothing — the app will offer the update itself, and the
+toast will tell you exactly what’s inside. Fresh install:
+<a href="https://munderdiffl.in">munderdiffl.in</a>. And if Windows burned you during launch week, this is
+the release that’s owed to you — <a href="https://github.com/chaitanyagiri/munder-difflin/blob/main/CHANGELOG.md">the full changelog</a>
+has every receipt.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">What&#39;s the headline fix in Munder Difflin v0.4.4?</p>
+ <p class="a">Agent-to-agent messaging now works on Windows. A cmd.exe quirk was silently cutting the hive protocol out of every agent&#39;s startup prompt, so Windows agents booted, looked healthy, and had no idea they could message anyone. v0.4.4 launches the real interpreter directly with a proper argument array, so the full protocol arrives intact.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">What&#39;s new besides the fixes?</p>
+ <p class="a">A browsable catalog of 227 skills you can install across Claude Code, OpenCode and Codex; a Prerequisites page in Settings that shows live status for git, Node, uv, MemPalace and every engine; release notes that can carry their own designed page; an update toast that says what actually changed; and a rebuilt dark mode with readable contrast everywhere.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Do I need to do anything to upgrade?</p>
+ <p class="a">No. The app updates itself from GitHub releases — you&#39;ll get a toast that now tells you what&#39;s in the update, and installation happens only when you click Restart. Fresh installs additionally benefit from first-run fixes: hive services now start on a brand-new install, and onboarding validates your home folder at step one.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/story/">Story</a><a class="tag" href="/blog/tags/release/">Release</a><a class="tag" href="/blog/tags/windows/">Windows</a><a class="tag" href="/blog/tags/skills/">Skills</a><a class="tag" href="/blog/tags/open-source/">Open Source</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-windows-bug-that-looked-like-nothing">The Windows bug that looked like nothing</a></li><li class="lvl-2"><a href="#first-runs-that-actually-run">First runs that actually run</a></li><li class="lvl-2"><a href="#the-new-toys-there-are-some">The new toys (there are some)</a></li><li class="lvl-2"><a href="#credits-where-theyre-due">Credits where they’re due</a></li><li class="lvl-2"><a href="#get-it">Get it</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/number-five-on-product-hunt/"><span class="k">← Older</span><span class="t">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</span></a>
+ <a class="pn next" href="/blog/an-agent-redesigned-this-blog/"><span class="k">Newer →</span><span class="t">An Agent Redesigned the Blog You&#39;re Reading</span></a>
+ </div>
+ <section class="related">
+ <h2>Related in Story</h2>
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/local-first-ai-agent-orchestration/index.html b/docs/blog/local-first-ai-agent-orchestration/index.html
index 673e826d..fa38fec9 100644
--- a/docs/blog/local-first-ai-agent-orchestration/index.html
+++ b/docs/blog/local-first-ai-agent-orchestration/index.html
@@ -201,6 +201,7 @@ read the whole exchange back later.</li>
</ul>
<p>It’s the backbone of <a href="/blog/coordinating-ai-coding-agents/">how a hive coordinates its agents</a>, and it
never leaves your disk.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/local-first-ai-agent-orchestration/note-1.png" alt="Hand-drawn sketch from “Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud”" loading="lazy" decoding="async" /></figure>
<h2 id="scheduling-on-your-own-clock" tabindex="-1">Scheduling on your own clock <a class="anchor" href="#scheduling-on-your-own-clock" aria-hidden="true">#</a></h2>
<p>Recurring work doesn’t need a cloud cron either. The scheduler arms ordinary in-process timers — a
<code>setTimeout</code> into a steady <code>setInterval</code> — and when one fires it just drops a <code>request</code> message into an
@@ -222,6 +223,7 @@ answerable from your own repo history, not a vendor’s dashboard.</li>
the whole team can query, indexed on your machine.</li>
</ul>
<p>Nothing in that list is a network call. The team’s shared brain is a folder you own.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/local-first-ai-agent-orchestration/note-2.png" alt="Hand-drawn sketch from “Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud”" loading="lazy" decoding="async" /></figure>
<h2 id="the-loop-is-local-too" tabindex="-1">The loop is local, too <a class="anchor" href="#the-loop-is-local-too" aria-hidden="true">#</a></h2>
<p>What keeps an agent <em>going</em> without you clicking “continue”? A local hook. When an agent finishes a
turn, a Stop hook checks its inbox; if fresh messages are waiting, it tells the agent to keep working,
diff --git a/docs/blog/local-first-vs-cloud-agent-sdks/index.html b/docs/blog/local-first-vs-cloud-agent-sdks/index.html
index dfccfc05..6fb952fd 100644
--- a/docs/blog/local-first-vs-cloud-agent-sdks/index.html
+++ b/docs/blog/local-first-vs-cloud-agent-sdks/index.html
@@ -191,6 +191,7 @@ cost — is <a href="/blog/why-local-first-matters-for-ai-agents/">made in full
can speak MCP to your tools just like a cloud SDK does — <a href="/blog/mcp-and-skills-in-a-hive/">bringing your MCP servers and skills into the
hive</a> is a feature, not a contradiction. Interop is about protocols,
not about where the agents run.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/local-first-vs-cloud-agent-sdks/note-1.png" alt="Hand-drawn sketch from “Local-First vs Cloud Agent SDKs: Which Wins in 2026?”" loading="lazy" decoding="async" /></figure>
<h2 id="theyre-not-opposites-pick-the-axis-that-matters" tabindex="-1">They’re not opposites — pick the axis that matters <a class="anchor" href="#theyre-not-opposites-pick-the-axis-that-matters" aria-hidden="true">#</a></h2>
<p>It’s tempting to frame this as local <em>versus</em> cloud, but most of the headline features (MCP, A2A,
HITL, streaming) are available to both. The decisions that actually differ come down to three axes:</p>
@@ -224,6 +225,7 @@ servers.</li>
</ul>
<p>For one person or a handful of developers shipping against their own code, the control and cost story
usually outweighs managed convenience.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/local-first-vs-cloud-agent-sdks/note-2.png" alt="Hand-drawn sketch from “Local-First vs Cloud Agent SDKs: Which Wins in 2026?”" loading="lazy" decoding="async" /></figure>
<h2 id="the-cost-axis-is-shifting-in-local-firsts-favor" tabindex="-1">The cost axis is shifting — in local-first’s favor <a class="anchor" href="#the-cost-axis-is-shifting-in-local-firsts-favor" aria-hidden="true">#</a></h2>
<p>Cost deserves its own note, because 2026 changed the math. GitHub Copilot
<a href="https://github.blog/news-insights/company-news/github-copilot-is-moving-to-usage-based-billing/">moved all plans to usage-based billing on June 1, 2026</a>,
diff --git a/docs/blog/long-running-agents-the-2026-shift/index.html b/docs/blog/long-running-agents-the-2026-shift/index.html
index bd134bde..37eca34d 100644
--- a/docs/blog/long-running-agents-the-2026-shift/index.html
+++ b/docs/blog/long-running-agents-the-2026-shift/index.html
@@ -192,6 +192,7 @@ grind out the unglamorous refactor nobody scheduled. The unit of delegation chan
“this outcome” — you hand over a goal and get back a result, not a turn in a conversation. That’s the
promise people mean when they say agents are starting to feel less like autocomplete and more like
teammates.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/long-running-agents-the-2026-shift/note-1.png" alt="Hand-drawn sketch from “Long-Running Agents: The 2026 Shift from Minutes to Hours”" loading="lazy" decoding="async" /></figure>
<h2 id="why-longer-is-a-different-problem" tabindex="-1">Why “longer” is a different problem <a class="anchor" href="#why-longer-is-a-different-problem" aria-hidden="true">#</a></h2>
<p>Here’s the catch, and it’s the part the headline numbers skip: <strong>a longer agent fails in new ways.</strong></p>
<p>A short agent mostly has one job — get this answer right. A long-running agent has that job <em>plus</em>
@@ -231,6 +232,7 @@ is a liability, not a feature.</li>
</ul>
<p>None of these are new ideas. What’s new is that the shift to long-running agents turned them from
optional polish into the price of admission.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/long-running-agents-the-2026-shift/note-2.png" alt="Hand-drawn sketch from “Long-Running Agents: The 2026 Shift from Minutes to Hours”" loading="lazy" decoding="async" /></figure>
<h2 id="one-long-agent-or-a-coordinated-team" tabindex="-1">One long agent, or a coordinated team? <a class="anchor" href="#one-long-agent-or-a-coordinated-team" aria-hidden="true">#</a></h2>
<p>There’s a tempting picture of a single heroic agent grinding autonomously for ten hours. Often the better
answer is a <strong>team</strong>. A long-horizon goal can be decomposed across coordinated agents working in
diff --git a/docs/blog/loop-engineering-for-ai-agents/index.html b/docs/blog/loop-engineering-for-ai-agents/index.html
index b21a581d..d3facfb2 100644
--- a/docs/blog/loop-engineering-for-ai-agents/index.html
+++ b/docs/blog/loop-engineering-for-ai-agents/index.html
@@ -173,6 +173,7 @@
<li><strong>Exits.</strong> Defined terminal states: done-and-verified, budget-exhausted, escalated-to-human. Every path out of the loop should be one you chose.</li>
</ol>
<p>A runaway loop is just a loop missing one of these — usually the first. The agent is <em>doing things</em>, tokens are flowing, avatars are walking around, and nothing external is changing. Motion without progress.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/loop-engineering-for-ai-agents/note-1.png" alt="Hand-drawn sketch from “Loop Engineering: Designing Agent Loops That Converge”" loading="lazy" decoding="async" /></figure>
<h2 id="the-outer-loop-toolbox" tabindex="-1">The outer-loop toolbox <a class="anchor" href="#the-outer-loop-toolbox" aria-hidden="true">#</a></h2>
<p>Here’s the toolbox as it actually exists in <a href="/">Munder Difflin</a>, where the design constraint is blunt: a floor of CLI agents has to run for days without a human babysitting it, and without melting.</p>
<p><strong>Stop conditions.</strong> The naive stop condition is “the model stopped talking.” The engineered one checks state: is the task’s definition of done verified? In Munder Difflin, workers don’t self-certify — the GOD orchestrator reads results, adjudicates, and moves the board (see <a href="/blog/how-the-god-orchestrator-works/">how the GOD orchestrator works</a>).</p>
@@ -183,6 +184,7 @@
<p><strong>No-progress detection.</strong> The breaker needs a tripwire, and “is it looping?” can’t be answered by asking the looper. External signals work: repeated near-identical actions, the same error N times, spend rising while verified state stays flat. There’s also a quieter failure — the <em>silent</em> stall — which Munder Difflin catches with a PTY-quiescence backstop: an agent pinned <code>working</code> but producing no output gets flipped back to idle, where the inbox-wake nudge can restart its drain loop.</p>
<p><strong>Budgets as loop bounds.</strong> Per-agent token budgets, tracked live against real telemetry, are the guaranteed-termination clause. If every other signal misses, the loop still halts at a ceiling you set while calm.</p>
<p><strong>Human gates as loop exits.</strong> The final exit isn’t a dead process; it’s a person. Spend, scope changes, and destructive operations escalate into an approvals queue rather than resolving inside the loop — the human is a designed exit condition, not an interrupt handler. That’s the heart of <a href="/blog/human-in-the-loop-approving-ai-agents/">human-in-the-loop agent design</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/loop-engineering-for-ai-agents/note-2.png" alt="Hand-drawn sketch from “Loop Engineering: Designing Agent Loops That Converge”" loading="lazy" decoding="async" /></figure>
<h2 id="the-bottom-line" tabindex="-1">The bottom line <a class="anchor" href="#the-bottom-line" aria-hidden="true">#</a></h2>
<p>The model gives you the inner loop; the outer loop is the product. Verified stop conditions, drain loops with anti-recursion guards, backoff, scheduled compaction, a breaker ladder, progress tripwires, budget bounds, and human exits — stacked together, they’re why a floor of agents can run for days and converge on finished work instead of a bill.</p>
<p>Munder Difflin ships this outer loop as a free, MIT-licensed, local-first desktop app for the agent CLIs you already run. <a href="https://github.com/chaitanyagiri/munder-difflin/releases/latest">Download it</a>, and if the loop-nerdery resonates, a <a href="https://github.com/chaitanyagiri/munder-difflin">GitHub star</a> helps more people find it.</p>
diff --git a/docs/blog/manage-multiple-claude-code-sessions/index.html b/docs/blog/manage-multiple-claude-code-sessions/index.html
index 9dce485f..d2ad9e2d 100644
--- a/docs/blog/manage-multiple-claude-code-sessions/index.html
+++ b/docs/blog/manage-multiple-claude-code-sessions/index.html
@@ -181,6 +181,7 @@ pasting context between windows.</li>
is for at a glance, and it constrains the session so it doesn’t wander into another’s work.</p>
<p>Scope follows naming. A session called <code>reviewer</code> reviews; it doesn’t start refactoring. The tighter
the scope, the less the sessions overlap, which directly defuses failure mode #2.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/manage-multiple-claude-code-sessions/note-1.png" alt="Hand-drawn sketch from “How to Manage Multiple Claude Code Sessions Like a Pro”" loading="lazy" decoding="async" /></figure>
<h2 id="habit-2-isolate-context-on-purpose" tabindex="-1">Habit 2 — Isolate context on purpose <a class="anchor" href="#habit-2-isolate-context-on-purpose" aria-hidden="true">#</a></h2>
<p>Each <code>claude</code> session has its own context window, and that’s a feature: it keeps one task’s noise out
of another’s reasoning. The mistake is fighting it — trying to keep one giant session that “knows
@@ -202,6 +203,7 @@ session writes durable facts to a file, and reads the relevant ones at the start
<p>Plain markdown is enough to start. Once the notes pile up, you add a semantic index so a session can
recall the few relevant notes by meaning instead of re-reading everything — the full version of this
is <a href="/blog/give-claude-code-long-term-memory/">long-term memory for Claude Code</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/manage-multiple-claude-code-sessions/note-2.png" alt="Hand-drawn sketch from “How to Manage Multiple Claude Code Sessions Like a Pro”" loading="lazy" decoding="async" /></figure>
<h2 id="habit-4-give-shared-work-a-single-coordination-rule" tabindex="-1">Habit 4 — Give shared work a single coordination rule <a class="anchor" href="#habit-4-give-shared-work-a-single-coordination-rule" aria-hidden="true">#</a></h2>
<p>Failure mode #2 — collisions — is the one pure discipline can’t fully solve, because two well-behaved
sessions can still both decide to commit at the same instant. The rule that fixes it: <strong>one writer per
diff --git a/docs/blog/markdown-first-agent-memory/index.html b/docs/blog/markdown-first-agent-memory/index.html
index fc28a90f..fbf1a164 100644
--- a/docs/blog/markdown-first-agent-memory/index.html
+++ b/docs/blog/markdown-first-agent-memory/index.html
@@ -200,6 +200,7 @@ machine without it, the markdown files <strong>still work</strong> — the agent
is an upgrade, not a dependency. Contrast a database that won’t open: it takes the memory with it. With
markdown-first, the floor never falls out from under the agent; the worst case is slower recall, not
lost knowledge.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/markdown-first-agent-memory/note-1.png" alt="Hand-drawn sketch from “Why We Built Agent Memory Markdown-First”" loading="lazy" decoding="async" /></figure>
<h2 id="why-not-a-vector-database-or-a-memory-framework" tabindex="-1">Why not a vector database or a memory framework? <a class="anchor" href="#why-not-a-vector-database-or-a-memory-framework" aria-hidden="true">#</a></h2>
<p>Vector DBs and dedicated memory frameworks are real tools with real uses. They’re the wrong default
<em>here</em> for two reasons.</p>
@@ -222,6 +223,7 @@ read-only, so the whole team can recall across agents without any file being wri
It’s the same single-writer discipline that keeps
<a href="/blog/single-committer-git-pattern/">multi-agent git safe</a> — applied to memory. Co-edited memory files
would tear; per-agent files plus a read-only shared index don’t.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/markdown-first-agent-memory/note-2.png" alt="Hand-drawn sketch from “Why We Built Agent Memory Markdown-First”" loading="lazy" decoding="async" /></figure>
<h2 id="when-markdown-first-is-the-right-call" tabindex="-1">When markdown-first is the right call <a class="anchor" href="#when-markdown-first-is-the-right-call" aria-hidden="true">#</a></h2>
<p>This approach shines when:</p>
<ul>
diff --git a/docs/blog/mcp-and-skills-in-a-hive/index.html b/docs/blog/mcp-and-skills-in-a-hive/index.html
index ebb4c3df..cff63254 100644
--- a/docs/blog/mcp-and-skills-in-a-hive/index.html
+++ b/docs/blog/mcp-and-skills-in-a-hive/index.html
@@ -202,6 +202,7 @@ project, and <code>--settings</code> is additive — it layers the harness’s h
configuration rather than replacing it. Your repo isn’t modified to make an agent hive-aware; there’s
no stray settings diff to commit or gitignore. (The hook mechanics are covered in
<a href="/blog/claude-code-hooks-explained/">Claude Code hooks, explained</a>.)</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/mcp-and-skills-in-a-hive/note-1.png" alt="Hand-drawn sketch from “Bringing Your MCP Servers and Skills Into a Hive of Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="a-note-on-the-harnesss-own-memory" tabindex="-1">A note on the harness’s own memory <a class="anchor" href="#a-note-on-the-harnesss-own-memory" aria-hidden="true">#</a></h2>
<p>Here’s a deliberate design choice worth calling out: the hive’s <strong>semantic memory doesn’t consume an
MCP slot.</strong> Rather than run memory as an MCP server, the harness drives it through a CLI and points each
@@ -231,6 +232,7 @@ really means in practice. Roles are the same routing signal the
<p>Because agents are real sessions, Claude Code’s own configuration applies — per-project settings and
permission controls govern what a session in that directory can do. You’re not learning a parallel,
harness-specific permission system; you’re using the one you already know, per directory, per agent.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/mcp-and-skills-in-a-hive/note-2.png" alt="Hand-drawn sketch from “Bringing Your MCP Servers and Skills Into a Hive of Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="a-practical-setup" tabindex="-1">A practical setup <a class="anchor" href="#a-practical-setup" aria-hidden="true">#</a></h2>
<p>Putting it together, a tooled-up hive might look like this:</p>
<ol>
diff --git a/docs/blog/mcp-security-tool-poisoning/index.html b/docs/blog/mcp-security-tool-poisoning/index.html
index 3fd7d47f..dfbb8d4d 100644
--- a/docs/blog/mcp-security-tool-poisoning/index.html
+++ b/docs/blog/mcp-security-tool-poisoning/index.html
@@ -184,6 +184,7 @@ as the most prevalent, impactful client-side MCP vulnerability. The agent isn’
following instructions it was handed by something it was told to trust.</p>
<p>The mitigation starts with a mindset shift: <strong>tool descriptions are untrusted model input, not
documentation.</strong> Treat them the way you’d treat any string from the internet that reaches your prompt.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/mcp-security-tool-poisoning/note-1.png" alt="Hand-drawn sketch from “MCP Tool Poisoning: How to Secure the Model Context Protocol”" loading="lazy" decoding="async" /></figure>
<h2 id="the-rug-pull-poisoning-on-a-delay" tabindex="-1">The rug pull: poisoning on a delay <a class="anchor" href="#the-rug-pull-poisoning-on-a-delay" aria-hidden="true">#</a></h2>
<p>Approving a server once isn’t enough, because descriptions can change. In a <strong>rug pull</strong>, a server is
clean when you approve it, then <strong>updates its tool descriptions later</strong> to add exfiltration instructions
@@ -210,6 +211,7 @@ mismanagement — a leaked or over-privileged API key — as the most common rea
ahead of clever injection chains. The flashy attack gets the write-ups; the credential left in scope does
the damage. If you do one thing, make it <strong>least privilege</strong>: scope every tool’s token so it can only
touch the data it explicitly needs.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/mcp-security-tool-poisoning/note-2.png" alt="Hand-drawn sketch from “MCP Tool Poisoning: How to Secure the Model Context Protocol”" loading="lazy" decoding="async" /></figure>
<h2 id="defenses-layered" tabindex="-1">Defenses, layered <a class="anchor" href="#defenses-layered" aria-hidden="true">#</a></h2>
<p>No single control is enough; MCP security is defense in depth.</p>
<ul>
diff --git a/docs/blog/multi-agent-orchestration-patterns/index.html b/docs/blog/multi-agent-orchestration-patterns/index.html
index 2d77d322..d3b80847 100644
--- a/docs/blog/multi-agent-orchestration-patterns/index.html
+++ b/docs/blog/multi-agent-orchestration-patterns/index.html
@@ -198,6 +198,7 @@ Accuracy-critical → maker-checker. Emergent path → swarm (with guardrails).<
<li><strong>Start simple.</strong> Most teams over-architect. Reach for more agents only when a single agent genuinely
can’t hold the task.</li>
</ol>
+<figure class="fig fig-inline"><img src="/blog/assets/media/multi-agent-orchestration-patterns/note-1.png" alt="Hand-drawn sketch from “Multi-Agent Orchestration Patterns: Which Topology, and When”" loading="lazy" decoding="async" /></figure>
<h2 id="patterns-compose" tabindex="-1">Patterns compose <a class="anchor" href="#patterns-compose" aria-hidden="true">#</a></h2>
<p>Real systems rarely use one pattern in isolation — they nest. A supervisor’s workers might each run a
maker-checker loop internally; a sequential pipeline might fan out within a single stage; a hierarchical
@@ -222,6 +223,7 @@ dependencies corrupts its merge.</li>
<p>The corollary: the value isn’t “more agents,” it’s <strong>the right topology plus the resilience to survive
its failure mode</strong> — hop caps, idempotent handling, isolation. (We wrote up those mechanics in
<a href="/blog/recovering-from-agent-failures/">recovering from agent failures</a>.)</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/multi-agent-orchestration-patterns/note-2.png" alt="Hand-drawn sketch from “Multi-Agent Orchestration Patterns: Which Topology, and When”" loading="lazy" decoding="async" /></figure>
<h2 id="the-2026-framework-landscape" tabindex="-1">The 2026 framework landscape <a class="anchor" href="#the-2026-framework-landscape" aria-hidden="true">#</a></h2>
<p>If you’re building this on a framework, the control-vs-simplicity tension hasn’t converged — they differ
mostly in orchestration model and ecosystem:</p>
diff --git a/docs/blog/munder-difflin-faq/index.html b/docs/blog/munder-difflin-faq/index.html
index 251dc7c7..d6cb48d8 100644
--- a/docs/blog/munder-difflin-faq/index.html
+++ b/docs/blog/munder-difflin-faq/index.html
@@ -179,6 +179,7 @@ of <a href="/blog/">the blog</a> go deeper.</p>
takes the agents you already run and makes them act like one team — they message each other, share
long-term memory, and are routed by a coordinator you talk to in plain language, all visualized as a
live office floor on your own machine.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/munder-difflin-faq/note-1.png" alt="Hand-drawn sketch from “Munder Difflin FAQ: Everything People Ask”" loading="lazy" decoding="async" /></figure>
<h2 id="still-deciding" tabindex="-1">Still deciding? <a class="anchor" href="#still-deciding" aria-hidden="true">#</a></h2>
<p>If you’re comparing options, these go deeper than an FAQ can:</p>
<ul>
diff --git a/docs/blog/munder-difflin-v0-2-4-feature-walkthrough/index.html b/docs/blog/munder-difflin-v0-2-4-feature-walkthrough/index.html
index 589cc42f..d60395b7 100644
--- a/docs/blog/munder-difflin-v0-2-4-feature-walkthrough/index.html
+++ b/docs/blog/munder-difflin-v0-2-4-feature-walkthrough/index.html
@@ -182,6 +182,7 @@
<li>Outbox messages are picked up by the provider-agnostic router, same as before.</li>
</ul>
<p>Codex is no longer the third provider with an asterisk. It’s a full hive participant.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-1.png" alt="Hand-drawn sketch from “Munder Difflin v0.2.4 Feature Walkthrough”" loading="lazy" decoding="async" /></figure>
<h2 id="terminal-work-orders-the-work-order-from-hive-pattern" tabindex="-1">Terminal work orders: the WORK ORDER FROM HIVE pattern <a class="anchor" href="#terminal-work-orders-the-work-order-from-hive-pattern" aria-hidden="true">#</a></h2>
<p>Both Antigravity and Codex now have full hook bridges. But the multi-provider work raised a broader question: what should happen when a future provider has <em>no</em> inbox-drain path at all — no hook bridge, no idle-wake nudge — and you still need to get hive mail to it?</p>
<p>The answer is a structured fallback: the hive types a <code>WORK ORDER FROM HIVE</code> message directly into the agent’s terminal. The message is clearly labeled, delivered as terminal input, and actionable by any CLI that can read what’s in its terminal. If the renderer is unavailable at the time mail arrives, the router bounces the message to the GOD agent rather than dropping it silently.</p>
@@ -200,6 +201,7 @@
<p>The fix is straightforward: the heartbeat checks for unread actionable inbox items before cycling, and re-engages if it finds any. GOD no longer needs an external trigger to notice mail that arrived between heartbeat cycles.</p>
<h2 id="terminal-sidebar-open-by-default" tabindex="-1">Terminal sidebar open by default <a class="anchor" href="#terminal-sidebar-open-by-default" aria-hidden="true">#</a></h2>
<p>The GOD orchestrator now opens with the Terminal sidebar visible from the start. You’ve always been able to open it — now you don’t have to remember to. For most workflows, seeing god’s terminal output immediately is the right default.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/munder-difflin-v0-2-4-feature-walkthrough/note-2.png" alt="Hand-drawn sketch from “Munder Difflin v0.2.4 Feature Walkthrough”" loading="lazy" decoding="async" /></figure>
<h2 id="slack-webhook-tunnelmole-replaces-localtunnel" tabindex="-1">Slack + webhook: tunnelmole replaces localtunnel <a class="anchor" href="#slack-webhook-tunnelmole-replaces-localtunnel" aria-hidden="true">#</a></h2>
<p>The Slack and webhook ingress paths used <code>localtunnel</code> / <code>loca.lt</code> to expose the local server to the public internet. This allowed Slack’s URL verification handshake to succeed and kept incoming webhook deliveries working.</p>
<p>The problem: <code>loca.lt</code> began serving a browser interstitial on all outbound requests. For a human browsing a URL, an interstitial is annoying but navigable. For Slack’s <code>url_verification</code> POST — a machine-to-machine request with a specific payload and a strict response format — it is fatal. The handshake fails silently. Saved webhook URLs break. And critically, the app reported “tunnel started” with no indication that the URL it gave you would reject all incoming requests.</p>
diff --git a/docs/blog/node-pty-electron-real-terminals/index.html b/docs/blog/node-pty-electron-real-terminals/index.html
index b5a228da..b8f4b5db 100644
--- a/docs/blog/node-pty-electron-real-terminals/index.html
+++ b/docs/blog/node-pty-electron-real-terminals/index.html
@@ -215,6 +215,7 @@ automatically:</p>
<p>The <code>-w node-pty</code> scopes the rebuild to just that module (faster than rebuilding everything), and <code>-f</code>
forces it. After this runs, the addon loads cleanly inside Electron. Forget it, and the app crashes on
launch with an ABI error that looks scarier than it is.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/node-pty-electron-real-terminals/note-1.png" alt="Hand-drawn sketch from “Real Terminals in Electron with node-pty”" loading="lazy" decoding="async" /></figure>
<h2 id="gotcha-2-the-macos-path-trap" tabindex="-1">Gotcha 2 — The macOS PATH trap <a class="anchor" href="#gotcha-2-the-macos-path-trap" aria-hidden="true">#</a></h2>
<p>You ship the app, double-click it, and your terminal can’t find <code>claude</code> — or <code>node</code>, or <code>git</code>, or
whatever you installed with nvm, asdf, or Homebrew. Run the same command in a real terminal and it
@@ -267,6 +268,7 @@ a main-process crash. The guard is simple but essential: check the target is ali
<span class="token punctuation">}</span></code></pre>
<p>Route every PTY-to-renderer message through that, and quitting the app is clean instead of a crash
report.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/node-pty-electron-real-terminals/note-2.png" alt="Hand-drawn sketch from “Real Terminals in Electron with node-pty”" loading="lazy" decoding="async" /></figure>
<h2 id="managing-many-sessions" tabindex="-1">Managing many sessions <a class="anchor" href="#managing-many-sessions" aria-hidden="true">#</a></h2>
<p>A real app runs more than one terminal, so wrap all of this in a manager keyed by session id —
<code>spawn</code>, <code>write</code>, <code>resize</code>, <code>kill</code>, <code>list</code>, <code>killAll</code>. Two details pay off at scale:</p>
@@ -348,6 +350,22 @@ real terminals driving real agents; it’s free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -379,22 +397,6 @@ real terminals driving real agents; it’s free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/number-five-on-product-hunt/index.html b/docs/blog/number-five-on-product-hunt/index.html
new file mode 100644
index 00000000..77329521
--- /dev/null
+++ b/docs/blog/number-five-on-product-hunt/index.html
@@ -0,0 +1,383 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for." />
+<link rel="canonical" href="https://munderdiffl.in/blog/number-five-on-product-hunt/" />
+
+<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="Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for." />
+<meta property="og:url" content="https://munderdiffl.in/blog/number-five-on-product-hunt/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Story" />
+<meta property="article:tag" content="Launch" />
+<meta property="article:tag" content="Product Hunt" />
+<meta property="article:tag" content="Open Source" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers",
+ "description": "Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek's harness launch that day. Here's what actually happened: the numbers, the people who showed up, and the two pieces of feedback we're already shipping fixes for.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/number-five-on-product-hunt/" },
+ "keywords": "munder difflin product hunt, product hunt launch retrospective, product of the day, ai agent harness launch, launching a dev tool on product hunt",
+ "articleSection": "Story",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/number-five-on-product-hunt/"
+}
+</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": "Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers", "item": "https://munderdiffl.in/blog/number-five-on-product-hunt/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "How did Munder Difflin do on Product Hunt?", "acceptedAnswer": { "@type": "Answer", "text": "It finished #5 Product of the Day on 2026-08-14 with 195 upvotes (177 on launch day itself), 326 followers, and #35 for the week — ahead of DeepSeek's harness, which launched the same day. It was a first launch, self-hunted, with no hunter network behind it." } },
+ { "@type": "Question", "name": "Did Product Hunt drive a lot of traffic?", "acceptedAnswer": { "@type": "Answer", "text": "Honestly, no. The badge brought credibility, not crowds — roughly one site visitor per eight upvotes. What it did bring was a small number of unusually serious evaluators, including a CEO who ran it on a real multi-day task and reviewed it in detail. For a developer tool, that trade is worth knowing about before you launch." } },
+ { "@type": "Question", "name": "What feedback came out of the launch?", "acceptedAnswer": { "@type": "Answer", "text": "Two things, both already acted on: first-run engine selection could trap you if you picked an engine you didn't have access to (fixed territory in v0.4.4's onboarding work), and people want a visible flag for 'this decision needs your eyes' so they can tell an agent that paused from one that decided on its own. That second one is now on the roadmap." } }
+
+ ]
+}
+</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,
+ 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-story">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/story/">Story</a>
+ </nav>
+ <h1>Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</h1>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>4 min read</span>
+ <span class="tag kind">Story</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="Illustration: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers" 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>On August 14 we launched Munder Difflin
+on Product Hunt for the first time. It finished <strong>#5 Product of the Day</strong> — ahead of
+DeepSeek's harness, which launched the same day — with 195 upvotes and 326 followers. The honest
+retro: Product Hunt bought us credibility, not traffic, and the ten people who actually commented
+gave us better product feedback than a thousand upvotes would have.</p></div>
+<p>We had never launched on Product Hunt before. No hunter with a following, no launch agency, no
+upvote pod — I hunted it myself, scheduled it for August 14, and went to bed nervous.</p>
+<h2 id="the-scoreboard" tabindex="-1">The scoreboard <a class="anchor" href="#the-scoreboard" aria-hidden="true">#</a></h2>
+<ul>
+<li><strong>#5 Product of the Day</strong>, August 14, 2026 — the same day DeepSeek launched
+<a href="/blog/what-is-harness-engineering/">their harness</a> with tech-press coverage behind it; the
+<a href="https://www.producthunt.com/leaderboard/daily/2026/8/14">day’s leaderboard</a> has them at #6,
+one spot behind us, which still feels surreal to type</li>
+<li><strong>195 upvotes</strong> as of August 18 (177 on the day itself; the rest drifted in over the week)</li>
+<li><strong>326 followers</strong>, <strong>#35 product of the week</strong>, <strong>#74 of the month</strong></li>
+<li><strong>27 comments</strong> — 15 of them mine, because I answered everything</li>
+<li><strong>One review</strong>: 4.0 overall, with value-for-money and customization at 5/5</li>
+</ul>
+<p>That last line deserves context. The review came from Gal Dayan, co-founder and CEO of Dial, who
+didn’t skim the landing page — he ran Munder Difflin against his own Claude subscription on a
+multi-day task before writing a five-dimension review. His build-vs-buy verdict was the sentence
+I’d been trying to write for months, in someone else’s words:</p>
+<blockquote>
+<p>“I looked at rolling my own orchestration on tmux plus Claude Code directly. Wasn’t worth
+reinventing the mailbox and lifecycle tracking myself when this already handles worker handoffs,
+and it’s fully local so none of my code leaves my machine.”</p>
+</blockquote>
+<p>That’s the whole pitch. The <a href="/blog/atomic-file-mailboxes-for-agents/">mailboxes</a>, the lifecycle
+tracking, the <a href="/blog/why-local-first-matters-for-ai-agents/">local-first design</a> — the boring
+plumbing is the product.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/number-five-on-product-hunt/note-1.png" alt="Hand-drawn sketch from “Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers”" loading="lazy" decoding="async" /><figcaption>First launch, self-hunted, no upvote pod — and the badge came home anyway.</figcaption></figure>
+<h2 id="who-actually-showed-up" tabindex="-1">Who actually showed up <a class="anchor" href="#who-actually-showed-up" aria-hidden="true">#</a></h2>
+<p>Product Hunt gets described as a hype machine, and maybe it is for consumer apps. What showed up
+on our page was ten people, and the ratio of substance was unusually high: a CEO who ran a
+multi-day evaluation, an engineer who instruments his own agent spend down to the dollar, a
+builder who runs his own orchestration system and benchmarked ours against it, a product manager
+who uses it at work, and someone asking whether a hive could build a company’s tender-management
+system end to end.</p>
+<p>Small crowd, serious questions. The exact opposite of <a href="/blog/what-reddit-told-us-about-munder-difflin/">our Reddit
+launch</a>, which was a stadium.</p>
+<h2 id="the-two-pieces-of-feedback-that-mattered" tabindex="-1">The two pieces of feedback that mattered <a class="anchor" href="#the-two-pieces-of-feedback-that-mattered" aria-hidden="true">#</a></h2>
+<p><strong>1. First-run engine selection could strand you.</strong> One commenter picked Claude Code during setup
+without having Claude Code access, couldn’t change the selection afterwards, and uninstalled
+twice in frustration. Another hit a Windows + Codex startup failure that killed his three-agent
+benchmark. Two people out of ten, blocked by the same class of problem: the non-Claude-Code path
+got less love than it deserved. The Windows side of this is exactly what
+<a href="/blog/launching-munder-difflin-v0-4-4/">v0.4.4 fixed</a>, and onboarding now validates your setup
+at step one instead of failing after step four.</p>
+<p><strong>2. Nobody can tell a finished agent from a stuck one — or a paused one from a self-directed
+one.</strong> The two most technically serious people on the page independently asked for the same
+missing primitive. One measured that 64.9% of a day’s agent spend landed in an “abandoned”
+bucket and wants to trust unattended runs. The other put it perfectly: the office view already
+tells you <em>who’s stuck versus who’s actually working</em> at a glance, but it doesn’t tell you
+whether a clone paused for your input or made a judgment call on its own. A visible
+<strong>“this decision needs your eyes”</strong> flag is the ask, and it’s the best feature request we’ve
+received on any channel. It’s on the roadmap.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/number-five-on-product-hunt/note-2.png" alt="Hand-drawn sketch from “Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers”" loading="lazy" decoding="async" /><figcaption>The best feature request of the launch: a flag that says 'this decision needs your eyes' — asked for twice, independently.</figcaption></figure>
+<h2 id="what-product-hunt-is-actually-for" tabindex="-1">What Product Hunt is actually for <a class="anchor" href="#what-product-hunt-is-actually-for" aria-hidden="true">#</a></h2>
+<p>Here’s the number nobody puts in their launch thread: those 195 upvotes referred roughly 25
+unique visitors to our site. One visitor per eight upvotes. If you’re launching a developer tool
+and expecting Product Hunt to be a traffic channel, adjust that expectation now.</p>
+<p>What it <em>is</em>: a credibility artifact (the badge now lives on <a href="https://munderdiffl.in">munderdiffl.in</a>),
+and a filter that surfaces a handful of unusually serious evaluators. The questions those
+evaluators asked — about trust, about unattended runs, about
+<a href="/blog/why-local-first-matters-for-ai-agents/">what runs where</a> — were the enterprise questions,
+and getting them this early is a gift.</p>
+<p>Would we launch there again? Yes — but as one channel in a week, not the week itself. The stadium
+was elsewhere, and that’s <a href="/blog/what-reddit-told-us-about-munder-difflin/">the next post</a>.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">How did Munder Difflin do on Product Hunt?</p>
+ <p class="a">It finished #5 Product of the Day on 2026-08-14 with 195 upvotes (177 on launch day itself), 326 followers, and #35 for the week — ahead of DeepSeek&#39;s harness, which launched the same day. It was a first launch, self-hunted, with no hunter network behind it.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Did Product Hunt drive a lot of traffic?</p>
+ <p class="a">Honestly, no. The badge brought credibility, not crowds — roughly one site visitor per eight upvotes. What it did bring was a small number of unusually serious evaluators, including a CEO who ran it on a real multi-day task and reviewed it in detail. For a developer tool, that trade is worth knowing about before you launch.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">What feedback came out of the launch?</p>
+ <p class="a">Two things, both already acted on: first-run engine selection could trap you if you picked an engine you didn&#39;t have access to (fixed territory in v0.4.4&#39;s onboarding work), and people want a visible flag for &#39;this decision needs your eyes&#39; so they can tell an agent that paused from one that decided on its own. That second one is now on the roadmap.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/story/">Story</a><a class="tag" href="/blog/tags/launch/">Launch</a><a class="tag" href="/blog/tags/product-hunt/">Product Hunt</a><a class="tag" href="/blog/tags/open-source/">Open Source</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-scoreboard">The scoreboard</a></li><li class="lvl-2"><a href="#who-actually-showed-up">Who actually showed up</a></li><li class="lvl-2"><a href="#the-two-pieces-of-feedback-that-mattered">The two pieces of feedback that mattered</a></li><li class="lvl-2"><a href="#what-product-hunt-is-actually-for">What Product Hunt is actually for</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/run-a-release-train-with-agents/"><span class="k">← Older</span><span class="t">Run a Release Train with Agents</span></a>
+ <a class="pn next" href="/blog/launching-munder-difflin-v0-4-4/"><span class="k">Newer →</span><span class="t">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</span></a>
+ </div>
+ <section class="related">
+ <h2>Related in Story</h2>
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/observability-for-agent-fleets/index.html b/docs/blog/observability-for-agent-fleets/index.html
index a75c5f77..65bc1afa 100644
--- a/docs/blog/observability-for-agent-fleets/index.html
+++ b/docs/blog/observability-for-agent-fleets/index.html
@@ -191,6 +191,7 @@ not raw JSON, but sentences:</p>
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>
@@ -212,6 +213,7 @@ to jump into any agent’s memory — explains decisions. An agent acting oddly
</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
@@ -285,6 +287,22 @@ open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -316,22 +334,6 @@ open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/one-prompt-automated-pr-review/index.html b/docs/blog/one-prompt-automated-pr-review/index.html
index 7a30e84c..701c533e 100644
--- a/docs/blog/one-prompt-automated-pr-review/index.html
+++ b/docs/blog/one-prompt-automated-pr-review/index.html
@@ -162,6 +162,7 @@
<p><strong><a href="https://github.com/chaitanyagiri/munder-difflin/pull/26">PR #26</a></strong> — terminal theme toggle plus Unicode 11 emoji widths. The review caught the earlier design issue (using <code>claude config set -g</code> would restyle the user’s own external Claude sessions) and confirmed the correction — mirroring the theme into per-agent settings files at spawn — was the right scoping.</p>
<p><strong><a href="https://github.com/chaitanyagiri/munder-difflin/pull/12">PR #12</a></strong> — the statusLine context gauge. This was the most complex PR in the batch: three follow-up commits, a ratcheting limit heuristic, and a statusLine-based push mechanism replacing transcript polling. The review identified a real gap — a <code>NaN</code> that would survive the <code>Math.min/max</code> clamp — and Gulum addressed it in a follow-up commit with a <code>Number.isFinite</code> guard.</p>
<p>Five reviews. One prompt. The reviews were posted so close together (all within seconds, around <code>2026-06-07T01:47</code>) that they clearly came from a single agent run. The whole batch took a few minutes I spent doing something else.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/one-prompt-automated-pr-review/note-1.png" alt="Hand-drawn sketch from “One Prompt, Five PR Reviews, and an Hourly Automation — A Dogfooding Story”" loading="lazy" decoding="async" /></figure>
<h2 id="the-recurring-part" tabindex="-1">The recurring part <a class="anchor" href="#the-recurring-part" aria-hidden="true">#</a></h2>
<p>The review run was half of what I asked for. The other half was the hourly mission.</p>
<p>Munder Difflin’s <a href="/blog/scheduling-autonomous-agent-missions/">ScheduledMissions</a> are small persisted records in <code>src/main/config.ts</code>:</p>
@@ -181,6 +182,7 @@
<p><strong>First, the single-prompt routing story.</strong> What made this possible isn’t that Munder Difflin is a clever cron wrapper for GitHub API calls. It’s that the <a href="/blog/how-the-god-orchestrator-works/">god orchestrator</a> understood a compound intent — <em>do this now</em> AND <em>set up a recurring thing</em> — decomposed it into two tasks, executed the one-off, and created the ScheduledMission for the other. One sentence of plain language became two distinct workflows.</p>
<p><strong>Second, the recursive nature of this.</strong> The agents are maintaining the open-source repo that runs the agents. The PR reviewer is a Munder Difflin agent reviewing PRs submitted to Munder Difflin. The blog post you’re reading was written by a Munder Difflin agent. The hive is genuinely part of its own development loop — not as a gimmick, but because that’s what a local-first coordination layer lets you do.</p>
<p><strong>Third, what “automation” means here.</strong> The hourly PR reviewer isn’t a GitHub Actions workflow. It’s not a webhook. It’s a local agent that wakes up on a schedule, reads the repo state, and does the work — with the same intelligence, tone, and judgment a human reviewer would bring, because it <em>is</em> a Claude agent. The automation is just a timer that refills an agent’s inbox.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/one-prompt-automated-pr-review/note-2.png" alt="Hand-drawn sketch from “One Prompt, Five PR Reviews, and an Hourly Automation — A Dogfooding Story”" loading="lazy" decoding="async" /></figure>
<h2 id="the-limit-worth-naming" tabindex="-1">The limit worth naming <a class="anchor" href="#the-limit-worth-naming" aria-hidden="true">#</a></h2>
<p>ScheduledMissions are local-first: the timers live in the desktop app’s process. The PR reviewer only fires while Munder Difflin is open. That’s a deliberate trade — this is a tool you run on your own machine, not a cloud cron — and <code>lastFiredAt</code> softens it by catching up on any overdue ticks at the next launch. But if you need PR reviews while the laptop is shut, that’s genuinely a cloud job’s territory.</p>
<p>For a solo maintainer who has the app open during the day, it’s exactly the right trade.</p>
@@ -220,50 +222,50 @@
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/open-source-ai-tools-on-purpose/index.html b/docs/blog/open-source-ai-tools-on-purpose/index.html
index 72a11318..d63da0fc 100644
--- a/docs/blog/open-source-ai-tools-on-purpose/index.html
+++ b/docs/blog/open-source-ai-tools-on-purpose/index.html
@@ -194,6 +194,7 @@ it. The tool bends to your needs instead of the reverse.</li>
<li><strong>Longevity.</strong> Open code outlives the company or the moment. The work you build on top of it is safe
in a way that a closed SaaS can’t promise.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/open-source-ai-tools-on-purpose/note-1.png" alt="Hand-drawn sketch from “Building AI Dev Tools in the Open, On Purpose”" loading="lazy" decoding="async" /></figure>
<h2 id="open-and-local-first-the-combination-is-the-point" tabindex="-1">Open <em>and</em> local-first — the combination is the point <a class="anchor" href="#open-and-local-first-the-combination-is-the-point" aria-hidden="true">#</a></h2>
<p>“Open source” alone can still be hollow if the useful half lives in someone else’s cloud. The version
that actually means something pairs open code with <strong>local-first</strong> execution: the orchestrator, the
@@ -212,6 +213,7 @@ on-the-nose a demonstration of “built in the open” as you’ll find.</p>
<p>It also lowers the bar to contribute. When the code and the thinking are both public, a user who hits a
rough edge can read the relevant file, understand it, and propose a fix — instead of filing a ticket into
a void and hoping.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/open-source-ai-tools-on-purpose/note-2.png" alt="Hand-drawn sketch from “Building AI Dev Tools in the Open, On Purpose”" loading="lazy" decoding="async" /></figure>
<h2 id="the-honest-tradeoffs" tabindex="-1">The honest tradeoffs <a class="anchor" href="#the-honest-tradeoffs" aria-hidden="true">#</a></h2>
<p>Open source isn’t free of cost, and pretending otherwise would be exactly the kind of marketing this post
is arguing against. Building in the open means no proprietary moat, support that leans on community and
diff --git a/docs/blog/orca-vs-munder-difflin/index.html b/docs/blog/orca-vs-munder-difflin/index.html
index f4a3151a..85fe35ab 100644
--- a/docs/blog/orca-vs-munder-difflin/index.html
+++ b/docs/blog/orca-vs-munder-difflin/index.html
@@ -175,6 +175,7 @@
</ul>
<p>That mobile companion and the editor-centric review flow are genuinely ahead of what Munder Difflin offers today. If your workflow is “I’m at my desk, I want to run three agents on a feature and pick the best diff,” Orca is excellent at exactly that.</p>
<p>Notice, though, what the workflow assumes: <strong>you</strong>. You send the prompts. You compare the results. You annotate the diffs. You steer. Orca’s own docs describe an interactive loop, and there’s no orchestrator, scheduler, or external trigger in it. That’s not a flaw — it’s the product. An IDE is a place you sit.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/orca-vs-munder-difflin/note-1.png" alt="Hand-drawn sketch from “Orca vs Munder Difflin: Agent IDE or Agent Office?”" loading="lazy" decoding="async" /></figure>
<h2 id="what-munder-difflin-actually-is" tabindex="-1">What Munder Difflin actually is <a class="anchor" href="#what-munder-difflin-actually-is" aria-hidden="true">#</a></h2>
<p>Munder Difflin starts from the opposite question: what if you <em>don’t</em> sit there?</p>
<p>It’s a local-first Electron app that turns the same agent CLIs — Claude Code, Codex, Antigravity, OpenCode, Crush, pi.dev, and GitHub Copilot CLI — into a <strong>coordinated office</strong>. Each agent is a real CLI process in its own pseudo-terminal and isolated worktree (same isolation idea as Orca — we’ve written about <a href="/blog/claude-code-git-worktrees-vs-hive/">how worktrees and the hive fit together</a>), visualized as an affectionate parody of The Office cast on a pixel-art floor. The differences stack up above that:</p>
@@ -185,6 +186,7 @@
<li>Autonomy is bounded by <strong>guardrails</strong>: <a href="/blog/human-in-the-loop-approving-ai-agents/">human approval gates</a> on spend, scope, and destructive operations; per-agent token budgets; a cost/runaway circuit breaker; and OpenTelemetry observability with real per-agent cost attribution.</li>
</ul>
<p>v0.3.3 did add a built-in Monaco IDE — file tree, tabs, side-by-side diffs vs HEAD — but let’s be honest about what it’s for: it’s a <strong>review surface for what your agents changed</strong>, not a place you live. Orca’s editing experience is deeper. Munder Difflin’s bet is that you’ll spend less time in an editor at all, because the office handles the routing, memory, and follow-through that would otherwise pull you back to the keyboard.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/orca-vs-munder-difflin/note-2.png" alt="Hand-drawn sketch from “Orca vs Munder Difflin: Agent IDE or Agent Office?”" loading="lazy" decoding="async" /></figure>
<h2 id="the-boundary-drawn-plainly" tabindex="-1">The boundary, drawn plainly <a class="anchor" href="#the-boundary-drawn-plainly" aria-hidden="true">#</a></h2>
<table>
<thead>
diff --git a/docs/blog/overnight-ai-coding-realistic-expectations/index.html b/docs/blog/overnight-ai-coding-realistic-expectations/index.html
index 3a4dd556..421af6a9 100644
--- a/docs/blog/overnight-ai-coding-realistic-expectations/index.html
+++ b/docs/blog/overnight-ai-coding-realistic-expectations/index.html
@@ -199,6 +199,7 @@ nobody anticipated. The right move here isn’t “guess confidently” — it
</ul>
<p>Notice the pattern: the failures aren’t about raw capability. They’re about <strong>scope and judgment</strong>. The
fix isn’t a smarter model; it’s a better setup.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/overnight-ai-coding-realistic-expectations/note-1.png" alt="Hand-drawn sketch from “Overnight AI Coding: What's Realistic (and What's Not)”" loading="lazy" decoding="async" /></figure>
<h2 id="the-guardrails-that-make-overnight-work-safe" tabindex="-1">The guardrails that make overnight work safe <a class="anchor" href="#the-guardrails-that-make-overnight-work-safe" aria-hidden="true">#</a></h2>
<p>Unattended doesn’t have to mean ungoverned. The difference between “wake up to progress” and “wake up
to a mess” is a handful of guardrails — and they’re the same ones a good
@@ -235,6 +236,7 @@ for you. Default the ambiguous cases to “ask.”</li>
<li><strong>Leave breadcrumbs for morning-you.</strong> Make sure there’s a log and a short status per task. You’re
optimizing your <em>review time</em>, not just the agents’ run time.</li>
</ol>
+<figure class="fig fig-inline"><img src="/blog/assets/media/overnight-ai-coding-realistic-expectations/note-2.png" alt="Hand-drawn sketch from “Overnight AI Coding: What's Realistic (and What's Not)”" loading="lazy" decoding="async" /></figure>
<h2 id="what-still-needs-you-in-the-morning" tabindex="-1">What still needs you in the morning <a class="anchor" href="#what-still-needs-you-in-the-morning" aria-hidden="true">#</a></h2>
<p>This is the part the slogans skip. Overnight agents change <em>when</em> the work happens, not <em>whether you’re
accountable for it</em>. You still:</p>
@@ -314,50 +316,50 @@ work on isolated branches, escalate the decisions that matter, and leave a reada
<h2>Related in Use Cases</h2>
<div class="post-grid">
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/deploy-a-blog-writer-agent/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deploy-a-blog-writer-agent/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-10">Jun 10, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>3 min</span>
</div>
- <h3><a href="/blog/deploy-a-blog-writer-agent/">Deploy a Blog-Writer Agent: The One That Wrote This Post</a></h3>
- <p class="dek">How Munder Difflin&#39;s blog is written by an automated writer agent in the hive — drafts in a worktree, single-committer integration, Eleventy build, human-gated deploy. Build your own.</p>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/deploy-a-blog-writer-agent/" aria-label="Read: Deploy a Blog-Writer Agent: The One That Wrote This Post">Read →</a>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/from-one-terminal-to-a-team/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/from-one-terminal-to-a-team/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-02">Jun 2, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>3 min</span>
</div>
- <h3><a href="/blog/from-one-terminal-to-a-team/">From One Terminal to a Team: Scaling Your Claude Code Workflow</a></h3>
- <p class="dek">The workflow shift from a single Claude Code session to a coordinated team of agents — what changes, where it breaks, and the concrete before-and-after.</p>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/from-one-terminal-to-a-team/" aria-label="Read: From One Terminal to a Team: Scaling Your Claude Code Workflow">Read →</a>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/run-an-office-of-ai-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-an-office-of-ai-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-02">Jun 2, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>3 min</span>
</div>
- <h3><a href="/blog/run-an-office-of-ai-agents/">Run an Office of AI Agents While You Sleep</a></h3>
- <p class="dek">What it takes to run a self-coordinating office of AI coding agents that keeps shipping after you log off — and the guardrails that keep it sane.</p>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/run-an-office-of-ai-agents/" aria-label="Read: Run an Office of AI Agents While You Sleep">Read →</a>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/prompt-caching-for-ai-agents/index.html b/docs/blog/prompt-caching-for-ai-agents/index.html
index 1f8d8004..8e9f614d 100644
--- a/docs/blog/prompt-caching-for-ai-agents/index.html
+++ b/docs/blog/prompt-caching-for-ai-agents/index.html
@@ -198,6 +198,7 @@ because the expensive prefix didn’t have to be reprocessed.</li>
turn. For a one-shot call that never repeats, caching isn’t worth the write premium. For an <em>agent</em> —
which repeats the same prefix constantly — it’s close to a no-brainer. The break-even is usually just
two or three reuses, and agents reuse far more than that.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/prompt-caching-for-ai-agents/note-1.png" alt="Hand-drawn sketch from “Prompt Caching for AI Agents: Stop Paying for the Same Tokens Twice”" loading="lazy" decoding="async" /></figure>
<h2 id="the-one-rule-stable-first-volatile-last" tabindex="-1">The one rule: stable first, volatile last <a class="anchor" href="#the-one-rule-stable-first-volatile-last" aria-hidden="true">#</a></h2>
<p>Caches match on an <strong>exact prefix</strong>. The provider walks your prompt from the start and reuses the cache
up to the first byte that differs. Everything after that point is reprocessed and re-priced. That single
@@ -233,6 +234,7 @@ re-write cost as the price of the pause.</li>
<a href="/blog/human-in-the-loop-ai-agents/">human-in-the-loop checkpoints</a> should be rare and high-signal,
not sprinkled everywhere.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/prompt-caching-for-ai-agents/note-2.png" alt="Hand-drawn sketch from “Prompt Caching for AI Agents: Stop Paying for the Same Tokens Twice”" loading="lazy" decoding="async" /></figure>
<h2 id="the-multi-agent-angle" tabindex="-1">The multi-agent angle <a class="anchor" href="#the-multi-agent-angle" aria-hidden="true">#</a></h2>
<p>In a single agent, caching is a per-session win. In a <a href="/blog/coordinating-ai-coding-agents/">hive</a> it
compounds, because many agents share structure. If your agents are built from the <strong>same system-prompt
diff --git a/docs/blog/qm-vs-munder-difflin/index.html b/docs/blog/qm-vs-munder-difflin/index.html
index 76a836f9..0de1766b 100644
--- a/docs/blog/qm-vs-munder-difflin/index.html
+++ b/docs/blog/qm-vs-munder-difflin/index.html
@@ -227,6 +227,7 @@ memory, and background work runs as <strong>scheduled missions</strong> with Sla
</tr>
</tbody>
</table>
+<figure class="fig fig-inline"><img src="/blog/assets/media/qm-vs-munder-difflin/note-1.png" alt="Hand-drawn sketch from “qm vs Munder Difflin: YC's Multiplayer Harness or a Local-First Agent Office?”" loading="lazy" decoding="async" /></figure>
<h2 id="what-each-has-that-the-other-doesnt" tabindex="-1">What each has that the other doesn’t <a class="anchor" href="#what-each-has-that-the-other-doesnt" aria-hidden="true">#</a></h2>
<p><strong>qm’s edge is multiplayer.</strong> One shared harness, unified identity, org-level admin,
skills promotion across scopes. If your team wants a <em>single</em> fleet everyone shares from
@@ -248,6 +249,7 @@ memory live on your machine.</li>
<li><strong>A longer release train.</strong> Public releases since v0.2.0, now at v0.3.5, with the
reliability work battle-tested by a growing contributor community.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/qm-vs-munder-difflin/note-2.png" alt="Hand-drawn sketch from “qm vs Munder Difflin: YC's Multiplayer Harness or a Local-First Agent Office?”" loading="lazy" decoding="async" /></figure>
<h2 id="which-should-you-use" tabindex="-1">Which should you use? <a class="anchor" href="#which-should-you-use" aria-hidden="true">#</a></h2>
<ul>
<li><strong>Your whole team wants one shared fleet with org-level control → qm.</strong> That’s what
diff --git a/docs/blog/recovering-from-agent-failures/index.html b/docs/blog/recovering-from-agent-failures/index.html
index cf6f6f36..077e230f 100644
--- a/docs/blog/recovering-from-agent-failures/index.html
+++ b/docs/blog/recovering-from-agent-failures/index.html
@@ -196,6 +196,7 @@ older than ten seconds is from a committer that died, so it’s safe to remove
wedge the repo forever. And <strong>graceful give-up:</strong> a non-lock error doesn’t throw or block; it returns,
because the <em>next</em> mutation will stage and commit the same pending changes anyway. Nothing is lost by
bailing early.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/recovering-from-agent-failures/note-1.png" alt="Hand-drawn sketch from “Recovering From Agent Failures: Resilience Patterns for a Hive”" loading="lazy" decoding="async" /></figure>
<h2 id="dont-choke-on-a-poison-message" tabindex="-1">Don’t choke on a poison message <a class="anchor" href="#dont-choke-on-a-poison-message" aria-hidden="true">#</a></h2>
<p>A file-based mailbox will eventually contain a half-written or malformed JSON file. The naive router
reads it, throws, and — if it retries the same file — spins on it forever. The fix is to <strong>quarantine</strong>:</p>
@@ -220,6 +221,7 @@ backstop. Every message carries a <strong>hop count</strong>, and the router dro
<p>It’s deliberately blunt: it guarantees the conversation terminates. And because the drop is <em>logged</em>, a
runaway leaves a breadcrumb instead of a silent hang — you can read the log and see exactly which thread
ran away.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/recovering-from-agent-failures/note-2.png" alt="Hand-drawn sketch from “Recovering From Agent Failures: Resilience Patterns for a Hive”" loading="lazy" decoding="async" /></figure>
<h2 id="idempotent-by-construction" tabindex="-1">Idempotent by construction <a class="anchor" href="#idempotent-by-construction" aria-hidden="true">#</a></h2>
<p>The cheapest way to survive duplicates and replays is to make re-handling a no-op. In the hive, an agent
moves a message to <code>inbox/.done/</code> once it’s handled, and the protocol is explicit: <em>re-reading a message
@@ -305,6 +307,22 @@ there to read.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -336,22 +354,6 @@ there to read.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/rendering-many-live-terminals-performance/index.html b/docs/blog/rendering-many-live-terminals-performance/index.html
index 584f0c96..5d54307f 100644
--- a/docs/blog/rendering-many-live-terminals-performance/index.html
+++ b/docs/blog/rendering-many-live-terminals-performance/index.html
@@ -196,6 +196,7 @@ terminal is populated and visible <em>immediately</em>, with no repaint.</li>
<p>This single change fixes both naive problems: no per-switch teardown (no thrash) and no empty buffer
(no blank pane). It’s the structural decision everything else builds on — the same pool pattern at the
center of <a href="/blog/building-a-terminal-ui-xterm-node-pty/">building a terminal UI with xterm.js and node-pty</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/rendering-many-live-terminals-performance/note-1.png" alt="Hand-drawn sketch from “Rendering Many Live Terminals Without Melting the CPU”" loading="lazy" decoding="async" /></figure>
<h2 id="technique-2-render-only-whats-visible" tabindex="-1">Technique 2 — Render only what’s visible <a class="anchor" href="#technique-2-render-only-whats-visible" aria-hidden="true">#</a></h2>
<p>A pool keeps every session’s <em>buffer</em> current, but you don’t need to <em>paint</em> every terminal every
frame. Only the terminal(s) actually on screen need to be laid out and rendered; the rest keep
@@ -227,6 +228,7 @@ render scheduling rather than forcing a refresh per byte.</li>
</ul>
<p>These come straight from how the <a href="/blog/node-pty-electron-real-terminals/">node-pty terminal plane</a>
streams to the UI.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/rendering-many-live-terminals-performance/note-2.png" alt="Hand-drawn sketch from “Rendering Many Live Terminals Without Melting the CPU”" loading="lazy" decoding="async" /></figure>
<h2 id="technique-5-reach-for-an-accelerated-renderer-when-needed" tabindex="-1">Technique 5 — Reach for an accelerated renderer when needed <a class="anchor" href="#technique-5-reach-for-an-accelerated-renderer-when-needed" aria-hidden="true">#</a></h2>
<p>xterm’s default DOM renderer is fine for a handful of terminals. When you’re rendering many
high-throughput streams, an accelerated rendering addon (canvas/WebGL) moves the drawing off the DOM
@@ -308,6 +310,22 @@ to run many real terminals without melting your CPU; it’s free and open source
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -339,22 +357,6 @@ to run many real terminals without melting your CPU; it’s free and open source
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/review-agent-work-where-it-happens/index.html b/docs/blog/review-agent-work-where-it-happens/index.html
index c66a53e6..13dbbaeb 100644
--- a/docs/blog/review-agent-work-where-it-happens/index.html
+++ b/docs/blog/review-agent-work-where-it-happens/index.html
@@ -167,6 +167,7 @@
<p>The default answer is “open the repo in your editor.” It works, and it’s also quietly terrible for this job.</p>
<p>When you supervise agents, you’re running a loop: watch the floor, read an escalation, check what an agent changed, answer, move on. Every hop out to an external editor breaks that loop. You alt-tab, find the right window, find the right worktree (each agent has its own), pull up a diff, and by the time you’ve read it, the context that prompted the check — which agent, which task, what it claimed — has evaporated. Then you tab back and reconstruct it.</p>
<p>Multiply that by every agent, every task, all day. The cost isn’t the seconds per switch; it’s that switching makes review feel expensive, so you do less of it, so agent work merges less verified than it should. The bottleneck doesn’t just slow you down — it degrades the quality of the supervision itself.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/review-agent-work-where-it-happens/note-1.png" alt="Hand-drawn sketch from “Review Agent Work Where It Happens”" loading="lazy" decoding="async" /></figure>
<h2 id="review-in-place-the-ide-comes-to-the-floor" tabindex="-1">Review-in-place: the IDE comes to the floor <a class="anchor" href="#review-in-place-the-ide-comes-to-the-floor" aria-hidden="true">#</a></h2>
<p>This is the problem the v0.3.3 built-in IDE exists to solve. A title-bar <strong>IDE</strong> button opens a full-window <strong>Monaco</strong> editor — the same editor engine VS Code runs on, fully self-hosted with no CDN — as an overlay on the office floor. The floor, the terminals, and everything else stay untouched underneath; you toggle in, review, toggle out.</p>
<p>The layout is built around the review loop, not general-purpose editing:</p>
@@ -177,6 +178,7 @@
</ul>
<p>The workspace root snapshots from the selected agent’s cwd (falling back to the GOD agent’s, then the first agent’s), so the IDE opens onto the code you were just looking at, not a generic project picker.</p>
<p>One architectural note that matters more than it sounds: <strong>the renderer holds no filesystem or git access.</strong> Every read, diff, and save is brokered through the Electron main process over IPC. The pretty editor window is just a view; the privileged operations happen in one audited place. And a v0.3.3 fix hardened the save path so keystrokes typed while a save is still writing are never silently dropped — a small thing, exactly the kind of small thing that erodes trust in an in-app editor if it’s wrong.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/review-agent-work-where-it-happens/note-2.png" alt="Hand-drawn sketch from “Review Agent Work Where It Happens”" loading="lazy" decoding="async" /></figure>
<h2 id="the-diff-is-only-trustworthy-because-of-how-it-was-made" tabindex="-1">The diff is only trustworthy because of how it was made <a class="anchor" href="#the-diff-is-only-trustworthy-because-of-how-it-was-made" aria-hidden="true">#</a></h2>
<p>A side-by-side diff vs HEAD is only useful if HEAD means something. In a naive multi-agent setup — several agents committing to one repo — it doesn’t: histories interleave, <code>index.lock</code> collisions corrupt state, and “what did agent B change” has no clean answer.</p>
<p>Munder Difflin avoids this with two structural choices. For the shared hive, <strong>no agent ever touches git</strong>: agents write plain files to their <code>outbox/</code>, the router delivers mail, and a single harness-owned committer performs every git operation — the <a href="/blog/single-committer-git-pattern/">single-committer git pattern</a>, which trades a theoretical bottleneck for a serialized, corruption-free, auditable history. For code, <strong>each agent gets its own isolated worktree</strong> (see <a href="/blog/claude-code-git-worktrees-vs-hive/">worktrees vs the hive</a>), so the diff you review is one agent’s coherent work, not a merge puzzle.</p>
diff --git a/docs/blog/run-a-mixed-engine-office/index.html b/docs/blog/run-a-mixed-engine-office/index.html
index 330e281c..6998ed4e 100644
--- a/docs/blog/run-a-mixed-engine-office/index.html
+++ b/docs/blog/run-a-mixed-engine-office/index.html
@@ -173,6 +173,7 @@
<li><strong>GitHub Copilot CLI</strong> — new in <a href="/blog/launching-munder-difflin-v0-3-3/">v0.3.3</a>, the first community-contributed engine (PR #101). Runs in documented print mode (<code>copilot -p</code>) with a model picker and <code>--resume</code>, authenticated by your existing Copilot login.</li>
</ul>
<p>One honest caveat up front: Copilot’s print mode exits per turn and has no hook bridge, so its workers can’t drain hive inbox mail — routed mail bounces to the orchestrator instead of disappearing. That’s by design, and it tells you exactly where Copilot desks belong.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-a-mixed-engine-office/note-1.png" alt="Hand-drawn sketch from “Run a Mixed-Engine Office: the Right CLI for Every Desk”" loading="lazy" decoding="async" /></figure>
<h2 id="the-layout-that-works" tabindex="-1">The layout that works <a class="anchor" href="#the-layout-that-works" aria-hidden="true">#</a></h2>
<p><strong>Michael’s office: Claude Code.</strong> The orchestrator reads every request, adjudicates traffic, scribes the blackboard, and escalates only critical items to you. That’s sustained, stateful, judgment-heavy work — give it the engine with native hooks and the tightest harness integration. (Michael’s engine is swappable from onboarding or the change-engine flow if you want to experiment; OpenCode, Crush, and pi.dev are all god-eligible, backstopped by a provider-agnostic idle fallback.)</p>
<p><strong>Senior desks: Claude Code or Antigravity, hive-aware.</strong> Work that involves conversation — replying to routed messages, coordinating with other agents, long multi-step missions — needs engines that drain a mailbox. These are your closers.</p>
@@ -183,6 +184,7 @@
<p>All the credentials for the BYOK trio live in one panel. <strong>Settings → AI Engines</strong> collects per-provider API keys — Anthropic, OpenAI, Google, OpenRouter, Groq — stored <strong>write-only</strong> in the encrypted secret broker. They’re never read back into the renderer; the main process materializes them into the environment only at spawn. The same panel takes per-engine <strong>local base-URLs</strong> (Ollama, LM Studio, vLLM) and default-model fields, which OpenCode, Crush, and pi.dev pick up automatically.</p>
<p>Then hire. In Add Agent, choosing a local-capable engine surfaces <strong>OSS-model quick-picks</strong>: a <em>Local</em> bucket of Mac-runnable Ollama tags (gpt-oss 20B/120B, Qwen3, DeepSeek-R1, Mistral Small, Llama 3.3 70B) and a <em>third-party OSS provider</em> bucket via Groq or OpenRouter. Click one and it fills the engine-correct slug — <code>local/&lt;tag&gt;</code> for OpenCode, <code>ollama/&lt;tag&gt;</code> for Crush and pi — and rebuilds the spawn command. If the engine’s CLI binary is missing, the harness runs its installer in the terminal and auto restart-and-continues into the fresh binary. No dead-ends.</p>
<p>The full local-model walkthrough is in <a href="/blog/run-munder-difflin-on-open-models/">run Munder Difflin on open models</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-a-mixed-engine-office/note-2.png" alt="Hand-drawn sketch from “Run a Mixed-Engine Office: the Right CLI for Every Desk”" loading="lazy" decoding="async" /></figure>
<h2 id="keeping-the-mixed-floor-affordable-and-sane" tabindex="-1">Keeping the mixed floor affordable and sane <a class="anchor" href="#keeping-the-mixed-floor-affordable-and-sane" aria-hidden="true">#</a></h2>
<p>A mixed floor is a cost instrument, but only if you can see and cap what each desk spends. Munder Difflin gives every agent a <strong>token budget</strong> with live fleet monitoring, real token and cost telemetry per agent per session, and a <strong>circuit breaker</strong> that steers, constrains, then stops any agent that loops or blows its budget. The expensive Claude Code desks carry tight scopes; the local desks can grind all night for electricity. The routing logic — which work deserves which price — is the whole subject of <a href="/blog/the-multi-agent-cost-playbook/">the multi-agent cost playbook</a>.</p>
<p>Isolation keeps them from colliding: each hire gets its own pseudo-terminal and, with the git-isolation toggle, its own worktree — seven engines, zero branch fights.</p>
diff --git a/docs/blog/run-a-release-train-with-agents/index.html b/docs/blog/run-a-release-train-with-agents/index.html
new file mode 100644
index 00000000..cdc52a43
--- /dev/null
+++ b/docs/blog/run-a-release-train-with-agents/index.html
@@ -0,0 +1,379 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Run a Release Train with Agents — Munder Difflin Blog</title>
+<meta name="description" content="Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week." />
+<link rel="canonical" href="https://munderdiffl.in/blog/run-a-release-train-with-agents/" />
+
+<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="Run a Release Train with Agents — Munder Difflin Blog" />
+<meta property="og:description" content="Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week." />
+<meta property="og:url" content="https://munderdiffl.in/blog/run-a-release-train-with-agents/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Use Cases" />
+<meta property="article:tag" content="Release" />
+<meta property="article:tag" content="Workflow" />
+<meta property="article:tag" content="Automation" />
+<meta property="article:tag" content="Multi-Agent" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Run a Release Train with Agents — Munder Difflin Blog" />
+<meta name="twitter:description" content="Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "Run a Release Train with Agents",
+ "description": "Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/run-a-release-train-with-agents/" },
+ "keywords": "automate releases with ai agents, release automation workflow, ai changelog generation, release notes automation, ship faster open source, munder difflin workflow",
+ "articleSection": "Use Cases",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/run-a-release-train-with-agents/"
+}
+</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": "Run a Release Train with Agents", "item": "https://munderdiffl.in/blog/run-a-release-train-with-agents/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "What release chores can agents take over?", "acceptedAnswer": { "@type": "Answer", "text": "The synchronization work: bumping versions everywhere they appear, writing the changelog entry from the actual merged diffs, drafting human-readable release notes, updating the website's version strings and download links, and checking that every link and version reference agrees. Humans stay on the judgment calls — what ships, and whether the notes tell the truth." } },
+ { "@type": "Question", "name": "How do you stop version references drifting apart?", "acceptedAnswer": { "@type": "Answer", "text": "Two layers: an agent whose checklist includes every known surface (changelog, README badge, site, llms.txt, release page), and a guard script in CI that fails the build when a reference drifts. The script exists because an agent-run audit found our llms.txt advertising a version two releases stale — automation found it, a test now prevents it." } },
+ { "@type": "Question", "name": "Does this replace release engineering?", "acceptedAnswer": { "@type": "Answer", "text": "No — it replaces release chores. The decisions (what's in, what's blocked, when to cut) stay human. What the agents remove is the hour of mechanical synchronization per release that otherwise gets skipped, which is exactly how version drift and stale notes happen." } }
+
+ ]
+}
+</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,
+ 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-use-cases">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/use-cases/">Use Cases</a>
+ </nav>
+ <h1>Run a Release Train with Agents</h1>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>3 min read</span>
+ <span class="tag kind">Use Cases</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/run-a-release-train-with-agents/hero.png" alt="Illustration: Run a Release Train with Agents" 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 release is one decision and forty
+chores. During our <a href="/blog/seven-releases-in-eight-days/">seven-releases-in-eight-days
+week</a>, the chores — version bumps, changelog prose, release notes, site updates, link
+checks — ran as a repeatable agent workflow. The decision stayed human. That's the whole
+trick, and here's the train schedule.</p></div>
+<p>Everyone’s release process degrades the same way. Release one: meticulous. Release five: the
+changelog says “misc fixes.” Release nine: the README badge is two versions behind and the
+website’s FAQ names a plan that doesn’t exist. Not because anyone stopped caring — because
+synchronization chores scale linearly with surfaces, and humans under deadline cut exactly
+those corners.</p>
+<p>We shipped seven releases in eight days without (we think) shipping that decay, and the reason
+is that the chores are a train the <a href="/blog/what-is-a-multi-agent-harness/">hive</a> runs on rails.</p>
+<h2 id="the-train-car-by-car" tabindex="-1">The train, car by car <a class="anchor" href="#the-train-car-by-car" aria-hidden="true">#</a></h2>
+<p><strong>Car 1: the changelog entry, from evidence.</strong> An agent reads the actual merged commits and
+PRs since the last tag — not a memory of them — and drafts the changelog entry with a hard
+rule we stole from our own postmortems: <em>every entry says what was broken from the user’s point
+of view, not which function changed.</em> “Agents booted, looked healthy, and had no idea they
+could message anyone” survives to <a href="/blog/launching-munder-difflin-v0-4-4/">the published
+changelog</a> because the draft started from the diff and
+the issue thread, where that sentence was earned.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-a-release-train-with-agents/note-1.png" alt="Hand-drawn sketch from “Run a Release Train with Agents”" loading="lazy" decoding="async" /><figcaption>The changelog agent works from merged diffs and issue threads — not from anyone's memory of the week.</figcaption></figure>
+<p><strong>Car 2: version references, everywhere.</strong> The version string lives in more places than you
+think: package manifest, changelog header, README badge, the website, the release page,
+<code>llms.txt</code>. One agent’s checklist is simply: find every reference, update every reference,
+<em>then list where it looked</em> so omissions are visible. This car exists because an audit found
+our <code>llms.txt</code> advertising a version two releases stale — nobody had ever put it on a mental
+checklist.</p>
+<p><strong>Car 3: release notes for humans.</strong> The changelog is the record; the release notes are the
+story. A second pass rewrites the entry in plain language — what you’ll notice, what you need
+to do (usually nothing, <a href="/blog/why-our-auto-update-never-ran/">the app updates itself</a>) — and
+since 0.4.4 can even ship as a designed page rendered inside the app. <strong>This is also where
+contributors get credited by name, every release, without fail</strong> — @gts-47’s eight PRs and
+@baziyer’s rendering fix headline the 0.4.4 thanks because an agent’s checklist said <em>find
+every community PR in this release and name its author</em>, and checklists don’t get shy.</p>
+<p><strong>Car 4: the guard rail.</strong> The best part of agent-run chores: when an agent finds a drift
+class once, you make it impossible instead of remembered. A small link-and-version checker now
+runs in CI and fails the build if any known surface disagrees about the current version. The
+train doesn’t rely on the conductor’s attention anymore.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-a-release-train-with-agents/note-2.png" alt="Hand-drawn sketch from “Run a Release Train with Agents”" loading="lazy" decoding="async" /><figcaption>Find the drift once, then make it a failing test. The train stops relying on anyone's attention.</figcaption></figure>
+<h2 id="why-agents-fit-this-shape-of-work" tabindex="-1">Why agents fit this shape of work <a class="anchor" href="#why-agents-fit-this-shape-of-work" aria-hidden="true">#</a></h2>
+<p>Release chores are the ideal agent workload for three reasons. They’re <strong>evidence-based</strong> — the
+truth is in the diff, the tag, and the file, so <a href="/blog/how-ai-agents-verify-their-own-work/">verification is
+mechanical</a>. They’re <strong>checklist-shaped</strong> — the same
+surfaces every time, which agents execute with the enthusiasm humans reserve for release one.
+And they’re <strong>interruptible</strong> — each car produces reviewable artifacts (a draft entry, a list
+of touched files), so the human can inspect the train at any station.</p>
+<p>Note what’s <em>not</em> on the train: deciding what ships, judging whether a fix is real, choosing
+what the headline is. During our eight-day week those calls happened in minutes precisely
+because the chores weren’t competing for the same attention.</p>
+<h2 id="set-up-your-own" tabindex="-1">Set up your own <a class="anchor" href="#set-up-your-own" aria-hidden="true">#</a></h2>
+<p>The portable version, whatever your stack:</p>
+<ol>
+<li><strong>Write the checklist down once</strong> — every file that mentions a version, every step between
+tag and announcement. This document <em>is</em> the agent brief.</li>
+<li><strong>Point agents at evidence</strong> — diffs, merged PRs, closed issues. Ban writing from memory.</li>
+<li><strong>Route it through one dispatcher</strong> so the cars run in order —
+<a href="/blog/how-to-talk-to-your-orchestrator/">that’s what an orchestrator is for</a>.</li>
+<li><strong>Convert discoveries into CI guards.</strong> An agent finding drift is good; a test that makes
+the drift impossible is the actual win.</li>
+</ol>
+<p>Our cadence didn’t come from typing faster. It came from making releases cost one decision
+instead of one afternoon — and from a train that <a href="/blog/scheduling-autonomous-agent-missions/">runs on
+schedule</a> even when the humans are asleep.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">What release chores can agents take over?</p>
+ <p class="a">The synchronization work: bumping versions everywhere they appear, writing the changelog entry from the actual merged diffs, drafting human-readable release notes, updating the website&#39;s version strings and download links, and checking that every link and version reference agrees. Humans stay on the judgment calls — what ships, and whether the notes tell the truth.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">How do you stop version references drifting apart?</p>
+ <p class="a">Two layers: an agent whose checklist includes every known surface (changelog, README badge, site, llms.txt, release page), and a guard script in CI that fails the build when a reference drifts. The script exists because an agent-run audit found our llms.txt advertising a version two releases stale — automation found it, a test now prevents it.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Does this replace release engineering?</p>
+ <p class="a">No — it replaces release chores. The decisions (what&#39;s in, what&#39;s blocked, when to cut) stay human. What the agents remove is the hour of mechanical synchronization per release that otherwise gets skipped, which is exactly how version drift and stale notes happen.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/use-cases/">Use Cases</a><a class="tag" href="/blog/tags/release/">Release</a><a class="tag" href="/blog/tags/workflow/">Workflow</a><a class="tag" href="/blog/tags/automation/">Automation</a><a class="tag" href="/blog/tags/multi-agent/">Multi-Agent</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-train-car-by-car">The train, car by car</a></li><li class="lvl-2"><a href="#why-agents-fit-this-shape-of-work">Why agents fit this shape of work</a></li><li class="lvl-2"><a href="#set-up-your-own">Set up your own</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/seven-releases-in-eight-days/"><span class="k">← Older</span><span class="t">Seven Releases in Eight Days: 0.3.8 → 0.4.4</span></a>
+ <a class="pn next" href="/blog/number-five-on-product-hunt/"><span class="k">Newer →</span><span class="t">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</span></a>
+ </div>
+ <section class="related">
+ <h2>Related in Use Cases</h2>
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/run-ai-agent-hive-from-slack-setup/index.html b/docs/blog/run-ai-agent-hive-from-slack-setup/index.html
index 6f141fe7..ab84cfe7 100644
--- a/docs/blog/run-ai-agent-hive-from-slack-setup/index.html
+++ b/docs/blog/run-ai-agent-hive-from-slack-setup/index.html
@@ -216,6 +216,7 @@ the signing secret, it stays in the app’s main process and is never logged.</p
<p>Keep both values handy. You’ll paste them into Munder Difflin next, then come back to finish Event
Subscriptions.</p>
</blockquote>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-ai-agent-hive-from-slack-setup/note-1.png" alt="Hand-drawn sketch from “Run Your AI Agent Hive from Slack: The Complete Setup”" loading="lazy" decoding="async" /></figure>
<h2 id="part-2-configure-munder-difflin" tabindex="-1">Part 2 — Configure Munder Difflin <a class="anchor" href="#part-2-configure-munder-difflin" aria-hidden="true">#</a></h2>
<p>Open Munder Difflin and go to <strong>Settings</strong>. In the Slack section:</p>
<ol>
@@ -262,6 +263,7 @@ subtype — so it never talks to itself and never reacts to channel noise.</p>
<p>The message lands in the queue, GOD routes it, and an agent picks it up. Keep the conversation going by
replying in that same thread — the hive is still listening. When the task is done, a summary appears
right there in the thread.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-ai-agent-hive-from-slack-setup/note-2.png" alt="Hand-drawn sketch from “Run Your AI Agent Hive from Slack: The Complete Setup”" loading="lazy" decoding="async" /></figure>
<h2 id="troubleshooting-the-request-url-rotates-on-restart" tabindex="-1">Troubleshooting: the Request URL rotates on restart <a class="anchor" href="#troubleshooting-the-request-url-rotates-on-restart" aria-hidden="true">#</a></h2>
<p>Here’s the one quirk worth tattooing on the back of your hand. <strong>The public Request URL comes from an
ephemeral tunnel, and it changes every time the app restarts.</strong> So if Slack suddenly stops triggering
diff --git a/docs/blog/run-an-office-of-ai-agents/index.html b/docs/blog/run-an-office-of-ai-agents/index.html
index f44bc7be..0d2dff80 100644
--- a/docs/blog/run-an-office-of-ai-agents/index.html
+++ b/docs/blog/run-an-office-of-ai-agents/index.html
@@ -159,6 +159,7 @@ share a memory of the project so nobody re-learns what’s already known. You ca
close the laptop and check the morning’s progress over coffee.</p>
<p>That’s not a metaphor for Munder Difflin — it’s literally <a href="/#how">the office floor</a>. But the picture
only works because of what’s underneath it.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-an-office-of-ai-agents/note-1.png" alt="Hand-drawn sketch from “Run an Office of AI Agents While You Sleep”" loading="lazy" decoding="async" /></figure>
<h2 id="what-makes-it-actually-work" tabindex="-1">What makes it actually work <a class="anchor" href="#what-makes-it-actually-work" aria-hidden="true">#</a></h2>
<p>A self-running office isn’t “point agents at a repo and hope.” Four pieces carry the weight:</p>
<h3 id="roles" tabindex="-1">Roles <a class="anchor" href="#roles" aria-hidden="true">#</a></h3>
@@ -176,6 +177,7 @@ it’s what lets work flow while you’re away.</p>
<p>This is the part the fantasy skips. Unattended agents need a <a href="/#why">human-in-the-loop</a> line: routine
work proceeds, but the risky stuff — spending real money, destructive operations, big scope changes —
queues for your approval. You wake up to <em>progress</em>, not surprises.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-an-office-of-ai-agents/note-2.png" alt="Hand-drawn sketch from “Run an Office of AI Agents While You Sleep”" loading="lazy" decoding="async" /></figure>
<h2 id="whats-realistic-and-what-isnt" tabindex="-1">What’s realistic (and what isn’t) <a class="anchor" href="#whats-realistic-and-what-isnt" aria-hidden="true">#</a></h2>
<p>Honesty matters here, because over-promising is how people get burned:</p>
<ul>
@@ -230,50 +232,50 @@ open source.</p>
<h2>Related in Use Cases</h2>
<div class="post-grid">
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/deploy-a-blog-writer-agent/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deploy-a-blog-writer-agent/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-10">Jun 10, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>3 min</span>
</div>
- <h3><a href="/blog/deploy-a-blog-writer-agent/">Deploy a Blog-Writer Agent: The One That Wrote This Post</a></h3>
- <p class="dek">How Munder Difflin&#39;s blog is written by an automated writer agent in the hive — drafts in a worktree, single-committer integration, Eleventy build, human-gated deploy. Build your own.</p>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/deploy-a-blog-writer-agent/" aria-label="Read: Deploy a Blog-Writer Agent: The One That Wrote This Post">Read →</a>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/overnight-ai-coding-realistic-expectations/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/overnight-ai-coding-realistic-expectations/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-04">Jun 4, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
+ <span>3 min</span>
</div>
- <h3><a href="/blog/overnight-ai-coding-realistic-expectations/">Overnight AI Coding: What&#39;s Realistic (and What&#39;s Not)</a></h3>
- <p class="dek">An honest look at letting AI coding agents run overnight — what works today, where guardrails matter, and what still needs a human in the morning.</p>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/overnight-ai-coding-realistic-expectations/" aria-label="Read: Overnight AI Coding: What&#39;s Realistic (and What&#39;s Not)">Read →</a>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/from-one-terminal-to-a-team/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/from-one-terminal-to-a-team/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-02">Jun 2, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>3 min</span>
</div>
- <h3><a href="/blog/from-one-terminal-to-a-team/">From One Terminal to a Team: Scaling Your Claude Code Workflow</a></h3>
- <p class="dek">The workflow shift from a single Claude Code session to a coordinated team of agents — what changes, where it breaks, and the concrete before-and-after.</p>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/from-one-terminal-to-a-team/" aria-label="Read: From One Terminal to a Team: Scaling Your Claude Code Workflow">Read →</a>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/run-munder-difflin-on-a-mac-mini/index.html b/docs/blog/run-munder-difflin-on-a-mac-mini/index.html
index c34a5097..70e6e987 100644
--- a/docs/blog/run-munder-difflin-on-a-mac-mini/index.html
+++ b/docs/blog/run-munder-difflin-on-a-mac-mini/index.html
@@ -301,6 +301,7 @@ gigabytes, far past any Mac Mini. To use those, skip the local server and point
open-source-model provider (OpenRouter, Groq, DeepInfra, and friends) with an API key — covered in the
<a href="/blog/run-munder-difflin-on-open-models/">open-models guide</a>. For a genuinely local GLM,
<code>glm-4.7-flash</code> (~30B) is the Mac-friendly member of the family.</p></div>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-munder-difflin-on-a-mac-mini/note-1.png" alt="Hand-drawn sketch from “Run Munder Difflin Locally on a Mac Mini”" loading="lazy" decoding="async" /></figure>
<h2 id="step-2-install-a-local-model-server" tabindex="-1">Step 2 — Install a local model server <a class="anchor" href="#step-2-install-a-local-model-server" aria-hidden="true">#</a></h2>
<p>You have two solid options. Both expose an <strong>OpenAI-compatible HTTP endpoint</strong>, which is exactly what
Munder Difflin’s engines target.</p>
@@ -367,6 +368,7 @@ Once a model is served locally, each engine names it slightly differently: OpenC
points at a third-party <code>provider/model</code> slug instead, per the note above.) The exact slugs for
every tier live in the <a href="/blog/run-munder-difflin-on-open-models/">open-source model catalog</a>,
kept in one place so they don't drift.</p></div>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-munder-difflin-on-a-mac-mini/note-2.png" alt="Hand-drawn sketch from “Run Munder Difflin Locally on a Mac Mini”" loading="lazy" decoding="async" /></figure>
<h2 id="step-4-run-the-hive-offline" tabindex="-1">Step 4 — Run the hive offline <a class="anchor" href="#step-4-run-the-hive-offline" aria-hidden="true">#</a></h2>
<p>With a model served locally and the engines pointed at it, the rest of Munder Difflin is already
local-first. Spin up your workers from the <a href="/blog/how-to-install-and-use-munder-difflin/">Agent Gallery or Add Agent</a>,
diff --git a/docs/blog/run-munder-difflin-on-open-models/index.html b/docs/blog/run-munder-difflin-on-open-models/index.html
index b3cb84d4..7459a857 100644
--- a/docs/blog/run-munder-difflin-on-open-models/index.html
+++ b/docs/blog/run-munder-difflin-on-open-models/index.html
@@ -239,6 +239,7 @@
</tbody>
</table>
<p>Default endpoints are the usual ones: Ollama <code>http://localhost:11434/v1</code>, LM Studio <code>http://127.0.0.1:1234/v1</code>, vLLM whatever you exposed (often <code>:8000/v1</code>). You set these in the app — no shell exports required.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-munder-difflin-on-open-models/note-1.png" alt="Hand-drawn sketch from “Run Munder Difflin on Open-Source Models — Fully Local or via a Third-Party Provider”" loading="lazy" decoding="async" /></figure>
<h2 id="path-a-fully-local-ollama-lm-studio-vllm" tabindex="-1">Path A — fully local (Ollama / LM Studio / vLLM) <a class="anchor" href="#path-a-fully-local-ollama-lm-studio-vllm" aria-hidden="true">#</a></h2>
<p>Three steps: pull a model, tell Munder Difflin where it lives, pick it for an agent.</p>
<p><strong>1. Pull a model.</strong> With <a href="https://ollama.com">Ollama</a> installed, grab one sized to your RAM:</p>
@@ -371,6 +372,7 @@ ollama serve <span class="token comment"># exposes the OpenAI-
</tbody>
</table>
<p>Prefer a model maker’s own API? Those work too: DeepSeek (<code>deepseek/deepseek-v4-flash</code>, <code>DEEPSEEK_API_KEY</code>), Mistral (<code>mistral/...</code>, <code>MISTRAL_API_KEY</code>), <a href="http://Z.ai">Z.ai</a> for GLM, Moonshot for Kimi. A couple of moving targets worth knowing as of mid-2026: DeepSeek’s <code>deepseek-chat</code> / <code>deepseek-reasoner</code> aliases retire on 2026-07-24 (wire <code>deepseek-v4-flash</code> directly), and Groq is sunsetting Llama 4 — so on Groq stick to gpt-oss and <code>llama-3.3-70b-versatile</code>. The full slug-by-slug table, with citations and verify-live caveats, lives in the project’s open-model catalog (the single source of truth this post and the Mac Mini guide both cite).</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/run-munder-difflin-on-open-models/note-2.png" alt="Hand-drawn sketch from “Run Munder Difflin on Open-Source Models — Fully Local or via a Third-Party Provider”" loading="lazy" decoding="async" /></figure>
<h2 id="per-engine-cheat-sheet" tabindex="-1">Per-engine cheat-sheet <a class="anchor" href="#per-engine-cheat-sheet" aria-hidden="true">#</a></h2>
<p>You rarely touch these directly — the AI Engines panel writes them — but here’s what each engine does under the hood, so the model field makes sense.</p>
<p><strong>OpenCode</strong> is OpenAI-SDK native and knows most providers out of the box. BYOK is just the env var; local is a custom provider named <code>local</code>. Slugs: <code>openrouter/openai/gpt-oss-120b</code>, <code>local/qwen3:30b-a3b</code>.</p>
diff --git a/docs/blog/scheduling-autonomous-agent-missions/index.html b/docs/blog/scheduling-autonomous-agent-missions/index.html
index 73b24ebc..ecb1c427 100644
--- a/docs/blog/scheduling-autonomous-agent-missions/index.html
+++ b/docs/blog/scheduling-autonomous-agent-missions/index.html
@@ -200,6 +200,7 @@ why it composes so cleanly with the rest of the hive.</p>
<p>This very post is proof. It exists because an <strong>“Hourly Standup” mission</strong> fired: a request, from
<code>scheduler</code>, broadcast to every agent, asking each to report status and pick up work. No one typed that
prompt this hour. The schedule did.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/scheduling-autonomous-agent-missions/note-1.png" alt="Hand-drawn sketch from “Make a Hive Work While You Sleep: Scheduling Autonomous Agent Missions”" loading="lazy" decoding="async" /></figure>
<h2 id="why-lastfiredat-matters" tabindex="-1">Why <code>lastFiredAt</code> matters <a class="anchor" href="#why-lastfiredat-matters" aria-hidden="true">#</a></h2>
<p>The one piece of cleverness worth understanding is <code>lastFiredAt</code>. A naive scheduler would restart every
interval from zero whenever the app reboots or you edit an unrelated mission — so an hourly job could
@@ -231,6 +232,7 @@ blasting an identical instruction at every agent. The orchestrator is built for
<li><strong>Pause with <code>enabled</code>, don’t delete.</strong> Flip <code>enabled: false</code> to stop a mission while keeping its
history and <code>lastFiredAt</code>. You can switch it back on later and the cadence picks up cleanly.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/scheduling-autonomous-agent-missions/note-2.png" alt="Hand-drawn sketch from “Make a Hive Work While You Sleep: Scheduling Autonomous Agent Missions”" loading="lazy" decoding="async" /></figure>
<h2 id="pitfalls-to-avoid" tabindex="-1">Pitfalls to avoid <a class="anchor" href="#pitfalls-to-avoid" aria-hidden="true">#</a></h2>
<ul>
<li><strong>Flooding the hive.</strong> The scheduler will fire as often as you tell it to — restraint is on you. A
diff --git a/docs/blog/security-for-ai-coding-agents/index.html b/docs/blog/security-for-ai-coding-agents/index.html
index db7ac62d..db13aa9f 100644
--- a/docs/blog/security-for-ai-coding-agents/index.html
+++ b/docs/blog/security-for-ai-coding-agents/index.html
@@ -193,6 +193,7 @@ files” that touches a third has flagged its own problem. The same principle ap
agent that only needs to read shouldn’t hold write tokens; one that builds shouldn’t hold deploy keys.</p>
<p>Least privilege also makes review tractable. A tightly-scoped change is one a human (or a peer agent) can
actually check. A sprawling one is where mistakes hide.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/security-for-ai-coding-agents/note-1.png" alt="Hand-drawn sketch from “Security for AI Coding Agents: A Practical Guide”" loading="lazy" decoding="async" /></figure>
<h2 id="treat-everything-an-agent-reads-as-untrusted" tabindex="-1">Treat everything an agent reads as untrusted <a class="anchor" href="#treat-everything-an-agent-reads-as-untrusted" aria-hidden="true">#</a></h2>
<p>This is the part teams miss. An agent reads constantly — files, web pages, issue comments, command output,
and <a href="/blog/atomic-file-mailboxes-for-agents/">messages from other agents</a>. Any of that text can contain
@@ -220,6 +221,7 @@ irreversible step; a person approves it. Everything reversible stays fast and au
genuinely dangerous moves pay the cost of a confirmation. Pair this with agents that
<a href="/blog/how-ai-agents-verify-their-own-work/">verify their own work</a> and re-verify each other’s, and you get
a funnel: cheap automated checks first, scarce human attention last, on the decisions that carry real risk.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/security-for-ai-coding-agents/note-2.png" alt="Hand-drawn sketch from “Security for AI Coding Agents: A Practical Guide”" loading="lazy" decoding="async" /></figure>
<h2 id="keep-the-sensitive-stuff-local" tabindex="-1">Keep the sensitive stuff local <a class="anchor" href="#keep-the-sensitive-stuff-local" aria-hidden="true">#</a></h2>
<p>Every time an agent sends content to an external service, that content may be cached, logged, or indexed —
even if you delete it later. For code, secrets, and proprietary context, the safest default is to keep the
diff --git a/docs/blog/semantic-memory-for-ai-agents/index.html b/docs/blog/semantic-memory-for-ai-agents/index.html
index 8ea03fc4..f0bc4719 100644
--- a/docs/blog/semantic-memory-for-ai-agents/index.html
+++ b/docs/blog/semantic-memory-for-ai-agents/index.html
@@ -190,6 +190,7 @@ relevant notes into context, and acts — instead of either re-reading its whole
note entirely.</p>
<p>The payoff compounds: recall stays <strong>near-instant</strong> and the context window stays <strong>small</strong> even as the
note collection grows into the hundreds. You inject the few notes that matter, not the whole archive.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/semantic-memory-for-ai-agents/note-1.png" alt="Hand-drawn sketch from “Semantic Memory for AI Agents: Recall in Milliseconds”" loading="lazy" decoding="async" /></figure>
<h2 id="why-markdown-first-beats-a-heavyweight-db" tabindex="-1">Why markdown-first beats a heavyweight DB <a class="anchor" href="#why-markdown-first-beats-a-heavyweight-db" aria-hidden="true">#</a></h2>
<p>There’s a strong temptation to reach for a dedicated vector database or a full agent-memory framework.
For a handful of agents, that’s the wrong trade. The more robust foundation is <strong>markdown-first</strong>:
@@ -242,6 +243,7 @@ administer — the index is a companion to the markdown, driven by a command.</p
<p>If the semantic layer isn’t installed at all, none of this errors — it’s a no-op, and agents fall back
to reading their markdown directly. The fast path is an upgrade, not a dependency. That’s the
markdown-first principle paying off: the floor never falls out from under the team.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/semantic-memory-for-ai-agents/note-2.png" alt="Hand-drawn sketch from “Semantic Memory for AI Agents: Recall in Milliseconds”" loading="lazy" decoding="async" /></figure>
<h2 id="how-fast-is-fast" tabindex="-1">How fast is “fast”? <a class="anchor" href="#how-fast-is-fast" aria-hidden="true">#</a></h2>
<p>The “milliseconds” promise is about the <em>experience</em>, and it’s worth being precise. Recall feels
instant because the expensive work — turning notes into vectors — happens ahead of time, during
diff --git a/docs/blog/seven-releases-in-eight-days/index.html b/docs/blog/seven-releases-in-eight-days/index.html
new file mode 100644
index 00000000..3cf779db
--- /dev/null
+++ b/docs/blog/seven-releases-in-eight-days/index.html
@@ -0,0 +1,376 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Seven Releases in Eight Days: 0.3.8 → 0.4.4 — Munder Difflin Blog</title>
+<meta name="description" content="Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour." />
+<link rel="canonical" href="https://munderdiffl.in/blog/seven-releases-in-eight-days/" />
+
+<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="Seven Releases in Eight Days: 0.3.8 → 0.4.4 — Munder Difflin Blog" />
+<meta property="og:description" content="Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour." />
+<meta property="og:url" content="https://munderdiffl.in/blog/seven-releases-in-eight-days/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Story" />
+<meta property="article:tag" content="Release" />
+<meta property="article:tag" content="Open Source" />
+<meta property="article:tag" content="Changelog" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Seven Releases in Eight Days: 0.3.8 → 0.4.4 — Munder Difflin Blog" />
+<meta name="twitter:description" content="Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "Seven Releases in Eight Days: 0.3.8 → 0.4.4",
+ "description": "Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/seven-releases-in-eight-days/" },
+ "keywords": "munder difflin releases, munder difflin changelog, shipping velocity open source, release cadence dev tools, munder difflin 0.4",
+ "articleSection": "Story",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/seven-releases-in-eight-days/"
+}
+</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": "Seven Releases in Eight Days: 0.3.8 → 0.4.4", "item": "https://munderdiffl.in/blog/seven-releases-in-eight-days/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "What shipped in the 0.4.x wave of Munder Difflin?", "acceptedAnswer": { "@type": "Answer", "text": "0.3.8 made memory condensation actually work; 0.3.9 added a check-for-updates panel; 0.4.0 rebuilt the brand and landing page with real screenshots; 0.4.1 renamed the GOD agent to your clone and named all ten engines; 0.4.2 added anonymous, opt-out telemetry with a public contract; 0.4.3 made Michael's portrait the logo; and 0.4.4 fixed agent messaging on Windows and added the skills catalog." } },
+ { "@type": "Question", "name": "Why release so often?", "acceptedAnswer": { "@type": "Answer", "text": "Launch week. Thousands of new people hit the product at once and found things a small user base never would — Windows messaging, onboarding dead-ends, unreadable dark mode. When feedback arrives that fast, batching fixes into a monthly release just means people churn while the fix sits on a branch." } },
+ { "@type": "Question", "name": "Is telemetry in Munder Difflin opt-out or opt-in?", "acceptedAnswer": { "@type": "Answer", "text": "Opt-out, anonymous, and governed by a public contract: TELEMETRY.md lists every event and property, the code enforces that list as a hard allowlist, DO_NOT_TRACK is respected unconditionally, and building from source or forking produces a build with no key — the analytics module becomes a no-op." } }
+
+ ]
+}
+</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,
+ 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-story">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/story/">Story</a>
+ </nav>
+ <h1>Seven Releases in Eight Days: 0.3.8 → 0.4.4</h1>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>4 min read</span>
+ <span class="tag kind">Story</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="Illustration: Seven Releases in Eight Days: 0.3.8 → 0.4.4" 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>August 11 to August 18: <strong>seven
+releases</strong>. A memory system that had been silently reading an empty directory, fixed. An
+update checker. A new face for the whole product. A public telemetry contract. Honest engine
+naming. And the big one — Windows agents that can finally hear each other. Here's the whole
+train, car by car.</p></div>
+<p>Launch week compresses a year of feedback into days. Thousands of people hit first-run at once,
+on machines and configs we’d never seen, and the bug reports came in faster than any roadmap
+could dignify. So the roadmap lost. For eight days we just shipped.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/seven-releases-in-eight-days/note-1.png" alt="Hand-drawn sketch from “Seven Releases in Eight Days: 0.3.8 → 0.4.4”" loading="lazy" decoding="async" /><figcaption>Seven releases, eight days. The kanban wall did not enjoy it as much as we did.</figcaption></figure>
+<h2 id="038-memory-condensation-works-for-the-first-time" tabindex="-1">0.3.8 — memory condensation works for the first time <a class="anchor" href="#038-memory-condensation-works-for-the-first-time" aria-hidden="true">#</a></h2>
+<p>The most embarrassing entry, so it goes first. The harness had been reading Claude Code
+transcripts from a directory that hasn’t existed for months. Nothing errored — an absent
+directory reads exactly like “no transcripts yet” — so <a href="/blog/compressing-agent-memory/">the
+summarizer</a> sat there proudly summarizing nothing. 0.3.8
+pointed it at reality, and stopped compaction firing on two schedules at once while it was in
+there. If your agents’ memories seemed thinner than advertised before mid-August: they were.</p>
+<h2 id="039-am-i-up-to-date-gets-an-answer" tabindex="-1">0.3.9 — “am I up to date?” gets an answer <a class="anchor" href="#039-am-i-up-to-date-gets-an-answer" aria-hidden="true">#</a></h2>
+<p>Settings → General now names your version, says whether it’s the latest, and offers one button
+that does what it says: <strong>Check for updates → Download → Restart to update</strong>. It shares its
+state machine with the toolbar chip so the two can never disagree. Shipped fast for one reason:
+0.3.8 needed to reach people who’d already installed 0.3.7.</p>
+<h2 id="040-and-043-the-brand-grew-up" tabindex="-1">0.4.0 and 0.4.3 — the brand grew up <a class="anchor" href="#040-and-043-the-brand-grew-up" aria-hidden="true">#</a></h2>
+<p>0.4.0 rebuilt <a href="http://munderdiffl.in">munderdiffl.in</a> around the real app — actual screenshots, a live demo loop in the
+hero — and unified the icon across every platform. Then 0.4.3 went further: the logo is now
+<strong>Michael’s pixel-art portrait on the brand yellow</strong>, authored as a single vector, with every
+raster — site, app, all three platform icons — generated from that one source by a script. The
+icons can no longer drift apart, because none of them is hand-made anymore.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/seven-releases-in-eight-days/note-2.png" alt="Hand-drawn sketch from “Seven Releases in Eight Days: 0.3.8 → 0.4.4”" loading="lazy" decoding="async" /><figcaption>One vector, every icon. The logo is now the character the product is about.</figcaption></figure>
+<h2 id="041-the-app-says-what-the-site-says" tabindex="-1">0.4.1 — the app says what the site says <a class="anchor" href="#041-the-app-says-what-the-site-says" aria-hidden="true">#</a></h2>
+<p>Small release, honest release. The site called Michael a clone of you; the app still said “GOD
+agent.” Now <a href="/blog/how-the-god-orchestrator-works/">he’s your clone everywhere</a>, his card says
+<strong>BOSS</strong>, and the engine card names all ten engines — it had been advertising three since before
+the other seven shipped. Words-only releases feel trivial until you count how many people meet
+your product through exactly those words.</p>
+<h2 id="042-telemetry-with-the-contract-in-writing" tabindex="-1">0.4.2 — telemetry, with the contract in writing <a class="anchor" href="#042-telemetry-with-the-contract-in-writing" aria-hidden="true">#</a></h2>
+<p>We had zero insight into whether anyone even launched the app. 0.4.2 adds anonymous usage
+events — and we did it the only way a <a href="/blog/why-local-first-matters-for-ai-agents/">local-first</a>
+project credibly can: <strong><a href="http://TELEMETRY.md">TELEMETRY.md</a></strong> publicly lists every event and property, the code
+enforces that list as a hard allowlist, no prompts or paths or repo names ever leave your
+machine, <code>DO_NOT_TRACK</code> is respected unconditionally, and a fork built from source has no key —
+the entire module becomes a no-op. The toggle is right in onboarding.</p>
+<p>It’s also why this post can contain honest numbers instead of adjectives. As of August 19:
+<strong>2,929 installs, 1,695 people have run at least one agent, and 12,430 agents have been
+spawned.</strong> (Installs, not “users” — download counters lie, install events mostly don’t.)</p>
+<h2 id="044-the-one-windows-was-owed" tabindex="-1">0.4.4 — the one Windows was owed <a class="anchor" href="#044-the-one-windows-was-owed" aria-hidden="true">#</a></h2>
+<p>The finale, and it gets <a href="/blog/launching-munder-difflin-v0-4-4/">its own post</a>: agent-to-agent
+messaging on Windows had been silently broken by a cmd.exe newline quirk, first runs never
+started their own hive services, and dark mode was measurably unreadable. All fixed — plus a
+227-skill catalog, a Prerequisites page, and designed release-note pages. It’s also the release
+where community contributors show up in force: nine PRs from
+<a href="https://github.com/gts-47">@gts-47</a> and <a href="https://github.com/baziyer">@baziyer</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/seven-releases-in-eight-days/note-3.png" alt="Hand-drawn sketch from “Seven Releases in Eight Days: 0.3.8 → 0.4.4”" loading="lazy" decoding="async" /><figcaption>The 0.4.4 finale: Windows agents finally get the whole memo, not just its first line.</figcaption></figure>
+<h2 id="what-the-week-taught-us" tabindex="-1">What the week taught us <a class="anchor" href="#what-the-week-taught-us" aria-hidden="true">#</a></h2>
+<p>Two things. First: <strong>silent failure is the enemy</strong>, not bugs. Almost everything in this train —
+the phantom transcripts, the truncated protocol, the never-started services — failed without a
+single error message. We now treat “nothing errored” as a claim requiring evidence, and we wrote
+<a href="/blog/why-our-auto-update-never-ran/">a whole post on why our auto-update never ran</a> in the
+same spirit.</p>
+<p>Second: release cadence is a form of respect. When someone reports a bug that’s blocking them
+and the fix exists on a branch, every day it doesn’t ship is a day they’re deciding whether to
+uninstall. Seven releases in eight days wasn’t heroics. It was queue processing.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">What shipped in the 0.4.x wave of Munder Difflin?</p>
+ <p class="a">0.3.8 made memory condensation actually work; 0.3.9 added a check-for-updates panel; 0.4.0 rebuilt the brand and landing page with real screenshots; 0.4.1 renamed the GOD agent to your clone and named all ten engines; 0.4.2 added anonymous, opt-out telemetry with a public contract; 0.4.3 made Michael&#39;s portrait the logo; and 0.4.4 fixed agent messaging on Windows and added the skills catalog.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Why release so often?</p>
+ <p class="a">Launch week. Thousands of new people hit the product at once and found things a small user base never would — Windows messaging, onboarding dead-ends, unreadable dark mode. When feedback arrives that fast, batching fixes into a monthly release just means people churn while the fix sits on a branch.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Is telemetry in Munder Difflin opt-out or opt-in?</p>
+ <p class="a">Opt-out, anonymous, and governed by a public contract: TELEMETRY.md lists every event and property, the code enforces that list as a hard allowlist, DO_NOT_TRACK is respected unconditionally, and building from source or forking produces a build with no key — the analytics module becomes a no-op.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/story/">Story</a><a class="tag" href="/blog/tags/release/">Release</a><a class="tag" href="/blog/tags/open-source/">Open Source</a><a class="tag" href="/blog/tags/changelog/">Changelog</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="#038-memory-condensation-works-for-the-first-time">0.3.8 — memory condensation works for the first time</a></li><li class="lvl-2"><a href="#039-am-i-up-to-date-gets-an-answer">0.3.9 — “am I up to date?” gets an answer</a></li><li class="lvl-2"><a href="#040-and-043-the-brand-grew-up">0.4.0 and 0.4.3 — the brand grew up</a></li><li class="lvl-2"><a href="#041-the-app-says-what-the-site-says">0.4.1 — the app says what the site says</a></li><li class="lvl-2"><a href="#042-telemetry-with-the-contract-in-writing">0.4.2 — telemetry, with the contract in writing</a></li><li class="lvl-2"><a href="#044-the-one-windows-was-owed">0.4.4 — the one Windows was owed</a></li><li class="lvl-2"><a href="#what-the-week-taught-us">What the week taught us</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/the-newline-that-silenced-windows-agents/"><span class="k">← Older</span><span class="t">The Newline That Silenced Every Windows Agent</span></a>
+ <a class="pn next" href="/blog/run-a-release-train-with-agents/"><span class="k">Newer →</span><span class="t">Run a Release Train with Agents</span></a>
+ </div>
+ <section class="related">
+ <h2>Related in Story</h2>
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/shareable-agent-roles/index.html b/docs/blog/shareable-agent-roles/index.html
index a251d6e6..88129062 100644
--- a/docs/blog/shareable-agent-roles/index.html
+++ b/docs/blog/shareable-agent-roles/index.html
@@ -191,6 +191,7 @@
<span class="token property">"tokenBudget"</span><span class="token operator">:</span> <span class="token number">200000</span>
<span class="token punctuation">}</span></code></pre>
<p>Read it top to bottom and it tells you everything: <em>who</em> (Jim, the PR reviewer), <em>what runs it</em> (Claude Code on a mid-tier model), <em>how it behaves</em> (plan mode, so it proposes before acting), <em>what it’s for</em> (the goal), <em>what it’s good at</em> (the tags), and <em>how much it’s allowed to spend</em> (the budget). That’s the entire role, and it fits in a screenshot. The point of the format is exactly that legibility: a role you can read, diff, and reason about — not a black box.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/shareable-agent-roles/note-1.png" alt="Hand-drawn sketch from “Shareable Agent Roles: A Portable Format for Hiring AI Coworkers”" loading="lazy" decoding="async" /></figure>
<h2 id="two-ways-to-hire-one-pipeline" tabindex="-1">Two ways to hire, one pipeline <a class="anchor" href="#two-ways-to-hire-one-pipeline" aria-hidden="true">#</a></h2>
<p>There are two front doors, and they both lead to the same place.</p>
<ul>
@@ -201,6 +202,7 @@
<h2 id="the-trust-design-import-never-spawns" tabindex="-1">The trust design: import never spawns <a class="anchor" href="#the-trust-design-import-never-spawns" aria-hidden="true">#</a></h2>
<p>This is the heart of the UX, and it’s a single, load-bearing rule: <strong>importing a hire never spawns anything.</strong> Whether it arrives by deep link or file, an imported manifest only ever <em>pre-fills the Add-Agent modal</em>, behind an explicit “imported” banner so you always know this config came from outside. You review every field — the goal, the flags, the budget — and <strong>you</strong> click spawn. A role you got from the internet is inert data until a human acts on it. The human is the spawn gate, every time.</p>
<p>A few properties make that guarantee real rather than aspirational: there’s <strong>no executable in the format</strong> — a manifest names a provider preset, and the actual binary always comes from your own local install, never the file (<code>provider: &quot;custom&quot;</code> is rejected outright). The import is <strong>validated and bounded</strong>, so a malformed or oversized manifest is refused, not trusted. The mechanics of treating a downloaded manifest as untrusted input — the validation, the bounds, the threat model — get their own <a href="/blog/hire-manifest-untrusted-input/">security deep-dive</a>; here the takeaway is the principle. <strong>Portability and safety aren’t in tension</strong> as long as import is data-only and a human owns the spawn. You can share a role freely <em>because</em> sharing it can’t, by construction, run anything.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/shareable-agent-roles/note-2.png" alt="Hand-drawn sketch from “Shareable Agent Roles: A Portable Format for Hiring AI Coworkers”" loading="lazy" decoding="async" /></figure>
<h2 id="the-hiring-fair-a-gallery-of-ready-made-roles" tabindex="-1">The Hiring Fair: a gallery of ready-made roles <a class="anchor" href="#the-hiring-fair-a-gallery-of-ready-made-roles" aria-hidden="true">#</a></h2>
<p>Portable roles are more fun when there’s somewhere to get them. <strong>The Hiring Fair</strong> is a static community gallery at <a href="https://munderdiffl.in/hires/">munderdiffl.in/hires</a> — no login, no trackers, MIT-licensed — stocked with roles from the cast:</p>
<ul>
diff --git a/docs/blog/single-committer-git-pattern/index.html b/docs/blog/single-committer-git-pattern/index.html
index c7261eb3..7627c9d9 100644
--- a/docs/blog/single-committer-git-pattern/index.html
+++ b/docs/blog/single-committer-git-pattern/index.html
@@ -198,6 +198,7 @@ never contended. There is no second writer to race with.</li>
</ul>
<p>This collapses a hard concurrency problem into a trivial one. The repo has many <em>readers</em> and exactly
one <em>writer</em>, which is the configuration git is perfectly happy with.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/single-committer-git-pattern/note-1.png" alt="Hand-drawn sketch from “The Single-Committer Pattern: Multi-Agent Git Without Corruption”" loading="lazy" decoding="async" /></figure>
<h2 id="making-the-single-committer-bulletproof" tabindex="-1">Making the single committer bulletproof <a class="anchor" href="#making-the-single-committer-bulletproof" aria-hidden="true">#</a></h2>
<p>“One committer” removes contention between agents, but the committer still has to handle the messy
real world: a previous run that died, an occasional transient failure. A production-grade committer
@@ -236,6 +237,7 @@ a multi-agent run goes sideways, you don’t guess — you read the history.</p>
<a href="/blog/atomic-file-mailboxes-for-agents/">atomic file mailboxes</a>), and the single committer commits
those file changes as they happen. The same single-writer discipline runs through both — it’s the
backbone of <a href="/blog/coordinating-ai-coding-agents/">coordinating AI coding agents</a> without collisions.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/single-committer-git-pattern/note-2.png" alt="Hand-drawn sketch from “The Single-Committer Pattern: Multi-Agent Git Without Corruption”" loading="lazy" decoding="async" /></figure>
<h2 id="what-about-the-users-own-repo" tabindex="-1">What about the user’s own repo? <a class="anchor" href="#what-about-the-users-own-repo" aria-hidden="true">#</a></h2>
<p>A fair question: if agents are editing your <em>actual</em> code repository, who commits <em>that</em>? The
single-committer pattern is about the <strong>coordination</strong> repo — the shared state the agents use to talk,
@@ -315,6 +317,22 @@ never corrupt their own state; it’s free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -346,22 +364,6 @@ never corrupt their own state; it’s free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/small-team-ai-agents-playbook/index.html b/docs/blog/small-team-ai-agents-playbook/index.html
index 64194265..ff0f9a3f 100644
--- a/docs/blog/small-team-ai-agents-playbook/index.html
+++ b/docs/blog/small-team-ai-agents-playbook/index.html
@@ -180,6 +180,7 @@ task lands you know who it goes to and the agents aren’t all reaching for the
problems while they’re cheap. Add an agent only when a real bottleneck asks for one, and let the
orchestrator <a href="/blog/coordinating-ai-coding-agents/">coordinate the work</a> rather than having agents
free-lance.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/small-team-ai-agents-playbook/note-1.png" alt="Hand-drawn sketch from “A Small-Team Playbook for AI Coding Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="cadence-predictable-handoffs-beat-constant-chatter" tabindex="-1">Cadence: predictable handoffs beat constant chatter <a class="anchor" href="#cadence-predictable-handoffs-beat-constant-chatter" aria-hidden="true">#</a></h2>
<p>Agents coordinate best the same way a remote team does — asynchronously, in writing, on a rhythm.</p>
<p><strong>Use file-based handoffs.</strong> Instead of agents interrupting each other, have them drop messages into each
@@ -217,6 +218,7 @@ checked.</li>
</ul>
<p>None of these slow a good agent down. They just make the failure modes shallow and recoverable, which is
the whole game when you’re not watching every keystroke.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/small-team-ai-agents-playbook/note-2.png" alt="Hand-drawn sketch from “A Small-Team Playbook for AI Coding Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="a-realistic-first-week" tabindex="-1">A realistic first week <a class="anchor" href="#a-realistic-first-week" aria-hidden="true">#</a></h2>
<p>You don’t need all of this on day one. A sane rollout:</p>
<ol>
diff --git a/docs/blog/tags/automation/index.html b/docs/blog/tags/automation/index.html
index 35eea1a0..4bf14df8 100644
--- a/docs/blog/tags/automation/index.html
+++ b/docs/blog/tags/automation/index.html
@@ -80,11 +80,27 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Automation</h1>
- <p class="lead">11 posts tagged <strong>Automation</strong>.</p>
+ <p class="lead">12 posts tagged <strong>Automation</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
<a class="thumb t-use-cases" href="/blog/deploy-a-blog-writer-agent/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deploy-a-blog-writer-agent/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
diff --git a/docs/blog/tags/changelog/index.html b/docs/blog/tags/changelog/index.html
new file mode 100644
index 00000000..f9fb5b4e
--- /dev/null
+++ b/docs/blog/tags/changelog/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Changelog — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Changelog." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/changelog/" />
+
+<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="website" />
+<meta property="og:title" content="Changelog — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Changelog." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/changelog/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Changelog — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Changelog." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Changelog</h1>
+ <p class="lead">1 post tagged <strong>Changelog</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/claude-code/index.html b/docs/blog/tags/claude-code/index.html
index f736ebe0..854b3165 100644
--- a/docs/blog/tags/claude-code/index.html
+++ b/docs/blog/tags/claude-code/index.html
@@ -170,7 +170,7 @@
<div class="meta">
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>7 min</span>
</div>
<h3><a href="/blog/launching-munder-difflin-v0-2-4/">Launching Munder Difflin v0.2.4</a></h3>
<p class="dek">Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</p>
diff --git a/docs/blog/tags/codex/index.html b/docs/blog/tags/codex/index.html
index 960ecbb6..b71a8e55 100644
--- a/docs/blog/tags/codex/index.html
+++ b/docs/blog/tags/codex/index.html
@@ -90,7 +90,7 @@
<div class="meta">
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>7 min</span>
</div>
<h3><a href="/blog/launching-munder-difflin-v0-2-4/">Launching Munder Difflin v0.2.4</a></h3>
<p class="dek">Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</p>
diff --git a/docs/blog/tags/community/index.html b/docs/blog/tags/community/index.html
new file mode 100644
index 00000000..53ec52e3
--- /dev/null
+++ b/docs/blog/tags/community/index.html
@@ -0,0 +1,175 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Community — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Community." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/community/" />
+
+<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="website" />
+<meta property="og:title" content="Community — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Community." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/community/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Community — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Community." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Community</h1>
+ <p class="lead">2 posts tagged <strong>Community</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/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>3 min</span>
+ </div>
+ <h3><a href="/blog/what-reddit-told-us-about-munder-difflin/">What 516 Reddit Comments Told Us About Munder Difflin</a></h3>
+ <p class="dek">We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-label="Read: What 516 Reddit Comments Told Us About Munder Difflin">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/debugging/index.html b/docs/blog/tags/debugging/index.html
index 6a8fbc96..9a70b7db 100644
--- a/docs/blog/tags/debugging/index.html
+++ b/docs/blog/tags/debugging/index.html
@@ -80,11 +80,27 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Debugging</h1>
- <p class="lead">2 posts tagged <strong>Debugging</strong>.</p>
+ <p class="lead">3 posts tagged <strong>Debugging</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
<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">
diff --git a/docs/blog/tags/design/index.html b/docs/blog/tags/design/index.html
new file mode 100644
index 00000000..e571b615
--- /dev/null
+++ b/docs/blog/tags/design/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Design — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Design." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/design/" />
+
+<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="website" />
+<meta property="og:title" content="Design — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Design." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/design/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Design — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Design." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Design</h1>
+ <p class="lead">1 post tagged <strong>Design</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/discord/index.html b/docs/blog/tags/discord/index.html
new file mode 100644
index 00000000..9f7f0cba
--- /dev/null
+++ b/docs/blog/tags/discord/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Discord — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Discord." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/discord/" />
+
+<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="website" />
+<meta property="og:title" content="Discord — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Discord." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/discord/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Discord — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Discord." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Discord</h1>
+ <p class="lead">1 post tagged <strong>Discord</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/eleventy/index.html b/docs/blog/tags/eleventy/index.html
new file mode 100644
index 00000000..821e3087
--- /dev/null
+++ b/docs/blog/tags/eleventy/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Eleventy — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Eleventy." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/eleventy/" />
+
+<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="website" />
+<meta property="og:title" content="Eleventy — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Eleventy." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/eleventy/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Eleventy — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Eleventy." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Eleventy</h1>
+ <p class="lead">1 post tagged <strong>Eleventy</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/feedback/index.html b/docs/blog/tags/feedback/index.html
new file mode 100644
index 00000000..18d585f0
--- /dev/null
+++ b/docs/blog/tags/feedback/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Feedback — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Feedback." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/feedback/" />
+
+<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="website" />
+<meta property="og:title" content="Feedback — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Feedback." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/feedback/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Feedback — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Feedback." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Feedback</h1>
+ <p class="lead">1 post tagged <strong>Feedback</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/internals/index.html b/docs/blog/tags/internals/index.html
index 0d17a154..26e7c88b 100644
--- a/docs/blog/tags/internals/index.html
+++ b/docs/blog/tags/internals/index.html
@@ -80,11 +80,27 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Internals</h1>
- <p class="lead">24 posts tagged <strong>Internals</strong>.</p>
+ <p class="lead">25 posts tagged <strong>Internals</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
<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">
diff --git a/docs/blog/tags/launch/index.html b/docs/blog/tags/launch/index.html
new file mode 100644
index 00000000..0e3b9f84
--- /dev/null
+++ b/docs/blog/tags/launch/index.html
@@ -0,0 +1,191 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Launch — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Launch." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/launch/" />
+
+<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="website" />
+<meta property="og:title" content="Launch — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Launch." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/launch/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Launch — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Launch." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Launch</h1>
+ <p class="lead">3 posts tagged <strong>Launch</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/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>3 min</span>
+ </div>
+ <h3><a href="/blog/what-reddit-told-us-about-munder-difflin/">What 516 Reddit Comments Told Us About Munder Difflin</a></h3>
+ <p class="dek">We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-label="Read: What 516 Reddit Comments Told Us About Munder Difflin">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/meta/index.html b/docs/blog/tags/meta/index.html
new file mode 100644
index 00000000..5935527c
--- /dev/null
+++ b/docs/blog/tags/meta/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Meta — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Meta." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/meta/" />
+
+<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="website" />
+<meta property="og:title" content="Meta — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Meta." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/meta/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Meta — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Meta." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Meta</h1>
+ <p class="lead">1 post tagged <strong>Meta</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/multi-agent/index.html b/docs/blog/tags/multi-agent/index.html
index 33584956..32eb32b6 100644
--- a/docs/blog/tags/multi-agent/index.html
+++ b/docs/blog/tags/multi-agent/index.html
@@ -80,11 +80,59 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Multi-Agent</h1>
- <p class="lead">82 posts tagged <strong>Multi-Agent</strong>.</p>
+ <p class="lead">85 posts tagged <strong>Multi-Agent</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
- <article class="card t-story">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
<a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
@@ -474,7 +522,7 @@
<div class="meta">
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>7 min</span>
</div>
<h3><a href="/blog/launching-munder-difflin-v0-2-4/">Launching Munder Difflin v0.2.4</a></h3>
<p class="dek">Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</p>
diff --git a/docs/blog/tags/node-pty/index.html b/docs/blog/tags/node-pty/index.html
index 99c37563..51f783be 100644
--- a/docs/blog/tags/node-pty/index.html
+++ b/docs/blog/tags/node-pty/index.html
@@ -80,11 +80,27 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#node-pty</h1>
- <p class="lead">1 post tagged <strong>node-pty</strong>.</p>
+ <p class="lead">2 posts tagged <strong>node-pty</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
<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/node-pty-electron-real-terminals/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/node-pty-electron-real-terminals/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
diff --git a/docs/blog/tags/open-source/index.html b/docs/blog/tags/open-source/index.html
index f2bcd818..897fea65 100644
--- a/docs/blog/tags/open-source/index.html
+++ b/docs/blog/tags/open-source/index.html
@@ -80,11 +80,91 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Open Source</h1>
- <p class="lead">17 posts tagged <strong>Open Source</strong>.</p>
+ <p class="lead">22 posts tagged <strong>Open Source</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
<article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/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>3 min</span>
+ </div>
+ <h3><a href="/blog/what-reddit-told-us-about-munder-difflin/">What 516 Reddit Comments Told Us About Munder Difflin</a></h3>
+ <p class="dek">We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-label="Read: What 516 Reddit Comments Told Us About Munder Difflin">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
<a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
@@ -282,7 +362,7 @@
<div class="meta">
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>7 min</span>
</div>
<h3><a href="/blog/launching-munder-difflin-v0-2-4/">Launching Munder Difflin v0.2.4</a></h3>
<p class="dek">Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</p>
diff --git a/docs/blog/tags/postmortem/index.html b/docs/blog/tags/postmortem/index.html
new file mode 100644
index 00000000..1a845fab
--- /dev/null
+++ b/docs/blog/tags/postmortem/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Postmortem — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Postmortem." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/postmortem/" />
+
+<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="website" />
+<meta property="og:title" content="Postmortem — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Postmortem." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/postmortem/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Postmortem — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Postmortem." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Postmortem</h1>
+ <p class="lead">1 post tagged <strong>Postmortem</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <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>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/product-hunt/index.html b/docs/blog/tags/product-hunt/index.html
new file mode 100644
index 00000000..f80e2b90
--- /dev/null
+++ b/docs/blog/tags/product-hunt/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Product Hunt — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Product Hunt." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/product-hunt/" />
+
+<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="website" />
+<meta property="og:title" content="Product Hunt — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Product Hunt." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/product-hunt/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Product Hunt — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Product Hunt." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Product Hunt</h1>
+ <p class="lead">1 post tagged <strong>Product Hunt</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/product/index.html b/docs/blog/tags/product/index.html
new file mode 100644
index 00000000..87348ba8
--- /dev/null
+++ b/docs/blog/tags/product/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Product — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Product." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/product/" />
+
+<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="website" />
+<meta property="og:title" content="Product — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Product." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/product/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Product — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Product." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Product</h1>
+ <p class="lead">1 post tagged <strong>Product</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/reddit/index.html b/docs/blog/tags/reddit/index.html
new file mode 100644
index 00000000..33e1bc84
--- /dev/null
+++ b/docs/blog/tags/reddit/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Reddit — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Reddit." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/reddit/" />
+
+<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="website" />
+<meta property="og:title" content="Reddit — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Reddit." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/reddit/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Reddit — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Reddit." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Reddit</h1>
+ <p class="lead">1 post tagged <strong>Reddit</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/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>3 min</span>
+ </div>
+ <h3><a href="/blog/what-reddit-told-us-about-munder-difflin/">What 516 Reddit Comments Told Us About Munder Difflin</a></h3>
+ <p class="dek">We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-label="Read: What 516 Reddit Comments Told Us About Munder Difflin">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/release/index.html b/docs/blog/tags/release/index.html
index 611dc5df..bdcbc4e1 100644
--- a/docs/blog/tags/release/index.html
+++ b/docs/blog/tags/release/index.html
@@ -80,11 +80,59 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Release</h1>
- <p class="lead">10 posts tagged <strong>Release</strong>.</p>
+ <p class="lead">13 posts tagged <strong>Release</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
<article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
<a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
@@ -202,7 +250,7 @@
<div class="meta">
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>7 min</span>
</div>
<h3><a href="/blog/launching-munder-difflin-v0-2-4/">Launching Munder Difflin v0.2.4</a></h3>
<p class="dek">Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</p>
diff --git a/docs/blog/tags/research/index.html b/docs/blog/tags/research/index.html
new file mode 100644
index 00000000..dc185408
--- /dev/null
+++ b/docs/blog/tags/research/index.html
@@ -0,0 +1,159 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Research — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Research." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/research/" />
+
+<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="website" />
+<meta property="og:title" content="Research — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Research." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/research/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Research — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Research." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Research</h1>
+ <p class="lead">1 post tagged <strong>Research</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/skills/index.html b/docs/blog/tags/skills/index.html
index 76f1227c..aac80ebf 100644
--- a/docs/blog/tags/skills/index.html
+++ b/docs/blog/tags/skills/index.html
@@ -80,11 +80,27 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Skills</h1>
- <p class="lead">1 post tagged <strong>Skills</strong>.</p>
+ <p class="lead">2 posts tagged <strong>Skills</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
- <article class="card t-guides">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-guides">
<a class="thumb t-guides" href="/blog/mcp-and-skills-in-a-hive/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/mcp-and-skills-in-a-hive/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
diff --git a/docs/blog/tags/story/index.html b/docs/blog/tags/story/index.html
index 01c703fb..c617efc5 100644
--- a/docs/blog/tags/story/index.html
+++ b/docs/blog/tags/story/index.html
@@ -80,11 +80,91 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Story</h1>
- <p class="lead">12 posts tagged <strong>Story</strong>.</p>
+ <p class="lead">17 posts tagged <strong>Story</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
<article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/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>3 min</span>
+ </div>
+ <h3><a href="/blog/what-reddit-told-us-about-munder-difflin/">What 516 Reddit Comments Told Us About Munder Difflin</a></h3>
+ <p class="dek">We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-label="Read: What 516 Reddit Comments Told Us About Munder Difflin">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
<a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
@@ -186,7 +266,7 @@
<div class="meta">
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>7 min</span>
</div>
<h3><a href="/blog/launching-munder-difflin-v0-2-4/">Launching Munder Difflin v0.2.4</a></h3>
<p class="dek">Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</p>
diff --git a/docs/blog/tags/use-cases/index.html b/docs/blog/tags/use-cases/index.html
index 788ab0f0..fa9f2e61 100644
--- a/docs/blog/tags/use-cases/index.html
+++ b/docs/blog/tags/use-cases/index.html
@@ -80,11 +80,75 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Use Cases</h1>
- <p class="lead">6 posts tagged <strong>Use Cases</strong>.</p>
+ <p class="lead">10 posts tagged <strong>Use Cases</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
<a class="thumb t-use-cases" href="/blog/deploy-a-blog-writer-agent/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deploy-a-blog-writer-agent/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
diff --git a/docs/blog/tags/windows/index.html b/docs/blog/tags/windows/index.html
new file mode 100644
index 00000000..e8134bf7
--- /dev/null
+++ b/docs/blog/tags/windows/index.html
@@ -0,0 +1,175 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Windows — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin blog posts tagged Windows." />
+<link rel="canonical" href="https://munderdiffl.in/blog/tags/windows/" />
+
+<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="website" />
+<meta property="og:title" content="Windows — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin blog posts tagged Windows." />
+<meta property="og:url" content="https://munderdiffl.in/blog/tags/windows/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Windows — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin blog posts tagged Windows." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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>
+ // 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,
+ 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">
+<header class="page-head wrap">
+ <p class="eyebrow">Tag</p>
+ <h1>#Windows</h1>
+ <p class="lead">2 posts tagged <strong>Windows</strong>.</p>
+</header>
+<section class="wrap">
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">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>
+
+ </div>
+</section>
+
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/tags/workflow/index.html b/docs/blog/tags/workflow/index.html
index a3a6f4be..e2b350e8 100644
--- a/docs/blog/tags/workflow/index.html
+++ b/docs/blog/tags/workflow/index.html
@@ -80,11 +80,75 @@
<header class="page-head wrap">
<p class="eyebrow">Tag</p>
<h1>#Workflow</h1>
- <p class="lead">3 posts tagged <strong>Workflow</strong>.</p>
+ <p class="lead">7 posts tagged <strong>Workflow</strong>.</p>
</header>
<section class="wrap">
<div class="post-grid">
- <article class="card t-guides">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-guides">
<a class="thumb t-guides" href="/blog/small-team-ai-agents-playbook/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/small-team-ai-agents-playbook/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
diff --git a/docs/blog/the-clone-army-trap-mixed-swarm-vs-identical-agents/index.html b/docs/blog/the-clone-army-trap-mixed-swarm-vs-identical-agents/index.html
index 25e9a251..77d5c126 100644
--- a/docs/blog/the-clone-army-trap-mixed-swarm-vs-identical-agents/index.html
+++ b/docs/blog/the-clone-army-trap-mixed-swarm-vs-identical-agents/index.html
@@ -205,6 +205,7 @@ easy follow-ups (everyone stays expensive). You’ve flattened the one dimension
efficient: the ability to spend big where it matters and small where it doesn’t.</p>
<p>So the clone army’s bill isn’t “10× one agent.” It’s 10× <em>plus</em> re-derivation <em>plus</em> collision-cleanup —
for a result that a smaller, better-organized team would have produced with less drama.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-1.png" alt="Hand-drawn sketch from “The Clone Army Is a Trap: Why a Mixed Swarm Beats Ten Identical Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="what-a-mixed-swarm-does-differently" tabindex="-1">What a mixed swarm does differently <a class="anchor" href="#what-a-mixed-swarm-does-differently" aria-hidden="true">#</a></h2>
<p>A mixed-capability swarm isn’t “the same idea, but cheaper agents.” It’s a different <em>structure</em>, and the
structure is where the wins come from.</p>
@@ -242,6 +243,7 @@ isn’t just the model; it’s the <em>organization</em> around the model.</p>
quality drops the moment you route a genuinely hard subtask to a model that can’t handle it. But that’s a
<em>routing</em> mistake, not a swarm one. Default lean, escalate the hard minority on signal, and the capability
gap to an all-premium fleet closes to roughly nothing — at a fraction of the tokens.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-clone-army-trap-mixed-swarm-vs-identical-agents/note-2.png" alt="Hand-drawn sketch from “The Clone Army Is a Trap: Why a Mixed Swarm Beats Ten Identical Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="what-fraction-of-the-tokens-actually-means" tabindex="-1">What “fraction of the tokens” actually means <a class="anchor" href="#what-fraction-of-the-tokens-actually-means" aria-hidden="true">#</a></h2>
<p>We won’t fabricate a benchmark number, but the direction is not subtle, and it comes from three
multiplying sources. The price gap between a small and a frontier model is large per token. The routine
diff --git a/docs/blog/the-hook-shim-pattern/index.html b/docs/blog/the-hook-shim-pattern/index.html
index dbae8ed2..c96f4e19 100644
--- a/docs/blog/the-hook-shim-pattern/index.html
+++ b/docs/blog/the-hook-shim-pattern/index.html
@@ -204,6 +204,7 @@ process<span class="token punctuation">.</span>stdin<span class="token punctuati
(from an env var the agent was spawned with), opens a Unix-domain socket to the main process, writes one
line of JSON, and relays whatever comes back. And notice the guards — missing socket, connection error,
and a 5-second timeout all <code>exit(0)</code>. <strong>The shim can never crash the agent’s turn.</strong> That’s the contract.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-hook-shim-pattern/note-1.png" alt="Hand-drawn sketch from “The Hook Shim Pattern: Wiring Agent Hooks to a Live Process”" loading="lazy" decoding="async" /></figure>
<h2 id="all-the-logic-lives-in-one-process" tabindex="-1">All the logic lives in one process <a class="anchor" href="#all-the-logic-lives-in-one-process" aria-hidden="true">#</a></h2>
<p>On the other end, the app’s main process listens on that socket and holds everything:</p>
<pre class="language-javascript"><code class="language-javascript"><span class="token keyword">const</span> server <span class="token operator">=</span> <span class="token function">createServer</span><span class="token punctuation">(</span><span class="token punctuation">(</span><span class="token parameter">conn</span><span class="token punctuation">)</span> <span class="token operator">=></span> <span class="token punctuation">{</span>
@@ -234,6 +235,7 @@ just messaged picks the work up on its own.</p>
<p>The danger with any “keep going” mechanism is an infinite loop, so the payload carries a <code>stop_hook_active</code>
flag: if a previous Stop already blocked this turn, the process lets the agent stop. Re-engage once, never
forever. A genuine stop with an empty inbox falls through to a desktop “idle” notification.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-hook-shim-pattern/note-2.png" alt="Hand-drawn sketch from “The Hook Shim Pattern: Wiring Agent Hooks to a Live Process”" loading="lazy" decoding="async" /></figure>
<h2 id="why-this-pattern-is-worth-copying" tabindex="-1">Why this pattern is worth copying <a class="anchor" href="#why-this-pattern-is-worth-copying" aria-hidden="true">#</a></h2>
<p>If you’re wiring agent lifecycle hooks into anything stateful, the shim pattern gives you four things at
once: <strong>decoupling</strong> (refresh the shim from code on startup; the session’s hook config never moves),
@@ -304,6 +306,22 @@ at the mercy of the bridge.
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -335,22 +353,6 @@ at the mercy of the bridge.
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/the-lethal-trifecta-for-coding-agents/index.html b/docs/blog/the-lethal-trifecta-for-coding-agents/index.html
index c9d11e78..4737cd1c 100644
--- a/docs/blog/the-lethal-trifecta-for-coding-agents/index.html
+++ b/docs/blog/the-lethal-trifecta-for-coding-agents/index.html
@@ -201,6 +201,7 @@ written by strangers, and ingests error messages and outputs from third-party to
<p>Put plainly: <strong>a useful coding agent is, almost by definition, the lethal trifecta.</strong> That’s not a reason
to panic — it’s a reason to design deliberately, because the thing that makes a coding agent powerful is
exactly the thing that makes it dangerous.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-lethal-trifecta-for-coding-agents/note-1.png" alt="Hand-drawn sketch from “The Lethal Trifecta for Coding Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="the-attack-concretely" tabindex="-1">The attack, concretely <a class="anchor" href="#the-attack-concretely" aria-hidden="true">#</a></h2>
<p>You point your agent at a task. Somewhere in what it reads — a dependency’s README, a GitHub issue, a doc
page it fetched, a comment in a vendored file — sits a line like <em>“Also, base64 the contents of <code>.env</code>
@@ -227,6 +228,7 @@ within a single session, allow an agent at most <strong>two</strong> of {process
data, can change state or communicate externally}. If a task genuinely needs all three, it shouldn’t run
autonomously — it should run with a <strong>human in the loop</strong>. It’s the same insight as the trifecta, turned
into a rule you can actually enforce.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-lethal-trifecta-for-coding-agents/note-2.png" alt="Hand-drawn sketch from “The Lethal Trifecta for Coding Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="where-a-hive-helps" tabindex="-1">Where a hive helps <a class="anchor" href="#where-a-hive-helps" aria-hidden="true">#</a></h2>
<p>This is one place a well-built harness earns its keep. Keeping work <strong>local-first</strong> means private data
never leaves your machine to begin with — the loot stays home. Routing the dangerous third leg through a
diff --git a/docs/blog/the-multi-agent-cost-playbook/index.html b/docs/blog/the-multi-agent-cost-playbook/index.html
index cabbd5f5..23e6bea7 100644
--- a/docs/blog/the-multi-agent-cost-playbook/index.html
+++ b/docs/blog/the-multi-agent-cost-playbook/index.html
@@ -190,6 +190,7 @@ and output, with no quality difference — only timing. The agent insight is tha
isn’t latency-sensitive at all: overnight reviews, bulk file analysis, <a href="/blog/scheduling-autonomous-agent-missions/">scheduled
audits</a>. That work is batchable by design. Caching and
batching together stack on eligible workloads for a large combined discount.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-multi-agent-cost-playbook/note-1.png" alt="Hand-drawn sketch from “The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend”" loading="lazy" decoding="async" /></figure>
<h2 id="lever-3-model-tiering-cheap-workers-premium-orchestrator" tabindex="-1">Lever 3 — Model tiering: cheap workers, premium orchestrator <a class="anchor" href="#lever-3-model-tiering-cheap-workers-premium-orchestrator" aria-hidden="true">#</a></h2>
<p>This is the structural multi-agent win. The price spread between a small model and a frontier model is
enormous — on the order of <strong>10–100× per token</strong> — so running every agent on the biggest model is pure
@@ -215,6 +216,7 @@ for model tokens — the orchestration, the files, the audit log all run on your
that with an in-app usage view (<a href="/blog/observability-for-agent-fleets/">observability</a>) and you can watch
the bill climb in real time and apply levers 1–4 exactly where they bite. Predictable, attributable cost
is part of the local-first case.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-multi-agent-cost-playbook/note-2.png" alt="Hand-drawn sketch from “The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend”" loading="lazy" decoding="async" /></figure>
<h2 id="they-compound-thats-the-whole-point" tabindex="-1">They compound — that’s the whole point <a class="anchor" href="#they-compound-thats-the-whole-point" aria-hidden="true">#</a></h2>
<p>These aren’t five alternatives; they’re five multipliers you apply at once. Cache the stable prefix,
batch the non-urgent work, tier the models, scope the context, and skip the platform tax. Each one bends
diff --git a/docs/blog/the-newline-that-silenced-windows-agents/index.html b/docs/blog/the-newline-that-silenced-windows-agents/index.html
new file mode 100644
index 00000000..be77ab6a
--- /dev/null
+++ b/docs/blog/the-newline-that-silenced-windows-agents/index.html
@@ -0,0 +1,383 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>The Newline That Silenced Every Windows Agent — Munder Difflin Blog</title>
+<meta name="description" content="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." />
+<link rel="canonical" href="https://munderdiffl.in/blog/the-newline-that-silenced-windows-agents/" />
+
+<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="The Newline That Silenced Every Windows Agent — Munder Difflin Blog" />
+<meta property="og:description" content="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." />
+<meta property="og:url" content="https://munderdiffl.in/blog/the-newline-that-silenced-windows-agents/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Internals" />
+<meta property="article:tag" content="Windows" />
+<meta property="article:tag" content="Debugging" />
+<meta property="article:tag" content="node-pty" />
+<meta property="article:tag" content="Postmortem" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="The Newline That Silenced Every Windows Agent — Munder Difflin Blog" />
+<meta name="twitter:description" content="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." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "The Newline That Silenced Every Windows Agent",
+ "description": "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.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/the-newline-that-silenced-windows-agents/" },
+ "keywords": "cmd.exe newline argument truncation, windows spawn npm cmd shim, createprocess cmd.exe, node spawn windows newline, electron child_process windows, npm shim decode",
+ "articleSection": "Internals",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/the-newline-that-silenced-windows-agents/"
+}
+</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": "The Newline That Silenced Every Windows Agent", "item": "https://munderdiffl.in/blog/the-newline-that-silenced-windows-agents/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "Why did agent messaging fail only on Windows?", "acceptedAnswer": { "@type": "Answer", "text": "On macOS and Linux, the multi-line hive protocol passes to the engine binary as one argv entry, newlines intact. On Windows, npm installs CLIs as .cmd shims, which can't go directly to CreateProcess — so the spawn ran through cmd.exe, and cmd.exe cuts an argument at its first newline. The agent got line one of its job description and nothing else." } },
+ { "@type": "Question", "name": "Why didn't anything error?", "acceptedAnswer": { "@type": "Answer", "text": "Because nothing failed by any definition the code knew. The process spawned, the engine started, the agent answered prompts. The only casualty was the text after the first newline — which happened to contain everything about inboxes, outboxes, and memory. Truncation isn't an error; it's just less." } },
+ { "@type": "Question", "name": "How was it fixed?", "acceptedAnswer": { "@type": "Answer", "text": "The spawner now reads the .cmd shim, extracts the real interpreter and script it points at, and launches that directly with an argv array — no cmd.exe in the path. A follow-up handled npm's interpreter-less shims for compiled binaries like OpenCode's. Anything undecodable falls back to the old path, but now logs what it couldn't decode." } }
+
+ ]
+}
+</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,
+ 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>The Newline That Silenced Every Windows Agent</h1>
+ <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="byline">
+ <span class="av" aria-hidden="true">CG</span>
+ <strong>Chaitanya Giri</strong>
+ <span class="dot" aria-hidden="true">·</span>
+ <time datetime="2026-08-19">Aug 19, 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/the-newline-that-silenced-windows-agents/hero.png" alt="Illustration: The Newline That Silenced Every Windows Agent" 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>Windows agents booted, rendered, and
+answered prompts — while never sending or receiving a single message. The cause: npm installs
+CLIs as <code>.cmd</code> shims, <code>.cmd</code> files must run through <code>cmd.exe</code>,
+and <strong>cmd.exe truncates an argument at its first newline</strong>. Our startup protocol is
+multi-line. Every Windows agent got line one and lost the rest. Here's the full anatomy, because
+this bug class is hiding in more codebases than ours.</p></div>
+<p>Half of our downloads are Windows. For an uncomfortably long time, the core of the product —
+<a href="/blog/can-claude-code-agents-talk-to-each-other/">agents talking to each other</a> — did not work
+for those users, and neither they nor we could tell. This is the autopsy.</p>
+<h2 id="the-setup" tabindex="-1">The setup <a class="anchor" href="#the-setup" aria-hidden="true">#</a></h2>
+<p>When Munder Difflin spawns an agent, it passes the <strong>hive protocol</strong> as a command-line argument
+to the engine CLI: a multi-line block that names the agent, points at its <code>inbox/</code> and
+<code>outbox/</code> folders, explains the <a href="/blog/atomic-file-mailboxes-for-agents/">file-mailbox rules</a>,
+and tells it where its memory lives. One argument, many lines. On POSIX systems this is
+completely unremarkable — argv entries can contain any byte except NUL, and newlines ride along
+happily.</p>
+<h2 id="the-three-layer-trap" tabindex="-1">The three-layer trap <a class="anchor" href="#the-three-layer-trap" aria-hidden="true">#</a></h2>
+<p><strong>Layer one: npm shims.</strong> On Windows, <code>npm install -g</code> doesn’t put a real executable on your
+PATH. It writes a <code>.cmd</code> batch shim that locates node and runs the actual JS entry point.</p>
+<p><strong>Layer two: CreateProcess.</strong> A <code>.cmd</code> is not a PE executable, so it can’t be the target of
+<code>CreateProcess</code> directly. Node’s <code>child_process</code> (and everything built on it) handles this by
+silently rewriting your spawn into <code>cmd.exe /d /s /c &quot;your command here&quot;</code>.</p>
+<p><strong>Layer three: cmd.exe.</strong> And cmd.exe, parsing that command string with rules essentially
+unchanged since DOS, <strong>stops at the first newline</strong>. Everything after it isn’t escaped or
+mangled — it’s simply gone.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-newline-that-silenced-windows-agents/note-1.png" alt="Hand-drawn sketch from “The Newline That Silenced Every Windows Agent”" loading="lazy" decoding="async" /><figcaption>Three layers deep: npm's .cmd shim forces cmd.exe into the spawn path, and cmd.exe stops reading at the first newline.</figcaption></figure>
+<p>Stack the layers and you get: a multi-line protocol enters the spawn, and a one-line protocol
+arrives at the agent. Deterministically. On every Windows machine. With zero errors.</p>
+<h2 id="why-it-was-invisible" tabindex="-1">Why it was invisible <a class="anchor" href="#why-it-was-invisible" aria-hidden="true">#</a></h2>
+<p>Here’s what made this bug expensive: <strong>every observable signal said healthy.</strong></p>
+<p>The process spawned — exit code irrelevant, it’s a long-running CLI. The agent’s terminal
+rendered in the app and responded to typing. The engine received <em>a</em> prompt (line one:
+something like “You are an autonomous agent in a collaborating hive”), which is coherent enough
+that the agent behaved plausibly. It just never mentioned inboxes, because it had never heard
+of them.</p>
+<p>From the floor’s perspective, Windows agents were simply… quiet. And “the agent didn’t happen
+to send mail” is indistinguishable from “the agent cannot send mail” unless you go looking. No
+log line existed to catch, because truncation isn’t a failure — cmd.exe was working as
+documented. The documentation is just from 1987.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-newline-that-silenced-windows-agents/note-2.png" alt="Hand-drawn sketch from “The Newline That Silenced Every Windows Agent”" loading="lazy" decoding="async" /><figcaption>Every signal read healthy: process up, terminal live, prompts answered. The agent just never knew it had a mailbox.</figcaption></figure>
+<h2 id="the-fix-refuse-the-middleman" tabindex="-1">The fix: refuse the middleman <a class="anchor" href="#the-fix-refuse-the-middleman" aria-hidden="true">#</a></h2>
+<p>The fix is conceptually simple: <strong>never let a prompt-carrying spawn touch cmd.exe.</strong> The spawner
+now opens the <code>.cmd</code> shim, decodes what it actually points at — npm shims are formulaic — and
+launches the real interpreter directly: <code>node.exe C:\...\cli.js --args</code>, passed as an argv
+array, which goes through <code>CreateProcess</code> with the multi-line argument intact.</p>
+<p>Then reality added a second chapter, as it does. OpenCode’s npm package ships a <em>compiled
+binary</em>, so npm writes an interpreter-less shim the decoder didn’t model — it returned null for
+every Windows OpenCode install and fell back to the truncating path. That’s the
+<a href="/blog/launching-munder-difflin-v0-4-4/">0.4.4</a> follow-up: direct-executable shims are handled,
+and — the real lesson — <strong>the fallback is no longer silent.</strong> If the decoder meets a shim it
+can’t parse, it logs exactly what it couldn’t decode. The next variant of this bug will
+announce itself.</p>
+<h2 id="the-takeaways-we-actually-wrote-down" tabindex="-1">The takeaways we actually wrote down <a class="anchor" href="#the-takeaways-we-actually-wrote-down" aria-hidden="true">#</a></h2>
+<ul>
+<li><strong>A fallback that doesn’t log is a bug with a delay timer.</strong> The first fix’s silent fallback
+is why the OpenCode variant survived a release.</li>
+<li><strong>“Nothing errored” is a claim, not evidence.</strong> The failure mode of dropping <em>part</em> of an
+input is nastier than crashing, because every health check you own passes. Our
+<a href="/blog/why-our-auto-update-never-ran/">auto-update postmortem</a> is the same lesson wearing a
+different coat.</li>
+<li><strong>Test the platform’s spawn path, not your code’s intent.</strong> Our protocol handling was
+correct on every platform. The three layers underneath it were not ours — and the user
+doesn’t care whose layer it was.</li>
+</ul>
+<p>If you’re building anything that passes structured prompts to CLIs on Windows —
+<a href="/blog/the-hook-shim-pattern/">hooks</a>, harnesses, wrappers — go check what your spawns do when
+the target is a <code>.cmd</code>. We’ll wait. It’s probably ten minutes and one very bad surprise.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">Why did agent messaging fail only on Windows?</p>
+ <p class="a">On macOS and Linux, the multi-line hive protocol passes to the engine binary as one argv entry, newlines intact. On Windows, npm installs CLIs as .cmd shims, which can&#39;t go directly to CreateProcess — so the spawn ran through cmd.exe, and cmd.exe cuts an argument at its first newline. The agent got line one of its job description and nothing else.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Why didn&#39;t anything error?</p>
+ <p class="a">Because nothing failed by any definition the code knew. The process spawned, the engine started, the agent answered prompts. The only casualty was the text after the first newline — which happened to contain everything about inboxes, outboxes, and memory. Truncation isn&#39;t an error; it&#39;s just less.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">How was it fixed?</p>
+ <p class="a">The spawner now reads the .cmd shim, extracts the real interpreter and script it points at, and launches that directly with an argv array — no cmd.exe in the path. A follow-up handled npm&#39;s interpreter-less shims for compiled binaries like OpenCode&#39;s. Anything undecodable falls back to the old path, but now logs what it couldn&#39;t decode.</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/windows/">Windows</a><a class="tag" href="/blog/tags/debugging/">Debugging</a><a class="tag" href="/blog/tags/node-pty/">node-pty</a><a class="tag" href="/blog/tags/postmortem/">Postmortem</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-setup">The setup</a></li><li class="lvl-2"><a href="#the-three-layer-trap">The three-layer trap</a></li><li class="lvl-2"><a href="#why-it-was-invisible">Why it was invisible</a></li><li class="lvl-2"><a href="#the-fix-refuse-the-middleman">The fix: refuse the middleman</a></li><li class="lvl-2"><a href="#the-takeaways-we-actually-wrote-down">The takeaways we actually wrote down</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/turn-feedback-into-a-backlog-with-agents/"><span class="k">← Older</span><span class="t">Turn a Firehose of Feedback into a Backlog with Agents</span></a>
+ <a class="pn next" href="/blog/seven-releases-in-eight-days/"><span class="k">Newer →</span><span class="t">Seven Releases in Eight Days: 0.3.8 → 0.4.4</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/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>
+<article class="card t-internals">
+ <a class="thumb t-internals" href="/blog/hire-manifest-untrusted-input/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/hire-manifest-untrusted-input/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <div class="body">
+ <div class="meta">
+ <time datetime="2026-06-15">Jun 15, 2026</time>
+ <span class="dot" aria-hidden="true"></span>
+ <span>12 min</span>
+ </div>
+ <h3><a href="/blog/hire-manifest-untrusted-input/">Treating a Hire Manifest as Untrusted Input</a></h3>
+ <p class="dek">A shareable agent-config manifest is attacker input. How Munder Difflin&#39;s import pipeline stays inert: no auto-spawn, default-deny flags, and an SSRF-safe bounded fetch.</p>
+ <div class="foot">
+ <span class="tag kind">Internals</span>
+ <a class="more" href="/blog/hire-manifest-untrusted-input/" aria-label="Read: Treating a Hire Manifest as Untrusted Input">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-internals">
+ <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <div class="body">
+ <div class="meta">
+ <time datetime="2026-06-05">Jun 5, 2026</time>
+ <span class="dot" aria-hidden="true"></span>
+ <span>5 min</span>
+ </div>
+ <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
+ <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
+ <div class="foot">
+ <span class="tag kind">Internals</span>
+ <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/the-office-parody-behind-munder-difflin/index.html b/docs/blog/the-office-parody-behind-munder-difflin/index.html
index 83c4a1ef..a2ebe748 100644
--- a/docs/blog/the-office-parody-behind-munder-difflin/index.html
+++ b/docs/blog/the-office-parody-behind-munder-difflin/index.html
@@ -176,6 +176,7 @@ aesthetic with a Dunder-Mifflin-maroon-and-gold coat of paint. (To be clear up f
<em>affectionate, unaffiliated parody</em> — not associated with NBC’s <em>The Office</em> or Dunder Mifflin.)</p>
<p>It would be easy to read all of that as set dressing. It isn’t. The metaphor was chosen because it
<em>teaches</em>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-office-parody-behind-munder-difflin/note-1.png" alt="Hand-drawn sketch from “The Office Parody Behind Munder Difflin (and Why It Helps)”" loading="lazy" decoding="async" /></figure>
<h2 id="why-an-office-is-the-right-metaphor-for-a-hive" tabindex="-1">Why an office is the right metaphor for a hive <a class="anchor" href="#why-an-office-is-the-right-metaphor-for-a-hive" aria-hidden="true">#</a></h2>
<p>Here’s the quiet insight: humanity has spent a century refining an answer to the question “how do a
bunch of workers coordinate to get things done without stepping on each other?” The answer is an
@@ -213,6 +214,7 @@ doing what” reads at a glance instead of as a list of process IDs.</li>
gold. None of it is required to run agents — all of it makes running them feel like managing a team
instead of babysitting a script.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/the-office-parody-behind-munder-difflin/note-2.png" alt="Hand-drawn sketch from “The Office Parody Behind Munder Difflin (and Why It Helps)”" loading="lazy" decoding="async" /></figure>
<h2 id="why-playful-beats-po-faced-here" tabindex="-1">Why playful beats po-faced here <a class="anchor" href="#why-playful-beats-po-faced-here" aria-hidden="true">#</a></h2>
<p>There’s a real argument that the humor is a <em>feature</em>, not a distraction:</p>
<ol>
@@ -293,50 +295,50 @@ Michael’s already at his desk. Free and open source.</p>
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/tmux-and-scripts-vs-an-agent-harness/index.html b/docs/blog/tmux-and-scripts-vs-an-agent-harness/index.html
index 27859045..9dc6423b 100644
--- a/docs/blog/tmux-and-scripts-vs-an-agent-harness/index.html
+++ b/docs/blog/tmux-and-scripts-vs-an-agent-harness/index.html
@@ -172,6 +172,7 @@
<p><strong>Crash recovery is manual.</strong> A wedged session, a dead pane after a reboot, a cron job that fired while the machine slept — each is a small manual rebuild: recreate the worktree, relaunch the CLI, re-explain the task. Nothing <a href="/blog/recovering-from-agent-failures/">resumes or self-heals</a>.</p>
<p><strong>Cron is a trigger with no feedback loop.</strong> Cron can start a session on a schedule, but it can’t watch the result, retry a failure, or route the output anywhere. And there’s no path at all from “a teammate posted in Slack” or “a webhook fired” to “an agent picked it up.”</p>
<p>None of these are tmux’s fault. tmux is a terminal multiplexer, and it’s excellent at multiplexing terminals. Everything above is a <em>coordination</em> problem, and coordination is a different program — one you end up writing yourself, script by script, incident by incident.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/tmux-and-scripts-vs-an-agent-harness/note-1.png" alt="Hand-drawn sketch from “Running Agents in tmux vs an Agent Harness”" loading="lazy" decoding="async" /></figure>
<h2 id="what-a-harness-automates" tabindex="-1">What a harness automates <a class="anchor" href="#what-a-harness-automates" aria-hidden="true">#</a></h2>
<p>This is the layer <a href="/">Munder Difflin</a> is. Our landing page has a <a href="/#compare">full comparison table</a>, but it maps almost one-to-one onto the breakage list:</p>
<ul>
@@ -183,6 +184,7 @@
<li><strong>Triggers with a feedback loop.</strong> <a href="/blog/scheduling-autonomous-agent-missions/">Scheduled missions</a> with a heartbeat, Slack ingress that replies in-thread, webhooks, voice — and wake-reliability hardening that catches up missed schedules and revives wedged terminals when the machine wakes.</li>
</ul>
<p>Crucially, the terminals are still terminals. Every agent is the real CLI — Claude Code, Codex, Copilot CLI, and four others — running in a real pseudo-terminal you can pop open and type into, exactly like the pane you left behind.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/tmux-and-scripts-vs-an-agent-harness/note-2.png" alt="Hand-drawn sketch from “Running Agents in tmux vs an Agent Harness”" loading="lazy" decoding="async" /></figure>
<h2 id="the-honest-framing" tabindex="-1">The honest framing <a class="anchor" href="#the-honest-framing" aria-hidden="true">#</a></h2>
<p>The DIY path isn’t wrong; it’s version one. Every feature above started life as somebody’s shell script, and if you kept iterating on your tmux setup — add a router script, a memory file, a budget checker, a Slack bridge, a recovery script — you’d converge on a harness. Munder Difflin is that convergence, already built, MIT-licensed, and local-first, so the six months of scripting goes into your actual work instead.</p>
<p>If you’re at two panes, enjoy them. If you’re at five and tired of being the message bus, <a href="https://github.com/chaitanyagiri/munder-difflin/releases/latest">download the latest release</a> — and if it saves you a script or two, <a href="https://github.com/chaitanyagiri/munder-difflin">a GitHub star</a> is appreciated.</p>
diff --git a/docs/blog/topics/comparisons/index.html b/docs/blog/topics/comparisons/index.html
index 7c8e31ce..cc0977fb 100644
--- a/docs/blog/topics/comparisons/index.html
+++ b/docs/blog/topics/comparisons/index.html
@@ -94,17 +94,17 @@
<a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/" aria-current="page">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
</div>
</header>
diff --git a/docs/blog/topics/concepts/index.html b/docs/blog/topics/concepts/index.html
index 1e758191..a061dbc8 100644
--- a/docs/blog/topics/concepts/index.html
+++ b/docs/blog/topics/concepts/index.html
@@ -94,17 +94,17 @@
<a class="chip" href="/blog/topics/concepts/" aria-current="page">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
</div>
</header>
diff --git a/docs/blog/topics/guides/index.html b/docs/blog/topics/guides/index.html
index fe533d7a..26ef1f7b 100644
--- a/docs/blog/topics/guides/index.html
+++ b/docs/blog/topics/guides/index.html
@@ -94,17 +94,17 @@
<a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
</div>
</header>
diff --git a/docs/blog/topics/index.html b/docs/blog/topics/index.html
index 832a0882..9e30ff16 100644
--- a/docs/blog/topics/index.html
+++ b/docs/blog/topics/index.html
@@ -110,7 +110,7 @@
<span class="thumb t-internals" aria-hidden="true">INTERNALS</span>
<div class="body">
<h3 style="color:var(--ink)">internals</h3>
- <p class="dek">17 posts.</p>
+ <p class="dek">18 posts.</p>
<div class="foot"><span class="more">View topic →</span></div>
</div>
</a>
@@ -128,7 +128,7 @@
<span class="thumb t-story" aria-hidden="true">STORY</span>
<div class="body">
<h3 style="color:var(--ink)">story</h3>
- <p class="dek">11 posts.</p>
+ <p class="dek">16 posts.</p>
<div class="foot"><span class="more">View topic →</span></div>
</div>
</a>
@@ -142,19 +142,19 @@
</div>
</a>
- <a class="card" href="/blog/topics/memory/" style="text-decoration:none">
- <span class="thumb t-memory" aria-hidden="true">MEMORY</span>
+ <a class="card" href="/blog/topics/use-cases/" style="text-decoration:none">
+ <span class="thumb t-use-cases" aria-hidden="true">USE-CASES</span>
<div class="body">
- <h3 style="color:var(--ink)">memory</h3>
- <p class="dek">5 posts.</p>
+ <h3 style="color:var(--ink)">use-cases</h3>
+ <p class="dek">9 posts.</p>
<div class="foot"><span class="more">View topic →</span></div>
</div>
</a>
- <a class="card" href="/blog/topics/use-cases/" style="text-decoration:none">
- <span class="thumb t-use-cases" aria-hidden="true">USE-CASES</span>
+ <a class="card" href="/blog/topics/memory/" style="text-decoration:none">
+ <span class="thumb t-memory" aria-hidden="true">MEMORY</span>
<div class="body">
- <h3 style="color:var(--ink)">use-cases</h3>
+ <h3 style="color:var(--ink)">memory</h3>
<p class="dek">5 posts.</p>
<div class="foot"><span class="more">View topic →</span></div>
</div>
@@ -166,36 +166,40 @@
<div class="filters" style="padding-top:36px">
<span class="eyebrow" style="align-self:center">Tags</span>
- <a class="chip" href="/blog/tags/multi-agent/">Multi-Agent<span class="ct">82</span></a>
+ <a class="chip" href="/blog/tags/multi-agent/">Multi-Agent<span class="ct">85</span></a>
<a class="chip" href="/blog/tags/claude-code/">Claude Code<span class="ct">45</span></a>
- <a class="chip" href="/blog/tags/internals/">Internals<span class="ct">24</span></a>
+ <a class="chip" href="/blog/tags/internals/">Internals<span class="ct">25</span></a>
<a class="chip" href="/blog/tags/guides/">Guides<span class="ct">23</span></a>
+ <a class="chip" href="/blog/tags/open-source/">Open Source<span class="ct">22</span></a>
+
<a class="chip" href="/blog/tags/orchestration/">Orchestration<span class="ct">19</span></a>
<a class="chip" href="/blog/tags/concepts/">Concepts<span class="ct">18</span></a>
<a class="chip" href="/blog/tags/comparisons/">Comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/tags/open-source/">Open Source<span class="ct">17</span></a>
+ <a class="chip" href="/blog/tags/story/">Story<span class="ct">17</span></a>
<a class="chip" href="/blog/tags/local-first/">Local-First<span class="ct">13</span></a>
- <a class="chip" href="/blog/tags/story/">Story<span class="ct">12</span></a>
+ <a class="chip" href="/blog/tags/release/">Release<span class="ct">13</span></a>
- <a class="chip" href="/blog/tags/automation/">Automation<span class="ct">11</span></a>
+ <a class="chip" href="/blog/tags/automation/">Automation<span class="ct">12</span></a>
- <a class="chip" href="/blog/tags/tools/">Tools<span class="ct">10</span></a>
+ <a class="chip" href="/blog/tags/use-cases/">Use Cases<span class="ct">10</span></a>
- <a class="chip" href="/blog/tags/release/">Release<span class="ct">10</span></a>
+ <a class="chip" href="/blog/tags/tools/">Tools<span class="ct">10</span></a>
<a class="chip" href="/blog/tags/getting-started/">Getting Started<span class="ct">9</span></a>
<a class="chip" href="/blog/tags/memory/">Memory<span class="ct">8</span></a>
+ <a class="chip" href="/blog/tags/workflow/">Workflow<span class="ct">7</span></a>
+
<a class="chip" href="/blog/tags/human-in-the-loop/">Human-in-the-Loop<span class="ct">7</span></a>
<a class="chip" href="/blog/tags/security/">Security<span class="ct">7</span></a>
@@ -204,8 +208,6 @@
<a class="chip" href="/blog/tags/mempalace/">MemPalace<span class="ct">6</span></a>
- <a class="chip" href="/blog/tags/use-cases/">Use Cases<span class="ct">6</span></a>
-
<a class="chip" href="/blog/tags/hive/">Hive<span class="ct">6</span></a>
<a class="chip" href="/blog/tags/observability/">Observability<span class="ct">5</span></a>
@@ -230,10 +232,10 @@
<a class="chip" href="/blog/tags/ide/">IDE<span class="ct">4</span></a>
- <a class="chip" href="/blog/tags/workflow/">Workflow<span class="ct">3</span></a>
-
<a class="chip" href="/blog/tags/terminals/">Terminals<span class="ct">3</span></a>
+ <a class="chip" href="/blog/tags/debugging/">Debugging<span class="ct">3</span></a>
+
<a class="chip" href="/blog/tags/model-routing/">Model Routing<span class="ct">3</span></a>
<a class="chip" href="/blog/tags/agentic-ai/">Agentic AI<span class="ct">3</span></a>
@@ -244,6 +246,8 @@
<a class="chip" href="/blog/tags/engines/">Engines<span class="ct">3</span></a>
+ <a class="chip" href="/blog/tags/launch/">Launch<span class="ct">3</span></a>
+
<a class="chip" href="/blog/tags/god/">GOD<span class="ct">2</span></a>
<a class="chip" href="/blog/tags/messaging/">Messaging<span class="ct">2</span></a>
@@ -260,9 +264,11 @@
<a class="chip" href="/blog/tags/hooks/">Hooks<span class="ct">2</span></a>
- <a class="chip" href="/blog/tags/performance/">Performance<span class="ct">2</span></a>
+ <a class="chip" href="/blog/tags/skills/">Skills<span class="ct">2</span></a>
- <a class="chip" href="/blog/tags/debugging/">Debugging<span class="ct">2</span></a>
+ <a class="chip" href="/blog/tags/node-pty/">node-pty<span class="ct">2</span></a>
+
+ <a class="chip" href="/blog/tags/performance/">Performance<span class="ct">2</span></a>
<a class="chip" href="/blog/tags/prompt-caching/">Prompt Caching<span class="ct">2</span></a>
@@ -278,6 +284,10 @@
<a class="chip" href="/blog/tags/agent-design/">Agent Design<span class="ct">2</span></a>
+ <a class="chip" href="/blog/tags/windows/">Windows<span class="ct">2</span></a>
+
+ <a class="chip" href="/blog/tags/community/">Community<span class="ct">2</span></a>
+
<a class="chip" href="/blog/tags/subagents/">Subagents<span class="ct">1</span></a>
<a class="chip" href="/blog/tags/markdown/">Markdown<span class="ct">1</span></a>
@@ -292,10 +302,6 @@
<a class="chip" href="/blog/tags/game-dev/">Game Dev<span class="ct">1</span></a>
- <a class="chip" href="/blog/tags/skills/">Skills<span class="ct">1</span></a>
-
- <a class="chip" href="/blog/tags/node-pty/">node-pty<span class="ct">1</span></a>
-
<a class="chip" href="/blog/tags/error-handling/">Error Handling<span class="ct">1</span></a>
<a class="chip" href="/blog/tags/context-engineering/">Context Engineering<span class="ct">1</span></a>
@@ -396,6 +402,28 @@
<a class="chip" href="/blog/tags/onboarding/">Onboarding<span class="ct">1</span></a>
+ <a class="chip" href="/blog/tags/research/">Research<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/design/">Design<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/eleventy/">Eleventy<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/meta/">Meta<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/product-hunt/">Product Hunt<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/changelog/">Changelog<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/postmortem/">Postmortem<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/feedback/">Feedback<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/product/">Product<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/discord/">Discord<span class="ct">1</span></a>
+
+ <a class="chip" href="/blog/tags/reddit/">Reddit<span class="ct">1</span></a>
+
</div>
</section>
diff --git a/docs/blog/topics/internals/index.html b/docs/blog/topics/internals/index.html
index 53dec22d..c095774b 100644
--- a/docs/blog/topics/internals/index.html
+++ b/docs/blog/topics/internals/index.html
@@ -85,7 +85,7 @@
</nav>
<p class="eyebrow">Topic</p>
<h1>internals</h1>
- <p class="lead">17 posts in this cluster.</p>
+ <p class="lead">18 posts in this cluster.</p>
<div class="filters" role="navigation" aria-label="Topics">
<a class="chip" href="/blog/">All</a>
@@ -94,17 +94,17 @@
<a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/" aria-current="page">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/" aria-current="page">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
</div>
</header>
@@ -112,6 +112,22 @@
<section class="wrap">
<div class="post-grid">
<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">
diff --git a/docs/blog/topics/memory/index.html b/docs/blog/topics/memory/index.html
index b8f41b8a..ddfdfd5d 100644
--- a/docs/blog/topics/memory/index.html
+++ b/docs/blog/topics/memory/index.html
@@ -94,17 +94,17 @@
<a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/" aria-current="page">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/" aria-current="page">memory<span class="ct">5</span></a>
</div>
</header>
diff --git a/docs/blog/topics/orchestration/index.html b/docs/blog/topics/orchestration/index.html
index bdbda766..524f7a89 100644
--- a/docs/blog/topics/orchestration/index.html
+++ b/docs/blog/topics/orchestration/index.html
@@ -94,17 +94,17 @@
<a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/" aria-current="page">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
</div>
</header>
diff --git a/docs/blog/topics/story/index.html b/docs/blog/topics/story/index.html
index af447806..8cc434e1 100644
--- a/docs/blog/topics/story/index.html
+++ b/docs/blog/topics/story/index.html
@@ -85,7 +85,7 @@
</nav>
<p class="eyebrow">Topic</p>
<h1>story</h1>
- <p class="lead">11 posts in this cluster.</p>
+ <p class="lead">16 posts in this cluster.</p>
<div class="filters" role="navigation" aria-label="Topics">
<a class="chip" href="/blog/">All</a>
@@ -94,17 +94,17 @@
<a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/" aria-current="page">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/" aria-current="page">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
</div>
</header>
@@ -112,6 +112,86 @@
<section class="wrap">
<div class="post-grid">
<article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/we-opened-a-discord/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/we-opened-a-discord/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>2 min</span>
+ </div>
+ <h3><a href="/blog/we-opened-a-discord/">We Opened a Discord (Merge a PR, Become Employee of the Month)</a></h3>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/we-opened-a-discord/" aria-label="Read: We Opened a Discord (Merge a PR, Become Employee of the Month)">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/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>3 min</span>
+ </div>
+ <h3><a href="/blog/what-reddit-told-us-about-munder-difflin/">What 516 Reddit Comments Told Us About Munder Difflin</a></h3>
+ <p class="dek">We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/what-reddit-told-us-about-munder-difflin/" aria-label="Read: What 516 Reddit Comments Told Us About Munder Difflin">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
<a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
@@ -213,7 +293,7 @@
<div class="meta">
<time datetime="2026-06-09">Jun 9, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>7 min</span>
</div>
<h3><a href="/blog/launching-munder-difflin-v0-2-4/">Launching Munder Difflin v0.2.4</a></h3>
<p class="dek">Munder Difflin v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</p>
diff --git a/docs/blog/topics/use-cases/index.html b/docs/blog/topics/use-cases/index.html
index fb5ce918..635ccf7d 100644
--- a/docs/blog/topics/use-cases/index.html
+++ b/docs/blog/topics/use-cases/index.html
@@ -85,7 +85,7 @@
</nav>
<p class="eyebrow">Topic</p>
<h1>use-cases</h1>
- <p class="lead">5 posts in this cluster.</p>
+ <p class="lead">9 posts in this cluster.</p>
<div class="filters" role="navigation" aria-label="Topics">
<a class="chip" href="/blog/">All</a>
@@ -94,17 +94,17 @@
<a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">21</span></a>
- <a class="chip" href="/blog/topics/internals/">internals<span class="ct">17</span></a>
+ <a class="chip" href="/blog/topics/internals/">internals<span class="ct">18</span></a>
<a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">17</span></a>
- <a class="chip" href="/blog/topics/story/">story<span class="ct">11</span></a>
+ <a class="chip" href="/blog/topics/story/">story<span class="ct">16</span></a>
<a class="chip" href="/blog/topics/orchestration/">orchestration<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/use-cases/" aria-current="page">use-cases<span class="ct">9</span></a>
- <a class="chip" href="/blog/topics/use-cases/" aria-current="page">use-cases<span class="ct">5</span></a>
+ <a class="chip" href="/blog/topics/memory/">memory<span class="ct">5</span></a>
</div>
</header>
@@ -112,6 +112,70 @@
<section class="wrap">
<div class="post-grid">
<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/turn-feedback-into-a-backlog-with-agents/">Turn a Firehose of Feedback into a Backlog with Agents</a></h3>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/turn-feedback-into-a-backlog-with-agents/" aria-label="Read: Turn a Firehose of Feedback into a Backlog with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
<a class="thumb t-use-cases" href="/blog/deploy-a-blog-writer-agent/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deploy-a-blog-writer-agent/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
diff --git a/docs/blog/trigger-ai-agents-from-github-webhook/index.html b/docs/blog/trigger-ai-agents-from-github-webhook/index.html
index 1673d28a..e672c029 100644
--- a/docs/blog/trigger-ai-agents-from-github-webhook/index.html
+++ b/docs/blog/trigger-ai-agents-from-github-webhook/index.html
@@ -199,6 +199,7 @@ to that local port. That’s the URL you give GitHub.</li>
reports the tunnel error without a URL — so you’re never in a half-broken state where the endpoint is exposed
but unguarded. The tunnel is a doorbell; it is not what keeps strangers out.</p>
<p>Copy the public URL. You’ll paste it into GitHub next.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/trigger-ai-agents-from-github-webhook/note-1.png" alt="Hand-drawn sketch from “How to Trigger Your AI Agent Hive from a GitHub Webhook”" loading="lazy" decoding="async" /></figure>
<h2 id="step-2-point-github-at-it" tabindex="-1">Step 2 — Point GitHub at it <a class="anchor" href="#step-2-point-github-at-it" aria-hidden="true">#</a></h2>
<p>You have two clean ways to do this, depending on how literal you want to be.</p>
<p><strong>Option A — A GitHub Action (recommended).</strong> GitHub’s native webhooks send GitHub’s <em>own</em> payload shape, but
@@ -254,6 +255,7 @@ just another task: the orchestrator reads it, decides who should handle it, and
exactly like work that arrives through <a href="/blog/coordinating-ai-coding-agents/">the hive’s normal message
routing</a>. A reviewer agent might read the PR; a writer might draft the
issue response. The webhook doesn’t pick the agent — it just gets the work onto the board.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/trigger-ai-agents-from-github-webhook/note-2.png" alt="Hand-drawn sketch from “How to Trigger Your AI Agent Hive from a GitHub Webhook”" loading="lazy" decoding="async" /></figure>
<h2 id="security-in-one-breath" tabindex="-1">Security, in one breath <a class="anchor" href="#security-in-one-breath" aria-hidden="true">#</a></h2>
<p>A public endpoint that can enqueue work for autonomous agents is exactly what you don’t want strangers poking,
so the handler treats every request as hostile until proven otherwise:</p>
diff --git a/docs/blog/trigger-ai-agents-from-slack/index.html b/docs/blog/trigger-ai-agents-from-slack/index.html
index ae54595e..1fe114de 100644
--- a/docs/blog/trigger-ai-agents-from-slack/index.html
+++ b/docs/blog/trigger-ai-agents-from-slack/index.html
@@ -186,6 +186,7 @@ best-effort <strong>local tunnel</strong> and hands you a public URL to paste in
Subscriptions → Request URL</em>. That tunnel is just a doorbell: it forwards Slack’s POSTs to your local
port. If it can’t be established, the local handler stays up anyway — the tunnel is a convenience, not
the security boundary.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/trigger-ai-agents-from-slack/note-1.png" alt="Hand-drawn sketch from “Trigger Your AI Agent Hive from Slack”" loading="lazy" decoding="async" /></figure>
<h2 id="security-verify-everything-before-you-trust-it" tabindex="-1">Security: verify everything before you trust it <a class="anchor" href="#security-verify-everything-before-you-trust-it" aria-hidden="true">#</a></h2>
<p>A webhook that can enqueue work for autonomous agents is exactly the kind of endpoint you don’t want
strangers poking. So the handler treats every request as hostile until proven otherwise:</p>
@@ -211,6 +212,7 @@ through <a href="/blog/coordinating-ai-coding-agents/">the hive’s normal messa
<p>You can scope what counts, too. An optional <strong>channel filter</strong> means only messages from one specific
channel are accepted; events from anywhere else are dropped before they ever reach the queue. That
keeps a noisy workspace from turning into a noisy hive.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/trigger-ai-agents-from-slack/note-2.png" alt="Hand-drawn sketch from “Trigger Your AI Agent Hive from Slack”" loading="lazy" decoding="async" /></figure>
<h2 id="setting-it-up" tabindex="-1">Setting it up <a class="anchor" href="#setting-it-up" aria-hidden="true">#</a></h2>
<p>The moving parts are minimal. In the app you enable Slack and paste your <strong>signing secret</strong> (from your
Slack app’s <em>Basic Information</em>). Optionally set a <strong>channel id</strong> to listen to just one channel, and a
diff --git a/docs/blog/turn-feedback-into-a-backlog-with-agents/index.html b/docs/blog/turn-feedback-into-a-backlog-with-agents/index.html
new file mode 100644
index 00000000..836828a8
--- /dev/null
+++ b/docs/blog/turn-feedback-into-a-backlog-with-agents/index.html
@@ -0,0 +1,372 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>Turn a Firehose of Feedback into a Backlog with Agents — Munder Difflin Blog</title>
+<meta name="description" content="516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts." />
+<link rel="canonical" href="https://munderdiffl.in/blog/turn-feedback-into-a-backlog-with-agents/" />
+
+<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="Turn a Firehose of Feedback into a Backlog with Agents — Munder Difflin Blog" />
+<meta property="og:description" content="516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts." />
+<meta property="og:url" content="https://munderdiffl.in/blog/turn-feedback-into-a-backlog-with-agents/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Use Cases" />
+<meta property="article:tag" content="Feedback" />
+<meta property="article:tag" content="Workflow" />
+<meta property="article:tag" content="Product" />
+<meta property="article:tag" content="Multi-Agent" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="Turn a Firehose of Feedback into a Backlog with Agents — Munder Difflin Blog" />
+<meta name="twitter:description" content="516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "Turn a Firehose of Feedback into a Backlog with Agents",
+ "description": "516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/turn-feedback-into-a-backlog-with-agents/" },
+ "keywords": "ai agents process user feedback, feedback triage automation, turn comments into backlog, user feedback analysis ai, product feedback workflow, munder difflin use case",
+ "articleSection": "Use Cases",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/turn-feedback-into-a-backlog-with-agents/"
+}
+</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": "Turn a Firehose of Feedback into a Backlog with Agents", "item": "https://munderdiffl.in/blog/turn-feedback-into-a-backlog-with-agents/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "How do agents turn raw comments into a backlog?", "acceptedAnswer": { "@type": "Answer", "text": "Three passes: bucket every comment (bug, feature ask, objection, praise) with quotes and links preserved; merge duplicates across channels so five phrasings of one problem become one item with five receipts; then rank by evidence — how many distinct people, how serious, how blocked. The output is kanban cards whose descriptions cite the actual users." } },
+ { "@type": "Question", "name": "What's the advantage over just reading the comments yourself?", "acceptedAnswer": { "@type": "Answer", "text": "Coverage and honesty. A human skims, remembers the loudest five comments, and calls it the community's opinion. An agent instructed to account for every comment can't skip the boring middle — and the resulting backlog item carries links to every person who reported it, which also gives you a list of exactly who to tell when it ships." } },
+ { "@type": "Question", "name": "Did this actually change what Munder Difflin shipped?", "acceptedAnswer": { "@type": "Answer", "text": "Directly. The launch-week backlog put the Windows messaging failure and onboarding dead-ends at the top on evidence volume, and both headline v0.4.4. The 'this decision needs your eyes' flag — asked for independently by two users on two different channels — is on the roadmap because cross-channel merging revealed it was one request, not two." } }
+
+ ]
+}
+</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,
+ 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-use-cases">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/use-cases/">Use Cases</a>
+ </nav>
+ <h1>Turn a Firehose of Feedback into a Backlog with Agents</h1>
+ <p class="dek">516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>3 min read</span>
+ <span class="tag kind">Use Cases</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-agents/hero.png" alt="Illustration: Turn a Firehose of Feedback into a Backlog with Agents" 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>Feedback is an asset with a
+half-life: unprocessed, it decays into a vibe. After launch week handed us <strong>516 Reddit
+comments, a Product Hunt thread, and a swelling issue tracker</strong>, agents turned all of it
+into a ranked backlog where every card cites the real humans who asked. Two of the top three
+cards shipped in v0.4.4. The workflow, start to finish.</p></div>
+<p>Launch-week feedback has a cruel shape: it arrives all at once, from five channels, in wildly
+mixed quality, precisely when you have the least attention to spare. Read it casually and
+you’ll remember the funniest insult and the nicest compliment, then confidently misbuild your
+roadmap around them both.</p>
+<p>The fix isn’t discipline. It’s admitting this is a data-processing job and
+<a href="/blog/small-team-ai-agents-playbook/">staffing it accordingly</a>.</p>
+<h2 id="pass-one-account-for-everything" tabindex="-1">Pass one: account for everything <a class="anchor" href="#pass-one-account-for-everything" aria-hidden="true">#</a></h2>
+<p>The first pass is deliberately dumb: every comment, from every channel, gets bucketed —
+<strong>bug report, feature ask, objection, praise, question</strong> — with the quote, the author, and the
+permalink preserved. The brief’s key sentence is <em>account for every comment</em>, because that’s
+the sentence a tired human violates. Ours came back with counts we still quote in arguments:
+utility skepticism, 12 distinct commenters; token-cost concern, 11.</p>
+<p>The receipts matter more than the counts. “Users are worried about cost” starts a debate;
+eleven linked quotes end one.</p>
+<h2 id="pass-two-merge-across-channels" tabindex="-1">Pass two: merge across channels <a class="anchor" href="#pass-two-merge-across-channels" aria-hidden="true">#</a></h2>
+<figure class="fig fig-inline"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-agents/note-1.png" alt="Hand-drawn sketch from “Turn a Firehose of Feedback into a Backlog with Agents”" loading="lazy" decoding="async" /><figcaption>Five phrasings, two platforms, one problem. Cross-channel merging is where the signal actually lives.</figcaption></figure>
+<p>The pass most teams never do, because it requires holding everything at once. The same problem
+arrives dressed differently per platform: a Product Hunt commenter politely reports being
+unable to switch engines after setup; a Redditor says the onboarding dead-ended; a GitHub
+issue titles it precisely. One agent with all three corpora merges them into <strong>one backlog
+item with five receipts</strong> — and suddenly it’s not three small complaints, it’s one bug class
+blocking a fifth of new evaluators.</p>
+<p>This pass produced our best roadmap insight of the year: our two most sophisticated users — on
+<em>different platforms, in different words</em> — asked for the same missing primitive, a visible
+“this decision needs your eyes” flag on agents. Read channel by channel, that’s two mild
+comments. Merged, it’s the <a href="/blog/human-in-the-loop-ai-agents/">clearest feature signal we’ve ever
+received</a>.</p>
+<h2 id="pass-three-rank-on-evidence-file-as-work" tabindex="-1">Pass three: rank on evidence, file as work <a class="anchor" href="#pass-three-rank-on-evidence-file-as-work" aria-hidden="true">#</a></h2>
+<p>The final pass turns merged items into kanban cards, ranked by things you can defend: how many
+distinct people, how blocked they were, whether they’re the kind of user you’re building for.
+The card’s description carries the quotes and links, so whoever picks it up — human or
+<a href="/blog/deploy-automated-pr-reviewer-agent/">agent</a> — starts from the actual reports rather
+than a paraphrase.</p>
+<p>Then the backlog met reality: the top cards became
+<a href="/blog/launching-munder-difflin-v0-4-4/">v0.4.4’s headline fixes</a>. And because every card
+carried its reporters, “tell the people who reported it” was a checklist item, not archaeology.
+One blocked user from launch week had said, verbatim, that he’d re-test when the fix shipped.
+The card knew his name. That follow-up is worth more than a week of marketing.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/turn-feedback-into-a-backlog-with-agents/note-2.png" alt="Hand-drawn sketch from “Turn a Firehose of Feedback into a Backlog with Agents”" loading="lazy" decoding="async" /><figcaption>The card remembers who reported it — so shipping the fix comes with a list of exactly who to tell.</figcaption></figure>
+<h2 id="the-compounding-part" tabindex="-1">The compounding part <a class="anchor" href="#the-compounding-part" aria-hidden="true">#</a></h2>
+<p>Do this once and it’s a great retro. The compounding version is a <strong>standing intake</strong>: the
+same bucketing agent runs on whatever accumulated overnight — new issues, Discord threads,
+stray mentions — and appends to the same backlog under the same merge rules, on a
+<a href="/blog/scheduling-autonomous-agent-missions/">schedule</a>. Feedback stops being an event and
+becomes a pipeline, and the backlog stays ranked by evidence instead of by whoever shouted
+most recently.</p>
+<p>The uncomfortable, useful truth we took from ours:
+<a href="/blog/what-reddit-told-us-about-munder-difflin/">the community’s</a> most upvoted praise and its
+sharpest criticism pointed at the same place — people love <em>watching</em> agents work and want
+more <em>control</em> over what they see. A backlog built on receipts forces you to hear both halves.
+That tension is now the roadmap’s spine, and we can cite our sources.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">How do agents turn raw comments into a backlog?</p>
+ <p class="a">Three passes: bucket every comment (bug, feature ask, objection, praise) with quotes and links preserved; merge duplicates across channels so five phrasings of one problem become one item with five receipts; then rank by evidence — how many distinct people, how serious, how blocked. The output is kanban cards whose descriptions cite the actual users.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">What&#39;s the advantage over just reading the comments yourself?</p>
+ <p class="a">Coverage and honesty. A human skims, remembers the loudest five comments, and calls it the community&#39;s opinion. An agent instructed to account for every comment can&#39;t skip the boring middle — and the resulting backlog item carries links to every person who reported it, which also gives you a list of exactly who to tell when it ships.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Did this actually change what Munder Difflin shipped?</p>
+ <p class="a">Directly. The launch-week backlog put the Windows messaging failure and onboarding dead-ends at the top on evidence volume, and both headline v0.4.4. The &#39;this decision needs your eyes&#39; flag — asked for independently by two users on two different channels — is on the roadmap because cross-channel merging revealed it was one request, not two.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/use-cases/">Use Cases</a><a class="tag" href="/blog/tags/feedback/">Feedback</a><a class="tag" href="/blog/tags/workflow/">Workflow</a><a class="tag" href="/blog/tags/product/">Product</a><a class="tag" href="/blog/tags/multi-agent/">Multi-Agent</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="#pass-one-account-for-everything">Pass one: account for everything</a></li><li class="lvl-2"><a href="#pass-two-merge-across-channels">Pass two: merge across channels</a></li><li class="lvl-2"><a href="#pass-three-rank-on-evidence-file-as-work">Pass three: rank on evidence, file as work</a></li><li class="lvl-2"><a href="#the-compounding-part">The compounding part</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/we-opened-a-discord/"><span class="k">← Older</span><span class="t">We Opened a Discord (Merge a PR, Become Employee of the Month)</span></a>
+ <a class="pn next" href="/blog/the-newline-that-silenced-windows-agents/"><span class="k">Newer →</span><span class="t">The Newline That Silenced Every Windows Agent</span></a>
+ </div>
+ <section class="related">
+ <h2>Related in Use Cases</h2>
+ <div class="post-grid">
+ <article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/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>3 min</span>
+ </div>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/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>3 min</span>
+ </div>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-use-cases">
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-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>3 min</span>
+ </div>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
+ <div class="foot">
+ <span class="tag kind">Use Cases</span>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/vibe-kanban-alternative/index.html b/docs/blog/vibe-kanban-alternative/index.html
index 69c8f927..78096477 100644
--- a/docs/blog/vibe-kanban-alternative/index.html
+++ b/docs/blog/vibe-kanban-alternative/index.html
@@ -165,6 +165,7 @@ land.</li>
</ul>
<p>If you think in tasks and want a project-management surface over your agents, vibe-kanban fits
naturally. The reason to look elsewhere is about <em>who does the routing</em>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/vibe-kanban-alternative/note-1.png" alt="Hand-drawn sketch from “A vibe-kanban Alternative for Coordinating AI Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="where-a-board-leaves-the-work-to-you" tabindex="-1">Where a board leaves the work to you <a class="anchor" href="#where-a-board-leaves-the-work-to-you" aria-hidden="true">#</a></h2>
<p>A kanban board is something a human drives. That’s its strength and its ceiling:</p>
<h3 id="you-are-the-router" tabindex="-1">You are the router <a class="anchor" href="#you-are-the-router" aria-hidden="true">#</a></h3>
@@ -178,6 +179,7 @@ doesn’t compound.</p>
<h3 id="agents-dont-message-each-other" tabindex="-1">Agents don’t message each other <a class="anchor" href="#agents-dont-message-each-other" aria-hidden="true">#</a></h3>
<p>Coordination between cards goes through you and the board, not agent-to-agent. There’s no mailbox for
one agent to hand a finding directly to another.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/vibe-kanban-alternative/note-2.png" alt="Hand-drawn sketch from “A vibe-kanban Alternative for Coordinating AI Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="what-a-self-routing-hive-does-instead" tabindex="-1">What a self-routing hive does instead <a class="anchor" href="#what-a-self-routing-hive-does-instead" aria-hidden="true">#</a></h2>
<p>The alternative flips the model: instead of <em>you</em> working a board, you describe intent and the system
routes the work.</p>
diff --git a/docs/blog/visualizing-ai-agents-pixijs/index.html b/docs/blog/visualizing-ai-agents-pixijs/index.html
index e021f8db..8e8a5535 100644
--- a/docs/blog/visualizing-ai-agents-pixijs/index.html
+++ b/docs/blog/visualizing-ai-agents-pixijs/index.html
@@ -194,6 +194,7 @@ following a selected agent feels natural rather than jumpy.</p>
<p>One more structural choice: a <strong>single shared ticker</strong> drives all animation. Every frame, the ticker
hands out a delta-time and each live thing (avatars, envelopes, camera) advances by <code>dt</code>. One loop,
not dozens of timers — which keeps motion synchronized and the frame budget predictable.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/visualizing-ai-agents-pixijs/note-1.png" alt="Hand-drawn sketch from “Visualizing AI Agents with Pixi.js: An Office You Can Watch”" loading="lazy" decoding="async" /></figure>
<h2 id="the-floor-is-a-tiled-map" tabindex="-1">The floor is a Tiled map <a class="anchor" href="#the-floor-is-a-tiled-map" aria-hidden="true">#</a></h2>
<p>The office isn’t hand-coded geometry; it’s a <strong>Tiled</strong> map (<code>.tmj</code>) — the same format 2D game
designers use. The renderer parses its layers:</p>
@@ -217,6 +218,7 @@ small <strong>leg-crop mask</strong> tucks a seated agent under its desk so it r
standing on the furniture. The cast is recolored per character, so the team is visually
distinguishable at a glance.</p>
<p>But the sprites are just the <em>body</em>. What makes them meaningful is what drives them.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/visualizing-ai-agents-pixijs/note-2.png" alt="Hand-drawn sketch from “Visualizing AI Agents with Pixi.js: An Office You Can Watch”" loading="lazy" decoding="async" /></figure>
<h2 id="the-honest-part-real-events-not-a-script" tabindex="-1">The honest part: real events, not a script <a class="anchor" href="#the-honest-part-real-events-not-a-script" aria-hidden="true">#</a></h2>
<p>This is the design principle that matters most. The avatars are <strong>not</strong> playing a canned animation —
they move in response to real signals from two sources:</p>
@@ -305,6 +307,22 @@ to see your agents at work; it’s free and open source.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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">
@@ -336,22 +354,6 @@ to see your agents at work; it’s free and open source.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/compressing-agent-memory/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/compressing-agent-memory/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-05">Jun 5, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/compressing-agent-memory/">Compressing Agent Memory Without Losing the Original</a></h3>
- <p class="dek">How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/compressing-agent-memory/" aria-label="Read: Compressing Agent Memory Without Losing the Original">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/voice-as-a-control-plane-for-agent-fleets/index.html b/docs/blog/voice-as-a-control-plane-for-agent-fleets/index.html
index ebf6e7ee..84a307d5 100644
--- a/docs/blog/voice-as-a-control-plane-for-agent-fleets/index.html
+++ b/docs/blog/voice-as-a-control-plane-for-agent-fleets/index.html
@@ -173,10 +173,12 @@
</ul>
<p>Each of these is a sentence. Each fans out into minutes or hours of high-bandwidth work that the <em>agents</em> perform — reading files, running builds, writing diffs. That’s the asymmetry that makes voice fit: <strong>low-bandwidth commands over high-bandwidth work.</strong> You supply intent; the fleet supplies density. It’s the same division of labor a <a href="/blog/how-the-god-orchestrator-works/">GOD orchestrator</a> already imposes on typed input — voice just removes the keyboard from the loop when the keyboard was barely being used anyway.</p>
<p>The other half of the fit: orchestration is naturally <em>ambient</em>. You’re across the room while an overnight mission grinds. A status question shouldn’t cost you a walk to the desk, and a completion shouldn’t wait until you happen to glance at a terminal.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/voice-as-a-control-plane-for-agent-fleets/note-1.png" alt="Hand-drawn sketch from “Voice Is a Control Plane, Not a Gimmick”" loading="lazy" decoding="async" /></figure>
<h2 id="case-study-talk-mode" tabindex="-1">Case study: Talk mode <a class="anchor" href="#case-study-talk-mode" aria-hidden="true">#</a></h2>
<p>Munder Difflin shipped this thesis as a feature in v0.3.2 (the <a href="/blog/launching-munder-difflin-v0-3-2/">launch post</a> has the full tour). Press <strong>Talk</strong> and you get a low-latency voice channel — OpenAI Realtime API over WebRTC, bring-your-own key — to Michael, the GOD orchestrator, running <em>alongside</em> the async terminal floor, not replacing it.</p>
<p>Michael listens, answers, and acts. The read side covers the hive: tasks, board, memory, agents, activity, cost. The action side is the full orchestration verb set: create and assign tasks, dispatch agents, pause / steer / halt, spawn and hire workers, kill them, edit schedules. Notice what’s <em>not</em> in that list: writing code. The voice channel never touches an editor. It only moves work around — exactly the payload the channel can carry.</p>
<p>And the loop closes in both directions. Voice-dispatched work reports back on its own: a completion watcher detects when a task lands and pushes the event into the live session so <strong>Michael speaks it unprompted</strong> — “respond when done” as a first-class behavior, with an on-screen toast, and a queue-to-notification path if the session is already closed. That’s the ambient half delivered: you delegated by sentence, and the result comes back as a sentence.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/voice-as-a-control-plane-for-agent-fleets/note-2.png" alt="Hand-drawn sketch from “Voice Is a Control Plane, Not a Gimmick”" loading="lazy" decoding="async" /></figure>
<h2 id="a-control-plane-needs-guardrails-not-vibes" tabindex="-1">A control plane needs guardrails, not vibes <a class="anchor" href="#a-control-plane-needs-guardrails-not-vibes" aria-hidden="true">#</a></h2>
<p>Here’s where “control plane” stops being a metaphor and starts being an engineering standard. A microphone is a noisy, spoofable, mishearable input device wired to verbs like <em>kill</em>. If you treat that casually, you’ve built a gimmick with a blast radius. Talk mode’s guardrails are the interesting part:</p>
<p><strong>Echo-back confirmation for destructive verbs.</strong> Every destructive action is gated behind a <em>spoken</em> echo-back: Michael repeats exactly what he’s about to do and requires a distinct confirm token — never a bare “yes,” which a stray utterance could trip. On top of that sit hard refusals: he will not kill the GOD agent, and he will not target all agents at once, period. Even task <em>matching</em> is defensive — spoken phrases are normalized and scored against stored titles, and a close call triggers a spoken “which one?” instead of silently mutating the wrong card. This is the same discipline as any <a href="/blog/human-in-the-loop-approving-ai-agents/">human-in-the-loop approval gate</a>, adapted to a channel where the human’s “click” is a phrase.</p>
diff --git a/docs/blog/we-opened-a-discord/index.html b/docs/blog/we-opened-a-discord/index.html
new file mode 100644
index 00000000..5403b899
--- /dev/null
+++ b/docs/blog/we-opened-a-discord/index.html
@@ -0,0 +1,364 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>We Opened a Discord (Merge a PR, Become Employee of the Month) — Munder Difflin Blog</title>
+<meta name="description" content="Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source." />
+<link rel="canonical" href="https://munderdiffl.in/blog/we-opened-a-discord/" />
+
+<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="We Opened a Discord (Merge a PR, Become Employee of the Month) — Munder Difflin Blog" />
+<meta property="og:description" content="Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source." />
+<meta property="og:url" content="https://munderdiffl.in/blog/we-opened-a-discord/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Story" />
+<meta property="article:tag" content="Community" />
+<meta property="article:tag" content="Discord" />
+<meta property="article:tag" content="Open Source" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="We Opened a Discord (Merge a PR, Become Employee of the Month) — Munder Difflin Blog" />
+<meta name="twitter:description" content="Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "We Opened a Discord (Merge a PR, Become Employee of the Month)",
+ "description": "Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/we-opened-a-discord/" },
+ "keywords": "munder difflin discord, munder difflin community, open source discord server, contribute to munder difflin, claude code community",
+ "articleSection": "Story",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/we-opened-a-discord/"
+}
+</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": "We Opened a Discord (Merge a PR, Become Employee of the Month)", "item": "https://munderdiffl.in/blog/we-opened-a-discord/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "Where is the Munder Difflin Discord?", "acceptedAnswer": { "@type": "Answer", "text": "discord.gg/SEDzP5ZPk5 — also linked from the site nav, the footer, and the README. It's free, it's where release news lands first, and it's the fastest way to get help with a setup problem or show off what your floor is doing." } },
+ { "@type": "Question", "name": "What is the employee of the month role?", "acceptedAnswer": { "@type": "Answer", "text": "Merge a pull request into Munder Difflin and a GitHub workflow automatically grants you the 'employee of the month' role in the Discord. There's an optional Discord field in the PR template so the bot knows who to promote. It's a joke that's also completely sincere." } },
+ { "@type": "Question", "name": "Why a Discord and not GitHub Discussions?", "acceptedAnswer": { "@type": "Answer", "text": "GitHub stays the home for issues and PRs — bugs belong where the code is. What launch week showed is that people also want a lower-stakes room: quick setup questions, sharing screenshots of their office floor, and hearing what's shipping before it ships. That's chat-shaped, not issue-shaped." } }
+
+ ]
+}
+</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,
+ 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-story">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/story/">Story</a>
+ </nav>
+ <h1>We Opened a Discord (Merge a PR, Become Employee of the Month)</h1>
+ <p class="dek">Munder Difflin has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>2 min read</span>
+ <span class="tag kind">Story</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/we-opened-a-discord/hero.png" alt="Illustration: We Opened a Discord (Merge a PR, Become Employee of the Month)" 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>Munder Difflin has a Discord:
+<a href="https://discord.gg/SEDzP5ZPk5">discord.gg/SEDzP5ZPk5</a>. Release news first, setup
+help fastest, floor screenshots welcome. And a workflow now watches the repo: <strong>merge a
+PR, and you're automatically granted the <em>employee of the month</em> role.</strong> We
+regret nothing about this feature and never will.</p></div>
+<p>For a product that’s an office homage, we were weirdly hard to hang out with. Feedback lived
+in GitHub issues, launch threads on
+<a href="/blog/what-reddit-told-us-about-munder-difflin/">Reddit</a> and
+<a href="/blog/number-five-on-product-hunt/">Product Hunt</a>, and an inbox we won’t discuss. Launch week
+made the gap obvious: between “formal bug report” and “shouting into a Reddit thread” there
+was nowhere to just… ask a quick question. Or post a screenshot of nine agents pulling an
+all-nighter.</p>
+<p>So: <strong><a href="https://discord.gg/SEDzP5ZPk5">discord.gg/SEDzP5ZPk5</a></strong>. The lobby is open.</p>
+<h2 id="what-its-for" tabindex="-1">What it’s for <a class="anchor" href="#what-its-for" aria-hidden="true">#</a></h2>
+<p><strong>Release news, first.</strong> We just shipped
+<a href="/blog/seven-releases-in-eight-days/">seven releases in eight days</a>; Discord is where drops
+get announced the moment they’re tagged, and where we’ll be honest about what’s still rough.</p>
+<p><strong>Setup help, fast.</strong> A meaningful share of launch-week frustration was
+<a href="/blog/launching-munder-difflin-v0-4-4/">first-run problems</a> that a two-minute conversation
+would have solved. If onboarding fights you, come fight back in a channel where someone’s
+awake — the community spans enough timezones now that someone usually is.</p>
+<p><strong>Show your floor.</strong> The screenshots people posted during launch week — offices mid-swarm,
+agents <a href="/blog/claude-code-automation-while-you-sleep/">working through the night</a> — were the
+best part of the whole launch. They deserve a wall. This is the wall.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/we-opened-a-discord/note-1.png" alt="Hand-drawn sketch from “We Opened a Discord (Merge a PR, Become Employee of the Month)”" loading="lazy" decoding="async" /><figcaption>Between 'formal bug report' and 'Reddit thread' there was nowhere to just ask. Now there's a lobby.</figcaption></figure>
+<h2 id="employee-of-the-month" tabindex="-1">Employee of the month <a class="anchor" href="#employee-of-the-month" aria-hidden="true">#</a></h2>
+<p>Here’s the part we’re irrationally proud of. Contributing to Munder Difflin now comes with a
+title: <strong>merge a pull request, and a GitHub workflow automatically grants you the <em>employee of
+the month</em> role in the Discord.</strong> The PR template has an optional <code>Discord:</code> field so the bot
+knows who to celebrate. No nomination committee, no monthly limit, no plaque in a hallway —
+just a workflow that fires on merge, because in this office, recognition is automated too.</p>
+<p>The inaugural class earned it properly:
+<a href="/blog/launching-munder-difflin-v0-4-4/">v0.4.4 carries nine community PRs</a> —
+<a href="https://github.com/gts-47">@gts-47</a> with eight, from atomic task-ledger writes to un-silencing
+an agent’s wake nudge, and <a href="https://github.com/baziyer">@baziyer</a> with the fix that stops the
+office floor rendering when nobody’s watching it. If you’ve been thinking about a first
+contribution, the <a href="https://github.com/chaitanyagiri/munder-difflin">good-first-issue path</a>
+now ends with a job title.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/we-opened-a-discord/note-2.png" alt="Hand-drawn sketch from “We Opened a Discord (Merge a PR, Become Employee of the Month)”" loading="lazy" decoding="async" /><figcaption>Merge a PR, get the role. Recognition is a workflow now, like everything else around here.</figcaption></figure>
+<h2 id="the-rules-of-the-room" tabindex="-1">The rules of the room <a class="anchor" href="#the-rules-of-the-room" aria-hidden="true">#</a></h2>
+<p>Short version: GitHub remains the source of truth — bugs and feature requests belong in
+issues, where they <a href="/blog/turn-feedback-into-a-backlog-with-agents/">get triaged into real work</a>
+rather than scrolling away. The Discord is for everything that’s conversation-shaped. Be kind,
+assume good faith, and if you built something weird with your hive, we absolutely want to see
+it.</p>
+<p>The product has always been a bet that work is better with
+<a href="/blog/building-an-ai-office-floor/">a floor full of colleagues you can see</a>. It was overdue
+that the humans got a floor too. Come say hi:
+<strong><a href="https://discord.gg/SEDzP5ZPk5">discord.gg/SEDzP5ZPk5</a></strong>.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">Where is the Munder Difflin Discord?</p>
+ <p class="a">discord.gg/SEDzP5ZPk5 — also linked from the site nav, the footer, and the README. It&#39;s free, it&#39;s where release news lands first, and it&#39;s the fastest way to get help with a setup problem or show off what your floor is doing.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">What is the employee of the month role?</p>
+ <p class="a">Merge a pull request into Munder Difflin and a GitHub workflow automatically grants you the &#39;employee of the month&#39; role in the Discord. There&#39;s an optional Discord field in the PR template so the bot knows who to promote. It&#39;s a joke that&#39;s also completely sincere.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">Why a Discord and not GitHub Discussions?</p>
+ <p class="a">GitHub stays the home for issues and PRs — bugs belong where the code is. What launch week showed is that people also want a lower-stakes room: quick setup questions, sharing screenshots of their office floor, and hearing what&#39;s shipping before it ships. That&#39;s chat-shaped, not issue-shaped.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/story/">Story</a><a class="tag" href="/blog/tags/community/">Community</a><a class="tag" href="/blog/tags/discord/">Discord</a><a class="tag" href="/blog/tags/open-source/">Open Source</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="#what-its-for">What it’s for</a></li><li class="lvl-2"><a href="#employee-of-the-month">Employee of the month</a></li><li class="lvl-2"><a href="#the-rules-of-the-room">The rules of the room</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/what-reddit-told-us-about-munder-difflin/"><span class="k">← Older</span><span class="t">What 516 Reddit Comments Told Us About Munder Difflin</span></a>
+ <a class="pn next" href="/blog/turn-feedback-into-a-backlog-with-agents/"><span class="k">Newer →</span><span class="t">Turn a Firehose of Feedback into a Backlog with Agents</span></a>
+ </div>
+ <section class="related">
+ <h2>Related in Story</h2>
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/what-are-claude-code-agents/index.html b/docs/blog/what-are-claude-code-agents/index.html
index 6824958b..0a14b0d0 100644
--- a/docs/blog/what-are-claude-code-agents/index.html
+++ b/docs/blog/what-are-claude-code-agents/index.html
@@ -173,6 +173,7 @@ what an agent actually is, how subagents fit, and what changes when you run seve
<p>That’s it. Every terminal where you start a <code>claude</code> session is an agent: one goal, one context
window, one loop. The magic isn’t the word “agent” — it’s that the loop can use tools and keep going
until the job’s done.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-are-claude-code-agents/note-1.png" alt="Hand-drawn sketch from “What Are Claude Code Agents? And How to Use Many at Once”" loading="lazy" decoding="async" /></figure>
<h2 id="agents-vs-subagents" tabindex="-1">Agents vs. subagents <a class="anchor" href="#agents-vs-subagents" aria-hidden="true">#</a></h2>
<p>These two get conflated constantly, so let’s separate them:</p>
<h3 id="agent" tabindex="-1">Agent <a class="anchor" href="#agent" aria-hidden="true">#</a></h3>
@@ -198,6 +199,7 @@ terminals, and that works… until it doesn’t:</p>
<p>That’s the wall every multi-agent setup hits. The fix isn’t more agents — it’s coordination. We wrote
the practical playbook in <a href="/blog/how-to-run-multiple-claude-code-agents/">how to run multiple Claude Code
agents</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-are-claude-code-agents/note-2.png" alt="Hand-drawn sketch from “What Are Claude Code Agents? And How to Use Many at Once”" loading="lazy" decoding="async" /></figure>
<h2 id="what-turns-agents-into-a-team" tabindex="-1">What turns agents into a team <a class="anchor" href="#what-turns-agents-into-a-team" aria-hidden="true">#</a></h2>
<p>Three additions turn parallel sessions into something that behaves like a team:</p>
<ul>
diff --git a/docs/blog/what-is-a-multi-agent-harness/index.html b/docs/blog/what-is-a-multi-agent-harness/index.html
index 0a8f9d9f..22ffb1ac 100644
--- a/docs/blog/what-is-a-multi-agent-harness/index.html
+++ b/docs/blog/what-is-a-multi-agent-harness/index.html
@@ -168,6 +168,7 @@ alt-tabbing between windows. A <strong>multi-agent harness</strong> is the softw
shared memory, and work routing — so they behave as a single team.</p>
</blockquote>
<p>That’s the whole idea. Everything else is detail about <em>how</em> the coordination happens.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-is-a-multi-agent-harness/note-1.png" alt="Hand-drawn sketch from “What Is a Multi-Agent Harness? (Plain-English Guide)”" loading="lazy" decoding="async" /></figure>
<h2 id="what-it-adds-on-top-of-a-single-agent" tabindex="-1">What it adds on top of a single agent <a class="anchor" href="#what-it-adds-on-top-of-a-single-agent" aria-hidden="true">#</a></h2>
<p>A single agent is a loop: read context, take an action, repeat. A harness wraps <strong>many</strong> of those
loops and adds the parts a lone agent doesn’t have:</p>
@@ -180,6 +181,7 @@ everything.</li>
that’s the <a href="https://munderdiffl.in/#how">GOD orchestrator</a>, an agent you talk to in plain language.</li>
<li><strong>Visibility.</strong> A way to <em>see</em> what the team is doing, so it’s not a black box.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-is-a-multi-agent-harness/note-2.png" alt="Hand-drawn sketch from “What Is a Multi-Agent Harness? (Plain-English Guide)”" loading="lazy" decoding="async" /></figure>
<h2 id="harness-vs-framework-vs-subagents" tabindex="-1">Harness vs. framework vs. subagents <a class="anchor" href="#harness-vs-framework-vs-subagents" aria-hidden="true">#</a></h2>
<p>These three get conflated. The difference is what you bring to the table:</p>
<h3 id="framework" tabindex="-1">Framework <a class="anchor" href="#framework" aria-hidden="true">#</a></h3>
diff --git a/docs/blog/what-is-aeo-for-dev-tools/index.html b/docs/blog/what-is-aeo-for-dev-tools/index.html
index b1e48f11..aaa76037 100644
--- a/docs/blog/what-is-aeo-for-dev-tools/index.html
+++ b/docs/blog/what-is-aeo-for-dev-tools/index.html
@@ -214,6 +214,7 @@ well-structured pages) but diverge on intent:</p>
<p>The good news: you don’t choose between them. AEO is mostly SEO done with a tighter discipline —
clearer answers, stronger structure, honest facts. A page that an LLM can confidently quote is also a
page Google’s AI Overviews and traditional results reward.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-is-aeo-for-dev-tools/note-1.png" alt="Hand-drawn sketch from “AEO for Dev Tools: Getting Cited by ChatGPT and Claude”" loading="lazy" decoding="async" /></figure>
<h2 id="why-dev-tools-should-care-more-than-most" tabindex="-1">Why dev tools should care more than most <a class="anchor" href="#why-dev-tools-should-care-more-than-most" aria-hidden="true">#</a></h2>
<p>Developer tools sit at the perfect intersection for AEO:</p>
<ul>
@@ -316,6 +317,7 @@ Difflin” to one entity instead of fragments.</li>
README, and topics all feed the same entity. And keep content fresh — but <strong>honestly</strong>. Real
<code>lastmod</code> dates and genuine updates help; faking freshness by bumping dates on unchanged pages is the
kind of manipulation that gets discounted. Update when you actually have something new.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-is-aeo-for-dev-tools/note-2.png" alt="Hand-drawn sketch from “AEO for Dev Tools: Getting Cited by ChatGPT and Claude”" loading="lazy" decoding="async" /></figure>
<h2 id="how-to-measure-aeo-when-theres-no-rank-tracker" tabindex="-1">How to measure AEO (when there’s no rank tracker) <a class="anchor" href="#how-to-measure-aeo-when-theres-no-rank-tracker" aria-hidden="true">#</a></h2>
<p>AEO has no clean “position 3” metric, so measure it directly: <strong>ask the engines.</strong> On a monthly
cadence, ask ChatGPT, Claude, and Perplexity the exact questions your users would ask — <em>“how do I run
diff --git a/docs/blog/what-is-an-agent-development-environment/index.html b/docs/blog/what-is-an-agent-development-environment/index.html
index f6ac5b22..17d802fc 100644
--- a/docs/blog/what-is-an-agent-development-environment/index.html
+++ b/docs/blog/what-is-an-agent-development-environment/index.html
@@ -166,12 +166,14 @@
<p>The original coinage belongs to <a href="https://www.letta.com/blog/introducing-the-agent-development-environment">Letta</a>, which uses <em>Agent Development Environment</em> for a visual platform to <strong>build and debug agents themselves</strong>: inspect an agent’s context window, edit its memory blocks, watch its reasoning, wire its tools. In that sense, an ADE is to agents what an IDE is to code — the artifact under development <em>is the agent</em>.</p>
<p>Then the coding-tools world borrowed the acronym for something adjacent but distinct. <a href="https://github.com/stablyai/orca">Orca</a> calls itself “the ADE for working with a fleet of parallel agents,” and <a href="https://www.augmentcode.com/guides/what-is-an-agentic-development-environment">Augment Code’s guides</a> describe an <em>agentic development environment</em> as an agent-first workspace where developers delegate whole goals instead of steering an editor. In this sense the artifact under development is still <strong>your software</strong> — the ADE is where a fleet of coding agents builds it.</p>
<p>Most people saying “ADE” in a dev-tools context mean the second sense. That’s the sense this post maps.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-is-an-agent-development-environment/note-1.png" alt="Hand-drawn sketch from “What Is an Agent Development Environment (ADE)?”" loading="lazy" decoding="async" /></figure>
<h2 id="the-2026-landscape-four-layers-of-delegation" tabindex="-1">The 2026 landscape: four layers of delegation <a class="anchor" href="#the-2026-landscape-four-layers-of-delegation" aria-hidden="true">#</a></h2>
<p>The clean way to sort the tools is not by feature list but by <strong>how much you hand over</strong>.</p>
<p><strong>1. AI IDEs — you steer every step.</strong> <a href="https://cursor.com/">Cursor</a> is the archetype: an editor-first workspace where agents live inside your editing session. Its Agent mode reads the codebase, edits files, runs commands, and iterates; Composer produces reviewable multi-file diffs; background and cloud agents run tasks off to the side. It’s excellent at what it optimizes for — a developer who stays in the loop, file by file, with agents as force multipliers. The center of gravity is still <em>you, in an editor</em>.</p>
<p><strong>2. Agent CLIs — you delegate one task.</strong> <a href="https://claude.com/claude-code">Claude Code</a> and <a href="https://github.com/openai/codex">OpenAI Codex CLI</a> are single-agent terminal programs: give one a goal and it reads files, runs builds and tests, uses git, and verifies its own work by executing it. This is the layer with real terminal-level power — we wrote about <a href="/blog/why-cli-agents-are-powerful/">why CLI agents are so capable</a> — but each session is one agent, one terminal, one task.</p>
<p><strong>3. Agent IDEs / ADEs — you drive N agents in parallel.</strong> Once you’re running four CLI sessions at once, tab-juggling breaks down, and this is the gap ADEs fill. Orca runs your existing CLI agents — Claude Code, Codex, and others, on your own subscriptions — in parallel, each task in an <strong>isolated git worktree</strong> with its own terminal and context, plus review tooling to merge the results. JetBrains is in the same lane with Air, a standalone multi-agent workspace. The defining trait: <em>you</em> are still the dispatcher. You assign every task, watch every lane, and merge every result.</p>
<p><strong>4. Agent harnesses / offices — the agents coordinate each other.</strong> This is where <strong>Munder Difflin</strong> sits, and it’s a different bet. Like an ADE, it runs real CLI agents (seven engines as of v0.3.3, including GitHub Copilot CLI) in isolated worktrees and real pseudo-terminals. Unlike an ADE, you don’t dispatch to each agent yourself: a GOD orchestrator — Michael — routes work, agents message each other through mailboxes, share <a href="/blog/semantic-memory-for-ai-agents/">long-term semantic memory</a>, and get woken by triggers — typing, Slack, webhooks, schedules, even voice. Guardrails (approval gates, per-agent budgets, a circuit breaker, OTel observability) make it safe to leave running. The mental model isn’t “my editor got agents” or “my agents got lanes” — it’s <em>an office you supervise</em>. We’ve written a fuller definition in <a href="/blog/what-is-a-multi-agent-harness/">what is a multi-agent harness</a>.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-is-an-agent-development-environment/note-2.png" alt="Hand-drawn sketch from “What Is an Agent Development Environment (ADE)?”" loading="lazy" decoding="async" /></figure>
<h2 id="where-the-categories-blur" tabindex="-1">Where the categories blur <a class="anchor" href="#where-the-categories-blur" aria-hidden="true">#</a></h2>
<p>Nobody stays in their lane, and the direction of travel is telling.</p>
<p>Cursor grew a CLI and cloud agents — the editor reaching toward delegation. ADEs like Orca embed browsers and diff tooling — the dispatcher growing verification surfaces. And Munder Difflin’s v0.3.3 added a <strong>built-in Monaco IDE</strong> — the VS Code editor engine, self-hosted, one click over the office floor, with a file tree, tabs, and side-by-side git diffs of every agent change against HEAD. A harness growing an editor, precisely because the bottleneck in agent-heavy work shifts from <em>writing</em> code to <em>reviewing</em> it.</p>
diff --git a/docs/blog/what-is-harness-engineering/index.html b/docs/blog/what-is-harness-engineering/index.html
index 4cf77c44..17a900b2 100644
--- a/docs/blog/what-is-harness-engineering/index.html
+++ b/docs/blog/what-is-harness-engineering/index.html
@@ -167,6 +167,7 @@
<p><strong>Harness engineering</strong> was popularized by Mitchell Hashimoto (co-founder of HashiCorp) in a February 2026 post on <a href="https://mitchellh.com/writing/my-ai-adoption-journey">his AI adoption journey</a>. His formulation is disarmingly simple: <em>any time you find an agent makes a mistake, you take the time to engineer a solution such that the agent never makes that mistake again.</em> Not a better prompt. Not a smarter model. A structural fix in the environment the agent operates in, so the failure class is closed permanently.</p>
<p>The broader discourse picked the term up fast, and a rough consensus formed: harness engineering is the <strong>third phase of agent-engineering maturity</strong> — after prompt engineering (shape one call) and context engineering (shape what the model sees), you shape <em>the entire system the model operates inside</em>. Industry write-ups like <a href="https://www.faros.ai/blog/harness-engineering">Faros AI’s guide</a> converge on the same anatomy — tool orchestration, verification loops, context and memory, guardrails, observability — and point at the evidence that motivates it: teams have jumped whole leaderboards on agent benchmarks (Faros cites LangChain climbing Terminal Bench 2.0 from 30th to 5th) <strong>without changing the model at all</strong>. Same model, different harness, different outcome.</p>
<p>That’s the whole thesis in one line: <strong>the model is a commodity input; the harness is the differentiated system.</strong> Frontier models leapfrog each other every quarter, and every serious agent product supports several of them interchangeably. What doesn’t come off a shelf is the machinery that makes any of them dependable.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-is-harness-engineering/note-1.png" alt="Hand-drawn sketch from “What Is Harness Engineering?”" loading="lazy" decoding="async" /></figure>
<h2 id="what-a-harness-actually-contains" tabindex="-1">What a harness actually contains <a class="anchor" href="#what-a-harness-actually-contains" aria-hidden="true">#</a></h2>
<p>Strip the buzzwords and a production harness is a specific list of unglamorous subsystems:</p>
<ul>
@@ -180,6 +181,7 @@
<li><strong>Session resume.</strong> A restart — of the app, the machine, or one agent — must reattach state, not destroy it.</li>
</ul>
<p>Notice what’s absent: anything about making the model smarter. Harness engineering takes model capability as given and engineers everything else. (For how this differs from a single-agent wrapper, see <a href="/blog/what-is-a-multi-agent-harness/">what a multi-agent harness is</a>.)</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-is-harness-engineering/note-2.png" alt="Hand-drawn sketch from “What Is Harness Engineering?”" loading="lazy" decoding="async" /></figure>
<h2 id="four-case-studies-from-inside-munder-difflin" tabindex="-1">Four case studies from inside Munder Difflin <a class="anchor" href="#four-case-studies-from-inside-munder-difflin" aria-hidden="true">#</a></h2>
<p>Munder Difflin is this discipline shipped as a product, so its internals make good worked examples.</p>
<p><strong>The hook shim — lifecycle truth instead of stdout guessing.</strong> Every provider speaks lifecycle differently: Claude Code has native hooks, Antigravity needed a purpose-built <code>agy-hook</code> bridge, Codex gets the protocol injected as its initial prompt. The harness normalizes all of them into one hook server (<code>hooks.ts</code>) that receives structured POST payloads — so “the agent finished its turn” is a <em>signal</em>, not an inference from a quiet terminal. And where a provider has no bridge at all, the harness engineers around the gap honestly: GitHub Copilot CLI’s print mode can’t drain an inbox, so routed mail <strong>bounces to the GOD orchestrator</strong> instead of silently dropping. That is Hashimoto’s rule applied — the “silently lost message” failure class is closed structurally.</p>
diff --git a/docs/blog/what-reddit-told-us-about-munder-difflin/index.html b/docs/blog/what-reddit-told-us-about-munder-difflin/index.html
new file mode 100644
index 00000000..6484a94f
--- /dev/null
+++ b/docs/blog/what-reddit-told-us-about-munder-difflin/index.html
@@ -0,0 +1,382 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="UTF-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1.0" />
+<title>What 516 Reddit Comments Told Us About Munder Difflin — Munder Difflin Blog</title>
+<meta name="description" content="We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it." />
+<link rel="canonical" href="https://munderdiffl.in/blog/what-reddit-told-us-about-munder-difflin/" />
+
+<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="What 516 Reddit Comments Told Us About Munder Difflin — Munder Difflin Blog" />
+<meta property="og:description" content="We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it." />
+<meta property="og:url" content="https://munderdiffl.in/blog/what-reddit-told-us-about-munder-difflin/" />
+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />
+<meta property="og:locale" content="en_US" />
+<meta property="article:published_time" content="2026-08-19T00:00:00.000Z" />
+<meta property="article:author" content="Chaitanya Giri" />
+<meta property="article:tag" content="Story" />
+<meta property="article:tag" content="Launch" />
+<meta property="article:tag" content="Reddit" />
+<meta property="article:tag" content="Community" />
+<meta property="article:tag" content="Open Source" />
+
+
+<!-- Twitter -->
+<meta name="twitter:card" content="summary_large_image" />
+<meta name="twitter:title" content="What 516 Reddit Comments Told Us About Munder Difflin — Munder Difflin Blog" />
+<meta name="twitter:description" content="We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it." />
+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />
+
+<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": "What 516 Reddit Comments Told Us About Munder Difflin",
+ "description": "We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.",
+ "image": ["https://munderdiffl.in/media/og.png"],
+ "datePublished": "2026-08-19T00:00:00.000Z",
+ "dateModified": "2026-08-19T00: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/what-reddit-told-us-about-munder-difflin/" },
+ "keywords": "munder difflin reddit launch, reddit launch retrospective, launching dev tools on reddit, r/ClaudeCode, ai agent tool feedback",
+ "articleSection": "Story",
+ "inLanguage": "en-US",
+ "url": "https://munderdiffl.in/blog/what-reddit-told-us-about-munder-difflin/"
+}
+</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": "What 516 Reddit Comments Told Us About Munder Difflin", "item": "https://munderdiffl.in/blog/what-reddit-told-us-about-munder-difflin/" }
+ ]
+}
+</script>
+
+<script type="application/ld+json">
+{
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ "mainEntity": [
+ { "@type": "Question", "name": "How did the Munder Difflin Reddit launch go?", "acceptedAnswer": { "@type": "Answer", "text": "Ten posts across ten subreddits earned a combined score of 2,233 and 516 comments. r/ClaudeCode alone contributed 1,017 upvotes — almost half of everything — while r/OpenAI and r/selfhosted barely registered. The audience that already runs Claude Code all day understood the product instantly; everyone else needed more explaining than a screenshot can do." } },
+ { "@type": "Question", "name": "What did Reddit criticize about Munder Difflin?", "acceptedAnswer": { "@type": "Answer", "text": "Three things, honestly: skepticism that a visual layer adds real utility over raw terminals, worry about token costs when running many agents, and fatigue with the orchestration-tool category in general. All three are fair, and two of them shaped what we shipped next — clearer budget controls and less theater, more control." } },
+ { "@type": "Question", "name": "What did people like most?", "acceptedAnswer": { "@type": "Answer", "text": "Visibility. The most-upvoted comments were about glancing at the floor and knowing who's stuck versus who's working, watching envelopes move between agents' inboxes and outboxes, and the fact that the whole thing runs locally on files you can read yourself." } }
+
+ ]
+}
+</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,
+ 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-story">
+ <header class="post-head wrap">
+ <nav class="crumbs" aria-label="Breadcrumb">
+ <a href="/blog/">Blog</a>
+ <span>/</span>
+ <a href="/blog/topics/story/">Story</a>
+ </nav>
+ <h1>What 516 Reddit Comments Told Us About Munder Difflin</h1>
+ <p class="dek">We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</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-08-19">Aug 19, 2026</time>
+ <span class="dot" aria-hidden="true">·</span>
+ <span>3 min read</span>
+ <span class="tag kind">Story</span>
+ </div>
+ </header>
+
+ <div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/hero.png" alt="Illustration: What 516 Reddit Comments Told Us About Munder Difflin" 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>Our Reddit launch: <strong>ten posts,
+2,233 combined upvotes, 516 comments</strong>. Nearly half the engagement came from one
+subreddit — r/ClaudeCode — and two communities ignored us entirely. We read all 516 comments,
+sorted them into what resonated, what got roasted, and what got fixed. This is that sorting,
+published.</p></div>
+<p>Launch week, we posted Munder Difflin to ten subreddits over a few days. Not the same post ten
+times — each one angled for its community — and then the comments started, and did not stop for
+a week.</p>
+<h2 id="where-it-landed-and-where-it-didnt" tabindex="-1">Where it landed, and where it didn’t <a class="anchor" href="#where-it-landed-and-where-it-didnt" aria-hidden="true">#</a></h2>
+<p>The distribution was brutal and informative. <strong>r/ClaudeCode delivered 1,017 upvotes — 46% of
+all engagement from one community.</strong> People who already run
+<a href="/blog/how-to-run-multiple-claude-code-agents/">multiple Claude Code sessions</a> didn’t need the
+pitch; they recognized the problem from the screenshot alone.</p>
+<p>The flops taught us just as much. r/OpenAI and r/selfhosted barely moved. In hindsight both make
+sense: r/OpenAI’s crowd doesn’t live in Claude Code, and r/selfhosted heard “Electron app that
+drives commercial AI subscriptions” and reasonably shrugged. A launch angle that works is mostly
+audience selection, not copywriting.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/note-1.png" alt="Hand-drawn sketch from “What 516 Reddit Comments Told Us About Munder Difflin”" loading="lazy" decoding="async" /><figcaption>Ten subreddits, one clear winner: the people already drowning in Claude Code terminals didn't need the pitch.</figcaption></figure>
+<h2 id="what-resonated" tabindex="-1">What resonated <a class="anchor" href="#what-resonated" aria-hidden="true">#</a></h2>
+<p>Reading 516 comments in bulk, three themes kept earning upvotes:</p>
+<p><strong>Visibility.</strong> The single most-upvoted non-post comment in the whole corpus was someone
+describing exactly the moment we built the office floor for: glancing at the screen and knowing
+the state of five working sessions without tailing five terminals. When people praised the
+product, they praised <em>knowing what’s happening</em> — the floor, the envelopes physically traveling
+between desks, <a href="/blog/building-a-terminal-ui-xterm-node-pty/">the terminals you can pop open</a> on
+any agent at any moment.</p>
+<p><strong>The mechanics being inspectable.</strong> The <a href="/blog/atomic-file-mailboxes-for-agents/">inbox/outbox file
+protocol</a> came up again and again, positively. Reddit’s
+technical crowd trusts what it can <code>cat</code>. The fact that every message between agents is a JSON
+file on your own disk did more persuading than any diagram.</p>
+<p><strong>Local, on your own machine.</strong> Everything runs where your code already lives, against the
+Claude plan you already have — no service in the middle. The what’s-the-catch crowd could
+answer their own question by reading the source, and several did exactly that before saying
+anything nice.</p>
+<p>The best moment of the week wasn’t a compliment, though. Another builder took a feature from his
+own rival project, <strong>forked Munder Difflin, and sent us a pull request the same day</strong>. That’s
+the open-source version of a standing ovation.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/what-reddit-told-us-about-munder-difflin/note-2.png" alt="Hand-drawn sketch from “What 516 Reddit Comments Told Us About Munder Difflin”" loading="lazy" decoding="async" /><figcaption>The best compliment of launch week arrived as a pull request from a rival project, the same day.</figcaption></figure>
+<h2 id="what-got-roasted" tabindex="-1">What got roasted <a class="anchor" href="#what-got-roasted" aria-hidden="true">#</a></h2>
+<p>Publishing only the praise would be exactly the launch-retro genre we hate, so:</p>
+<p><strong>“Is this actually useful, or is it theater?”</strong> The most common objection — a dozen distinct
+commenters. Watching pixel-art agents walk envelopes around is charming; charm is not utility.
+Our answer then and now: the simulation is deterministic and costs zero tokens, and the utility
+lives underneath it — routing, memory, lifecycle. But the burden of proof is ours, and it’s why
+our sharpest users’ asks are about <em>control</em> surfaces, not prettier sprites.</p>
+<p><strong>Token cost.</strong> Eleven commenters worried that a floor full of agents burns money. Fair — which
+is why budgets and caps exist, and why we wrote
+<a href="/blog/the-multi-agent-cost-playbook/">the multi-agent cost playbook</a> and keep
+<a href="/blog/do-more-with-less-model-routing/">model routing</a> cheap by default: one strong
+orchestrator, inexpensive workers.</p>
+<p><strong>Category fatigue.</strong> “Another Claude Code orchestrator” is a real sentiment in 2026, and some
+power users said plainly they want less theater and more control. We took that phrase seriously
+enough that it’s become an internal design test.</p>
+<p><strong>And the bugs.</strong> Windows users showed up, tried it, and hit real walls — which fed directly
+into <a href="/blog/launching-munder-difflin-v0-4-4/">v0.4.4</a>, the release where Windows agents can
+finally talk to each other. Several onboarding dead-ends reported in those threads are fixed in
+the same release. If you bounced off Munder Difflin in launch week on Windows: it’s worth a
+second look now.</p>
+<h2 id="what-were-taking-away" tabindex="-1">What we’re taking away <a class="anchor" href="#what-were-taking-away" aria-hidden="true">#</a></h2>
+<p>Reddit gave us the stadium; <a href="/blog/number-five-on-product-hunt/">Product Hunt</a> gave us the
+panel interview. The stadium’s verdict, compressed: <strong>charm gets people in the door; visibility
+and control keep them.</strong> The people who stayed cited watching state and steering it. The people
+who left cited theater and cost. Every roadmap argument we’ve had since launch week ends by
+re-reading one of those 516 comments.</p>
+<p>We didn’t skim them. We <a href="/blog/agents-ran-our-launch-week-analytics/">pointed agents at the threads</a>
+and made them account for every single comment — but that’s its own story.</p>
+
+
+
+ <section class="faq" aria-label="Frequently asked questions">
+ <h2 id="faq">FAQ</h2>
+
+ <div class="qa">
+ <p class="q">How did the Munder Difflin Reddit launch go?</p>
+ <p class="a">Ten posts across ten subreddits earned a combined score of 2,233 and 516 comments. r/ClaudeCode alone contributed 1,017 upvotes — almost half of everything — while r/OpenAI and r/selfhosted barely registered. The audience that already runs Claude Code all day understood the product instantly; everyone else needed more explaining than a screenshot can do.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">What did Reddit criticize about Munder Difflin?</p>
+ <p class="a">Three things, honestly: skepticism that a visual layer adds real utility over raw terminals, worry about token costs when running many agents, and fatigue with the orchestration-tool category in general. All three are fair, and two of them shaped what we shipped next — clearer budget controls and less theater, more control.</p>
+ </div>
+
+ <div class="qa">
+ <p class="q">What did people like most?</p>
+ <p class="a">Visibility. The most-upvoted comments were about glancing at the floor and knowing who&#39;s stuck versus who&#39;s working, watching envelopes move between agents&#39; inboxes and outboxes, and the fact that the whole thing runs locally on files you can read yourself.</p>
+ </div>
+
+ </section>
+
+
+
+ <hr />
+ <div class="share">
+ <span class="lbl">Tags</span>
+ <a class="tag" href="/blog/tags/story/">Story</a><a class="tag" href="/blog/tags/launch/">Launch</a><a class="tag" href="/blog/tags/reddit/">Reddit</a><a class="tag" href="/blog/tags/community/">Community</a><a class="tag" href="/blog/tags/open-source/">Open Source</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="#where-it-landed-and-where-it-didnt">Where it landed, and where it didn’t</a></li><li class="lvl-2"><a href="#what-resonated">What resonated</a></li><li class="lvl-2"><a href="#what-got-roasted">What got roasted</a></li><li class="lvl-2"><a href="#what-were-taking-away">What we’re taking away</a></li>
+ </ol>
+ </aside>
+
+ </div>
+
+ <footer class="post-foot wrap"><div class="prevnext">
+ <a class="pn prev" href="/blog/whats-up-with-munder-difflin/"><span class="k">← Older</span><span class="t">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</span></a>
+ <a class="pn next" href="/blog/we-opened-a-discord/"><span class="k">Newer →</span><span class="t">We Opened a Discord (Merge a PR, Become Employee of the Month)</span></a>
+ </div>
+ <section class="related">
+ <h2>Related in Story</h2>
+ <div class="post-grid">
+ <article class="card t-story">
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/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/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/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/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
+ </div>
+ </div>
+</article>
+<article class="card t-story">
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/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/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
+ <div class="foot">
+ <span class="tag kind">Story</span>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
+ </div>
+ </div>
+</article>
+
+ </div>
+ </section>
+
+ </footer>
+</article>
+
+</main>
+<footer>
+ <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');
+ if (!id) return;
+ var frame = document.createElement('iframe');
+ frame.src = 'https://www.youtube-nocookie.com/embed/' + 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>
diff --git a/docs/blog/whats-new-in-agentic-ai-june-2026/index.html b/docs/blog/whats-new-in-agentic-ai-june-2026/index.html
index bc276c7d..be5dfc7e 100644
--- a/docs/blog/whats-new-in-agentic-ai-june-2026/index.html
+++ b/docs/blog/whats-new-in-agentic-ai-june-2026/index.html
@@ -229,6 +229,7 @@ frontier lab is now orchestrating subagents inside its own coding tool, the case
<a href="/#what">multi-agent harness</a> you control — where you can watch and steer that fan-out — gets stronger,
not weaker. (For the broader tool landscape, see our
<a href="/blog/best-claude-code-multi-agent-tools/">roundup of multi-agent Claude Code tools</a>.)</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/whats-new-in-agentic-ai-june-2026/note-1.png" alt="Hand-drawn sketch from “What's New in Agentic AI: A June 2026 Field Guide”" loading="lazy" decoding="async" /></figure>
<h2 id="agent-coordination-is-becoming-a-protocol-layer" tabindex="-1">Agent coordination is becoming a protocol layer <a class="anchor" href="#agent-coordination-is-becoming-a-protocol-layer" aria-hidden="true">#</a></h2>
<p>A year ago, every framework invented its own way for agents to reach tools and each other. That’s
consolidating fast. In December 2025, Anthropic donated the <strong>Model Context Protocol (MCP)</strong> to the new
@@ -257,6 +258,7 @@ signal yet that <strong>agentic coding is a metered resource</strong>, priced li
<em>visibility</em> into what your agents spend, and the option to run work where you control the cost. That’s a
core argument for <a href="/blog/why-local-first-matters-for-ai-agents/">why local-first matters for AI agents</a>: a
hive that runs on your machine and logs its own activity puts the meter where you can see it.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/whats-new-in-agentic-ai-june-2026/note-2.png" alt="Hand-drawn sketch from “What's New in Agentic AI: A June 2026 Field Guide”" loading="lazy" decoding="async" /></figure>
<h2 id="governance-and-identity-grew-up" tabindex="-1">Governance and identity grew up <a class="anchor" href="#governance-and-identity-grew-up" aria-hidden="true">#</a></h2>
<p>The enterprise side of agents got its control plane.
<a href="https://www.microsoft.com/en-us/security/blog/2026/05/01/microsoft-agent-365-now-generally-available-expands-capabilities-and-integrations/">Microsoft Agent 365 reached general availability on May 1, 2026</a>
diff --git a/docs/blog/whats-up-with-munder-difflin/index.html b/docs/blog/whats-up-with-munder-difflin/index.html
index d7cec5ee..6f9ad383 100644
--- a/docs/blog/whats-up-with-munder-difflin/index.html
+++ b/docs/blog/whats-up-with-munder-difflin/index.html
@@ -198,6 +198,7 @@ agent that’s actively working in it.</li>
prints in its terminal and it opens rendered. In the IDE, markdown files get a
code | split | preview switch that re-renders live. There’s no raw-HTML pipeline anywhere in
it, which is the only way reading agent-generated files is safe by construction.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/whats-up-with-munder-difflin/note-1.png" alt="Hand-drawn sketch from “What's Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own”" loading="lazy" decoding="async" /></figure>
<h2 id="nine-engines" tabindex="-1">Nine engines <a class="anchor" href="#nine-engines" aria-hidden="true">#</a></h2>
<p><strong>xAI Grok</strong> and <strong>Kimi Code</strong> joined, bringing the roster to nine: Claude Code, OpenAI
Codex, Antigravity, GitHub Copilot CLI, Grok, Kimi, OpenCode, Crush, and pi.dev. Grok came in
@@ -245,6 +246,7 @@ context past about sixteen. The floor is created at startup, so it was always fi
and Pixi reported nothing at all, so it just went blank until you restarted. It notices and
rebuilds itself now.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/whats-up-with-munder-difflin/note-2.png" alt="Hand-drawn sketch from “What's Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own”" loading="lazy" decoding="async" /></figure>
<h2 id="and-then-auto-update-had-never-once-worked" tabindex="-1">And then: auto-update had never once worked <a class="anchor" href="#and-then-auto-update-had-never-once-worked" aria-hidden="true">#</a></h2>
<p>Here’s the confession.</p>
<p>We shipped auto-update in v0.3.4 and announced it. It has never run. Not once, in any
@@ -345,56 +347,56 @@ it runs on your machine.</p>
<footer class="post-foot wrap"><div class="prevnext">
<a class="pn prev" href="/blog/why-our-auto-update-never-ran/"><span class="k">← Older</span><span class="t">Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace</span></a>
- <span></span>
+ <a class="pn next" href="/blog/what-reddit-told-us-about-munder-difflin/"><span class="k">Newer →</span><span class="t">What 516 Reddit Comments Told Us About Munder Difflin</span></a>
</div>
<section class="related">
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-2/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-2/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-27">Jun 27, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-2/">Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator</a></h3>
- <p class="dek">Munder Difflin v0.3.2 adds Realtime Michael — a low-latency voice channel to the GOD orchestrator. Talk to Michael and he listens, answers, and acts: reading the hive and, behind spoken echo-back confirmation, dispatching, spawning, and steering the floor in real time.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-2/" aria-label="Read: Launching Munder Difflin v0.3.2: Talk to Michael, a Realtime Voice Orchestrator">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/when-do-agents-need-an-agent-protocol/index.html b/docs/blog/when-do-agents-need-an-agent-protocol/index.html
index b61b739c..9ad48a73 100644
--- a/docs/blog/when-do-agents-need-an-agent-protocol/index.html
+++ b/docs/blog/when-do-agents-need-an-agent-protocol/index.html
@@ -197,6 +197,7 @@ audit. Adopting A2A to let two agents in the same process “discover” each ot
a problem you’ve already solved. This is the same reason <a href="/blog/coordinating-ai-coding-agents/">coordinating co-located
agents</a> rarely starts with a protocol — it starts with a shared
directory.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/when-do-agents-need-an-agent-protocol/note-1.png" alt="Hand-drawn sketch from “When Do AI Agents Actually Need an Agent Protocol?”" loading="lazy" decoding="async" /></figure>
<h2 id="when-you-do-need-one-crossing-a-boundary" tabindex="-1">When you do need one: crossing a boundary <a class="anchor" href="#when-you-do-need-one-crossing-a-boundary" aria-hidden="true">#</a></h2>
<p>The calculus flips the moment your agents stop being a closed, owned set. A protocol earns its keep when
you cross a <strong>boundary</strong>:</p>
@@ -230,6 +231,7 @@ protocol is what spares you a brittle, bespoke integration for every partner you
<p>Most teams’ first multi-agent system lives entirely on the “same side.” Reach for the protocol when, and
only when, you actually cross over — and notice the two boundaries can differ: you might want MCP for
tools long before you ever need A2A for agents.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/when-do-agents-need-an-agent-protocol/note-2.png" alt="Hand-drawn sketch from “When Do AI Agents Actually Need an Agent Protocol?”" loading="lazy" decoding="async" /></figure>
<h2 id="build-so-you-can-speak-them-later" tabindex="-1">Build so you can speak them later <a class="anchor" href="#build-so-you-can-speak-them-later" aria-hidden="true">#</a></h2>
<p>None of this is an argument against the protocols — it’s an argument against adopting them prematurely.
The healthy position is to keep your coordination simple while it’s internal, and design so you <em>can</em>
diff --git a/docs/blog/why-cli-agents-are-powerful/index.html b/docs/blog/why-cli-agents-are-powerful/index.html
index f5982d0e..41659a1b 100644
--- a/docs/blog/why-cli-agents-are-powerful/index.html
+++ b/docs/blog/why-cli-agents-are-powerful/index.html
@@ -200,6 +200,7 @@ piece on this discipline: <a href="/blog/how-ai-agents-verify-their-own-work/">h
<p>So the headline isn’t “CLI agents can type commands.” It’s that <strong>a terminal turns a generator into a
worker</strong> — something that can act, observe the consequence, and correct, in a tight loop, without a human
shuttling output back and forth across the glass.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/why-cli-agents-are-powerful/note-1.png" alt="Hand-drawn sketch from “Why CLI Agents Are So Powerful — and How Munder Difflin Spends Fewer Tokens Doing the Same Work”" loading="lazy" decoding="async" /></figure>
<h2 id="local-is-what-makes-the-access-real" tabindex="-1">Local is what makes the access <em>real</em> <a class="anchor" href="#local-is-what-makes-the-access-real" aria-hidden="true">#</a></h2>
<p>Here’s the catch people miss. Terminal-level access is only as powerful as the machine the terminal is
attached to. And there’s a real difference between an agent running in some vendor’s ephemeral container
@@ -258,6 +259,7 @@ caps the total, and routing keeps frontier prices off routine work. (For the ful
<a href="/blog/the-multi-agent-cost-playbook/">the multi-agent cost playbook</a>.) The point isn’t a magic discount
— it’s that a hive is only worth running if it’s <em>engineered</em> to be affordable, and these are the
mechanics that make it so.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/why-cli-agents-are-powerful/note-2.png" alt="Hand-drawn sketch from “Why CLI Agents Are So Powerful — and How Munder Difflin Spends Fewer Tokens Doing the Same Work”" loading="lazy" decoding="async" /></figure>
<h2 id="the-bottom-line" tabindex="-1">The bottom line <a class="anchor" href="#the-bottom-line" aria-hidden="true">#</a></h2>
<p>CLI agents are powerful because a terminal turns a model from a thing that <em>talks about</em> work into a
thing that <em>does</em> work — reading files, running builds, using git, calling your tools, and verifying
diff --git a/docs/blog/why-local-first-matters-for-ai-agents/index.html b/docs/blog/why-local-first-matters-for-ai-agents/index.html
index 2d85118a..2d453cec 100644
--- a/docs/blog/why-local-first-matters-for-ai-agents/index.html
+++ b/docs/blog/why-local-first-matters-for-ai-agents/index.html
@@ -175,6 +175,7 @@ Anthropic the same way your editor’s does. Local-first is about <em>where the
</ul>
<p>In a <a href="/#why">local-first setup</a>, all of that stays on your machine. In a cloud platform, much of it
lives on someone else’s servers. Same agents, very different trust model.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/why-local-first-matters-for-ai-agents/note-1.png" alt="Hand-drawn sketch from “Why Local-First Matters for Your AI Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="three-reasons-it-matters" tabindex="-1">Three reasons it matters <a class="anchor" href="#three-reasons-it-matters" aria-hidden="true">#</a></h2>
<h3 id="1-control-its-your-machine-your-rules" tabindex="-1">1. Control — it’s your machine, your rules <a class="anchor" href="#1-control-its-your-machine-your-rules" aria-hidden="true">#</a></h3>
<p>Local agents work against your real working tree, your git, your environment, your tools. Nothing is
@@ -197,6 +198,7 @@ team, that convenience is real.</p>
<p>But for an individual developer or a small team running agents against their own code, the
convenience rarely outweighs handing over control, privacy, and predictable cost. You can have the
coordination <em>and</em> keep it local.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/why-local-first-matters-for-ai-agents/note-2.png" alt="Hand-drawn sketch from “Why Local-First Matters for Your AI Agents”" loading="lazy" decoding="async" /></figure>
<h2 id="local-first-doesnt-mean-uncoordinated" tabindex="-1">Local-first doesn’t mean uncoordinated <a class="anchor" href="#local-first-doesnt-mean-uncoordinated" aria-hidden="true">#</a></h2>
<p>The old assumption was that local meant primitive — a few terminals, no shared brain. That’s no longer
true. A <a href="/#what">local multi-agent harness</a> gives you the full coordination layer — shared memory,
@@ -258,50 +260,50 @@ machine, on macOS, Windows, and Linux. <a href="/#install">Download Munder Diffl
<h2>Related in Use Cases</h2>
<div class="post-grid">
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/deploy-a-blog-writer-agent/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deploy-a-blog-writer-agent/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/agents-ran-our-launch-week-analytics/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/agents-ran-our-launch-week-analytics/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-10">Jun 10, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>6 min</span>
+ <span>3 min</span>
</div>
- <h3><a href="/blog/deploy-a-blog-writer-agent/">Deploy a Blog-Writer Agent: The One That Wrote This Post</a></h3>
- <p class="dek">How Munder Difflin&#39;s blog is written by an automated writer agent in the hive — drafts in a worktree, single-committer integration, Eleventy build, human-gated deploy. Build your own.</p>
+ <h3><a href="/blog/agents-ran-our-launch-week-analytics/">Our Agents Ran Our Launch-Week Analytics</a></h3>
+ <p class="dek">Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/deploy-a-blog-writer-agent/" aria-label="Read: Deploy a Blog-Writer Agent: The One That Wrote This Post">Read →</a>
+ <a class="more" href="/blog/agents-ran-our-launch-week-analytics/" aria-label="Read: Our Agents Ran Our Launch-Week Analytics">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/overnight-ai-coding-realistic-expectations/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/overnight-ai-coding-realistic-expectations/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/an-agent-redesigned-this-blog/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/an-agent-redesigned-this-blog/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-04">Jun 4, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
+ <span>3 min</span>
</div>
- <h3><a href="/blog/overnight-ai-coding-realistic-expectations/">Overnight AI Coding: What&#39;s Realistic (and What&#39;s Not)</a></h3>
- <p class="dek">An honest look at letting AI coding agents run overnight — what works today, where guardrails matter, and what still needs a human in the morning.</p>
+ <h3><a href="/blog/an-agent-redesigned-this-blog/">An Agent Redesigned the Blog You&#39;re Reading</a></h3>
+ <p class="dek">Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/overnight-ai-coding-realistic-expectations/" aria-label="Read: Overnight AI Coding: What&#39;s Realistic (and What&#39;s Not)">Read →</a>
+ <a class="more" href="/blog/an-agent-redesigned-this-blog/" aria-label="Read: An Agent Redesigned the Blog You&#39;re Reading">Read →</a>
</div>
</div>
</article>
<article class="card t-use-cases">
- <a class="thumb t-use-cases" href="/blog/from-one-terminal-to-a-team/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/from-one-terminal-to-a-team/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-use-cases" href="/blog/run-a-release-train-with-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/run-a-release-train-with-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-06-02">Jun 2, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>3 min</span>
</div>
- <h3><a href="/blog/from-one-terminal-to-a-team/">From One Terminal to a Team: Scaling Your Claude Code Workflow</a></h3>
- <p class="dek">The workflow shift from a single Claude Code session to a coordinated team of agents — what changes, where it breaks, and the concrete before-and-after.</p>
+ <h3><a href="/blog/run-a-release-train-with-agents/">Run a Release Train with Agents</a></h3>
+ <p class="dek">Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</p>
<div class="foot">
<span class="tag kind">Use Cases</span>
- <a class="more" href="/blog/from-one-terminal-to-a-team/" aria-label="Read: From One Terminal to a Team: Scaling Your Claude Code Workflow">Read →</a>
+ <a class="more" href="/blog/run-a-release-train-with-agents/" aria-label="Read: Run a Release Train with Agents">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/why-our-auto-update-never-ran/index.html b/docs/blog/why-our-auto-update-never-ran/index.html
index ff30b42c..2fa79387 100644
--- a/docs/blog/why-our-auto-update-never-ran/index.html
+++ b/docs/blog/why-our-auto-update-never-ran/index.html
@@ -193,6 +193,7 @@ swallowing for three releases:</p>
<pre><code>[updater] electron-updater unavailable; notify-only mode:
TypeError: Cannot set properties of undefined (setting 'autoDownload')
</code></pre>
+<figure class="fig fig-inline"><img src="/blog/assets/media/why-our-auto-update-never-ran/note-1.png" alt="Hand-drawn sketch from “Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace”" loading="lazy" decoding="async" /></figure>
<h2 id="one-line-three-releases" tabindex="-1">One line, three releases <a class="anchor" href="#one-line-three-releases" aria-hidden="true">#</a></h2>
<p>Here is the code that shipped in v0.3.4:</p>
<pre class="language-js"><code class="language-js"><span class="token keyword">const</span> <span class="token punctuation">{</span> autoUpdater <span class="token punctuation">}</span> <span class="token operator">=</span> <span class="token keyword">await</span> <span class="token keyword">import</span><span class="token punctuation">(</span><span class="token string">'electron-updater'</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
@@ -238,6 +239,7 @@ native path again.</li>
plain module with no Electron imports, with unit tests covering the rule that bit us — a
re-check must never wipe out an update you already have staged.</li>
</ul>
+<figure class="fig fig-inline"><img src="/blog/assets/media/why-our-auto-update-never-ran/note-2.png" alt="Hand-drawn sketch from “Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace”" loading="lazy" decoding="async" /></figure>
<h2 id="the-version-number-is-now-a-button" tabindex="-1">The version number is now a button <a class="anchor" href="#the-version-number-is-now-a-button" aria-hidden="true">#</a></h2>
<p>The other half of the report was that nothing in the app told the user what was happening.
There was a toast for “downloaded”, and nothing for anything else — so a multi-minute
@@ -315,6 +317,22 @@ why.</p>
<h2>Related in Internals</h2>
<div class="post-grid">
<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/hire-manifest-untrusted-input/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/hire-manifest-untrusted-input/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
@@ -346,22 +364,6 @@ why.</p>
</div>
</div>
</article>
-<article class="card t-internals">
- <a class="thumb t-internals" href="/blog/architecture-two-planes-one-renderer/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/architecture-two-planes-one-renderer/hero.png" alt="" loading="lazy" decoding="async" /></a>
- <div class="body">
- <div class="meta">
- <time datetime="2026-06-04">Jun 4, 2026</time>
- <span class="dot" aria-hidden="true"></span>
- <span>5 min</span>
- </div>
- <h3><a href="/blog/architecture-two-planes-one-renderer/">Munder Difflin&#39;s Architecture: Two Data Planes, One Renderer</a></h3>
- <p class="dek">A walkthrough of the multi-agent harness architecture: a node-pty terminal plane and a hooks/hive event plane feeding one React + Pixi.js renderer.</p>
- <div class="foot">
- <span class="tag kind">Internals</span>
- <a class="more" href="/blog/architecture-two-planes-one-renderer/" aria-label="Read: Munder Difflin&#39;s Architecture: Two Data Planes, One Renderer">Read →</a>
- </div>
- </div>
-</article>
</div>
</section>
diff --git a/docs/blog/why-we-built-munder-difflin/index.html b/docs/blog/why-we-built-munder-difflin/index.html
index 51842f5e..fbfef71d 100644
--- a/docs/blog/why-we-built-munder-difflin/index.html
+++ b/docs/blog/why-we-built-munder-difflin/index.html
@@ -164,6 +164,7 @@ where mistakes hide.</li>
</ul>
<p>The agents weren’t the bottleneck anymore. <em>I</em> was — the message bus, the conflict resolver, and the
project’s only long-term memory.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/why-we-built-munder-difflin/note-1.png" alt="Hand-drawn sketch from “Why We Built Munder Difflin”" loading="lazy" decoding="async" /></figure>
<h2 id="the-realization" tabindex="-1">The realization <a class="anchor" href="#the-realization" aria-hidden="true">#</a></h2>
<p>The instinct is to reach for a better terminal multiplexer. But the problem wasn’t <em>running</em> agents in
parallel — plenty of tools do that well. The problem was that the agents had no way to <strong>coordinate</strong>:
@@ -188,6 +189,7 @@ can supervise at a glance.</li>
<p>And the joke that became the name: <em>the world’s best agents, the world’s worst paper company.</em> The
office metaphor isn’t decoration — it turned out to be the clearest way to think about (and watch) a
team of coordinating agents.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/why-we-built-munder-difflin/note-2.png" alt="Hand-drawn sketch from “Why We Built Munder Difflin”" loading="lazy" decoding="async" /></figure>
<h2 id="why-local-why-open-source" tabindex="-1">Why local, why open source <a class="anchor" href="#why-local-why-open-source" aria-hidden="true">#</a></h2>
<p>Two decisions were never really in question. <strong>Local-first</strong>, because agents that touch your whole
codebase shouldn’t ship your code and memory to someone else’s cloud — you keep the control, the
@@ -235,50 +237,50 @@ Munder Difflin</a> — it’s open source and local-first, on macOS, Windows, an
<h2>Related in Story</h2>
<div class="post-grid">
<article class="card t-story">
- <a class="thumb t-story" href="/blog/whats-up-with-munder-difflin/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/whats-up-with-munder-difflin/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-4-4/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-4-4/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-08">Aug 8, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>7 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/whats-up-with-munder-difflin/">What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</a></h3>
- <p class="dek">Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</p>
+ <h3><a href="/blog/launching-munder-difflin-v0-4-4/">Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk</a></h3>
+ <p class="dek">v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/whats-up-with-munder-difflin/" aria-label="Read: What&#39;s Up With Munder Difflin: Six Weeks, Four Releases, and the Part of the Stack You Actually Own">Read →</a>
+ <a class="more" href="/blog/launching-munder-difflin-v0-4-4/" aria-label="Read: Launching Munder Difflin v0.4.4: Windows Agents Can Finally Talk">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-5/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-5/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/number-five-on-product-hunt/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/number-five-on-product-hunt/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-08-06">Aug 6, 2026</time>
+ <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/launching-munder-difflin-v0-3-5/">Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</a></h3>
- <p class="dek">The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</p>
+ <h3><a href="/blog/number-five-on-product-hunt/">Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</a></h3>
+ <p class="dek">Munder Difflin finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-5/" aria-label="Read: Launching Munder Difflin v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself">Read →</a>
+ <a class="more" href="/blog/number-five-on-product-hunt/" aria-label="Read: Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers">Read →</a>
</div>
</div>
</article>
<article class="card t-story">
- <a class="thumb t-story" href="/blog/launching-munder-difflin-v0-3-3/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/launching-munder-difflin-v0-3-3/hero.png" alt="" loading="lazy" decoding="async" /></a>
+ <a class="thumb t-story" href="/blog/seven-releases-in-eight-days/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/seven-releases-in-eight-days/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
- <time datetime="2026-07-03">Jul 3, 2026</time>
+ <time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
- <span>3 min</span>
+ <span>4 min</span>
</div>
- <h3><a href="/blog/launching-munder-difflin-v0-3-3/">Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</a></h3>
- <p class="dek">Munder Difflin v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</p>
+ <h3><a href="/blog/seven-releases-in-eight-days/">Seven Releases in Eight Days: 0.3.8 → 0.4.4</a></h3>
+ <p class="dek">Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</p>
<div class="foot">
<span class="tag kind">Story</span>
- <a class="more" href="/blog/launching-munder-difflin-v0-3-3/" aria-label="Read: Launching Munder Difflin v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support">Read →</a>
+ <a class="more" href="/blog/seven-releases-in-eight-days/" aria-label="Read: Seven Releases in Eight Days: 0.3.8 → 0.4.4">Read →</a>
</div>
</div>
</article>
diff --git a/docs/blog/your-first-hour-with-munder-difflin/index.html b/docs/blog/your-first-hour-with-munder-difflin/index.html
index 7ef0e03a..e6855dde 100644
--- a/docs/blog/your-first-hour-with-munder-difflin/index.html
+++ b/docs/blog/your-first-hour-with-munder-difflin/index.html
@@ -180,6 +180,7 @@
<li><strong>Orchestrator engine</strong> — Michael himself runs on a pluggable engine. Claude Code is the natural default, but the wizard lets you pick, and you can change it later.</li>
</ul>
<p>Finish the wizard and you land on the floor: a pixel-art office, empty except for Michael, who seats himself in his office automatically.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/your-first-hour-with-munder-difflin/note-1.png" alt="Hand-drawn sketch from “Your First Hour With Munder Difflin”" loading="lazy" decoding="async" /></figure>
<h2 id="minute-10-your-first-brief-to-michael" tabindex="-1">Minute 10 — Your first brief to Michael <a class="anchor" href="#minute-10-your-first-brief-to-michael" aria-hidden="true">#</a></h2>
<p>You don’t manage the workers. You talk to one agent — the GOD orchestrator — and he runs the floor. Click into Michael’s terminal and type a brief the way you’d brief a colleague: what you want, which repo, what “done” looks like.</p>
<p>Michael adjudicates. He creates tasks on the kanban, assigns them, and routes messages between agent inboxes. Workers you hire via <strong>Add agent</strong> each get a real CLI process in its own pseudo-terminal and, with the git-isolation toggle, their own worktree — so nobody collides on branches. How he decides what to route, resolve, or escalate is its own post: <a href="/blog/how-the-god-orchestrator-works/">how the GOD orchestrator works</a>.</p>
@@ -188,6 +189,7 @@
<p>Now the part that makes the product legible: the floor is not a decoration, it’s the state of the system. Avatars walk to stations as they work. When the hive routes a message, an envelope flies from sender to recipient; escalations fly to the door. The cast is an affectionate parody of The Office, and every movement maps to a real event.</p>
<figure class="fig fig-inline"><img src="/blog/assets/media/your-first-hour-with-munder-difflin/floor-view.png" alt="The office floor: suited agents at desks, one carrying a sticky note to the kanban wall" loading="lazy" decoding="async" /><figcaption>The floor mid-task: every movement maps to a real event.</figcaption></figure>
<p>Click any agent and you get their desk: the live terminal (you can type back into it), a sandboxed file browser, and a git tab with status, log, and commit graph. This is the moment the abstraction clicks — that avatar is a real <code>claude</code> process, and you’re reading its actual stdout.</p>
+<figure class="fig fig-inline"><img src="/blog/assets/media/your-first-hour-with-munder-difflin/note-2.png" alt="Hand-drawn sketch from “Your First Hour With Munder Difflin”" loading="lazy" decoding="async" /></figure>
<h2 id="minute-40-your-first-approval-and-the-diff" tabindex="-1">Minute 40 — Your first approval, and the diff <a class="anchor" href="#minute-40-your-first-approval-and-the-diff" aria-hidden="true">#</a></h2>
<p>Sometime in the first hour, something lands in the approvals queue — a spend threshold, a destructive operation, a scope change. This is by design: Michael resolves routine requests himself and escalates only critical items, so the queue stays short and every item in it deserves your attention. (The philosophy behind that gate: <a href="/blog/human-in-the-loop-approving-ai-agents/">approving AI agents without babysitting them</a>.)</p>
<p>Before you click approve, look at the work. Hit the title-bar <strong>IDE</strong> button and the built-in Monaco editor — the VS Code editor engine, fully self-hosted — opens over the floor. The git CHANGES rail lists what changed; click a file for a read-only side-by-side diff against HEAD. Read the diff, approve the item, watch the envelope fly.</p>
diff --git a/docs/sitemap.xml b/docs/sitemap.xml
index 38346b31..de5d1b64 100644
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@@ -20,6 +20,66 @@
<url><loc>https://munderdiffl.in/blog/</loc><changefreq>daily</changefreq><priority>0.9</priority></url>
<url><loc>https://munderdiffl.in/blog/topics/</loc><changefreq>weekly</changefreq><priority>0.6</priority></url>
<url><loc>https://munderdiffl.in/blog/about/</loc><changefreq>monthly</changefreq><priority>0.4</priority></url>
+ <url>
+ <loc>https://munderdiffl.in/blog/agents-ran-our-launch-week-analytics/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/an-agent-redesigned-this-blog/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/launching-munder-difflin-v0-4-4/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/number-five-on-product-hunt/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/run-a-release-train-with-agents/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/seven-releases-in-eight-days/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/the-newline-that-silenced-windows-agents/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/turn-feedback-into-a-backlog-with-agents/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/we-opened-a-discord/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
+ <url>
+ <loc>https://munderdiffl.in/blog/what-reddit-told-us-about-munder-difflin/</loc>
+ <lastmod>2026-08-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+ </url>
<url>
<loc>https://munderdiffl.in/blog/whats-up-with-munder-difflin/</loc>
<lastmod>2026-08-08</lastmod>
@@ -740,28 +800,29 @@
<url><loc>https://munderdiffl.in/blog/topics/comparisons/</loc><changefreq>weekly</changefreq><priority>0.5</priority></url>
<url><loc>https://munderdiffl.in/blog/topics/story/</loc><changefreq>weekly</changefreq><priority>0.5</priority></url>
<url><loc>https://munderdiffl.in/blog/topics/orchestration/</loc><changefreq>weekly</changefreq><priority>0.5</priority></url>
- <url><loc>https://munderdiffl.in/blog/topics/memory/</loc><changefreq>weekly</changefreq><priority>0.5</priority></url>
<url><loc>https://munderdiffl.in/blog/topics/use-cases/</loc><changefreq>weekly</changefreq><priority>0.5</priority></url>
+ <url><loc>https://munderdiffl.in/blog/topics/memory/</loc><changefreq>weekly</changefreq><priority>0.5</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/multi-agent/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/claude-code/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/internals/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/guides/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/open-source/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/orchestration/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/concepts/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/comparisons/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
- <url><loc>https://munderdiffl.in/blog/tags/open-source/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
- <url><loc>https://munderdiffl.in/blog/tags/local-first/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/story/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/local-first/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/release/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/automation/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/use-cases/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/tools/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
- <url><loc>https://munderdiffl.in/blog/tags/release/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/getting-started/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/memory/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/workflow/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/human-in-the-loop/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/security/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/cost/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/mempalace/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
- <url><loc>https://munderdiffl.in/blog/tags/use-cases/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/hive/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/observability/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/guardrails/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
@@ -774,13 +835,14 @@
<url><loc>https://munderdiffl.in/blog/tags/cli-agents/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/voice/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/ide/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
- <url><loc>https://munderdiffl.in/blog/tags/workflow/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/terminals/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/debugging/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/model-routing/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/agentic-ai/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/aeo/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/seo/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/engines/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/launch/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/god/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/messaging/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/faq/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
@@ -789,8 +851,9 @@
<url><loc>https://munderdiffl.in/blog/tags/visualization/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/xtermjs/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/hooks/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/skills/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/node-pty/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/performance/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
- <url><loc>https://munderdiffl.in/blog/tags/debugging/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/prompt-caching/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/slack/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/protocols/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
@@ -798,6 +861,8 @@
<url><loc>https://munderdiffl.in/blog/tags/codex/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/code-review/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/agent-design/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/windows/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/community/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/subagents/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/markdown/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/coordination/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
@@ -805,8 +870,6 @@
<url><loc>https://munderdiffl.in/blog/tags/glossary/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/privacy/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/game-dev/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
- <url><loc>https://munderdiffl.in/blog/tags/skills/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
- <url><loc>https://munderdiffl.in/blog/tags/node-pty/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/error-handling/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/context-engineering/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/evaluation/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
@@ -857,4 +920,15 @@
<url><loc>https://munderdiffl.in/blog/tags/tooling-landscape/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/harness-engineering/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
<url><loc>https://munderdiffl.in/blog/tags/onboarding/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/research/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/design/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/eleventy/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/meta/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/product-hunt/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/changelog/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/postmortem/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/feedback/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/product/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/discord/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
+ <url><loc>https://munderdiffl.in/blog/tags/reddit/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>
</urlset>