dsh-deep-ptc-mode 1.8.0 → 1.8.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,20 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.8.2 — 2026-11-07
4
+
5
+ - 修正 npm 元数据:描述控制在 registry 的 255 字符以内,避免被截断;仅描述变更,不改变行为。
6
+
7
+ - Keep the npm description within the registry's 255-character limit so it is not truncated. Description only; no behavior change.
8
+ ## 1.8.1 — 2026-11-07
9
+
10
+ - 重写简介与 README:以“五个基本问题”为主线,再梳理“一切皆插件”的六项能力(动态预设/工具读取、创造模式、dsh-go 界面控制、多环境、外部插件工具/工作流适配、Skill 与工具读取)。
11
+ - 更新 npm 描述与 GitHub About;不承诺适配所有第三方插件,dsh-ops 为已专门测试的场景,其他插件走同一接口。
12
+ - 仅简介与文档变更,不改变运行时行为。
13
+
14
+ - Rewrite the introduction and README around the five basic problems, followed by the six “everything is a plugin” capabilities (dynamic preset/tool loading, creative mode, dsh-go screen control, multi-shell support, external tool/workflow adaptation, and leaner skill/tool loading).
15
+ - Update the npm description and GitHub About. No promise to fit every third-party plugin: dsh-ops is the specifically tested case and other plugins use the same interface.
16
+ - Documentation and description only; no runtime behavior change.
17
+
3
18
  ## 1.8.0 — 2026-11-07
4
19
 
5
20
  - 会话级 preset 身份兼容,两次尝试:不限制预设名称的外部插件拿原生 `deep-ptc`(第一层,直接可用);限制预设名称、列表里没有 `deep-ptc` 的插件拿基座 `ptc`(第二层,对包含 `ptc` 的列表必定通过)。显式支持 `deep-ptc` 的插件也拿原生。宿主内部(子代理 header、定时任务、注册表自身)保持精确 id,不影响继承与调度。
package/README.md CHANGED
@@ -1,30 +1,56 @@
1
1
  # Deep PTC mode
2
2
 
3
- [中文](README.zh.md) · MIT · **1.8.0**
3
+ [中文](README.zh.md) · MIT · **1.8.2**
4
4
 
5
5
  [1.7.3 实测汇总 / Test summary](TEST_REPORT.md)
6
- **Let plugins cooperate. Keep current official PTC tools as the fallback. Stay interruptible while work runs.**
6
+ **Reports. Asks. Stays awake. Plans. Stays reachable.**
7
+ **Five basics, one mode; everything is a plugin, with the official preset always as the fallback.**
7
8
 
8
- Deep PTC is a DeepSeek Harness agent preset built for a plugin ecosystem. It first looks for a suitable tool among the available external plugins, then continues with the running host’s dynamically discovered official PTC capability when no enhancement fits or a provider fails. Multiple plugins can contribute different parts of a task, each using its own schemas, discovery and result contracts. Deep PTC adds no task tools of its own.
9
+ Deep PTC is not another tool bundle. It is a DeepSeek Harness agent preset built around five basic problems in model work: working silently without reporting, guessing instead of asking when intent is ambiguous, sleeping and becoming unreachable during a task, not planning or not showing the plan, and not using the original PTC preset's concise context plus its unlimited-token prompt.
9
10
 
10
- Deep PTC 1.8.0 adds **session-scoped preset identity**: an external plugin that does not restrict preset names sees the native `deep-ptc`, a plugin that restricts them gets the base `ptc` (or `cordis` for a creative-mode row mounted by the plugin lab), and host internals keep the exact id. Normal PTC and creative sessions are untouched.
11
+ Those five are handled first by prompts and code. On top of that, following DSH's “everything is a plugin” philosophy, the preset adds dynamic preset/tool loading, creative-mode tools for building DSH plugins, dsh-go screen-control adaptation, wider shell support, external plugin tool/workflow adaptation, and a leaner skill/tool loading flow. Deep PTC adds no task tools itself; it provides the interface that lets a plugin's new tools be discovered, loaded and called.
11
12
 
12
- The same working rules remain: use the model's capability thoroughly, move long commands into managed background jobs, respond to your messages while work runs, plan by task size, clarify intent, and execute in your selected WSL / PowerShell / Zsh / Bash environment.
13
+ Not every third-party plugin is guaranteed to fit: the interface is verified for dsh-ops and reused by other plugins, but a plugin still has to support the installed host and publish its tools under the expected contract.
13
14
 
14
- ## A mode for “everything is a plugin”
15
+ ## Five basic problems
15
16
 
16
- Compatibility has two directions: follow the installed official PTC composition as it evolves, and cooperate with external tool plugins instead of assuming a fixed tool inventory. This follows DSH's composable, “everything is a plugin” approach: the mode supplies working rules and recovery guidance, while tool providers retain ownership of their capabilities.
17
+ | # | Problem | What Deep PTC does |
18
+ | --- | --- | --- |
19
+ | 1 | **Working silently without reporting** | One sentence before every `run_code`; a longer update at milestones; never more than two or three silent tool calls; a short final result with failed tools and providers. |
20
+ | 2 | **Guessing instead of asking** | Meaning belongs to the user, facts to the tools: ask one to three questions with options when names, targets, routes, scope or acceptance criteria are unclear; look up inspectable facts yourself. The user's answer wins. |
21
+ | 3 | **Sleeping or becoming unreachable** | Enforced in code: foreground waits move to the background after 30 s; a user message hands the waiting command to the background within about 2 s; foreground sleeps over 5 s are refused; job completion wakes the model. |
22
+ | 4 | **No plan, or an invisible plan** | Plan by estimated size: act silently under 5 minutes; show the plan and start without approval for 5–20 minutes; show it and wait for approval over 20 minutes. Re-plan when the estimate moves up; the user can redirect at any step. |
23
+ | 5 | **Not using the concise context and unlimited-token prompt** | Derive from the live official PTC composition, keep the tool catalog compact and load full schemas on demand, and state that this mode spends its token budget on reads, searches, commands and checks rather than rationing them. The prompt does not change billing or the real token limit. |
17
24
 
18
- | Responsibility | How the plugins cooperate |
19
- | --- | --- |
20
- | External capabilities first | Search the available plugin capabilities for the needed function; use a provider's own discovery/SDK loader when appropriate |
21
- | Multiple providers together | Use different plugins for different operations in the same task; no single enhancement plugin is required |
22
- | Current official fallback | Continue through the installed Harness's official PTC tools if an enhancement is absent or fails |
23
- | Shared task discipline | Preserve interruptible background work, clarification, planning and the selected execution environment |
25
+ ## Built for “everything is a plugin”
26
+
27
+ ### 1. Dynamic preset and tool loading
28
+
29
+ Read the running host's official PTC declaration and inherit its rows as they are; only the persona, execution group, reachability guard, job wrapper and question wrapper are replaced. Rebuild only when the declaration or settings change (checked every five seconds); fall back to the bundled snapshot with a warning if it cannot be loaded, parsed or derived. An official upgrade can add tools without a release of this preset; existing sessions are not forcibly switched.
30
+
31
+ ### 2. Flexible creative-mode tools
32
+
33
+ The plugin lab is off by default. When enabled, it reads the host's creative preset and appends only the rows that mode adds, specifically for building DSH plugins. Module names stay as declared; skill directories resolve relative to the creative preset file. Lab packages stay in process memory, are not written to the repository, shipped presets, desktop composition or this plugin's source, and run only through the host's existing approval. Loading reads the roster and documents only; it never calls `composedPreset`.
34
+
35
+ ### 3. dsh-go screen-control adaptation
36
+
37
+ Screen-control tools stay in the initial PTC SDK, are not moved on demand, and are not quarantined on failure. Recognition uses the tool's own `resident` mark, `dsh-go/view`, its name or its provider mark. Deep PTC does not claim dsh-go's slots or replace its settings form; if the tool-state projection fails, that control stays empty without tearing down the composer or screen-control UI.
38
+
39
+ ### 4. Wider execution environments
24
40
 
25
- An extension must publish into the `deep-ptc` scope and support the installed host. Keep official fallbacks visible in the provider's own configuration where supported. This is cooperative task-level selection, not a guarantee that every plugin or replacement executor is interchangeable. OPS is one possible provider, not a bundled dependency or a completed integration claim.
41
+ WSL Bash, PowerShell (including discovered 5.1 and 7 executables), Zsh and native Bash are supported. The choice applies to this preset only and does not change the global shell; sandbox, approval and process management stay official. WSL currently requires the host-authorized `danger-full-access` mode.
26
42
 
27
- The official fallback retains the 1.6.1 derivation mechanism: the plugin reads the running host’s PTC declaration and checks for changes every five seconds; only changed declarations or this plugin’s settings rebuild the preset and follows its module names and configuration. The bundled snapshot is used only if loading, parsing or derivation fails, with a warning. Reload after an official upgrade and use a new preset revision; existing sessions are not forcibly switched. DSH support starts at the installed desktop release candidate, `>=0.2.2-rc.1`. Only RC builds are supported; alpha builds are not. There is no upper bound on later release candidates, and a newer RC still needs a host-interface check.
43
+ ### 5. External plugin tool/workflow adaptation (dsh-ops tested)
44
+
45
+ This is the core interface: external plugins publish tools under their own contract; Deep PTC discovers them, loads them on demand, quarantines failures per conversation and falls back to official PTC. Extensions must support the installed host and publish into the `deep-ptc` scope; Deep PTC does not depend on any specific plugin or replace the executor.
46
+
47
+ **dsh-ops is specifically tested.** Its gate recognises only `minimal/standard/ptc/cordis`. Deep PTC first offers the native `deep-ptc`; when it detects that the plugin restricts preset names, it returns the base id the plugin accepts — `ptc` (or `cordis` for a creative row) — while host internals keep the exact `deep-ptc`. dsh-ops therefore needs no change for its new tools to be discovered and called; other plugins use the same interface, judged by their own packages. Unattributed tools are not quarantined; only a positively attributed external provider can be, and official tools are never quarantined.
48
+
49
+ ### 6. Leaner skill and tool loading
50
+
51
+ Search summaries first, then load full schemas: six entries per page by default (maximum eight), up to six schemas within a 16 KB budget per load, and up to twelve recent selections. Quarantine persists with the conversation: clear unavailability blocks immediately; temporary failures need three in a row and a success clears the count; wrong arguments, denial and normal business failures are not tool failures; one reset clears only the current conversation. Skills load in two stages: discovery reads metadata and invocation permission only; the official `skill` tool loads the body.
52
+
53
+ Three steps: install the plugin → choose an environment under **Settings → Plugins → Deep PTC** → choose **深度PTC模式** in the mode picker for a new task.
28
54
 
29
55
  ## 1.7.2: lightweight, on-demand tool orchestration
30
56
 
@@ -49,20 +75,7 @@ Set `compactToolCatalog: false` under `deep-ptc-settings` to retain the full hos
49
75
 
50
76
  Compaction only changes an untouched SDK section generated by the installed official renderer. Provider-owned/custom SDKs keep their own loaders. Extensions must support the host and publish into `deep-ptc`; this layer does not override hidden tools, authorization or an unloaded whole executor. Actual OPS/online-model end-to-end integration has not been performed.
51
77
 
52
- ## Overview
53
-
54
- Deep PTC targets six common problems in everyday agent work:
55
-
56
- | Problem | What Deep PTC does |
57
- | --- | --- |
58
- | Enhanced tools and presets do not naturally cooperate | Search external plugin capabilities first, combine suitable providers, and recover through the dynamically inherited official PTC baseline |
59
- | The model rations tokens, skipping reads and tests, and quality suffers | The persona states that it works at DeepSeek with an unlimited token budget in this mode: never skip a read, search, command or check to save tokens. Guardrails forbid padding, verbosity and context blow-ups |
60
- | Once work starts, the model sleeps or waits and ignores your messages | Enforced in code: foreground commands move to the background after 30 s, a message from you moves the waiting command to the background at once so the model reads it, and long sleeps are refused; job completion wakes the model (see "Enforced reachability" below) |
61
- | Every task starts the same way regardless of size | Three bands by estimated time: up to 5 minutes, plan internally and act; 5–20 minutes, show the plan and start without approval; over 20 minutes, show the plan and wait for approval |
62
- | It starts before understanding what you meant, then redoes the work | Meaning belongs to you, facts to the tools: unfamiliar names, competing targets or routes, scope and acceptance criteria are asked about (one to three questions with options), never guessed by searching; file locations and current behavior are looked up |
63
- | The command environment is fixed | Choose WSL Bash, PowerShell, Zsh (macOS/Linux) or native Bash in settings; the choice applies to this preset only and leaves the global shell alone |
64
78
 
65
- Three steps: install the plugin → pick an environment under **Settings → Plugins → Deep PTC** → choose **深度PTC模式** in the mode picker for a new task.
66
79
 
67
80
  ## Enforced reachability: no sleeping, always interruptible
68
81
 
@@ -158,10 +171,10 @@ A prompt changes the model's working tendency, not the real token limit or billi
158
171
  Requires Node `>=24` and DSH RC `>=0.2.2-rc.1` (the installed desktop). Alpha builds are not supported. Windows desktop rc.5 was used for real WSL/PowerShell command checks. macOS/Zsh configuration, argv and tool mounting were checked; native macOS execution has not been verified on this Windows host.
159
172
 
160
173
  ```js
161
- plugin_manager({ action: "install_bundle", target: "dsh-deep-ptc-mode@1.8.0" })
174
+ plugin_manager({ action: "install_bundle", target: "dsh-deep-ptc-mode@1.8.2" })
162
175
  // Or from a local checkout or archive:
163
176
  plugin_manager({ action: "install_bundle", target: "C:\\path\\to\\dsh-deep-ptc-mode" })
164
- // Or target: "C:\\path\\to\\dsh-deep-ptc-mode-1.8.0.tgz"
177
+ // Or target: "C:\\path\\to\\dsh-deep-ptc-mode-1.8.2.tgz"
165
178
  ```
166
179
 
167
180
  Repository locator: `github:lishize20040802-rgb/dsh-deep-ptc-mode`. It installs content actually published there; a local upgrade does not publish to GitHub or npm.
package/README.zh.md CHANGED
@@ -1,30 +1,56 @@
1
1
  # 深度 PTC 模式
2
2
 
3
- [English](README.md) · MIT · 当前版本:**1.8.0**
3
+ [English](README.md) · MIT · 当前版本:**1.8.2**
4
4
 
5
5
  [1.7.3 实测汇总 / Test summary](TEST_REPORT.md)
6
- **让插件协作,让当前官方 PTC 工具兜底,让任务始终可沟通。**
6
+ **会汇报,先提问,不休眠,有计划,能插话。**
7
+ **五个基本问题,一套模式;一切皆插件,官方始终兜底。**
7
8
 
8
- 深度 PTC 是面向插件生态的 DeepSeek Harness Agent 模式(preset):优先在当前可用的外部插件中寻找同功能工具,没有合适能力或插件工具故障时,再用当前官方 PTC 的工具继续完成任务。多个插件可以分工完成同一个任务,各自保留原有参数、发现方式和结果契约;深度 PTC 本身不提供新的任务工具。
9
+ 深度 PTC 不是又一个工具包,而是针对模型执行任务时五个基本问题设计的 DeepSeek Harness Agent 模式:闷头干活不汇报、有歧义先猜不问、跑起来就休眠失联、不做计划或计划不可见、以及没有用好原 PTC 的简洁上下文与 unlimited token 提示词。
9
10
 
10
- 1.8.0 增加**会话级预设身份兼容**:不限制预设名称的外部插件看到原生 `deep-ptc`,限制预设名称的插件拿到基座 `ptc`(实验台挂入的创造模式行可拿到 `cordis`),宿主内部保持精确 id。普通 PTC 会话与创造模式会话不受影响。
11
+ 这五个问题先由提示词和代码一起解决;在此基础上,再按官方“一切皆插件”的理念,把预设与工具动态读取、创造模式、dsh-go 界面控制、多 shell 环境、外部插件工具/工作流适配、Skill 与工具读取流程逐项接进来。深度 PTC 本身不提供新的任务工具,它提供的是让外部插件的新工具能被识别、加载、调用的那层接口。
11
12
 
12
- 原有的工作特点完整保留:把模型能力用满,长命令交给后台 job,运行中随时回应你的插话,按任务大小规划,意图不清先问,并在你选择的 WSL / PowerShell / Zsh / Bash 环境执行。
13
+ 不承诺适配所有第三方插件:接口对已测试场景(dsh-ops)负责,其他插件走同一接口,具体仍取决于插件自身是否支持当前宿主、是否按契约发布工具。
13
14
 
14
- ## 为「一切皆插件」的协作方式而设计
15
+ ## 五个基本问题
15
16
 
16
- 兼容性有两个方向:向官方,跟随当前安装版本的 PTC 组成演进;向外部,允许工具插件参与任务,不把工具清单固定下来。这更贴合 DSH「一切皆插件」的组合理念:模式负责工作规则和故障恢复指引,工具能力由各自的插件负责。
17
+ | # | 基本问题 | 深度 PTC 的做法 |
18
+ | --- | --- | --- |
19
+ | 1 | **闷头干活不汇报** | 每次 `run_code` 前一句话说明要做什么;里程碑稍长汇报;连续两三个工具调用必须出声;任务结束简短列出结果、失败工具与来源。 |
20
+ | 2 | **有歧义先猜不问** | 意思归用户、事实归工具:不认识的名称、多个可能目标、技术路线、范围和验收标准不确定时,先问 1–3 个带选项的问题,推荐项在前;可检查的事实自己查。你的回答优先于模型推断。 |
21
+ | 3 | **执行中休眠、失联** | 由代码强制:前台等待超过 30 秒自动转后台且不杀命令;你发消息时正在等待的命令约 2 秒内转后台,模型立刻看到消息;前台超过 5 秒的 sleep/Start-Sleep 直接拒绝;job 完成自动唤醒模型。 |
22
+ | 4 | **不做计划或计划不可见** | 按预计耗时分档:≤5 分钟内部计划直接做;5–20 分钟先展示计划,不等审批就执行;>20 分钟先给计划、等你批准。估计升档时重新说明;你可以在任一步调整方向,显式 plan mode 优先。 |
23
+ | 5 | **没用好简洁上下文与 unlimited token** | 预设从官方 PTC 现场派生,继承官方简洁组合;工具目录精简、完整 schema 按需加载,避免上下文被工具定义撑爆;人设写明本模式 token 预算无限、把预算花在读取/搜索/命令/验证上,同时禁止注水和啰嗦。提示词不改变实际计费或 token 上限。 |
17
24
 
18
- | 分工 | 如何协作 |
19
- | --- | --- |
20
- | 外部能力优先 | 先按功能寻找可用的插件工具,需要时使用该插件自己的发现/SDK 加载接口 |
21
- | 多插件相互配合 | 同一任务的不同步骤可以交给不同插件,不要求只绑定某一个增强插件 |
22
- | 当前官方工具兜底 | 增强能力缺失或故障时,回到当前安装 Harness 的官方 PTC 能力 |
23
- | 工作方式保持一致 | 保留后台运行、随时插话、澄清、任务规划和所选执行环境 |
25
+ ## 按“一切皆插件”做的进一步能力
26
+
27
+ ### 1. 预设与工具的动态读取
28
+
29
+ 运行时读取宿主正在发布的官方 PTC 声明,官方行原样继承;仅替换 persona、执行组、可达性守卫、job 与提问包装。每 5 秒检测声明变化,仅在声明或配置变化时重建;声明读不到/解析失败才用随包快照并记录日志。官方升级后无需为本模式发版即可继承新工具;新建会话使用新版,已有会话不强制切换。
30
+
31
+ ### 2. 创造模式工具的灵活加入
32
+
33
+ 插件实验台默认关闭;打开后读取宿主正在发布的创造模式,只追加相对 PTC 多出来的行,专门负责 DSH 本身的插件创造。模块名保持创造模式原文,官方改名时跟着宿主走;技能目录按创造模式文件位置解析。实验台包只留在本进程内存,不写仓库、已发布预设、桌面组合或插件源码,经宿主原有批准后运行。加载只读预设清单和文档,不调用 `composedPreset`。
34
+
35
+ ### 3. 适配 dsh-go 的界面控制
36
+
37
+ 屏幕控制工具留在初始 PTC SDK,不收进按需目录,失败后也不隔离。识别依据是工具自己的 `resident` 标记、`dsh-go/view`、名称或提供者标记;不声明 dsh-go 自己的槽位,也不替换它的设置表单。工具状态控件投影失败时留空,不拆输入区或屏幕控制界面。
38
+
39
+ ### 4. 扩展不同环境的适应范围
40
+
41
+ 支持 WSL Bash、PowerShell(含 5.1 与 7 的可执行文件选择)、Zsh、原生 Bash。只对本模式生效,不改全局 shell;沙箱、审批和进程管理仍用官方实现。WSL 目前仅支持宿主已授权的 `danger-full-access`。
24
42
 
25
- 外部插件需支持当前宿主,并在 `deep-ptc` 的作用域中发布工具;支持保留官方工具的插件,应在自身配置中保留兜底能力。这是任务级的合作选择机制,不代表所有插件或整个替换执行器都能直接互换。OPS 可以作为其中一个提供者,不是内置依赖,也不表示已经完成 OPS 的实际联调。
43
+ ### 5. 增强外部插件工具/工作流的适配(dsh-ops 已专测)
26
44
 
27
- 官方兜底沿用 1.6.1 的动态派生机制:自动读取实际运行宿主的官方 PTC 声明;每 5 秒检测声明变化,仅在声明或本插件配置变化时重建预设,工具模块和配置跟随该声明;仅在声明无法读取、解析或派生时使用随包快照并记录日志。官方升级后需重载并创建使用新版预设的会话,既有会话不被强制切换。最低支持当前桌面端 DSH RC `>=0.2.2-rc.1`。只支持 RC,不支持 alpha。不设 RC 上限;更高的 RC 仍需验证宿主接口。
45
+ 这是深度 PTC 的核心接口:外部插件按自己的契约发布工具,深度 PTC 负责发现、按需加载、隔离故障,并在失败时回到官方 PTC。外部插件需支持当前宿主,并在 `deep-ptc` 作用域中发布工具;深度 PTC 不把任何插件写成依赖,也不替换执行器。
46
+
47
+ **dsh-ops 专门测试**:它在工具门控里只认 `minimal/standard/ptc/cordis`;深度 PTC 先给原生 `deep-ptc`,识别到它限制预设名后,按它实际接受的基座 id 返回 `ptc`(创造模式行可用 `cordis`);宿主内部仍保持精确 `deep-ptc`。结果是 dsh-ops 不需要改造,它的新工具就能在深度 PTC 会话里被识别和调用;其他外部插件走同一接口,按包内容判断。未归属工具不隔离;只有能明确归属的外部提供者才可能被隔离;官方工具永不禁用。
48
+
49
+ ### 6. Skill 与工具的读取流程优化
50
+
51
+ 先搜摘要,再加载完整 schema:默认每页 6 项、最多 8 项;完整 schema 每次最多 6 个、总预算 16 KB;最多保留 12 个近期选择。故障按对话隔离:明确不可用立即禁用;临时错误连续 3 次才禁用,成功一次清零;参数错误、权限拒绝、业务失败不算故障;一键重载只清当前对话。Skill 两阶段:目录只查元数据与权限,正文交给官方 `skill` 工具,检索不读正文。
52
+
53
+ 使用三步:安装插件 → 在 **设置 → 插件 → 深度 PTC** 里选执行环境 → 新建任务时在模式选择器里选「深度PTC模式」。
28
54
 
29
55
  ## 1.7.2:轻量、按需、可恢复的工具调用层
30
56
 
@@ -49,20 +75,7 @@ const skills = await tools.deep_ptc_tools({ action: 'skills', query: 'build test
49
75
 
50
76
  精简只作用于当前官方渲染器生成且未被其他插件改写的 SDK 段;插件自建 SDK 继续由其自身加载器管理。外部插件仍须支持当前宿主并在 `deep-ptc` 作用域发布工具;本层不会绕过工具隐藏、授权或接管被卸载的整个执行器。未进行实际 OPS/在线模型端到端评测。
51
77
 
52
- ## 简介
53
78
 
54
- 日常 Agent 工作中常见六个问题,深度 PTC 模式逐一针对:
55
-
56
- | 你遇到的问题 | 深度PTC模式的做法 |
57
- | --- | --- |
58
- | 增强工具与自定义模式难以自然配合 | 外部插件能力优先,多提供者按功能协作,故障时使用动态继承的官方 PTC 基线恢复任务 |
59
- | 模型总想帮你省 token,少查、少测,结果质量打折 | 人设写明「在深度求索工作,本模式 token 预算无限,把预算花在工作上」:不为省 token 跳过读取、搜索、命令或验证;同时禁止注水、啰嗦和撑爆上下文 |
60
- | 任务跑起来后模型在 sleep 或干等,你发消息它不理 | 由代码强制:前台命令超过 30 秒自动转后台,你一发消息正在等的命令立即转后台、模型马上看到消息,长 sleep 直接拒绝;job 完成会自动唤醒模型(详见下方「代码层强制」) |
61
- | 不管大小任务都同一种开工方式 | 按预计耗时分三档:5 分钟内自己计划直接做;5–20 分钟先告诉你计划、不等审批就执行;超过 20 分钟先给计划、等你批准 |
62
- | 意思没弄懂就开干,最后返工 | 意思归用户,事实归工具:不认识的名称、多个可能目标、技术路线、范围和验收标准不确定时先问你(1–3 个带选项的问题),不靠搜索去猜你的意图;文件位置、当前行为这类事实自己查 |
63
- | 命令环境固定,Windows 上想用 WSL、Mac 上想用 Zsh 都不方便 | 设置里可选 WSL Bash、PowerShell、Zsh(macOS/Linux)或原生 Bash,只对本模式生效,不改全局 shell |
64
-
65
- 使用三步:安装插件 → 在 **设置 → 插件 → 深度 PTC** 里选执行环境 → 新建任务时在模式选择器里选「深度PTC模式」。
66
79
 
67
80
  ## 代码层强制:不休眠、随时可插话
68
81
 
@@ -160,10 +173,10 @@ WSL 命令使用 Linux/POSIX 语法;文件工具和 `workdir` 仍用 Windows
160
173
  本地目录或构建产物可通过插件管理器安装:
161
174
 
162
175
  ```js
163
- plugin_manager({ action: "install_bundle", target: "dsh-deep-ptc-mode@1.8.0" })
176
+ plugin_manager({ action: "install_bundle", target: "dsh-deep-ptc-mode@1.8.2" })
164
177
  // 也可从本地目录或安装包安装:
165
178
  plugin_manager({ action: "install_bundle", target: "C:\\path\\to\\dsh-deep-ptc-mode" })
166
- // 或 target: "C:\\path\\to\\dsh-deep-ptc-mode-1.8.0.tgz"
179
+ // 或 target: "C:\\path\\to\\dsh-deep-ptc-mode-1.8.2.tgz"
167
180
  ```
168
181
 
169
182
  GitHub 地址:`github:lishize20040802-rgb/dsh-deep-ptc-mode`。该地址安装远端实际内容;本地升级不会自动发布到 GitHub/npm。
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "dsh-deep-ptc-mode",
3
- "version": "1.8.0",
4
- "description": "Lightweight adaptive Deep PTC: session-scoped preset identity (native deep-ptc, base ptc, creative cordis fallback), live host presets, plugin cooperation and interruptible jobs. / 轻量自适配深度 PTC:会话级预设身份兼容(原生 deep-ptc、基座 ptc、创造模式 cordis 兜底)、动态宿主预设、插件协作与后台可插话。",
3
+ "version": "1.8.2",
4
+ "description": "Agent mode for DSH: reporting, asking, reachability, planning, budget use. Plugin-first, official PTC fallback, dynamic tools, creative lab, dsh-go, multi-shell, dsh-ops-tested. / 面向 DSH:汇报、先问、休眠、计划、预算;插件优先、官方兜底,动态工具、创造模式、dsh-go、多 shell 与外部工具(dsh-ops 已测)。",
5
5
  "type": "module",
6
6
  "keywords": [
7
7
  "dsh-plugin",