@deepseek-harness-tui/dsh-tui

Q: What happens when dsh upgrades?

Nothing declares a version window for @deepseek-harness-tui/dsh-tui: dsh --version tells you what you are running, and no check will tell you whether @deepseek-harness-tui/dsh-tui matches it.

An interactive terminal interface for DSH agents.

Version 0.20.0 of @deepseek-harness-tui/dsh-tui, last published 2026-11-12; the install command and the range come from its own manifest.

Install

dsh plugin add @deepseek-harness-tui/dsh-tui writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add @deepseek-harness-tui/dsh-tui

Compatibility

@deepseek-harness-tui/dsh-tui ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

Thirty-eight peers: it is a second front end over the same runtime, not a panel inside the web UI. Anything you patch for the web surface (themes, overlays, composer buttons) has no effect there, and a dsh upgrade that changes an internal package breaks it first.

Who made it

Author: ccch1mneyyy. Repository: https://github.com/ccch1mneyyy/dsh-TUI. Package page: https://www.npmjs.com/package/@deepseek-harness-tui/dsh-tui.

After install

It declares @deepseek-ai/cordis as a peer and renders a new callable tool in the tool list; after dsh plugin add @deepseek-harness-tui/dsh-tui, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

@deepseek-harness-tui/dsh-tui routes whatever it persists through @deepseek-ai/dsh-settings under $DSH_HOME, and its own dependency line sits in $DSH_HOME/profiles/<name>/package.json.

Removing it

Removing @deepseek-harness-tui/dsh-tui is the mirror command, dsh plugin --profile web remove @deepseek-harness-tui/dsh-tui; the surface goes with it, and whatever it stored under $DSH_HOME stays until you delete it.

Common questions

What does it hook into, and how do I check that slot is free?

Its manifest names no community counterpart, so the check is manual: after dsh plugin add @deepseek-harness-tui/dsh-tui, run dsh --profile web --dump-config and look for two rows claiming the same slot.

What happens when dsh upgrades?

Nothing declares a version window for @deepseek-harness-tui/dsh-tui: dsh --version tells you what you are running, and no check will tell you whether @deepseek-harness-tui/dsh-tui matches it.