seek://news/dsh-v0-1-2-rc-1
v0.1.2-rc.1: The 0.1.2 Series Gets Its First Release Candidate
TL;DR
One day after the fifth alpha, upstream cut v0.1.2-rc.1 — the first release candidate of the 0.1.2 series, aggregating the major changes since 0.1.1-rc.2. It adds an experimental Inspector and Web Preview, folding defaults, resizable width, queued sending, an image-pipeline rework and headless stderr progress, and carries the whole alpha-series compatibility ledger. Still flagged prerelease.
One day after Four Prereleases in Four Days: v0.1.2-alpha.2 Through alpha.5, upstream published v0.1.2-rc.1 — and changed what the version number says. For the first time since the release channel opened, the tag does not carry the alpha suffix: the notes introduce it as the 0.1.2 series’ first release candidate, summarizing the major user- and developer-facing changes since v0.1.1-rc.2.
What the candidate folds in beyond the alphas
The aggregate includes the whole train, but a fair amount in rc.1 never appeared in an alpha’s notes:
- Two experimental tools: an Inspector and a Web Preview, both landing as explicitly experimental.
- Reading defaults change: process details and the System prompt now fold before each completed answer; content width adapts or drags to size, with conversation-wide font scaling that Markdown tables follow.
- Composer behavior: drafts survive session switches, a pending draft flips the main button to Send with messages queuing, and prompt history renders as readable Q&A cards that mark unsubmitted states.
- The image pipeline is reworked: sent images display immediately while compression and upload continue in the background, compression gets faster with smaller uploads and better long-screenshot clarity, and context compression now accounts for image usage.
- For integrators: headless runs stream progress to stderr while stdout stays final-result-only, and pi-ai model support adds controls such as a vLLM thinking budget.
- Session records also take less disk space, and the
/and@menus get a round of polish.
The compatibility ledger, in one place
For anyone who skipped the alphas, rc.1’s Chores section restates every breaking or default-changing item in one list: the legacy ApiProxy is gone in favor of the Remote gateway; network access to the Web UI requires the one-time token in the launch URL; applications launch through dsh Profiles; Code Mode is renamed PTC mode; public WebFetch and per-runtime web_fetch are on by default; Web PTC Mode no longer exposes the general-purpose workflow tool; the optional SQLite session persistence backend is removed, with export via an older version; and Session.events is replaced by the on-demand read APIs seq, eventAt() and snapshotEvents(). One wording change is worth noticing: alpha.4 asked developers to watch compatibility on the SessionSeq / SessionLogOffset split — rc.1 states the same change while preserving forward compatibility.
The bug-fix list is aggregated too, from PowerShell and Bash output fixes through a Windows path-picker truncation involving characters such as 「开」, preset-directory loss at startup, WebSocket heartbeats for idle connections, and the Node.js 24.0–24.11.1 startup fix.
Still not the stable release
The releases API lists ten published releases and every one — rc.1 included — is flagged prerelease. The candidate label is a statement of intent, not a stability claim, and the updated safety notice still states the project has not been security-audited. Live repo metadata stays in the site’s build-time snapshot and stats page — this article cites no point-in-time star counts.
Official references