A WorkBuddy-style workspace where skills, experts, and plugins shape new workflows.
Inspired by WorkBuddy’s workflow and built on DeepSeek Harness plugins: start with personal use, then install Enterprise Connection for company models, collaboration, and colleague mentions.
Download Desktop · Explore the workflow · Personal and enterprise · User guide · 简体中文
A personal workspace with installable enterprise capabilities is a defining WorkDSH feature. Projects, the library, experts, skills, and connectors share the same implementation. Install Enterprise Connection and sign in to share text and files with @ colleagues and use Collaboration; add company models through model settings. Independent business plugins can also reuse member authentication through workdshEnterprise to call company business APIs.
The enterprise plugin is not listed in a plugin marketplace. Download Enterprise Connection, enter the downloaded file’s full path in “Plugins → Add plugin”, install and activate it, then connect through “Settings → Enterprise account”. Installation and login · Business plugin authentication · Separate admin backend
Captured from a local WorkDSH session. Project names and account figures are demonstration data, not bundled with the installer.
WorkDSH draws on WorkBuddy's way of organizing projects, material, experts, skills, and connectors, and implements those pages and management features on DeepSeek Harness. DSH is a complete agent application in its own right; it composes models, tools, skill support, and UI through plugins. WorkDSH adds its workspace features through the same mechanism.
| What you need to do | Where WorkDSH helps |
|---|---|
| Keep working toward a long-term goal | Projects bring instructions, plans, tasks, material, and capability settings together. |
| Give AI the files you already have | The library manages local files, search, and previews; tasks can reference material and its revision. |
| Reuse a team's working methods | Experts save role and capability settings; skills carry callable instructions and resources. |
| Keep the result beyond the chat | The deliverable workspace previews or edits supported working copies of documents, spreadsheets, presentations, HTML, and PDF. |
- Desktop execution, central administration: the Agent and tools run on the employee’s computer; the server handles accounts, authorization, collaboration data and model forwarding.
- The full official UI with shared feature plugins: personal and enterprise modes reuse the same library, experts, skills, and connectors.
- Bundled runtime: Desktop includes Node.js, pnpm, Python, and built-in plugins without downloading them on first login. Community skills and plugins are installed on demand.
- Reusable enterprise authentication for business plugins: independent plugins inject
workdshEnterpriseto call the company backend using the current member login, without reading or storing tokens. - Mention colleagues and share AI results: select organization colleagues with
@, share analysis text and files, and review received or sent shares in Collaboration. Requires the Enterprise Connection plugin and company login. - Personal and company models together: connect the company model API and select company models in the conversation model picker while retaining personal providers. Supplier keys remain in the admin backend.
Enterprise Desktop exposes workdshEnterprise to Host plugins. It reuses the current member login without returning backend tokens, local bridge credentials or passwords. Desktop Main authenticates requests; the backend enforces member and business permissions.
Run this example in your plugin's Host entry, not in its browser page. The Enterprise Connection plugin provides the service after installation, activation and company login; personal mode does not provide it.
import type { Context } from '@deepseek-ai/cordis'
import type { EnterpriseService } from 'workdsh-contracts/enterprise'
declare module '@deepseek-ai/cordis' {
interface Context { workdshEnterprise: EnterpriseService }
}
export default {
name: 'company-reports',
inject: ['workdshEnterprise'],
async apply(ctx: Context) {
const member = await ctx.workdshEnterprise.identity()
const reports = await ctx.workdshEnterprise.request<{ items: unknown[] }>({
plugin: 'reports',
operation: 'list',
method: 'POST',
body: { page: 1 },
})
},
}This calls POST /api/extensions/reports/list on the company backend. Implement the business endpoint and its authorization without another login flow. Requires Desktop 2.0.6-alpha.3 and Enterprise Connection 0.1.0-alpha.2. workdsh-contracts is not a published public npm SDK; see the integration guide for packaging the type dependency and request restrictions.
File in library ──reference──> Project task ──choose──> Expert / Skill / Connector
│
└──> Inspect the process and result; keep editing in supported editors
This path is WorkDSH's product direction. End-to-end validation of project document references, expert execution, and different Office formats is ongoing during Alpha. Preview, editing, and export fidelity differ by format; the current capabilities and limits describe them in more detail.
See an HTML deliverable from a real local conversation
A local task example showing deliverable cards and right-side preview; it does not imply lossless editing for every file.
It helps to distinguish the content people use from the software extension that manages it. A skill usually consists of instructions and resources containing SKILL.md; it can be installed directly into the local DSH Skills directory and is not necessarily a plugin. WorkDSH's skill manager is a DSH plugin. An expert configuration is not itself a plugin either; a WorkDSH plugin manages experts. Other DSH plugins can add tools or UI features directly. The plugin system can therefore support skills, experts, and software functions without making every skill or expert a separate plugin.
DSH plugins can be individual tools or combine UI, services, and other resources into a larger application scenario. For example, a data-management plugin could add data views and processing tools, then work with skills and experts across a workflow. This illustrates what the plugin model can support; it does not mean this release bundles such a data-management system. Users can discover and install skills through SkillHub and find DSH community plugins through dsh-market. Before installing a plugin, check what it provides and whether it supports the current DSH version.
WorkDSH connects two independently maintained catalogs: SkillHub for Skills and dsh-market for DSH plugins. SkillHub entries show their source and version, and open the source page for license information before installation. The DSH catalog is provided by the third-party dsh-market plugin inside the existing plugin page. Catalog entries are not all preinstalled, reviewed, or endorsed by WorkDSH; check each item's license, dependencies, and DSH compatibility. Skill management · Plugin development · Ecosystem manifesto
Live SkillHub results; catalog size and entries change over time. The local session shown is a demonstration environment.
The third-party dsh-market plugin supplies discovery and installation. The screenshot does not imply that catalog plugins are bundled with WorkDSH.
WorkDSH supports personal use and Enterprise Desktop. Personal and enterprise modes use the complete official DSH interface and the same WorkDSH feature packages. WorkDSH Admin manages company accounts, organizations, permissions and internal model APIs.
| Mode | Where the Agent and tools run | How to enter |
|---|---|---|
| Personal Desktop | On your computer, using personal files and model settings. | Open the app and choose personal use. |
| Enterprise Desktop | On the employee's computer, using local files and tools. | Install the desktop app and enterprise account plugin, then choose enterprise login. |
Desktop keeps personal and enterprise data and credentials in separate spaces. Install the enterprise account plugin when needed, then sign in with the company address and account; the backend still authorizes membership. Projects are included in Desktop. Enterprise collaboration is installed on demand and activates after company login; personal mode does not activate it. Enterprise Agent execution is not deployed on ECS. Notifications and business applications remain independently installed plugins.
The enterprise backend is developed and deployed independently in techflag/workdsh-admin. This repository provides the WorkDSH client and plugins. The backend provides company accounts, organization permissions, collaboration data, member-authorized conversation auditing and internal model API forwarding.
Administrators should follow the workdsh-admin deployment and usage guide, then provide members with the backend address and company accounts. Members install this repository's desktop app and Enterprise Connection plugin and connect to that address; the Agent and tools continue to run on their computer.
Enterprise features are enabled by an explicitly installed Enterprise Connection plugin, not bundled in the base Desktop. One package provides company accounts, colleague collaboration and authenticated requests for independent business plugins.
- Download
workdsh-enterprise-connection-0.1.0-alpha.2.tgzfrom this release and retain the file. - In personal mode, open Plugins → Add plugin, enter the full tgz path, install and click Enable now.
- Open Settings → Enterprise account → Connect enterprise and sign in using the company backend address and member account.
- Open Collaboration to review shares and configure the company API manually in model settings. Developers can inject
workdshEnterprise; see the integration guide.
Enterprise Connection is not listed in a plugin marketplace. Install the downloaded local .tgz file by its full path; searching the package name will not install it.
Example paths in the Add plugin input:
macOS: /Users/your-name/Downloads/workdsh-enterprise-connection-0.1.0-alpha.2.tgz
Windows: C:\Users\your-name\Downloads\workdsh-enterprise-connection-0.1.0-alpha.2.tgz
Use your actual username and location. On macOS, select the file in Finder and press Option + Command + C; on Windows, right-click and choose Copy as path, removing surrounding quotes before pasting. Paste the full path into Plugins → Add plugin, install, then click Enable now. Do not enter only the package name or upload the archive to the admin backend.
Download this release's Enterprise Connection tgz. Retain the original .tgz if your browser extracts downloads; an extracted folder path is not the archive path.
The Enterprise Connection package is delivered independently through our GitHub Releases, without a third-party marketplace. Download workdsh-enterprise-connection-<version>.tgz, retain the file and enter its full path in Add plugin. Release assets include the compatible DSH version manifest and SHA256SUMS.
In personal mode, open Plugins → Add plugin, enter the administrator-provided Enterprise Connection package path or installation address, verify the source and install, then click Enable now when installation finishes. One package provides account and collaboration plugins. Then open Settings → Enterprise account → Connect enterprise, enter the backend address and sign in. Installation uses the official progress and error feedback; no terminal command is required. Enterprise plugins are not yet published to a searchable catalog.
Desktop uses one base installer. Enter personal mode and install the Enterprise Connection package through plugin management, which includes account and collaboration. Then switch modes from the workspace menu, enter the administrator-provided backend address and sign in with your company account. Administrators can also preset the address when packaging. The management console remains accessible through a browser.
The enterprise screenshots in this section use demonstration accounts, organizations and local addresses. This sample data is not shipped with the app.
After signing in, use Settings → Enterprise account to view your name, organization and role, or sign out.
See the enterprise account and sign-out entry
Enterprise Desktop synchronizes visible user and assistant conversation text to the backend under the member's account. Thinking, tool traces and attachments are not uploaded as conversation text. Authorized administrators can read their organization's synchronized text through audited, read-only access.
Install and enable the Enterprise Connection plugin, then sign in with your company account. Type @ in the conversation composer to select organization colleagues and share analysis results and files through your task. Collaboration in the sidebar lists received and sent shares so you can review content and files and continue the discussion. One Enterprise Connection package provides identity and collaboration; enterprise collaboration is inactive in personal mode.
An administrator configures upstream model APIs, supplier keys, protocols and allowed model catalogs in WorkDSH Admin. Members receive an internal API address and access key, then use Settings → Models → Custom model API:
| Field | What to enter |
|---|---|
| Provider ID and display name | For example, company-api and Company models. |
| API address | The administrator's internal base URL, for example https://enterprise.example/api/model-gateway/v1. |
| API protocol | The protocol supported by that internal endpoint. |
| API key | The internal access key supplied by the administrator. |
| Model catalog | Fetch available models, or add the allowed model IDs provided by the administrator. |
Save the provider, then choose a model under Company models in the conversation model picker. The same composer supports mentioning colleagues with @.
Personal model providers can coexist with the company provider. Real supplier keys stay on the server; company providers are configured through the official settings rather than automatically injected into DSH. Model requests go to the configured API independently of where the Agent runs.
See company model configuration in the official settings
See the management console
WorkDSH Admin — organization overview:
The planned desktop installer release is 2.0.6-alpha.3. Its download links will become available after the GitHub Release is published:
| Platform | Download |
|---|---|
| Windows x64 | WorkDSH Setup.exe |
| macOS Apple Silicon | WorkDSH arm64.dmg |
| macOS Intel | WorkDSH x64.dmg |
Desktop installers include Node.js, pnpm and Python runtimes by default, so users do not need to install them separately. This is an Alpha release: end-to-end project document references, expert execution, and different Office formats are still being validated. The macOS DMGs are unsigned; download updates from Releases. Start with the user guide and FAQ.
The base Desktop package does not preinstall enterprise plugins. Install them separately to enable enterprise login. For existing downloads, available features are described in their corresponding release notes.
The Tools → Terminal command dsh (optional) menu lets you inspect, install, repair or remove the terminal command. Desktop chat does not require it; its dialog appears only when you select the menu. Installation creates a command entry using the packaged Node, pnpm and official CLI. Removing it does not delete the app or workspace. Commands display the active Desktop space; use --workdsh-space=personal or --workdsh-space=enterprise to select it explicitly. Initialize the space in Desktop first and keep Desktop signed in for enterprise operations. Plugin changes apply to that space’s Profile.
Host plugins inject workdshEnterprise and call request({ plugin: "reports", operation: "list", method: "POST", body: { page: 1 } }). Desktop attaches the current member authentication without exposing tokens. The backend must authorize every business operation. See the integration guide for code, type-package setup and the required new Desktop/plugin versions.
Source ownership: WorkDSH feature packages and Web · Desktop carrier · Architecture · All documentation. Running from source requires Node.js 22.19+ or 24+, Corepack, and Yarn 4.18.0:
corepack yarn install --immutable
corepack yarn devRun checks with corepack yarn check. On macOS or Windows, corepack yarn release:pack builds the Web Profile and Desktop package from the current commit. Once the Web package is published, use corepack yarn release:pack:published for the final installer. Both commands share the same packaging script. Contributing
The official DSH core uses published npm packages. Desktop Node, pnpm, Python, Office resources and command helpers are extracted from official installers. upstream.json locks their version, URLs, sizes and SHA-512 digests; no official source checkout is required. Initial packaging downloads the platform release. Windows build machines require 7-Zip to extract the installer.
The source layout separates application entry points from shared packages:
apps/desktop/ Electron application and installer
apps/web/ Web launch, deployment and verification
packages/ Shared plugins, providers, UI and contracts
profiles/ Personal and enterprise plugin composition
scripts/ Product build and release checks
After deploying WorkDSH Admin, the company administrator provides the public backend address when packaging Desktop. The configuration file contains only the address, for example:
{
"enterprise": {
"backendUrl": "https://enterprise.example"
}
}Set WORKDSH_DEPLOYMENT_CONFIG to this file. Packaging writes it to workdsh-config.json in application resources, and the employee entry uses the fixed address. Model API addresses and internal access keys are configured in the official model settings, outside the packaging configuration. See the Desktop packaging instructions.
Thanks to the maintainers and contributors of DeepSeek Harness, the foundation of our runtime and plugin system; Tencent SkillHub, whose public catalog API powers skill discovery; @cocofhu/skillhub, the bundled DSH SkillHub plugin; and dsh-market with the awesome-dsh-plugin catalog, which power community plugin discovery. WorkBuddy inspired the workspace design. The bundled skill-creator adaptation retains its Apache-2.0 notice. Feedback and contributions: GitHub Issues · Contributing
WorkDSH uses the MIT License. It is an independent community project and is not affiliated with, partnered with, authorized by, or endorsed by DeepSeek or WorkBuddy. Those names appear only to describe technical origins, compatibility, and design references. Upstream contributors shown on GitHub are inherited from synchronized commit history; this does not imply that they maintain this repository.