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
HTML agent-harnessagent-orchestrationagentsai-agentsautonomous-agentsclaude-codecodexcoding-agentsdesktop-appdeveloper-toolselectrongemini-cliharnessharness-engineeringlocal-firstmemorymulti-agentopencodeorchestrationtypescript
<!doctype html>
<html lang="en">
<head>
<!-- Google tag (gtag.js), Google Ads AW-18388216863. Loaded only when Do Not Track is
off, so it follows the same rule as the PostHog block on this site. -->
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){ dataLayer.push(arguments); }
if (navigator.doNotTrack !== '1') {
var gtagScript = document.createElement('script');
gtagScript.async = true;
gtagScript.src = 'https://www.googletagmanager.com/gtag/js?id=AW-18388216863';
document.head.appendChild(gtagScript);
gtag('js', new Date());
gtag('config', 'AW-18388216863');
}
</script>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>What Is Harness Engineering? — Munder Difflin Blog</title>
<meta name="description" content="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." />
<link rel="canonical" href="https://munderdiffl.in/blog/what-is-harness-engineering/" />
<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 Is Harness Engineering? — Munder Difflin Blog" />
<meta property="og:description" content="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." />
<meta property="og:url" content="https://munderdiffl.in/blog/what-is-harness-engineering/" />
<meta property="og:image" content="https://munderdiffl.in/blog/assets/media/what-is-harness-engineering/hero.png" />
<meta property="og:image:width" content="1600" />
<meta property="og:image:height" content="900" />
<meta property="og:image:alt" content="Illustration: What Is Harness Engineering?" />
<meta property="og:locale" content="en_US" />
<meta property="article:published_time" content="2026-07-03T00:00:00.000Z" />
<meta property="article:author" content="Chaitanya Giri" />
<meta property="article:tag" content="Concepts" />
<meta property="article:tag" content="Harness Engineering" />
<meta property="article:tag" content="Reliability" />
<meta property="article:tag" content="Multi-Agent" />
<meta property="article:tag" content="Architecture" />
<!-- Twitter -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="What Is Harness Engineering? — Munder Difflin Blog" />
<meta name="twitter:description" content="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." />
<meta name="twitter:image" content="https://munderdiffl.in/blog/assets/media/what-is-harness-engineering/hero.png" />
<meta name="twitter:image:alt" content="Illustration: What Is Harness Engineering?" />
<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&family=Source+Serif+4:opsz,[email protected],400;8..60,600;8..60,700&family=Space+Grotesk:wght@500;600;700&family=JetBrains+Mono:wght@400;600&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 Is Harness Engineering?",
"description": "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.",
"image": ["https://munderdiffl.in/blog/assets/media/what-is-harness-engineering/hero.png"],
"datePublished": "2026-07-03T00:00:00.000Z",
"dateModified": "2026-07-03T00: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-is-harness-engineering/" },
"keywords": "harness engineering, what is harness engineering, agent harness, ai agent reliability, the model is a commodity, agent infrastructure, multi-agent harness",
"articleSection": "Concepts",
"inLanguage": "en-US",
"url": "https://munderdiffl.in/blog/what-is-harness-engineering/"
}
</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 Is Harness Engineering?", "item": "https://munderdiffl.in/blog/what-is-harness-engineering/" }
]
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{ "@type": "Question", "name": "What is harness engineering?", "acceptedAnswer": { "@type": "Answer", "text": "Harness engineering is the discipline of building the environment around an AI model that turns it into a reliable agent: the process plumbing, lifecycle hooks, message routing, memory, budgets, human approval gates, observability, and recovery mechanics. The working equation is agent = model + harness. The model supplies raw capability; the harness determines whether that capability shows up predictably, safely, and repeatably in production." } },
{ "@type": "Question", "name": "Who coined the term harness engineering?", "acceptedAnswer": { "@type": "Answer", "text": "The term was popularized by Mitchell Hashimoto, co-founder of HashiCorp, in a February 2026 blog post about his AI adoption journey. His core premise: any time an agent makes a mistake, you engineer a solution so the agent never makes that mistake again. The 2026 agent-engineering discourse has since adopted it as the phase that follows prompt engineering and context engineering." } },
{ "@type": "Question", "name": "Why is the harness more important than the model?", "acceptedAnswer": { "@type": "Answer", "text": "Because models are increasingly interchangeable commodities and their failure modes are structural, not intelligence-limited. An agent that loops, forgets, overspends, or silently drops a message doesn't need a smarter model — it needs a circuit breaker, a memory layer, a budget, and a mailbox with delivery guarantees. Reported results back this up: teams have climbed agent benchmarks significantly by changing only the harness, with the model held constant." } },
{ "@type": "Question", "name": "What are the components of an agent harness?", "acceptedAnswer": { "@type": "Answer", "text": "A production harness typically covers: real execution plumbing (PTYs or sandboxes the agent acts through), lifecycle hooks (structured signals for turn start/end and tool use), inter-agent messaging with delivery guarantees, long-term memory, token budgets and cost controls, human-in-the-loop gates for destructive or expensive actions, observability (traces, costs, per-agent telemetry), and session resume so a restart doesn't destroy state." } },
{ "@type": "Question", "name": "Is harness engineering the same as prompt engineering?", "acceptedAnswer": { "@type": "Answer", "text": "No, but it absorbs it. Prompt engineering shapes a single model call; context engineering shapes what the model sees across a task; harness engineering shapes the entire system the model operates inside — including what happens when a call fails, a process dies, a budget is exceeded, or two agents need to hand off work. Prompts are one component of the harness, not a substitute for it." } },
{ "@type": "Question", "name": "Is Munder Difflin a harness?", "acceptedAnswer": { "@type": "Answer", "text": "Yes — that's the category. Munder Difflin is a free, MIT-licensed, local-first multi-agent harness: it wraps the agent CLIs you already run (Claude Code, Codex, Antigravity, OpenCode, Crush, pi.dev, GitHub Copilot CLI) in node-pty pseudo-terminals, wires them into a hive with mailboxes, shared memory, budgets, a circuit breaker, human approval gates, and observability, and puts a GOD orchestrator in charge." } }
]
}
</script>
<script>
// Anonymous blog analytics (PostHog) — same posture as the main site and the
// app's TELEMETRY.md: public write-only token ('' = inert), anonymous-only
// (person_profiles 'never'), no autocapture/recording, DNT respected.
(function () {
var PH_KEY = 'phc_qJzsokwcbtTGHemnvywR3nSqivNNgMjHeNVEWkZNydFB';
if (!PH_KEY || navigator.doNotTrack === '1') return;
var s = document.createElement('script');
s.async = true;
s.src = 'https://us-assets.i.posthog.com/static/array.js';
s.onload = function () {
if (!window.posthog) return;
window.posthog.init(PH_KEY, {
api_host: 'https://us.i.posthog.com',
person_profiles: 'never',
autocapture: false,
before_send: function (event) {
// PostHog fills $ip from the connection unless the event carries one.
// Null it here and disable the GeoIP lookup so no IP, city, postal
// code or lat/long is ever derived or stored for this page view.
if (event && event.properties) {
event.properties.$ip = null;
event.properties.$geoip_disable = true;
}
return event;
},
disable_session_recording: true,
respect_dnt: true
});
};
document.head.appendChild(s);
})();
</script>
</head>
<body class="theme-press">
<a class="skip-link" href="#main">Skip to content</a>
<nav id="nav">
<a class="brand" href="https://munderdiffl.in" aria-label="Munder Difflin home">
<img class="brand-logo" src="https://munderdiffl.in/logo.png" width="1318" height="840" alt="Munder Difflin, Inc. — Multi-Agent Harness" />
</a>
<span class="spacer"></span>
<div class="links">
<a href="/blog/">Latest</a>
<a href="/blog/topics/">Topics</a>
<a href="/blog/about/">About</a>
<a href="https://munderdiffl.in">↗ Product</a>
</div>
<div class="nav-actions">
<a class="btn sm" href="https://munderdiffl.in/blog/feed.xml" aria-label="RSS feed">⤵ RSS</a>
<a class="btn sm primary" href="https://munderdiffl.in/#install">⤓ Download</a>
</div>
</nav>
<main id="main">
<article class="t-concepts">
<header class="post-head wrap">
<nav class="crumbs" aria-label="Breadcrumb">
<a href="/blog/">Blog</a>
<span>/</span>
<a href="/blog/topics/concepts/">Concepts</a>
</nav>
<h1>What Is Harness Engineering?</h1>
<p class="dek">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.</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-07-03">Jul 3, 2026</time>
<span class="dot" aria-hidden="true">·</span>
<span>5 min read</span>
<span class="tag kind">Concepts</span>
</div>
</header>
<div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/what-is-harness-engineering/hero.png" alt="Illustration: What Is Harness Engineering?" 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>Harness engineering is the discipline of building everything around the model</strong> — the PTY plumbing, lifecycle hooks, mailboxes, memory, budgets, human gates, observability, and session resume that turn a capable model into a <strong>reliable agent</strong>. The 2026 consensus, popularized by Mitchell Hashimoto: <strong>the model is a commodity; the harness is where reliability comes from</strong>. Every time an agent fails, you engineer the harness so that failure becomes structurally impossible. Munder Difflin is this discipline shipped as a product — and its hook shim, node-pty layer, MemPalace, and circuit breaker are worked examples.</p></div>
<p>Ask why an agent failed and you’ll almost never hear “the model wasn’t smart enough.” You’ll hear: it looped for forty minutes, it forgot what it learned yesterday, it blew the budget overnight, it dropped a message and nobody noticed, the process died and took the session with it.</p>
<p>None of those are model problems. All of them are <strong>harness problems</strong>. And in 2026, fixing them got a name.</p>
<h2 id="the-term-and-where-it-came-from" tabindex="-1">The term, and where it came from <a class="anchor" href="#the-term-and-where-it-came-from" aria-hidden="true">#</a></h2>
<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>
<li><strong>Execution plumbing.</strong> A real place for the agent to act — a pseudo-terminal, a sandbox, a worktree — not a simulated one.</li>
<li><strong>Lifecycle hooks.</strong> Structured signals for turn start, turn end, and tool use, so the harness <em>knows</em> what the agent is doing rather than guessing from stdout.</li>
<li><strong>Mailboxes and routing.</strong> Inter-agent messages with delivery guarantees; a dropped handoff must bounce somewhere visible, never vanish.</li>
<li><strong>Memory.</strong> Durable, recallable knowledge that survives the session, so agents stop re-deriving the same facts.</li>
<li><strong>Budgets and breakers.</strong> Hard ceilings on tokens and cost, plus a mechanism that intervenes when an agent runs away.</li>
<li><strong>Human gates.</strong> Approval checkpoints on spend, scope changes, and destructive operations — human-in-the-loop by design.</li>
<li><strong>Observability.</strong> Traces, per-agent cost attribution, live telemetry — <a href="/blog/observability-for-agent-fleets/">you can’t operate a fleet you can’t see</a>.</li>
<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>
<p><strong>node-pty — real terminals, not string simulations.</strong> Each agent is a real CLI process in its own pseudo-terminal, byte-for-byte authentic, with full read/write/resize/kill — paired with per-agent git worktrees so agents never collide on branches. The unglamorous plumbing (a <code>PtyManager</code>, per-id IPC streams, a postinstall that rebuilds the native addon against Electron’s ABI) is exactly the kind of work the model can never do for you, and exactly what makes the agent’s terminal access <em>real</em>.</p>
<p><strong>MemPalace — memory as infrastructure.</strong> Agents write markdown-first long-term memory, mined into a shared semantic index for instant recall, with a MemoryReflector that condenses it so it doesn’t grow without bound. “The agent forgot” stops being a shrug and becomes a subsystem with behavior you can engineer — the deep dive is in <a href="/blog/semantic-memory-for-ai-agents/">semantic memory for AI agents</a>.</p>
<p><strong>The circuit breaker — graduated intervention, not a kill switch.</strong> The cost/runaway guard runs a <strong>steer → constrain → stop</strong> ladder: nudge an agent that’s looping, constrain it if it persists, stop it if it storms errors or blows its per-agent token budget. Paired with approval gates on spend and destructive ops, this is what makes 24/7 autonomy something you can actually sleep through — part of the larger practice of <a href="/blog/building-reliable-ai-agents/">building reliable AI agents</a>.</p>
<h2 id="why-this-is-a-discipline-not-a-feature-list" tabindex="-1">Why this is a discipline, not a feature list <a class="anchor" href="#why-this-is-a-discipline-not-a-feature-list" aria-hidden="true">#</a></h2>
<p>The pattern across all four: <strong>reliability was engineered into the environment, not prompted into the model.</strong> Each subsystem exists because a specific failure mode exists, and each closes that failure mode for every model, every provider, permanently. Swap Claude for Codex or a local model tomorrow — the breaker still breaks, the mail still routes, the memory still recalls. That’s what “the model is a commodity” means in practice: the harness is the part that compounds.</p>
<p>If you want to see a harness rather than read about one, <a href="https://github.com/chaitanyagiri/munder-difflin/releases/latest">download Munder Difflin</a> — free, MIT-licensed, local-first — and if the idea resonates, <a href="https://github.com/chaitanyagiri/munder-difflin">a GitHub star</a> helps more people find it.</p>
<p>Sources: <a href="https://mitchellh.com/writing/my-ai-adoption-journey">Mitchell Hashimoto — My AI Adoption Journey</a>;
<a href="https://www.faros.ai/blog/harness-engineering">Faros AI — Harness Engineering: Making AI Coding Agents Work in 2026</a>.</p>
<section class="faq" aria-label="Frequently asked questions">
<h2 id="faq">FAQ</h2>
<div class="qa">
<p class="q">What is harness engineering?</p>
<p class="a">Harness engineering is the discipline of building the environment around an AI model that turns it into a reliable agent: the process plumbing, lifecycle hooks, message routing, memory, budgets, human approval gates, observability, and recovery mechanics. The working equation is agent = model + harness. The model supplies raw capability; the harness determines whether that capability shows up predictably, safely, and repeatably in production.</p>
</div>
<div class="qa">
<p class="q">Who coined the term harness engineering?</p>
<p class="a">The term was popularized by Mitchell Hashimoto, co-founder of HashiCorp, in a February 2026 blog post about his AI adoption journey. His core premise: any time an agent makes a mistake, you engineer a solution so the agent never makes that mistake again. The 2026 agent-engineering discourse has since adopted it as the phase that follows prompt engineering and context engineering.</p>
</div>
<div class="qa">
<p class="q">Why is the harness more important than the model?</p>
<p class="a">Because models are increasingly interchangeable commodities and their failure modes are structural, not intelligence-limited. An agent that loops, forgets, overspends, or silently drops a message doesn't need a smarter model — it needs a circuit breaker, a memory layer, a budget, and a mailbox with delivery guarantees. Reported results back this up: teams have climbed agent benchmarks significantly by changing only the harness, with the model held constant.</p>
</div>
<div class="qa">
<p class="q">What are the components of an agent harness?</p>
<p class="a">A production harness typically covers: real execution plumbing (PTYs or sandboxes the agent acts through), lifecycle hooks (structured signals for turn start/end and tool use), inter-agent messaging with delivery guarantees, long-term memory, token budgets and cost controls, human-in-the-loop gates for destructive or expensive actions, observability (traces, costs, per-agent telemetry), and session resume so a restart doesn't destroy state.</p>
</div>
<div class="qa">
<p class="q">Is harness engineering the same as prompt engineering?</p>
<p class="a">No, but it absorbs it. Prompt engineering shapes a single model call; context engineering shapes what the model sees across a task; harness engineering shapes the entire system the model operates inside — including what happens when a call fails, a process dies, a budget is exceeded, or two agents need to hand off work. Prompts are one component of the harness, not a substitute for it.</p>
</div>
<div class="qa">
<p class="q">Is Munder Difflin a harness?</p>
<p class="a">Yes — that's the category. Munder Difflin is a free, MIT-licensed, local-first multi-agent harness: it wraps the agent CLIs you already run (Claude Code, Codex, Antigravity, OpenCode, Crush, pi.dev, GitHub Copilot CLI) in node-pty pseudo-terminals, wires them into a hive with mailboxes, shared memory, budgets, a circuit breaker, human approval gates, and observability, and puts a GOD orchestrator in charge.</p>
</div>
</section>
<hr />
<div class="share">
<span class="lbl">Tags</span>
<a class="tag" href="/blog/tags/concepts/">Concepts</a><a class="tag" href="/blog/tags/harness-engineering/">Harness Engineering</a><a class="tag" href="/blog/tags/reliability/">Reliability</a><a class="tag" href="/blog/tags/multi-agent/">Multi-Agent</a><a class="tag" href="/blog/tags/architecture/">Architecture</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-term-and-where-it-came-from">The term, and where it came from</a></li><li class="lvl-2"><a href="#what-a-harness-actually-contains">What a harness actually contains</a></li><li class="lvl-2"><a href="#four-case-studies-from-inside-munder-difflin">Four case studies from inside Munder Difflin</a></li><li class="lvl-2"><a href="#why-this-is-a-discipline-not-a-feature-list">Why this is a discipline, not a feature list</a></li>
</ol>
</aside>
</div>
<footer class="post-foot wrap"><div class="prevnext">
<a class="pn prev" href="/blog/your-first-hour-with-munder-difflin/"><span class="k">← Older</span><span class="t">Your First Hour With Munder Difflin 0.5.6: Onboarding From First Sign In to a Working Office</span></a>
<a class="pn next" href="/blog/what-is-an-agent-development-environment/"><span class="k">Newer →</span><span class="t">What Is an Agent Development Environment (ADE)?</span></a>
</div>
<section class="related">
<h2>Related in Concepts</h2>
<div class="post-grid">
<article class="card t-concepts">
<a class="thumb t-concepts" href="/blog/gpt-6-1-terra/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/gpt-6-1-terra/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-10-27">Oct 27, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>4 min</span>
</div>
<h3><a href="/blog/gpt-6-1-terra/">GPT-6.1 Terra: Price, Specs and How to Use It in Codex (Oct 2026)</a></h3>
<p class="dek">GPT-6.1 Terra is OpenAI's fast new model for images, computer use and writing: price, specs and how to pick it in Codex, checked 27 Oct 2026.</p>
<div class="foot">
<span class="tag kind">Concepts</span>
<a class="more" href="/blog/gpt-6-1-terra/" aria-label="Read: GPT-6.1 Terra: Price, Specs and How to Use It in Codex (Oct 2026)">Read →</a>
</div>
</div>
</article>
<article class="card t-concepts">
<a class="thumb t-concepts" href="/blog/what-is-claude-duet/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/what-is-claude-duet/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-10-22">Oct 22, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>5 min</span>
</div>
<h3><a href="/blog/what-is-claude-duet/">What Is Claude Duet? Anthropic's Proactive Agent App, Explained</a></h3>
<p class="dek">Claude Duet is Anthropic's proactive agent app, in research preview since 21 Oct 2026: who can join, how it works, what it asks first and its limits.</p>
<div class="foot">
<span class="tag kind">Concepts</span>
<a class="more" href="/blog/what-is-claude-duet/" aria-label="Read: What Is Claude Duet? Anthropic's Proactive Agent App, Explained">Read →</a>
</div>
</div>
</article>
<article class="card t-concepts">
<a class="thumb t-concepts" href="/blog/deepseek-v4-1-flash-1017/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deepseek-v4-1-flash-1017/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-10-17">Oct 17, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>4 min</span>
</div>
<h3><a href="/blog/deepseek-v4-1-flash-1017/">DeepSeek V4.1 Flash 1017: What Changed, the Price and Claude Code Setup</a></h3>
<p class="dek">DeepSeek V4.1 Flash 1017, released 17 Oct 2026 under MIT: what changed, DeepSeek's benchmarks, the API price and Claude Code setup.</p>
<div class="foot">
<span class="tag kind">Concepts</span>
<a class="more" href="/blog/deepseek-v4-1-flash-1017/" aria-label="Read: DeepSeek V4.1 Flash 1017: What Changed, the Price and Claude Code Setup">Read →</a>
</div>
</div>
</article>
</div>
</section>
</footer>
</article>
</main>
<footer class="site-foot">
<div class="wrap">
<div class="foot-top">
<a class="foot-brand brand" href="https://munderdiffl.in" aria-label="Munder Difflin home">
<img class="brand-logo" src="https://munderdiffl.in/logo.png" width="1318" height="840" alt="Munder Difflin, Inc. — Multi-Agent Harness" />
</a>
<div class="foot-links">
<a href="/blog/">Latest</a>
<a href="/blog/topics/">Topics</a>
<a href="/blog/about/">About</a>
<a href="https://munderdiffl.in/blog/feed.xml">RSS</a>
<a href="https://github.com/chaitanyagiri/munder-difflin">GitHub</a>
<a href="https://munderdiffl.in">munderdiffl.in ↗</a>
</div>
</div>
<div class="foot-meta">
© 2026 Munder Difflin · Local-first · MIT-licensed ·
Built on <a href="https://munderdiffl.in">Electron, React, Pixi.js, xterm.js & node-pty</a>.
Run an office of agents while you sleep.
</div>
</div>
</footer>
<script>
// sticky-nav border on scroll
(function () {
var nav = document.getElementById('nav');
if (!nav) return;
var onScroll = function () { nav.classList.toggle('scrolled', window.scrollY > 8); };
onScroll(); window.addEventListener('scroll', onScroll, { passive: true });
})();
// YouTube click-to-load: thumbnail button → youtube-nocookie iframe
(function () {
document.addEventListener('click', function (e) {
var btn = e.target.closest('.yt-load');
if (!btn) return;
var box = btn.closest('.yt');
var id = box && box.getAttribute('data-yt');
// Only an 11 character YouTube video id may reach the iframe URL.
if (!id || !/^[A-Za-z0-9_-]{11}$/.test(id)) return;
var frame = document.createElement('iframe');
frame.src = 'https://www.youtube-nocookie.com/embed/' + encodeURIComponent(id) + '?autoplay=1';
frame.title = box.getAttribute('data-title') || 'YouTube video';
frame.allow = 'accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share';
frame.setAttribute('allowfullscreen', '');
box.replaceChildren(frame);
});
})();
</script>
</body>
</html>