v0.2.8

What's Changed

• ci(release): create GitHub Release after npm publish by @DobyChao in #88
• feat(ux): UX-17 设为默认与本机机器行 by @DobyChao in #89
• docs(backlog): record UX-18 system prompt omits sw_status by @DobyChao in #94
• fix(sandbox): keep remote confine and official cores by @DobyChao in #95
• chore(release): bump to 0.2.8 by @DobyChao in #96

Full Changelog: v0.2.7...v0.2.8

v0.2.7

Plugin and remote core are both 0.2.7.

Packages master since v0.2.6: #84, #85, #86. Peer range unchanged: ^0.1.7-rc.2 || ^0.2.0-rc.1 || ^0.2.1-rc.1. Same major.minor still does not force a remote-core redeploy.

Changes

• Experimental sw_use_machine (REQ-I31, off by default): settings toggle under Experimental; when on (and host has workingDirectory, 0.2.1+), switches this session to another connected registered machine via host workingDirectory.set. Relative paths, file tools, default sw_exec machine, project-skill scan, and new terminals follow. Gate: danger-full-access only; target must already be connected; landing path must be a registered root.
• Projection-first session cwd read seam (REQ-I31): five former frozen-header.cwd readers now use effectiveCwdOf (projection first, header fallback) so host working_directory changes no longer leave remote paths on the old machine.
• Test cleanup (AUDIT-8): drop seven superseded unit tests and unused passthroughConfinedArgv export; behavior unchanged.

Fixes

• Nested remote workspace side terminal (BUG-20): canonicalize over shared SFTP instead of a new SSH exec per child path, so MaxSessions is not exhausted and side terminals can open; cancelled terminals close opened channels.
• Local primary sw_exec to remote secondary (BUG-21): mark argv from the command’s target cwd; do not treat the host confine Promise as argv.
• Remote session subagents miss project skills (BUG-22): processPath returns a routable placeholder while fileUrl stays remote POSIX.
• Remote sandbox “green success” when unavailable (BUG-23): tier none (no bwrap/Landlock) uses warning styling on banner and status chip.
• Subagent permission chip shows Custom (BUG-24): when approve=never and sandbox tier matches a preset, show that preset name.

npm: dsh-workspace-enhancement@0.2.7

v0.2.6

Plugin and remote core are both 0.2.6.

Packages master since v0.2.5: #80, #81, #82. Peer range unchanged: ^0.1.7-rc.2 || ^0.2.0-rc.1 || ^0.2.1-rc.1. Same major.minor still does not force a remote-core redeploy.

Changes

• Directory picker (UX-14): hover shows full connection name / user@host:port; editable path with Enter to jump and Esc to cancel; resizable panes; no gray hover band on the splitter.
• Refresh icon (UX-15): reconnect/recheck is a borderless refresh icon on sidebar rows, picker badges, session header, and settings; sidebar remote mark is a stroke server icon.
• Workspace hover (UX-16): remote workspaces show server + real remote path (copy still uses the host placeholder path).

Fixes

• Dialog drag-dismiss (BUG-18): new connection / folder / delete / confirm no longer close when press starts inside and release is on the backdrop.
• Remote file native preview (BUG-16): remote session files claimed via constrained workspace.read instead of local better-sidebar stat.
• Browser remote terminal (BUG-17): shell probe/lookup bound to session route; null success write callback not treated as failure.
• No env echo on remote terminal start (BUG-19): start command uses PTY exec as session payload so scrubbed env is not echoed by the login shell.

npm: dsh-workspace-enhancement@0.2.6

v0.2.5

Plugin and remote core are both 0.2.5.

Official claim for host @deepseek-ai/dsh 0.2.1-rc (alongside 0.1.7-rc / 0.2.0-rc). Landed via #78.

• Peer (all 13 seam packages): ^0.1.7-rc.2 || ^0.2.0-rc.1 || ^0.2.1-rc.1
• Drift: next channel installs 0.2.1-rc.*; pinned 0.2.0-rc.1 kept after next left that line
• Docs: compatibility.md §1 row for 0.2.5; PUB-9 → shipped, PUB-10 → this release
• Master since 0.2.4 also includes REQ-A6 host workspace-files primary path (#77) and watchLinuxScopeStart → INTERNAL_METHODS (#76)

The version gate still accepts any deployed 0.2.x core. Redeploy only if you want the rebuilt 0.2.5 binary sha on the wire.

Published to npm as dsh-workspace-enhancement@0.2.5 (latest).

v0.2.4

Plugin and remote core are both 0.2.4.

npm 0.2.3 shipped core 0.2.2. Everything below landed on master after that tag.

• Fence tiers (REQ-I29): functional bwrap probe, Landlock fallback, guided refusal, fenceinfo on deploy and status
• Per-call confine for the remote fence (REQ-I27)
• Side roots share the main root's workspace-write rights (REQ-I24)
• One remote execution path (AUDIT-7); settings approval dropdown removed (UX-7); user-facing 「核心」 is now 「远程组件」 (UX-9)
• Fixes: pwsh elevation on 0.2.0 hosts (BUG-12), direct-leg false EOF (BUG-13), picker drag-close (BUG-14), core sha registration when tar pipes are denied (BUG-15)
• Connection state colors use host tokens (UX-4); new/edit connection form no longer prefills root (UX-10)
• L1 headless smoke in CI (INFRA-23); weekly desktop composition watch (UPSTREAM-11)

The version gate still accepts any deployed 0.2.x core, so this release does not force a redeploy. Fence tiers live in the new binary — redeploy to get them. The 0.2.2 and 0.2.3 binary hashes stay on the compat list.

npm publish is queued on the npm-publish environment and waits for the repository owner's approval.