<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Context Management on ByF (BaiFan) · Daily Deep Think</title><link>https://blog.baifan.site/en/tags/context-management/</link><description>Recent content in Context Management on ByF (BaiFan) · Daily Deep Think</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF (BaiFan))</managingEditor><webMaster>blog@baifan.site (ByF (BaiFan))</webMaster><copyright>CC BY-NC 4.0</copyright><lastBuildDate>Wed, 12 Aug 2026 14:55:05 +0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/context-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Multi-Agent Collaboration: Value From Structure, Not Concurrency</title><link>https://blog.baifan.site/en/multi-agent-technical-core/</link><pubDate>Wed, 12 Aug 2026 14:33:59 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/multi-agent-technical-core/</guid><description>&lt;p&gt;Conclusion first: the value of multi-agent doesn&amp;rsquo;t come from more models; it comes from the right structure. Multi-agent without structure is just more expensive concurrency — burn 2 to 3 times the tokens to watch a group of models nod at each other. Multi-agent with structure is an execution system that can delegate, parallelize, and verify.&lt;/p&gt;&#10;&lt;!-- more --&gt;&#10;&#10;&lt;h2 class="relative group"&gt;Why a Single Agent Fails at Long Tasks&#10; &lt;div id="why-a-single-agent-fails-at-long-tasks" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-a-single-agent-fails-at-long-tasks" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Diagnosis first. A single agent executing complex tasks has five structural defects — blame the execution structure, not the model&amp;rsquo;s intelligence:&lt;/p&gt;</description></item><item><title>The Physical Cost of Context Compression: KV Cache Pressure, Attention Decay, and Lossy Summarization</title><link>https://blog.baifan.site/en/claude-code-context-compression/</link><pubDate>Sat, 23 May 2026 09:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/claude-code-context-compression/</guid><description>&lt;p&gt;Large language models possess no biological memory at the hardware tier; they operate entirely on Key-Value Caches that scale linearly in GPU High-Bandwidth Memory (HBM) alongside attention weight distributions that mathematically dilute as sequence length grows. The notion of long-horizon conversations presented by Claude Code is, at its engineering core, an eviction and compaction pipeline operating within the tight margins of memory capacity and numerical precision, trading away information entropy and prefix caching efficiency.&lt;/p&gt;</description></item><item><title>Claude Skills Progressive Disclosure via MCP: Skill in Anywhere</title><link>https://blog.baifan.site/en/mcp-claude-skills-progressive-disclosure/</link><pubDate>Fri, 26 Dec 2025 14:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/mcp-claude-skills-progressive-disclosure/</guid><description>&lt;figure&gt;&#10; &lt;img&#10; class="my-0 rounded-md"&#10; loading="lazy"&#10; decoding="async"&#10; fetchpriority="auto"&#10; alt="Claude Code Skill in Anywhere"&#10; width="2560"&#10; height="1440"&#10; src="https://blog.baifan.site/pictures/note/claudecodeskills_hu_3030e75c3d7e5ea7.png"&#10; srcset="https://blog.baifan.site/pictures/note/claudecodeskills_hu_3030e75c3d7e5ea7.png 800w,/pictures/note/claudecodeskills_hu_48299efe0d2363fe.png 1280w"&#10; sizes="(min-width: 768px) 50vw, 65vw"&#10; data-zoom-src="https://blog.baifan.site/pictures/note/claudecodeskills.png"&#10; /&gt;&#10; &#10; &lt;figcaption&gt;Claude Code Skill in Anywhere&lt;/figcaption&gt;&#10; &lt;/figure&gt;&#10;&#10;&lt;h1 class="relative group"&gt;Implementing Claude Skills&amp;rsquo; Progressive Disclosure via MCP: Reusing Claude Code Skills Anywhere&#10; &lt;div id="implementing-claude-skills-progressive-disclosure-via-mcp-reusing-claude-code-skills-anywhere" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#implementing-claude-skills-progressive-disclosure-via-mcp-reusing-claude-code-skills-anywhere" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h1&gt;&#10;&#10;&lt;h3 class="relative group"&gt;— A feasible approach to capability encapsulation and dynamic context extension (technical proposal and verification)&#10; &lt;div id="-a-feasible-approach-to-capability-encapsulation-and-dynamic-context-extension-technical-proposal-and-verification" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#-a-feasible-approach-to-capability-encapsulation-and-dynamic-context-extension-technical-proposal-and-verification" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h3&gt;&#10;&#10;&lt;h2 class="relative group"&gt;Preface&#10; &lt;div id="preface" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#preface" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Claude Skills introduced a remarkably advanced concept:&#10;&lt;strong&gt;encapsulating professional knowledge, process standards, and task methods into &amp;ldquo;skill packages&amp;rdquo; that load dynamically, only when a task actually needs them.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>