dsh-home-hosted

<div align="center">

📌 dsh-home-hosted

Prompt your servers into existence — keep them running and manage them via dsh / home-hosted panel UI.

_{Your whole home stack, up after every reboot — your dsh web included.}

A DeepSeek Harness plugin for

home-hosted, the panel that supervises your services.

Ask for a Gitea, a Jellyfin, an FTP server; dsh-home-hosted sets up the entries and manages them

— panel, ports, restarts and boot autostart included.

_{Nothing is installed or started until you say so.}






[🚀 Quick start](#-quick-start) · [🎛️ What the plugin does](#-what-the-plugin-does) · [🤖 Agent tools](#-agent-tools) · [🧩 Depth](#-depth)

</div>

<div align="center">

_{The Detailed style, then the same sections in Compact — both switchable from the page header.}

</div>

🚀 Quick start

dsh plugin --profile web add dsh-home-hosted

Open Settings → Home Hosted and add your servers — or just ask the agent:

add a Gitea on 3000, and a Jellyfin on 8096

Then, optionally, turn on Manage dsh and Autostart, so the panel — and everything in it —

comes back after a reboot.

🤔 Why

Ever tried setting up a media server, a Gitea and a few more yourself — then keeping them all

managed?

dsh-home-hosted uses home-hosted to do it: prompt for

the servers you want, let it write and configure the entries, and manage them all from dsh or the

panel — ports, health, restarts and autostart included.

   you ──▶ "add a Gitea, a Jellyfin, a cache…"
             │
             ▼
   dsh-home-hosted ──▶ home-hosted panel ──▶ ┌──────────────┐
     page · agent              │             │ gitea  :3000 │
                               │             └──────────────┘
                               ├──────────▶ ┌──────────────┐
                               │             │ jellyfin     │
                               │             │ :8096        │
                               │             └──────────────┘
                               └──────────▶ ┌──────────────┐
                                             │ postgres     │
                                             │ :5432        │
                                             └──────────────┘

   ★ OS boot entry ──▶ the panel comes back, and so does everything in it
     systemd · launchd · XDG · Run key

dsh is one entry in the panel, not the whole product. The panel is the supervisor: it starts

each entry, watches it, restarts what dies and reclaims its port. Add your Gitea, your Jellyfin,

your compose stack, your database — manage them from the page, or hand the entry ids to an agent.

Managing dsh itself is the bonus: the entry that keeps your harness up is a highlight on top of

the server management, not the thing this plugin is.

🎛️ What the plugin does

🖥️ Servers, set up by prompt · Add, edit, start, stop and restart entries — Gitea, Jellyfin, FTP, a compose stack. Written through the panel's API, so nothing restarts behind your back.

🏠 The whole home-hosted panel · Not just servers: BYOU custom UIs, workspaces, a reverse proxy with automatic HTTPS, backups (zip or AES-256), notifications, dynamic DNS, health probes, live logs and host vitals.

🤖 Agent tools · On by default, session permissions still gate every write.

🚀 Boot autostart · Highlight: installs, verifies and removes the OS entry, so the panel starts at boot. Opt in per machine.

🧭 Token warnings that mean something · A missing or refused API token is called out on the page, with one click to mint a working one.

🪟 Knows the other panels · Several panels on one machine? The agent is told which one this plugin manages, and asks before touching another.

🤖 Agent tools

Tool · Does

home_hosted_status · Panel, boot entry and managed-entry state

home_hosted_workspaces_list · Every workspace the panel serves, with counts

home_hosted_servers_list · Every supervised server in a workspace

home_hosted_servers_lifecycle · start · stop · restart

home_hosted_servers_edit · create · update · delete

home_hosted_autostart_manage · install · uninstall

home_hosted_ui_manage · status · update · revert · switch (official asset or local zip)

home_hosted_panel_logs · The panel's own console output. Needs no API token, so it works when the panel is up but not answering.

Every server tool names its workspace, because an id is only unique inside one.

A tool that changes something asks for approval only when the session is not already Full access.

<sub>A refused token is re-enrolled on the spot and the tool retries — see **aut

…(truncated)