Upstream Ships v0.1.2-alpha.1: Code Mode Becomes PTC Mode, Public WebFetch On by Default

On 2026-08-27 upstream published v0.1.2-alpha.1, the first release since 0.1.1-rc.2 (2026-08-21). Most of it is a wide interface-polish and performance batch, but the Chores section carries several changes that every deployment — and every plugin author — should actually read.

Code Mode is now PTC Mode

One line in the Chores section: Code Mode is renamed to PTC mode, and existing conversation records remain readable. The notes do not expand the acronym and do not state a motive, and this article will not invent either. What is observable: the rename went in through a dedicated rename worktree (branch worktree/ptc-rename-base, merged the same day the release was published), and same-day commits swept the remaining code-mode phrasing out of the docs. Ecosystem prose that still says Code Mode — plugin READMEs, older tutorials — now lags the upstream vocabulary.

Defaults that changed under you

• Public WebFetch ships enabled by default, with built-in SSRF protection and no per-request approval for public network access.
• Accessing the Web UI over a network now requires the one-time token in the launch URL.
• Official DeepSeek adapter requests include the enabled plugins’ package names and versions; configuration can turn this off. A separate opt-in incremental session-log upload defaults to off.
• The safety notice was updated to state the project has not been security-audited and that sandboxing, approvals, and permissions do not guarantee isolation. SAFETY.md goes further: do not treat DSH as production-ready, and do not rely on it as the sole security control for untrusted workloads.

For plugin authors: ApiProxy is gone

The legacy ApiProxy interface completed its migration to the @Remote gateway and was removed — code still calling ApiProxy has to move. The notes also fold application launches (Python SDK and ACP modes included) into dsh Profiles, and PTC Mode SDK features now stay inside run_code instead of being exposed as directly callable tools.

Everything else, briefly

Exact per-answer token usage in the conversation stream; subagent provider, model, and reasoning-effort selection within configured authorization; third-party UI languages; a Windows x64 Python SDK runtime; completed ACP support for session controls, model settings, MCP, permissions, and cancellation; provider sign-in controls that plugins can add to the Models settings page; syntax highlighting that keeps running while code blocks stream; images from users, assistants, and tool results shown in Trajectory. The long list is in the release notes.

Still pre-release channel: all five published GitHub releases, this one included, are flagged prerelease. Live repo metadata stays in the site’s build-time snapshot and stats page — this article cites no point-in-time numbers.