dsh-workforce

Readme

# DSH Workforce

English | [中文](README.zh.md)

DSH Workforce is a local Agent organization and project collaboration plugin for DeepSeek Harness (DSH). It brings long-lived Agents, project memberships, Work conversations, management conversations, and structured Meetings into one Workforce experience while continuing to use DSH for models, Tools, Skills, Sessions, and runtime execution.

Current version: `V0.1.1`

## Highlights

- WorkforceCenter manages long-lived Agent profiles, personas, model bindings, Tools, and Skills across projects.
- Project Sidebar shows the Workforce Project, Agents, Work, and Meetings associated with the active Workspace.
- Each Project × Agent has one reusable Work conversation and one management conversation.
- Project facts remain in the project directory, while long-lived Agent profiles remain in the user-level WorkforceCenter.
- Project Meetings provide participants, discussion rounds, explicit responses, and durable decisions without an external Room plugin.
- V0.1.1 is local-first, single-user, and backed by SQLite.

## Requirements

- Node.js 24
- DeepSeek Harness `>=0.1.1-rc.2`

Workforce never asks users to enter a model provider, API key, or model name inside the plugin. DSH remains the source of truth for model catalogs and provider configuration. If a DSH model source becomes unavailable, Workforce asks the user to rebind the Agent.

## Install

Pin release tags so unverified upstream changes cannot silently alter a working profile:

```bash
dsh plugin --profile web add github:esonx/dsh-workforce#v0.1.1
dsh web
```

You can also install the tarball attached to the GitHub Release:

```bash
dsh plugin --profile web add ./dsh-workforce-0.1.1.tgz
dsh web
```

See [Installation and upgrades](docs/INSTALLATION.md) for the complete procedure.

## Get started

1. Start DSH Web normally and open a Workspace.
2. Select **Workforce** in the lower-left navigation.
3. If the active Workspace is not yet a Workforce Project, select **Go!**.
4. Open **WorkforceCenter** to create or configure an Agent.
5. Add Agents to the current project, then open a management or Work conversation, or create a Meeting.

The project-local `.workforce/` directory stores project facts. `workforce-center/center.sqlite` under the user's DSH Home stores long-lived Agent profiles. Neither location stores provider API keys. See the [User guide](docs/USER_GUIDE.md) for backup and recovery guidance.

## Security boundary

- V0.1.1 assumes one local user operating DSH. It does not provide multi-user login, enterprise RBAC, or remote service deployment.
- DSH and plugins installed in the same Profile share a trusted host boundary. Do not install untrusted plugins in that Profile.
- loopback/Origin/`trustedHosts` constrain browser transport; they are not Host user authentication.
- DSH `allowed-once` authorizes only the current execution; it is not a persistent or replayable Host management capability.
- External Workspace, Session, and Preset identifiers are never Workforce organization primary keys.
- The browser cannot nominate a Project root, Session ID, provider key, or runtime authorization identity.
- Cross-Project access is denied by default. Unknown or partially completed external operations are never replayed automatically.

See [SECURITY.md](SECURITY.md) to report a security issue.

## V0.1.1 limitations

- Local, single-user operation only; multi-user accounts, multiple instances, and shared-database deployments are unsupported.
- Each Project × Agent can have at most one active Work conversation and one active management conversation. Historical conversation expansion is planned for a later version.
- Meetings are project-local structured collaboration records; free-form Room/private-chat channels are not part of the V1 product surface.
- PRD and Dev/Taskboard are still future Sidebar entry points.
- Memory V1 provides scoped long-term Agent memory extraction, consolidation, retrieval, UI governance, and policy-controlled Global promotion. Knowledge-base imports are not included.
- DSH is evolving quickly. Validate Workforce in a test Profile before upgrading DSH in a working environment.

## Architecture boundary

Workforce owns long-lived Agents, Project Memberships, Work, Meetings, external bindings, and its V1 Memory engine. DSH continues to own model execution and Sessions; task facts remain with their authoritative project plugin. See the [Architecture overview](docs/ARCHITECTURE.md).

## Uninstall

```bash
dsh plugin --profile web remove dsh-workforce
```

Uninstalling the plugin does not delete project `.workforce/` data or the WorkforceCenter SQLite database. This preserves reinstall and recovery options. Back up and remove those files manually only when they are no longer needed.

## License and third-party components

DSH Workforce is licensed under the [Apache License 2.0](LICENSE). See [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md) for runtime and companion component information.

Maintainer: `esonx`

Public repository: [github.com/esonx/dsh-workforce](https://github.com/esonx/dsh-workforce)