<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tool Scheduling on ByF (BaiFan) · Daily Deep Think</title><link>https://blog.baifan.site/en/tags/tool-scheduling/</link><description>Recent content in Tool Scheduling 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>Sun, 04 Oct 2026 22:06:00 +0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/tool-scheduling/index.xml" rel="self" type="application/rss+xml"/><item><title>Pi's CodeMode vs. DeepSeek Harness PTC Mode</title><link>https://blog.baifan.site/en/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/en/pi-codemode-vs-deepseek-harness-ptc/</guid><description>&lt;p&gt;When designing runtime architectures for modern coding agents, the traditional single-step tool-calling loop hits a hard engineering ceiling. In multi-file refactoring and cross-module codebase exploration, discrete JSON RPC turn-taking leads to interactive round-trip explosions and runaway context bloating. It also fails to express asynchronous dependencies between tool invocations. To overcome this scheduling bottleneck, Pi Coding Agent&amp;rsquo;s CodeMode and DeepSeek Harness&amp;rsquo;s (CLI: &lt;code&gt;dsh&lt;/code&gt;) Programmatic Tool Calling (PTC) mode represent two divergent code-execution paradigms.&lt;/p&gt;</description></item></channel></rss>