BailingHub for DeepSeek Harness
简体中文 | English
Ask your local DeepSeek Harness Agent to work with a business system connected to BailingHub: find records, update allowed fields, and follow the system's existing approval rules. BailingHub records which authorization was used and what each business action returned.
Version 0.4.0 lets one conversation use several authorizations for the same system. For example, after independently authorizing Store A and Store B, select both for a new conversation and ask:
Compare today's sales at Store A and Store B. Show each store separately.
The Agent can choose the right authorization for each call without asking you to switch the active connection. Available actions still depend on the capabilities and permissions your system exposes. This release does not provide orchestration across different systems or routes.
It also keeps the visible conversation together with links to its business actions. If uploading that record fails, it can retry after reconnecting or restarting without repeating those actions.
This is an independent community integration, not a plugin developed, certified, endorsed, or recommended by DeepSeek.
Install and start
You need Node.js 22.19.0+ or 24+, pnpm, and a compatible DeepSeek Harness release. Your administrator must first connect the business system to BailingHub. The matched release set is BailingHub Core 0.6.1 → BailingHub MCP/SDK 0.4.0 → this plugin 0.4.0.
npm install --global pnpm @deepseek-ai/[email protected]
dsh plugin --profile web add [email protected]The plugin installs its exact [email protected] dependency automatically. For an existing installation, read the 0.3 to 0.4 migration steps.
Follow the getting started guide to enter your administrator's four public connection values and authorize in the browser. Do not put a business password, Client Token, signing secret, or model-provider key into this plugin's settings or chat.
Choose the accounts for each conversation
Authorize each account separately through the original business authorization page. Give each connection a clear local name, such as Store A and Store B, and verify the actual identity on that page. The name is a label you provide; it does not prove identity or grant permission. Names like default and default-2 do not tell the Agent which store you mean.
In a new conversation, before the first message, run:
/bailinghub connections list
/bailinghub scope set <store-a-connection-key> <store-b-connection-key>
/bailinghub scopeReplace the placeholders with the fixed keys from the list, not connection names. You can select just one account. Multiple selections must share the same Hub, Client App, and workspace. Wait for the command to confirm the selection, then send your request.
New conversations start as ordinary chat until you select their business scope. Logging in or changing the default connection does not enable business tools. /bailinghub scope none explicitly chooses ordinary chat. The first user message freezes the selection; start a new conversation to change accounts or move from ordinary chat to business access.
For the selected accounts, matching tools are shared. The Agent chooses the authorization for each call; it does not receive credentials. Every action still uses that account's own permissions and approval rules. An approval-required action continues the original call after approval while that conversation is still running.
If any selected authorization is revoked, replaced, or cannot be checked, business access pauses for the whole conversation. The plugin never silently switches to another account. A temporary connection failure can be retried with the same original selection after the network returns. A confirmed revocation or identity change requires a new conversation with a valid selection.
Follow the conversation and its actions
With Core 0.6.1 and SDK 0.4.0, BailingHub can show the visible user and assistant messages, turn boundaries, and links to the original business runs as one conversation record. Each authorization also keeps its own business-call record; the combined reply is not copied into every account's memory.
/bailinghub archive status
/bailinghub archive syncarchive status shows whether the visible record has uploaded. archive sync retries the saved record without running the business actions again. This is separate from /bailinghub sync, which retries a pending run completion in the currently running conversation.
| Status | What it means |
|---|---|
synced | Saved events have been acknowledged by the Hub; this does not prove a business action succeeded |
pending | Upload is unfinished; retry when the connection is available |
blocked | Original authorization checks prevent upload; inspect /bailinghub scope |
unsupported | The connected SDK or Hub does not support this archive contract |
storage_error | A local write failed; some visible events may not yet be safely saved |
recovery_gap | Available DSH history shows missing archive events; the record is incomplete |
Reopening a saved business conversation restores its original selected accounts only after every original authorization is checked. If it was reopened offline, reconnect and run /bailinghub archive sync or /bailinghub scope in that same conversation to retry the check. This recovers scope and saved uploads, not pending business invocations or approvals after a process restart. A saved draft that never started needs explicit selection again. An older started conversation without a valid saved scope cannot adopt today's default account.
What is shared and stored
All selected accounts' context and your visible user request share the same local Agent/model conversation. The combined archive requires the full selected authorization set; an authorization for only one member is not sufficient to read the mixed conversation. Use separate conversations when those accounts' data must remain separate.
The plugin captures visible text from business turns enabled with this version, not all past conversations, attachments, or hidden reasoning. It cannot remove arbitrary secrets pasted into visible text. Missing local writes are reported as gaps when detectable; hosts without durable history report unverified coverage.
The private local outbox contains plaintext visible task text, including events already uploaded. It stays under the DSH home until the host/operator removes it; there is no automatic retention cleanup. Removing it does not delete the Hub's record. Credentials remain in SDK-owned secure storage. Review Privacy and Security before enabling business access.
Commands and administration
| Command | Purpose |
|---|---|
/bailinghub doctor | Check setup, SDK, authorization, and workspace without printing credentials |
/bailinghub login | Authorize the selected connection in the browser |
/bailinghub status | Inspect that connection's authorization |
/bailinghub connections list | List connection labels, fixed keys, and authorization state |
/bailinghub connections add <name> <hub-url> <client-app-id> <workspace> | Register a connection and select it for connection management; quote names containing spaces |
/bailinghub connections use <name-or-key> | Choose which connection to manage or authorize; does not change a conversation's scope |
/bailinghub connections remove <name-or-key> | Revoke its Agent Session before removing local credentials |
/bailinghub workspaces | List workspaces allowed by the current authorization |
/bailinghub use <workspace> | Select another already-authorized workspace for connection management |
/bailinghub logout | Revoke and remove the selected Agent Session |
Connection management and scope selection are user commands, not model tools. Reauthorizing the same trusted identity replaces its old connection and Agent Session. A different identity remains independent. If login reports cleanup required, the new connection is already authorized: inspect the listed old entry and retry its removal, rather than authorizing again. Details are in the host contract.
For integrators
DSH owns reasoning and tool orchestration. BailingHub Core owns trusted identity, governance, approvals, invocation state, and audit. The SDK owns browser authorization, secure credentials, and HTTP mapping. This plugin only adapts DSH sessions, prompts, commands, tools, and visible events; it does not call your business API directly or govern unrelated DSH tools.
Existing business integrations continue exposing the same capabilities and authorizing each identity separately. Custom DSH hosts must implement the scope selection and restore APIs and display confirmation before the first message. The native slash commands already use those APIs. Tool envelopes, persistence, event schemas, and recovery limits are documented in the Agent Client contract.
Use Native Tool Mode. DSH Code Mode is deliberately degraded because it cannot safely present the current-turn dynamic schemas. See the compatibility matrix.
Legacy 0.1.1 and feedback
Public [email protected] remains the separate static MCP compatibility path. It starts [email protected], uses one operator-provided route-scoped Client Token, and leaves orchestration in BailingHub. Version 0.4.0 does not read or convert that credential. Keep the exact legacy version when using that path and follow the migration guide.
Report issues at GitHub Issues with versions and redacted errors. Do not include tokens, private URLs, personal data, or production payloads. Compatibility tests and package downloads are not evidence of production adoption.
