<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Harness on ByF (BaiFan) · 每日深度思考</title>
    <link>https://blog.baifan.site/tags/harness/</link>
    <description>Recent content in Harness on ByF (BaiFan) · 每日深度思考</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-cn</language>
    <managingEditor>blog@baifan.site (ByF (BaiFan))</managingEditor>
    <webMaster>blog@baifan.site (ByF (BaiFan))</webMaster>
    <copyright>CC BY-NC 4.0</copyright>
    <lastBuildDate>Sun, 04 Oct 2026 22:06:00 +0800</lastBuildDate><atom:link href="https://blog.baifan.site/tags/harness/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Pi 的 CodeMode 对比 DeepSeek Harness 的 PTC 模式</title>
      <link>https://blog.baifan.site/pi-codemode-vs-deepseek-harness-ptc/</link>
      <pubDate>Sun, 04 Oct 2026 22:06:00 +0800</pubDate>
      <author>blog@baifan.site (ByF (BaiFan))</author>
      <guid>https://blog.baifan.site/pi-codemode-vs-deepseek-harness-ptc/</guid>
      <description>&lt;p&gt;在构建代码智能体（Coding Agent）的运行时架构时，传统的单步工具调用（Tool-Calling Loop）正在遭遇工程瓶颈：面对多文件重构与跨模块分析，单步 JSON RPC 往返导致交互轮次爆炸与上下文急剧膨胀，且无法高效表达工具间的异步依赖。为了突破这一调度天花板，Pi Coding Agent 的 CodeMode 与 DeepSeek Harness（CLI: dsh）的 PTC（Programmatic Tool Calling，编程式工具调用）模式给出了两条截然不同的代码执行路线。&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
