Introduction

DeepSeek Harness (DSH) is an AI agent development environment. When multiple DSH instances are deployed locally and remotely, managing them typically requires opening multiple browser tabs. dsh-fleet provides a console for managing local and remote DSH instances on a single page, and it supports reading historical sessions across devices.

What Is This

dsh-fleet was developed by loveXbanshee and produced by Punica Studio. It is a Fleet console. Its core function is to allow a local DSH instance to manage multiple remote DSH instances on a single page and to read cross-device conversation history.

Installation

Run the following command on the control-side machine:

dsh plugin --profile web add github:loveXbanshee/dsh-fleet

Restart dsh web, then enable the plugin in Settings → Harness Fleet.

Configure Remote Endpoints

Install the same plugin on each remote DSH instance that needs to be managed. Open Settings → Harness Fleet:
1. In Allow other devices to read local sessions, set a shared token (enter the same string on both machines).
2. It is recommended to set Local Role to controlled endpoint, to avoid interference from the right sidebar.

Core Features

  • Manage a local instance and multiple remote DSH instances on a single page.
  • Real-time remote busy/idle status.
  • Card-based instant switching with persistent online state.
  • Read historical sessions across devices.
  • One-click refresh or one-click restart for remote cards.
  • Control endpoint / controlled endpoint roles.
  • Certificate Assistant.
  • Fleet gateway.
  • Completion notification sound.

Usage

  • Check busy/idle status: View the card status in the right-side device panel. Green dot = idle, spinner = running, ✓ = just completed.
  • Switch device: Click a card; the page immediately switches to the corresponding remote DSH instance.
  • Refresh: Click the ⟳ refresh button on the card.
  • Restart: Click the restart button on the card.
  • Read history: On the settings page, find the corresponding remote card, then open the Sessions option to view and read historical records.
  • Handle certificates: If the remote self-signed HTTPS site cannot be opened, open the Certificate option on the remote card and install it as prompted.

Security and Precautions

  • The token is stored only in the host configuration; the browser does not access the token.
  • Session reading and restart operations require the correct token.
  • Endpoints that modify state, such as changing settings or restarting, only accept local same-origin requests.
  • For system-level actions such as installing certificates or granting permissions, the plugin only provides guidance; the user must personally confirm them in the system.

References