Skip to content
dsh-market Browse plugins GitHub 中文

FeatherHunter/dsh-im-companion

IM Companion for dsh-im: groups Feishu/WeChat/QQ bots by Agent in DSH workspaces and enhances DSH native session states (blue/orange/red rail markers for running, needs-review and error), with left badges, one-click filter, fleet overview and drag-to-move. Clean uninstall.

Stars ★ 17 Category UI Enhancements Listed 2026-09-04 npm dsh-im-companion

Install

Inside DeepSeek Harness, with dsh-market

dsh plugin --profile web add dshmarket

Or from the command line

dsh plugin --profile web add dsh-im-companion

Installing runs third-party code with your own permissions — it can read your files, use your credentials and reach the network. Review the source first, and pin a commit (github:owner/repo#sha) when you can.

Screenshots

README

Chinese · 中文

dsh-im-companion enhances dsh-im with the concepts of assistants and homes.

Your star means the world to me.

Give every agent a home — IM Companion handles the rest.

One minute to install (dsh-im first, then the companion).

Prerequisites: DSH (DeepSeek Harness) + dsh-im (the IM bot core).

# 1. Install the DSH CLI (skip if installed)
npm install -g @deepseek-ai/dsh

# 2. Install the dsh-im core first (skip if installed; --profile is required too)
dsh plugin --profile desktop add dsh-im
#     or
dsh plugin --profile web add dsh-im

# 3. Then install the companion (--profile is required: the entry you actually use)
dsh plugin --profile desktop add dsh-im-companion
#     or
dsh plugin --profile web add dsh-im-companion

# Pin a version for stability (current: 0.1.8)
dsh plugin --profile desktop add dsh-im-companion@0.1.8 --registry https://registry.npmjs.org

Refresh the page after installing and it takes effect. If the panel does not show up, quit DSH completely and reopen it.

Copy the text below and send it to your AI:

Please install the DeepSeek Harness plugin dsh-im-companion (the IM companion).
Read the repo README first: https://github.com/FeatherHunter/dsh-im-companion
First confirm which profile my DSH entry uses (desktop app goes to desktop, self-hosted web service goes to web),
then confirm the dsh-im core is in the same profile (install it first if missing), then install the companion into the right profile.

Below uses desktop as the example; web users replace --profile desktop with --profile web:

dsh plugin --profile desktop add dsh-im-companion@0.1.8 --registry https://registry.npmjs.org
npx --yes @deepseek-ai/dsh plugin --profile desktop add dsh-im-companion
dsh plugin --profile desktop add dsh-im-companion@latest --registry https://registry.npmjs.org

Upgrade · Uninstall:

dsh plugin --profile desktop update dsh-im-companion
dsh plugin --profile desktop remove dsh-im-companion
dsh-im-companion dsh-im Notes
0.1.16+ 4.21.1 (verified) Dual transport unchanged: 4.17.1+ uses the /api carrier, ≤4.17.0 falls back to the legacy route; 4.21.1's carrier rule re-checked as identical to 4.17.1 (dsh-im<channel> + { method, payload })
0.1.7 – 0.1.15 4.17.1 (verified) Dual transport: 4.17.1+ uses the /api carrier, ≤4.17.0 falls back to the legacy route automatically
0.1.6 4.17.1 Fails to assemble in a web profile (the host half used the retired prefix route: cannot get property "webServer" without inject) → upgrade to 0.1.7
0.1.4 ≤4.17.0 Broken after the dsh-im 4.17.1 carrier change (HTTP 405 in the connect wizard); upgrade to 0.1.7

Host @deepseek-ai/dsh 0.2.0-rc.2 verified (0.2.1 pairs with exactly this host version; the host must provide connection.fetch; older hosts fail loudly at assembly rather than degrading silently). The panel header shows two version capsules side by side, where the colour carries the identity: purple = this plugin's own version, blue-white = the compatible dsh-im version (dsh-im 4.21.1); the host dsh capsule has been removed, and host compatibility lives only in this section and the market badge (engines.dsh). Each capsule keeps only the axis name + version number, and the full wording lives on hover (values come from package.json, injected at build time).

dsh-im owns connecting; dsh-im-companion adds capabilities through the concepts of assistants and homes.

Home: which workspace has an assistant minding it, online or not, all in view; moving takes one drag.

👇 Click “with-assistant” to see only settled homes.

👇 Settings → IM companion: assistants, channels and online states on one screen.

👇 Switch to channels: same-channel assistants line up.

👇 Click “add connection”: pick a home, scan, bound.

👇 Open an assistant card: mode, status and per-channel switches at a glance.

👇 Fleet radar: the Agent × channel matrix shows the whole fleet online state.

👇 Session states at a glance (DSH enhanced).

👇 Click the robot-face icon in the toolbar to open the moving panel

👇 Move house: drag the photo to another home, confirm twice. Green on duty, yellow napping, grey asleep.

👇 Drag the card over another home and the target lights up

👇 Confirm before moving

That is the desktop app-market cache: freshly published versions are silently skipped for a few hours. Wait a few hours and update again; if you cannot wait, install once with the explicit official registry:

dsh plugin --profile desktop add dsh-im-companion@latest --registry https://registry.npmjs.org

dsh-opencode-palette —— 34 classic opencode themes, one-click switch

dsh-mattpocock-skills-deck —— Matt Pocock skills deck: 25 engineering and productivity skills, ready to use

dsh-chinese-skill-patch —— Chinese skill names that just work, no English rename needed

dsh-prompt —— Prompt toolbox: 24 deep templates at hand


Questions? File an ISSUE; read the docs/agents label rules before claiming.

MIT © FeatherHunter

Thanks to everyone who files Issues and PRs and joins discussions.

The first public release (v0.1.0) has no external contributors yet — the first person to file an Issue gets their name here.

Also thanks to upstream dsh-im: no core, no companion.

Bugs and ideas go straight to ISSUEs — faster and traceable.

File an ISSUE · Upstream dsh-im

Topic-group QR coming — a permanent one will live here once there is a group.

Content from the project README on GitHub ↗

Comments

Comments live in GitHub Discussions. Sign in with GitHub to post or react.