BailingHub for DeepSeek Harness

简体中文 | English

Use your local DeepSeek Harness Agent to operate the admin side of an online store, SaaS product, or other business system through BailingHub. Ask it to look up data, update records, or run other actions available to the connected account. The existing business identity, permissions, and approval rules still apply, and BailingHub keeps the authorization and action trail.

For example, depending on what the connected business system has exposed, you can ask the local Agent to:

• find an order, customer, product, or employee record;
• update an allowed field or business status;
• run another permitted admin action;
• return the result while BailingHub records the corresponding tool steps.

Reasoning and tool orchestration stay in DSH. BailingHub supplies the authorized business context, available capabilities, approval state, invocation recovery, and audit records required for the local Agent to act safely.

This is an independent community integration. It is not developed, certified, endorsed, or recommended by DeepSeek.

Current stable line: [email protected] uses the native Agent Client flow documented below. Public 0.1.1 remains available only as the explicit static MCP compatibility path.

For the shortest end-user path, follow the three-minute getting started guide.

How the 0.2 Agent Client fits together

DeepSeek Harness local Agent
  -> dsh-bailinghub native Cordis adapter
  -> bailinghub-mcp-server/sdk
  -> BailingHub Agent Auth + Agent API
  -> operator-selected business integration and final authorization

The packages have separate responsibilities:

• BailingHub Core owns Agent Auth, trusted business identity, runtime context, knowledge and memory projection, capability governance, approvals, invocation state, and audit records.
• bailinghub-mcp-server/sdk owns browser login, PKCE, credential storage, refresh, Hub/client/workspace connection isolation, and HTTP DTO mapping.
• dsh-bailinghub owns only DSH session, prompt, command, and dynamic-tool lifecycle integration. It does not store credentials or call a business API directly.

This Agent Client is not the BailingHub executor. The executor receives jobs from the Hub for work that must run near a machine; the Agent Client keeps the interactive reasoning loop on the user's local DSH Agent.

Before installing

The deployer and business integrator must prepare these public identifiers in BailingHub:

1. A reachable HTTPS BailingHub deployment with the matching Agent Auth and Agent API contracts.
2. A public Agent Client application id (clientAppId).
3. At least one authorized workspace. In Agent Client v1, the workspace id is the BailingHub route id.
4. A business authorization page and governed ACC/Tool Provider integration behind that route.

The end user does not enter a business API URL, business login credential, Tool Provider signing secret, BailingHub Client Token, or model-provider key into this plugin.

Install the 0.2 line

Prerequisites:

• Node.js 22.19.0+ or 24+;
• pnpm and DeepSeek Harness 0.1.0-rc.7;
• the BailingHub preparation above.

Install the exact stable version into the DSH Web profile:

npm install --global pnpm @deepseek-ai/[email protected]
dsh plugin --profile web add [email protected]

…