Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

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-13-deepseek-harness-alpha-2-removes-webruntime-old-overlays-can-stop-connection-startup

Alpha.2 removes webRuntime; old overlays can stop Connection startup. The old webRuntime service no longer mounts. Overlays that inject it can wait indefinitely for that service and prevent required Connection startup. The supported replacement is webStartup; trusted-host reads change and lanAddresses disappears.

Channel: preview-or-beta; alpha-only, not npm latest. Half: defect. Date: 2026-10-09 (first containing tag, alpha.2).

Operator consequence: Replace inject: [webRuntime] with inject: [webStartup], read ctx.webStartup.trustedHosts, remove lanAddresses, and fully restate patched configuration as the guide instructs. Do not infer release inclusion from the guide-directory name. This is the migration cost attached to section 7’s listener improvement.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-deepseek-harness-alpha-2-removes-webruntime-old-overlays-can-stop-connection-startup

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. DeepSeek Harness
    commit2026-10-13-deepseek-harness-alpha-2-removes-webruntime-old-overlays-can-stop-connection-startupgithub.com/deepseek-ai/deepseek-harness/commit/cb9a590c86d90948989247863bd921261bc0350btagged commit file2026-10-13-deepseek-harness-alpha-2-removes-webruntime-old-overlays-can-stop-connection-startupdeepseek-ai/deepseek-harness / docs/upgrade-guide/v0.2.1-alpha.1/web-listener-trust-config/guide.md

Versioned source: run artifact