DSH A2UI Studio

Your agent manages. A2UI Studio remembers.

A DeepSeek Harness plugin for delegating machine and application management to your agent. Describe the target and the job; the agent can register the machine, investigate its applications, save what matters, and build an interface you can use again.

中文 · Download v0.3.2 · Setup · End-to-end walkthrough

1. Tell the agent what to manage

“Register this machine as Queue server. Find the queue application and remember where it lives.”

The agent checks existing records and uses machine_manage to create or update the machine archive. Supply connection details through your approved access setup when needed; manual registration is an optional fallback, not a prerequisite.

8 seconds · Review the completed agent registration and open its saved record.

2. Turn application knowledge into a working panel

“Show running, waiting, completed and failed jobs, with concurrency. Start read-only.”

The agent reads the application, records its location and purpose, and proposes a tailored card. You review the execution definitions before publication; the plugin keeps the notes, card versions and operation receipts.

8 seconds · Inspect the saved application notes and refresh the published panel.

3. Use it directly—or delegate the next job

Open the machine to use its saved panel. Click @ when you want the agent to investigate or change something; it can retrieve the existing context instead of starting from scratch.

7.5 seconds · Attach the machine to chat; no new request is submitted.

Three short recordings of real DSH, using fictional local demo data. Completed results are revisited, not presented as live generation. Details and still images. The plugin keeps knowledge the agent explicitly saves; it does not automatically remember every conversation.

Another application: dual-GPU monitoring and power controls. The same workflow can leave you a very different interface.

What is included

Capability	What it gives you
Machine directory	Persistent records, multiple SSH paths, default connection, health checks, and @ references
Application cards	Model-authored layouts, data bindings, conditional controls, and numeric color scales
Persistent operations	Card revisions, publication review, execution permissions, and action receipts
Extensible UI	A component catalog plus custom card extensions when standard components are insufficient
Agent skills	Machine management, card authoring, and extension development guidance shipped with the plugin

The UI follows an A2UI-inspired approach: the agent describes a structured interface and the host renders it. This is not a claim of full A2UI protocol compatibility. Custom extensions are a separate, code-bearing capability and should be reviewed accordingly.

Install

Previously called DSH Control Studio. The install/package ID remains dsh-control-studio for compatibility; existing installations need no migration for this branding change.

Prerelease. Linux and Windows desktop; DSH 0.2.1-alpha.1 / 0.2.1-rc.2. See Windows setup and limits. Independent community project, not an official DeepSeek plugin.

Download and verify the prebuilt package:

curl -fL -o dsh-control-studio-0.3.2.tgz \
  https://github.com/zhaochengggg/dsh-a2ui-studio/releases/download/v0.3.2/dsh-control-studio-0.3.2.tgz
curl -fL -o SHA256SUMS \
  https://github.com/zhaochengggg/dsh-a2ui-studio/releases/download/v0.3.2/SHA256SUMS
sha256sum -c SHA256SUMS

After the checksum reports OK, install as the DSH user:

dsh plugin --profile web add ./dsh-control-studio-0.3.2.tgz --allow-build=esbuild
dsh --profile web --dump-config

Restart DSH and refresh the browser. Replace web with your profile name if needed. This is one package; no legacy plugins are required. Use the release tarball, not a git install. --allow-build=esbuild approves the extension builder's dependency script; see setup and permissions before enabling execution.

Start with a read-only card

Already using dsh-machine-apps? Follow the rename migration guide before installing. Do not enable both packages together.

Ask the agent to use machine-management to register the target and record its connection, then app-cards-authoring to inspect the application and propose a read-only panel. For a machine already in the directory, reference it with @. Add controls after confirming what each action executes.

Opening a card does not automatically apply its settings. Local execution is not authorized by default. This plugin does not change network exposure, proxies, authentication, or GPU services during installation.

Go deeper

• Setup, permissions, data locations, upgrades, and development
• GPU example: request, preview, and everyday use
• Card authoring skill
• Custom extension skill
• Machine management skill

Have an application you want to manage? Open an issue with your DSH version, intended panel, and redacted logs or screenshots. Do not include credentials or private machine addresses.