Blue 0.1.0-rc.2
Blue 0.1.0-rc.2
The first public preview release on npm: the complete Blue TUI — streaming
transcript, the editor with fuzzy slash commands, overlays and dock panes,
theming, and the model/provider/status command family — published as five
lockstep packages under the @dsh-blue scope, built against the
0.1.1-rc.2 harness line.
Highlights
- Streaming transcript — markdown rendered while it streams; tool calls
as cards with dedicated read/diff/terminal views; 30-step fold retention. - Editor — rounded-box input with fuzzy slash-command autocomplete and
argument ghost hints,!bash mode,@file completion,#skill
completion, Ctrl-V clipboard image paste, and large-paste folding. - Commands —
/model/effort/provider/permission/status
/context/version/theme/export/copy/btw/sessions
and friends; a subagent-group dock pane; session-level approval choices. - Theming —
/themehot-switching acrossdark/light/auto
(OSC 11 background detection) /custom(JSON palette). - Extensible by construction — every render component, interaction
provider, command, and status entry is a Cordis plugin; registries drive
the completion menu and/help.
Fixes
- rc.1 tarballs self-destructed on install (hash chunks outside
exports,
incompletefilesmanifests); rc.2 ships completefiles=["lib/**/*"]
manifests, acheck:libexport guard, and a local pack-install precheck
in the release pipeline (D51).
Known issues
- Preview semantics: packages carry the
rcdist-tag (lateststays
reserved for the stable line), and the harness line is pinned —
breaking upgrades are possible between previews. - Tool output is not streamed (presented when the tool completes); the
approval panel has no inline diff preview yet; no desktop notifications.
The full parked list lives in
docs/blue-roadmap.md. - pnpm 11 users:
minimumReleaseAge(default 24h) can silently resolve the
@rcdist-tag to the previous version during the first day after a
publish — see the FAQ workaround.