bailian-kb-dsh
面向 DeepSeek Harness 的 Bailian 知识库工具：通过 DashScope RAG API 提供 kb_search 和 kb_chat，以及 bl CLI 管理技能。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add bailian-kb-dsh@0.1.19Bailian Kb Dsh 以 bailian-kb-dsh 发布，当前版本为 0.1.19。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Knowledge-base retrieval tools for DeepSeek Harness, backed by Aliyun Model Studio (Bailian).
Bailian Console · 中文文档 · DeepSeek Harness · API Documentation
bailian-kb-dsh is a plugin (and dsh bundle) that gives a DeepSeek Harness agent access to knowledge bases hosted on Aliyun Model Studio (Bailian). It registers two model-facing tools — kb_search for raw evidence and kb_chat for grounded answers — and ships a settings page plus a management skill for the bl CLI.
Retrieval happens through retrieval services you deploy on Bailian: a service binds one or more knowledge bases to an embedding/rerank configuration and is addressed by its agent_id. The plugin keeps the list of deployed services in front of the model, so it can decide whether the question is answerable from your knowledge at all.
kb_search returns scored chunks with source references; kb_chat returns a complete grounded answerbl CLI login is adopted automaticallybailian-kb skill teaching the agent the bl CLI workflow for creating knowledge bases, ingesting documents, and deploying services@deepseek-ai/dsh-*), Node.js >= 22.12bl knowledge service create / bl knowledge service deploybl CLI (npm install -g bailian-cli) for anything on the management side — creating knowledge bases, ingesting documents, deploying services. Retrieval itself calls the API directly and never shells out, so kb_search / kb_chat work without itdsh plugin --profile web add bailian-kb-dsh
The CLI adds the bundle to the profile's layer stack; no manual YAML editing required. To remove it:
dsh plugin --profile web remove bailian-kb-dsh
Verify the plugin is composed — dsh --profile web --dump-config should list a tool-bailian-kb row.
After installation, Settings → Bailian KB appears in the web UI:
If you have already run bl auth login, the API key and workspace id are adopted once from ~/.bailian/config.json at startup. A value you deliberately clear is never re-filled.
# ~/.dsh/.env, or the credential store at ~/.dsh/.credentials.yaml
DASHSCOPE_API_KEY=sk-xxx # required
BAILIAN_WORKSPACE_ID=ws-xxx # required
BAILIAN_DEFAULT_RETRIEVE_AGENT_ID=aid-xxx # optional
BAILIAN_DEFAULT_CHAT_AGENT_ID=aid-xxx # optional
The bundle inserts its own entry into the profile; you can override it by id in ~/.dsh/cordis.patch.yml or the profile's patch file. An override replaces the whole config object (no deep merge):
- id: tool-bailian-kb
config:
defaultRetrieveAgentId: aid-search-service
defaultChatAgentId: aid-chat-service
chatTimeoutMs: 600000
Disable the plugin with - id: tool-bailian-kb plus disabled: true.
The config doubles as the bailian-kb settings section, so edits in the settings page or settings document apply to the next call without a restart.
| Field | Type | Default | Meaning |
|---|---|---|---|
workspaceId | string? | — | Bailian workspace id; the API host is the workspace subdomain https://<workspaceId>.<endpointHost> |
endpointHost | string | cn-beijing.maas.aliyuncs.com | Host suffix; replace for another region or a private deployment |
defaultRetrieveAgentId | string? | — | Service kb_search falls back to when the caller omits agent_id |
defaultChatAgentId | string? | — | Service kb_chat falls back to when the caller omits agent_id |
agentVersion | string? | — | beta (draft) or a published version number; defaults to the latest published version. Not exposed to the model |
chatTimeoutMs | number | 300000 | kb_chat timeout — the server side is a minutes-scale agentic loop |
| Value | Settings layer (settings page) | Entry config (profile patch) | Credential store / env |
|---|---|---|---|
DASHSCOPE_API_KEY | write-only control | — | DASHSCOPE_API_KEY |
| workspace id | ✅ workspaceId | ✅ workspaceId | BAILIAN_WORKSPACE_ID |
| default retrieval service | ✅ defaultRetrieveAgentId | ✅ defaultRetrieveAgentId | BAILIAN_DEFAULT_RETRIEVE_AGENT_ID |
| default Q&A service | ✅ defaultChatAgentId | ✅ defaultChatAgentId | BAILIAN_DEFAULT_CHAT_AGENT_ID |
Every value is re-read per call, so a rotated key or a switched workspace takes effect immediately. The API key and workspace id are mandatory: without them the tools fail with a message pointing at these configuration paths. Default services are optional — when the workspace has exactly one deployed service for a scene, that one is used.
| Tool | Parameters | Returns |
|---|---|---|
kb_search | query, agent_id (required), top_k? (default 5, applied client-side), images? (image URLs for multimodal) | Scored chunks with source references, plus a total |
kb_chat | message, agent_id (required) | The complete answer plus a request_id |
agent_id is required in both schemas: the schema cannot tell the model whether this deployment pins a default, and discovering a missing default at call time wastes a round-trip. The configured default is still honoured for programmatic calls that omit it.
The list of deployed services — id, name, and scene — is injected into the conversation as a context message, refreshed periodically and whenever a bl knowledge service command changes the inventory. Long lists are truncated with the total stated, so the model never mistakes a partial list for the full inventory.
agent_id that no longer exists, so the service list is refreshed and appended to the error message for immediate recovery~/.dsh/.env, ~/.dsh/.credentials.yaml, the settings page) and links to the console key pagekb_chat timeout — the message explains the server-side multi-turn retrieval and suggests retrying or switching to kb_searchkb_chat buffers the server stream, so there is no progress output while it runs.top_k is a client-side cut: the request body carries no such parameter, and how many chunks the server returns is decided by the service configuration.Product docs retrieval, not Service 1).pnpm --filter bailian-kb-dsh run build # tsc → dist/ (node half) + tsdown → dist/web/client.js (browser half)
pnpm --filter bailian-kb-dsh run typecheck # node and web tsconfigs
pnpm --filter bailian-kb-dsh run test
For local integration, add the working copy to a dev profile (the patch file is watched by HMR):
dsh plugin --profile dev add <this-repo>/packages/bailian-kb-dsh
Internal design notes — context injection strategy, service cache layout, refresh triggers — live in docs/kb-dsh/runtime-behavior.md; the maintenance checklist is docs/agents/dsh-plugin.md.
Bug reports, feature requests, and PRs are welcome. See CONTRIBUTING.md for developer setup and the contribution workflow.