<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Context Engineering on 卓琪的开发笔记</title>
    <link>https://zhuoqidev.com/tags/context-engineering/</link>
    <description>Recent content in Context Engineering on 卓琪的开发笔记</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <copyright>© 2026 Liu ZhuoQi</copyright>
    <lastBuildDate>Thu, 30 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://zhuoqidev.com/tags/context-engineering/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Claude&#39;s Tool Calling Paradigm Shift: A Deep Dive into Programmatic Tool Calling and Dynamic Filtering</title>
      <link>https://zhuoqidev.com/en/posts/claude-programmatic-tool-calling-dynamic-filter/</link>
      <pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://zhuoqidev.com/en/posts/claude-programmatic-tool-calling-dynamic-filter/</guid>
      <description>&lt;div class=&#34;lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl&#34;&gt;&#xA;  The important change is not “two more tool features.” It is the movement of multi-step orchestration into a code-execution environment, with only a compact result returning to model context.&#xA;&lt;/div&gt;&#xA;&#xA;&#xA;&lt;h2 class=&#34;relative group&#34;&gt;Background: The Cost Problem in Agent Tool Calling&#xA;    &lt;div id=&#34;background-the-cost-problem-in-agent-tool-calling&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#background-the-cost-problem-in-agent-tool-calling&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;In traditional agent tool-calling, every tool invocation requires a full cycle of &amp;ldquo;model inference → tool execution → result return → model re-inference.&amp;rdquo; This seemingly natural loop breaks down at scale in three ways:&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>RAG vs LLM Wiki vs Plain Text — A Decision Framework for Agent Long-Term Memory</title>
      <link>https://zhuoqidev.com/en/posts/memory-choice-framework/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://zhuoqidev.com/en/posts/memory-choice-framework/</guid>
      <description>&lt;div class=&#34;lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl&#34;&gt;&#xA;  Every Agent builder hits this question eventually: &lt;em&gt;where do I store user data so the agent remembers it next session?&lt;/em&gt;&#xA;&lt;/div&gt;&#xA;&#xA;&lt;p&gt;Three approaches dominate the landscape: RAG (vector retrieval), LLM Wiki (structured knowledge injection), and plain-text context memory (the CLAUDE.md / Cursor Rules pattern). Each has vocal advocates. But picking wrong is expensive — do RAG too light and it&amp;rsquo;s a noise generator; do plain text too heavy and it&amp;rsquo;s a token incinerator.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
