v0.37.10

One setup bar on every setup screen

The console's setup screens now share one bar, as on the hosted service. Tasks · Settings sit at the bar's right end with their icons, on the setup page, on the page that builds a new setup, and on the bar shown while a setup loads, so the tabs stay in one place from the first build onward. Settings › Agent harness starts with the setup's Harness ID and its Copy button, the bar's action reads "Connect your app", and Duplicate sits beside Delete setup. On narrow screens the tabs move to their own row at 860 px and under, share it equally at 600 px and under, and the bar's actions become icons at 480 px and under (#611).

Two smaller fixes come with it. A setup created through the API with its base named by its backend ("base": "claude") shows that base's name and mark. A Start demo picked before the list of agent harnesses has loaded now takes its own harness and model once the list arrives, instead of staying on Auto.

DeepSeek Harness model calls go through the runner's relay

The DeepSeek Harness ran a relay of its own inside its driver, which held the provider key and lacked most of what the runner's relay does. Its model calls now go through the runner's relay like every other agent harness's, and the key never enters the driver's process. That brings the dsh base the runner relay's repairs and its answer when a provider fails: a refused, dropped or timed-out connection now ends the turn with an error instead of a dead connection. Its turns now record the model that served them and their usage. A provider that takes no reasoning_effort gets the request again without it, including an OpenAI-compatible server that refuses the field in its own words.

Measured again on the release candidate, each on its own connection: Anthropic, Google, OpenAI and Azure all pass the five matrix scenarios, and a deck conversation that changes model family on every turn passes 5 of 5. Thanks to @yuesu0202 (#597, #382).

Full Changelog: v0.37.9...v0.37.10