Releases: NamesMT/dsh-home-hosted
Release list
v0.4.1
v0.4.0
v0.3.3
v0.3.2
🩹 Fixes
- Make the token warning visible, and put back a deleted entry (2113d47)
- Replace the panel token in one write, not clear-then-set (0df6a9f)
📖 Documentation
- An AGENTS.md for the next agent, and a true owned-key constant (2476446)
- Record the home-hosted CLI facts the token flow depends on (633e971)
❤️ Contributors
- NamesMT (@NamesMT)
v0.3.1
v0.3.0
dsh-home-hosted 0.2.2
Your dsh web server, up after every reboot.
- Starts dsh at boot. The managed
dshentry runs under home-hosted's nanny and is started when the panel comes up, so the web UI is there after a reboot without you touching anything. - Survives a panel restart. Restarting the panel no longer cuts a prompt mid-flight — verified end to end against home-hosted 0.6.4.
- Page style: Detailed / Compact. Detailed (default) opens every disclosure, explains each agent tool on a card, and gives each server a card whose face is live state with the config one disclosure down.
- A sign-in page that helps. dsh web's unauthenticated 401 points at the panel log holding the tokenised URL.
- Dependency moved to
home-hosted ^0.6.4;persistentis only written to a panel whose schema knows it. - Wording: 'Replace with global install', 'Manage boot autostart', 'Manage Panel UI'.
dsh-home-hosted 0.2.1
Docs only: the README is rewritten for a public first read — badges, a screenshot, a one-line pitch, a feature table and a tool table, with the depth moved into collapsible spoilers. No code changed.
npm renders a package's README from the published tarball, so this release exists to put the rewrite on the package page.
dsh-home-hosted 0.2.0
A concise settings page, merged agent tools, and platform-aware defaults.
Page
- Rebuilt around three signals — panel, autostart, harness entry — with the rest folded behind disclosures. One Refresh button instead of three, no restated section descriptions, a process table for servers, and the long pnpm path shortened from the middle (full path on hover).
- Panel and Options merged. Panel port is editable while the panel is stopped, and start uses it.
- Autostart is three buttons (Enable / Uninstall / Re-check); Enable reads Switch autostart mode when another mechanism is installed, and unsupported is hidden unless nothing else can work.
- Managed entries is one toggle. Adopt/Pause/Restore are gone; the Windows
kill-policy caveat is an inline note.
Defaults
onPortConflict: followon macOS/Linux,killonly on Windows, where a detached restart cannot be identified.- Health check accepts 401, which is normal once the panel has auth.
- Agent tools are on by default, and an older settings file is migrated on read (merged tool names, the old default pair,
manageDshinferred from its entry intent).
Agent tools
- Merged:
servers_lifecycle(start/stop/restart),servers_edit(create/update/delete),autostart_manage(install/uninstall). - New
ui_manage: status, update, revert to stock, or switch the panel's own UI to a local zip. - A mutating tool asks for approval only when the session is not already Full access.
Fixes
Nine host bugs from an internal audit, including: an empty tool allowlist turned every tool back on; an adopted entry could be deleted as if the plugin had created it; entries.remove could delete the entry the session runs as (it now pauses it); a non-integer port or unknown conflict policy could be written into the panel's config and stop it booting; concurrent token enrolments could lose the API credential; a failed panel takeover spawn ended the host process.
BREAKING CHANGE: agent tool names changed — see the commit message for the mapping. Settings migrate automatically; prompts and scripts that call the old names must use the new ones.
dsh-home-hosted 0.1.4
Mutating agent tools now respect the session's permission mode.
- Full access no longer fails. A mutating tool asked the approval service even when the calling session was already
danger-full-access, so a Full-access run was rejected by an auto-rejecting approval channel the moment it tried to create a server entry. It now skips the request when the session already grants full access, using the samectx.sandboxPolicyseam dsh's own tools use. - Below full access the tool still asks and still fails closed, and the refusal names the sandbox mode plus the remedy (Full access, or a session where approvals can be answered).