dsh-turbo

使用方法

1. 打开任意会话，在输入框旁点击 Turbo。
2. 开启后拖动两档滑块：极速 控制 Token 成本，极限 允许更多并行开销来换取更短等待。
3. 点击旁边的 ? 可以看到效果说明和同题测试建议。
4. 再次点击 Turbo 即可恢复默认模式；正在执行的请求不会被中途改写，新模式从下一次组装请求开始生效。

极限 只会加速能并行拆分的任务，不保证所有任务都更快；串行依赖、网络瓶颈和模型排队仍可能成为限制。

健康检查：

Invoke-RestMethod http://127.0.0.1:19387/api/dsh-turbo/health | ConvertTo-Json -Depth 5

卸载：

powershell -ExecutionPolicy Bypass -File scripts/uninstall.ps1 -Profile desktop

Configuration

Key	Default	Meaning
sectionOrder	700	Prompt section placement (unowned gap between plan/team policy and tool guidance).
reasoningEffort	inherit	Request-level reasoning while Turbo is ON: off/minimal/low/medium/high/max, or inherit to leave the route alone. The route decides what exists — the shipped DeepSeek Messages adapter accepts only off/low/high/max, so minimal is refused. A refusal disables the lever for that Agent and retries the turn rather than failing it, and the capability row says so.
maxReasoningEffort	low	Request-level effort for the Max gear. Max spends more through parallel breadth, while keeping per-request deliberation latency low.
evidenceLog	true	Append one JSON line per applied step to evidence.jsonl.
storageDir	dsh-turbo	Subdirectory of $DSH_HOME/storages. Remove evidenceLog to go without a log.
defaultMode	default	Mode a never-toggled Session reads as. turbo makes Turbo the deployment default; the benchmark harness uses it to pick an arm.

Unknown keys are rejected at load so a typo fails loudly instead of silently doing nothing.

Where the policy applies: the Host half has no hard service dependency, so the same bundle works in Web/Desktop, in the headless one-shot runner (dsh --profile headless "…"), and in SDK/ACP profiles. Only the HTTP bridge and the composer toggle need the Web surface; everywhere else the policy, metrics and evidence still run and the capability list says http-bridge: unavailable.

---