Evidence record / deepseek-harness
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-10-24-deepseek-harness-main-replaces-tools-configuration-with-explicit-executor-plugins
Main replaces tools configuration with explicit executor plugins. Main rejects removed tools.mode and tools.maxParallelSubCalls fields, moves the parallel-subcall limit to the PTC executor, and stops reading DSH_TOOLS_MODE. Native and PTC execution require explicit executor plugins; shipped profiles mount them, while custom compositions must do so. Invalid executor configuration or a missing required runtime provider can stop startup. The guide’s rc.2 directory name is not evidence of publication in rc.2 or rc.3.
Channel: main-unreleased. Half: both. Date: 2026-10-21.
Operator consequence: When testing main, migrate custom compositions, environment selectors and extension imports together, then confirm tool results reach the saved session. An explicit execution component offers a cleaner composition seam but adds migration work; no current rc requires this main-only migration.
Receipt
Finding metadata
Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0
Finding ID: 2026-10-24-deepseek-harness-main-replaces-tools-configuration-with-explicit-executor-plugins
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-24-deepseek-harness-main-replaces-tools-configuration-with-explicit-executor-pluginsgithub.com/deepseek-ai/deepseek-harness/commit/1c6c5584325b3325cd2d87a7da5877d6794a8203tagged commit file2026-10-24-deepseek-harness-main-replaces-tools-configuration-with-explicit-executor-pluginsdeepseek-ai/deepseek-harness / docs/upgrade-guide/v0.2.1-rc.2/tool-executor-plugins/guide.md
Versioned source: run artifact