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>Compressing Agent Memory Without Losing the Original — Munder Difflin Blog</title>
<meta name="description" content="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." />
<link rel="canonical" href="https://munderdiffl.in/blog/compressing-agent-memory/" />
<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="Compressing Agent Memory Without Losing the Original — Munder Difflin Blog" />
<meta property="og:description" content="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." />
<meta property="og:url" content="https://munderdiffl.in/blog/compressing-agent-memory/" />
<meta property="og:image" content="https://munderdiffl.in/blog/assets/media/compressing-agent-memory/hero.png" />
<meta property="og:image:width" content="1600" />
<meta property="og:image:height" content="900" />
<meta property="og:image:alt" content="Illustration: Compressing Agent Memory Without Losing the Original" />
<meta property="og:locale" content="en_US" />
<meta property="article:published_time" content="2026-06-05T00:00:00.000Z" />
<meta property="article:author" content="Chaitanya Giri" />
<meta property="article:tag" content="Internals" />
<meta property="article:tag" content="Memory" />
<meta property="article:tag" content="MemPalace" />
<meta property="article:tag" content="Multi-Agent" />
<!-- Twitter -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Compressing Agent Memory Without Losing the Original — Munder Difflin Blog" />
<meta name="twitter:description" content="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." />
<meta name="twitter:image" content="https://munderdiffl.in/blog/assets/media/compressing-agent-memory/hero.png" />
<meta name="twitter:image:alt" content="Illustration: Compressing Agent Memory Without Losing the Original" />
<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": "Compressing Agent Memory Without Losing the Original",
"description": "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.",
"image": ["https://munderdiffl.in/blog/assets/media/compressing-agent-memory/hero.png"],
"datePublished": "2026-06-05T00:00:00.000Z",
"dateModified": "2026-06-05T00: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/compressing-agent-memory/" },
"keywords": "compressing agent memory, agent memory compression, long-term memory ai agents, context compression",
"articleSection": "Internals",
"inLanguage": "en-US",
"url": "https://munderdiffl.in/blog/compressing-agent-memory/"
}
</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": "Compressing Agent Memory Without Losing the Original", "item": "https://munderdiffl.in/blog/compressing-agent-memory/" }
]
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{ "@type": "Question", "name": "Why compress an agent's memory instead of using a bigger context window?", "acceptedAnswer": { "@type": "Answer", "text": "Because a bigger window carries more noise, costs more per call, and still fills up. The 2026 consensus is to compress what the agent carries forward — fewer, denser tokens of signal — rather than chase a larger window. Compression is what lets a memory store grow for months while the wake-up context an agent loads stays small." } },
{ "@type": "Question", "name": "Doesn't compressing memory lose information?", "acceptedAnswer": { "@type": "Answer", "text": "It can — compression is non-deterministically lossy, and a summary can silently drop the one exception or classification tag that mattered. The fix is to never make the compressed copy the only copy: keep the lossless original on disk and treat the compressed form as a fast-recall accelerator built from it, not a replacement." } },
{ "@type": "Question", "name": "What actually gets compressed — the stored memory or the prompt?", "acceptedAnswer": { "@type": "Answer", "text": "Both are valid, at different layers. You can compact the live conversation as it approaches the window limit, and you can compress long-term stored memory so a session can absorb months of history in a few thousand tokens at wake-up. This post is mostly about the second: durable memory you recall across sessions." } }
]
}
</script>
<script>
// Anonymous blog analytics (PostHog) — same posture as the main site and the
// app's TELEMETRY.md: public write-only token ('' = inert), anonymous-only
// (person_profiles 'never'), no autocapture/recording, DNT respected.
(function () {
var PH_KEY = 'phc_qJzsokwcbtTGHemnvywR3nSqivNNgMjHeNVEWkZNydFB';
if (!PH_KEY || navigator.doNotTrack === '1') return;
var s = document.createElement('script');
s.async = true;
s.src = 'https://us-assets.i.posthog.com/static/array.js';
s.onload = function () {
if (!window.posthog) return;
window.posthog.init(PH_KEY, {
api_host: 'https://us.i.posthog.com',
person_profiles: 'never',
autocapture: false,
before_send: function (event) {
// PostHog fills $ip from the connection unless the event carries one.
// Null it here and disable the GeoIP lookup so no IP, city, postal
// code or lat/long is ever derived or stored for this page view.
if (event && event.properties) {
event.properties.$ip = null;
event.properties.$geoip_disable = true;
}
return event;
},
disable_session_recording: true,
respect_dnt: true
});
};
document.head.appendChild(s);
})();
</script>
</head>
<body class="theme-press">
<a class="skip-link" href="#main">Skip to content</a>
<nav id="nav">
<a class="brand" href="https://munderdiffl.in" aria-label="Munder Difflin home">
<img class="brand-logo" src="https://munderdiffl.in/logo.png" width="1318" height="840" alt="Munder Difflin, Inc. — Multi-Agent Harness" />
</a>
<span class="spacer"></span>
<div class="links">
<a href="/blog/">Latest</a>
<a href="/blog/topics/">Topics</a>
<a href="/blog/about/">About</a>
<a href="https://munderdiffl.in">↗ Product</a>
</div>
<div class="nav-actions">
<a class="btn sm" href="https://munderdiffl.in/blog/feed.xml" aria-label="RSS feed">⤵ RSS</a>
<a class="btn sm primary" href="https://munderdiffl.in/#install">⤓ Download</a>
</div>
</nav>
<main id="main">
<article class="t-internals">
<header class="post-head wrap">
<nav class="crumbs" aria-label="Breadcrumb">
<a href="/blog/">Blog</a>
<span>/</span>
<a href="/blog/topics/internals/">Internals</a>
</nav>
<h1>Compressing Agent Memory Without Losing the Original</h1>
<p class="dek">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.</p>
<div class="byline">
<span class="av" aria-hidden="true">CG</span>
<strong>Chaitanya Giri</strong>
<span class="dot" aria-hidden="true">·</span>
<time datetime="2026-06-05">Jun 5, 2026</time>
<span class="dot" aria-hidden="true">·</span>
<span>5 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/compressing-agent-memory/hero.png" alt="Illustration: Compressing Agent Memory Without Losing the Original" 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>An agent's memory grows forever; its context
window does not. The 2026 answer isn't a bigger window — it's <strong>compression</strong>: store dense,
high-signal memory so a session can load months of history in a few thousand tokens. The catch is that
compression is <strong>lossy in unpredictable ways</strong>. The pattern that makes it safe: keep the
<strong>lossless original</strong> on disk and compress a <em>copy</em> for fast recall — never let the
summary become the only record.</p></div>
<p>Every useful agent accumulates memory — decisions, facts, what worked and what didn’t. That store only
grows, while the context window an agent can actually read stays fixed. So “memory” for agents is really a
compression problem: how do you let the knowledge base grow for months without dragging all of it back
into a finite, expensive context every session? Here’s how to think about compressing agent memory, the
trap to avoid, and the pattern that keeps it safe.</p>
<h2 id="why-compress-at-all" tabindex="-1">Why compress at all <a class="anchor" href="#why-compress-at-all" aria-hidden="true">#</a></h2>
<p>The reflex is to reach for a larger context window. In 2026 the better instinct is the opposite. Teams
building the most capable agents have stopped chasing window size and started <strong>deliberately reducing what
the agent carries forward</strong> — because more context means more noise, higher cost per call, and a window
that still fills up. Compression buys three things at once:</p>
<ul>
<li><strong>A bounded wake-up.</strong> An agent should start a session by loading <em>what it knows</em> in a small, fixed token
budget — not by re-reading everything. Compression is what keeps that digest small as the store grows.</li>
<li><strong>Lower cost.</strong> Tokens are the bill. Denser memory is a cheaper agent, every call.</li>
<li><strong>Better signal.</strong> A tight, distilled memory recalls sharper than a transcript dump. This is the same
reason <a href="/blog/keep-agent-semantic-memory-clean/">memory hygiene</a> matters — what you feed the recall layer
decides what it returns.</li>
</ul>
<h2 id="the-compression-toolbox" tabindex="-1">The compression toolbox <a class="anchor" href="#the-compression-toolbox" aria-hidden="true">#</a></h2>
<p>A few techniques, cheapest to deepest:</p>
<ul>
<li><strong>Summarization</strong> — roll older history into summaries (hierarchical, so summaries-of-summaries keep the
oldest material tiny).</li>
<li><strong>Selective retention / pruning</strong> — keep mission-critical facts, drop the noise. Not everything is worth
remembering.</li>
<li><strong>Offloading</strong> — push bulky content to disk and keep a pointer plus a short preview, re-reading the full
thing only on demand.</li>
<li><strong>Provider-side compaction</strong> — some APIs compress older conversation turns at a threshold (reductions
around 80% are reported) so a long session keeps running.</li>
<li><strong>Structured distillation</strong> — pack each exchange into a dense, symbolic form. Reported ratios reach ~11x
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
the answer looks clean and computes the wrong number. A table summary that drops the upstream source kills
auditability. A summary that drops a data-classification tag forgets that something was sensitive. You
can’t reliably detect these losses after the fact, because each individual summary reads as plausible.</p>
<p>The governance rule that follows: <strong>every compressed chunk should retain a pointer back to its source</strong> —
version and timestamp included — so the system can always route from the dense form back to the exact
original. Which leads to the pattern worth copying.</p>
<h2 id="the-pattern-keep-the-original-compress-a-copy" tabindex="-1">The pattern: keep the original, compress a copy <a class="anchor" href="#the-pattern-keep-the-original-compress-a-copy" aria-hidden="true">#</a></h2>
<p>The clean answer is to refuse the false choice between “lossless but huge” and “compact but lossy” — and
keep both. This is how the hive’s <a href="/blog/semantic-memory-for-ai-agents/">semantic memory</a> layer (MemPalace)
is built, and it’s the part most worth stealing:</p>
<ul>
<li>Each raw memory lives in a <strong>drawer</strong> that holds the <strong>complete original, verbatim</strong> — never summarized,
never paraphrased. Search returns the exact words you stored.</li>
<li>When you turn compression on, a <strong>closet</strong> sits beside that drawer holding a <strong>compact, symbolic summary</strong>
(MemPalace’s AAAK dialect reports roughly 30x reduction) that preserves the semantic and relational gist.</li>
<li>At <strong>wake-up</strong>, an agent loads the compressed closets — absorbing a large span of history in a few
thousand tokens — while any deep lookup can still pull the lossless drawer.</li>
</ul>
<p>The harness side is deliberately thin: every agent writes plain
<a href="/blog/markdown-first-agent-memory/">markdown memory</a>, and a background miner feeds those notes into the
shared palace; recall is a <code>search</code> or a <code>wake-up</code> away. The markdown is the source of truth; the
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
task is <strong>audit- or compliance-critical</strong> and you need the exact source; when the content is full of
<strong>exceptions and edge-cases</strong> a summary tends to flatten; or when data carries <strong>classification or
provenance</strong> that must travel with it. The cross-cutting rule again: never let the compressed copy become
the <em>only</em> copy of something you might need to defend or trace.</p>
<h2 id="faq" tabindex="-1">FAQ <a class="anchor" href="#faq" aria-hidden="true">#</a></h2>
<p><strong>Is this the same as RAG?</strong> Related but not the same. Retrieval fetches relevant chunks; compression
changes how densely those chunks are stored and loaded. They compose — you retrieve, and what you retrieve
can be compressed for a smaller, sharper context.</p>
<p><strong>How much can I compress safely?</strong> As much as you like <em>if</em> the lossless original is preserved and
pointer-linked. The compressed form’s job is fast recall; correctness lives in the untouched source you can
always fall back to.</p>
<p><strong>Does compression help cost or just context size?</strong> Both. Fewer tokens loaded per session is directly
fewer tokens billed — compression is one of the cheapest levers on an agent’s running cost.</p>
<hr>
<p>Munder Difflin gives every Claude Code agent markdown memory plus
<a href="https://munderdiffl.in/#how">a shared semantic palace that keeps the lossless original and a compact, recall-fast copy</a>
— so months of context load in a few thousand tokens, locally.
<a href="https://munderdiffl.in/#install">Download Munder Difflin</a> to give your agents memory that compresses
without forgetting; it’s free and open source.</p>
<section class="faq" aria-label="Frequently asked questions">
<h2 id="faq">FAQ</h2>
<div class="qa">
<p class="q">Why compress an agent's memory instead of using a bigger context window?</p>
<p class="a">Because a bigger window carries more noise, costs more per call, and still fills up. The 2026 consensus is to compress what the agent carries forward — fewer, denser tokens of signal — rather than chase a larger window. Compression is what lets a memory store grow for months while the wake-up context an agent loads stays small.</p>
</div>
<div class="qa">
<p class="q">Doesn't compressing memory lose information?</p>
<p class="a">It can — compression is non-deterministically lossy, and a summary can silently drop the one exception or classification tag that mattered. The fix is to never make the compressed copy the only copy: keep the lossless original on disk and treat the compressed form as a fast-recall accelerator built from it, not a replacement.</p>
</div>
<div class="qa">
<p class="q">What actually gets compressed — the stored memory or the prompt?</p>
<p class="a">Both are valid, at different layers. You can compact the live conversation as it approaches the window limit, and you can compress long-term stored memory so a session can absorb months of history in a few thousand tokens at wake-up. This post is mostly about the second: durable memory you recall across sessions.</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/memory/">Memory</a><a class="tag" href="/blog/tags/mempalace/">MemPalace</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="#why-compress-at-all">Why compress at all</a></li><li class="lvl-2"><a href="#the-compression-toolbox">The compression toolbox</a></li><li class="lvl-2"><a href="#the-trap-lossy-in-ways-you-cant-predict">The trap: lossy in ways you can’t predict</a></li><li class="lvl-2"><a href="#the-pattern-keep-the-original-compress-a-copy">The pattern: keep the original, compress a copy</a></li><li class="lvl-2"><a href="#when-not-to-compress">When not to compress</a></li><li class="lvl-2"><a href="#faq">FAQ</a></li>
</ol>
</aside>
</div>
<footer class="post-foot wrap"><div class="prevnext">
<a class="pn prev" href="/blog/generative-engine-optimization-techniques/"><span class="k">← Older</span><span class="t">Generative Engine Optimization: The Techniques the Research Backs</span></a>
<a class="pn next" href="/blog/cline-vs-munder-difflin/"><span class="k">Newer →</span><span class="t">Cline vs Munder Difflin: One Agent Everywhere, or a Team of Agents?</span></a>
</div>
<section class="related">
<h2>Related in Internals</h2>
<div class="post-grid">
<article class="card t-internals">
<a class="thumb t-internals" href="/blog/the-spend-counter-that-went-back-to-zero/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/the-spend-counter-that-went-back-to-zero/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-08-22">Aug 22, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>10 min</span>
</div>
<h3><a href="/blog/the-spend-counter-that-went-back-to-zero/">The Spend Counter That Went Back to Zero</a></h3>
<p class="dek">Our own floor was under reporting what it cost by 59 percent. The counter was cumulative since process start, the app restarts, and the session id stayed the same. Here is how a monotonic invariant let us recover the real number from an append-only log.</p>
<div class="foot">
<span class="tag kind">Internals</span>
<a class="more" href="/blog/the-spend-counter-that-went-back-to-zero/" aria-label="Read: The Spend Counter That Went Back to Zero">Read →</a>
</div>
</div>
</article>
<article class="card t-internals">
<a class="thumb t-internals" href="/blog/the-newline-that-silenced-windows-agents/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/the-newline-that-silenced-windows-agents/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-08-19">Aug 19, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>4 min</span>
</div>
<h3><a href="/blog/the-newline-that-silenced-windows-agents/">The Newline That Silenced Every Windows Agent</a></h3>
<p class="dek">A cmd.exe parsing rule from the 1980s meant Windows agents received exactly one line of their multi-line startup protocol — and nothing errored. The anatomy of our worst silent failure, and the fix.</p>
<div class="foot">
<span class="tag kind">Internals</span>
<a class="more" href="/blog/the-newline-that-silenced-windows-agents/" aria-label="Read: The Newline That Silenced Every Windows Agent">Read →</a>
</div>
</div>
</article>
<article class="card t-internals">
<a class="thumb t-internals" href="/blog/why-our-auto-update-never-ran/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/why-our-auto-update-never-ran/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-08-08">Aug 8, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>5 min</span>
</div>
<h3><a href="/blog/why-our-auto-update-never-ran/">Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace</a></h3>
<p class="dek">Munder Difflin shipped auto-update in v0.3.4 and it silently never worked in a single packaged build. The cause was one destructuring assignment across the CommonJS/ESM boundary — and a catch block that threw the evidence away. Here's how we found it, and what v0.3.7 changes.</p>
<div class="foot">
<span class="tag kind">Internals</span>
<a class="more" href="/blog/why-our-auto-update-never-ran/" aria-label="Read: Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace">Read →</a>
</div>
</div>
</article>
</div>
</section>
</footer>
</article>
</main>
<footer class="site-foot">
<div class="wrap">
<div class="foot-top">
<a class="foot-brand brand" href="https://munderdiffl.in" aria-label="Munder Difflin home">
<img class="brand-logo" src="https://munderdiffl.in/logo.png" width="1318" height="840" alt="Munder Difflin, Inc. — Multi-Agent Harness" />
</a>
<div class="foot-links">
<a href="/blog/">Latest</a>
<a href="/blog/topics/">Topics</a>
<a href="/blog/about/">About</a>
<a href="https://munderdiffl.in/blog/feed.xml">RSS</a>
<a href="https://github.com/chaitanyagiri/munder-difflin">GitHub</a>
<a href="https://munderdiffl.in">munderdiffl.in ↗</a>
</div>
</div>
<div class="foot-meta">
© 2026 Munder Difflin · Local-first · MIT-licensed ·
Built on <a href="https://munderdiffl.in">Electron, React, Pixi.js, xterm.js & 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>