Connect workbuddy to DeepSeek Harness: DSH plugin setup

workbuddy is a desktop app that bundles several large models, and a DSH plugin such as dsh-workbuddy-connect can bring its models into DeepSeek Harness, usable directly from the model picker in the chat window (source). This guide covers why you would connect it, how to set it up, how to triage connection failures, and how to disconnect and uninstall.

What workbuddy is and why connect it to DeepSeek Harness

Connecting workbuddy to DeepSeek Harness is essentially reusing its existing models and login state, sparing you the chore of configuring third-party providers by hand. The workbuddy desktop app ships with several large models (such as GLM, DeepSeek, and Kimi); without a plugin like this you would fill in each provider, key, and endpoint inside DeepSeek Harness one by one. Connecting brings four direct benefits:

1. Zero-configuration integration — reuse the app's login state without refilling keys. Expected: the models show up in the model picker right after install.
2. Account and quota visible — the settings card shows account information, token expiry, and remaining quota. Expected: low quota or an expired login is visible at a glance.
3. Works across interfaces — usable in Web, Desktop, and TUI forms. Expected: switching interfaces needs no reconfiguration.
4. Follows account switching — change accounts in the app and the DeepSeek Harness side follows. Expected: you do not edit both sides.

In one sentence: it turns "an external model source" into a selectable option in DeepSeek Harness rather than a configuration to maintain.

Connect workbuddy with the DSH plugin: install, login state, profile

Installing dsh-workbuddy-connect takes one command, defaults to zero configuration, and reuses the WorkBuddy login state, so you usually do not type credentials or an address by hand. Getting started:

1. Install the plugin — run in your terminal:
   bash

   dsh plugin --profile web add dsh-workbuddy-connect
   

   Expected: the terminal echoes that the plugin joined the web profile.
2. Restart to take effect — restart DeepSeek Harness as prompted. Expected: the plugin enters the current config tree.
3. Pick a model — open DeepSeek Harness and choose a WorkBuddy model from the list. Expected: you can chat directly with no extra authentication step.
4. Check status — use the plugin command status to read the account and login state. Expected: it shows the current account, token expiry, and remaining quota.
5. Diagnose when abnormal — run doctor if it will not connect. Expected: it locates whether the problem is login, network, or version.

If you prefer not to use the command line, search workbuddy on DSH Plugin Hub and install from the entry in one click. Mind the profile scope: it is only available in the profile it was installed into.

When workbuddy will not connect in DeepSeek Harness: network, credentials, version

When it will not connect, run doctor for diagnostics first, then rule out login state, both ends' versions, and profile one at a time. The three layers and their typical symptoms:

1. Login state invalidated — the WorkBuddy token expired or was signed out, so the DeepSeek Harness side cannot use it. Expected: signing back in through the desktop app restores it.
2. Network unreachable — the request cannot reach the model service. Expected: once connectivity returns, the models work again.
3. Version mismatch — DeepSeek Harness or the plugin is too old and the capabilities do not line up. Expected: upgrade past the minimum supported line and retry.
4. Wrong profile — the plugin is installed in another profile, so the current session cannot see it. Expected: install into the profile you are using.

In order, status for login and quota and doctor for connection are usually enough to locate the layer.

DSH plugin workbuddy connection notes

1. Log in before use: sign in to WorkBuddy first so the DeepSeek Harness side can reuse it.
2. The profile must be right: install into the profile you are using, or the models will not appear.
3. Quota runs out: remaining quota and token expiry live in the settings card, so glance at them before a long task.
4. Log out to disconnect: to switch accounts or disable it, logout first, then uninstall.
5. Uninstall symmetrically: use dsh plugin --profile web remove dsh-workbuddy-connect.
6. Do not trust the UI alone: when status looks wrong, go by the output of status / doctor.

Sources: dsh-workbuddy-connect (DSH Plugin Hub), DeepSeek Harness docs - quickstart, docs - config catalog.