@tencentcloudadp/dsh-adp

Adp

Tencent Cloud ADP 作为 DeepSeek Harness 的外部插件包

目标 Profile

插件会安装到这里；不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add @tencentcloudadp/dsh-adp@0.1.2

Settings → Plugins → Tencent Cloud ADP card

兼容性与来源证明

Adp 以 @tencentcloudadp/dsh-adp 发布，当前版本为 0.1.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

DSH 兼容范围: *
运行环境: web
发布来源: npm
Registry 更新时间: 2026/9/10

版本

0.1.2stable

2026/9/10

0.1.1stable

2026/8/24

README

@tencentcloudadp/dsh-adp

Tencent Cloud ADP as a DeepSeek Harness plugin bundle.

English · 中文

This plugin connects a DSH profile to Tencent Cloud ADP: gateway models (Hunyuan and friends), Hunyuan AI web search, the API/MCP plugin marketplace, the skill plaza, and ADP apps as ask tools. It is not ADP Worker.

Install

dsh plugin --profile web add @tencentcloudadp/dsh-adp
dsh web

Then open Settings → Plugins → Tencent Cloud ADP and fill in credentials (next section). Install issues (stale plugin name, pnpm build approval): docs/pitfalls.md.

Configure

ADP has three credential planes. The patch stores reference names (ADP_API_KEY, …); values live in $DSH_HOME/.credentials.yaml or the environment.

Official ADP API docs cover control-plane AKSK and AppKey SSE chat. They do not document the OpenAI-shaped model gateway this plugin also uses. Endpoints and key sources: API overview. Planes and error codes: docs/credentials.md.

Settings → Plugins → Tencent Cloud ADP card

Plane	Reference	Official source	If missing
Tool Key	`ADP_API_KEY`	Create a Tool Key in the upper section of the site’s Key Management page	LLM / search / plugin calls fail with `MISSING_CREDENTIAL`
SecretId / SecretKey	`ADP_SECRET_ID` / `ADP_SECRET_KEY`	Public cloud: CAM API keys. Independent site: ADP console Key Management	Model / plugin / app catalogs stay empty
Per-app AppKey	`TENCENT_ADP_APP_KEY` (subagent default) or `ADP_APP_KEY_*`	App publish → API management or app Invoke (SSE)	Subagent / ask tools cannot call the published app

1. Open ADP

Register and complete real-name verification, then open the product (product overview). First login creates one enterprise and a default workspace; that workspace is not the string default_space this plugin ships in the patch (workspace overview).

Site	Console	Control host	Agent SSE
Independent site	adp.tencent.com	`capi.adp.tencent.com`	`https://adp.tencent.com/adp/v2/chat`
Public cloud	adp.cloud.tencent.com	`adp.tencentcloudapi.com`	`https://wss.lke.cloud.tencent.com/adp/v2/chat`

Both sites complete against https://api.adp.cloud.tencent.com/chat/completions (no /v1). There is no api.adp.tencent.com.

2. Get SecretId / SecretKey

Public cloud — CAM AKID… key (36 characters):

Open CAM → API Key Management.
Create a key if the list is empty (root account access keys). Copy SecretId and SecretKey at creation time; SecretKey is shown only once after 2023-11-30.
Sub-accounts need ADP (formerly Large Model Knowledge Engine) read/write on the CAM role (FAQ). Collaborator accounts are not supported (122569).

Independent site — ADP console key (~26 characters, not AKID):

Sign in at adp.tencent.com.
Open Key Management and copy SecretId / SecretKey (API overview · independent site).

That pair signs control-plane calls (DescribeModelList, DescribeSpaceList, marketplace). It is not ADP_API_KEY.

3. Get the Tool Key (`ADP_API_KEY`)

Independent site: open Key Management and create a Tool Key in the upper section.
Public cloud: open Key Management and click Create Tool Key in the upper section.

The Tool Key is used for Hunyuan / DeepSeek completions, Hunyuan search, and API/MCP plugin calls.

4. Optional: AppKey

Used by subagent_adp and adp_ask / adp_ask_<slug> (SSE to a published app), not for picking adp:Hunyuan/hy3. The provider migrated from dsh-plugin-subagent keeps its original default reference name, TENCENT_ADP_APP_KEY.

Publish the app.
Open App Publish → Service Status → API Management, or App Management → Invoke, and copy AppKey (104209, 105560).

5. Fill the DSH card

Run dsh web on loopback (127.0.0.1). Credential writes are loopback-only.
Settings → Plugins → Tencent Cloud ADP.
Choose Independent site or Public cloud.
Paste the Tool Key, SecretId, and SecretKey. Save. Values go through credentials.set into $DSH_HOME/.credentials.yaml.
After AKSK is stored, the card lists workspaces from DescribeSpaceList. Pick one. Public-cloud app and plugin calls need a real SpaceId; the patch default default_space is not a workspace on most accounts (control-plane 4510004). If the list is empty, paste a SpaceId from the ADP console (workspaces).
Paste AppKey if you will use ask tools. Save again.

A Claw-style “build the app entirely via API” walkthrough (CreateSpace → CreateApp → CreateAgent → CreateRelease → chat) is 133869. That path is AppKey SSE, not this plugin’s gateway adapter.

What you get

adp-core, llm-adp, web-adp, plugins-adp, skills-adp, control-adp, subagent-adp, and tool-subagent-adp start with the plugin. agents-adp remains available from the package's /agents entry but is not loaded by the default bundle:

Model picker — Tencent Cloud ADP group

Select adp:Hunyuan/hy3 (or another gateway model) and complete a tool-using turn. How catalog vs completions are wired: docs/seams.md.
web_search through Hunyuan AI search when this provider is selected (China-centric index).
Enable an API or MCP marketplace plugin via adp_plugin_list / adp_plugin_enable, or enabledPluginIds. Public-cloud plugin/app calls need the workspace chosen above.
Generated media links (~24h COS) are saved into the workspace as saved_files.
Skill plaza as a ctx.skills provider (entries without download URLs stay in list only).
Optional agents-adp provides adp_provision_agent and adp_ask / adp_ask_<slug>; manually load @tencentcloudadp/dsh-adp/agents when the legacy plain-tool mode is needed.
subagent_adp — run a published ADP app as a real DSH child Agent; reasoning, remote tool traces, and the final reply are projected into its native child session. Its AppKey defaults to TENCENT_ADP_APP_KEY; unless endpoint is explicit, every run follows the active adp-core site's SSE URL.
adp_list_actions / adp_call with allowMutating for App/Agent/Release CRUD. Mutating calls require approval.

Documentation

docs/credentials.md — where each key comes from and what breaks without it
docs/seams.md — contracts between this plugin and DSH
docs/pitfalls.md — known traps
docs/verification.md — manual checklist

Verify

pnpm test         # simulated HTTP; no secrets; CI gate
pnpm test:live    # real account; skips when env is absent

Contributing

Issues and pull requests are welcome on GitHub. Run pnpm test before opening a PR.

License

README

@tencentcloudadp/dsh-adp

Tencent Cloud ADP as a DeepSeek Harness plugin bundle.

English · 中文

Install

dsh plugin --profile web add @tencentcloudadp/dsh-adp
dsh web

Then open Settings → Plugins → Tencent Cloud ADP and fill in credentials (next section). Install issues (stale plugin name, pnpm build approval): docs/pitfalls.md.

Configure

ADP has three credential planes. The patch stores reference names (ADP_API_KEY, …); values live in $DSH_HOME/.credentials.yaml or the environment.

Settings → Plugins → Tencent Cloud ADP card

Plane	Reference	Official source	If missing
Tool Key	`ADP_API_KEY`	Create a Tool Key in the upper section of the site’s Key Management page	LLM / search / plugin calls fail with `MISSING_CREDENTIAL`
SecretId / SecretKey	`ADP_SECRET_ID` / `ADP_SECRET_KEY`	Public cloud: CAM API keys. Independent site: ADP console Key Management	Model / plugin / app catalogs stay empty
Per-app AppKey	`TENCENT_ADP_APP_KEY` (subagent default) or `ADP_APP_KEY_*`	App publish → API management or app Invoke (SSE)	Subagent / ask tools cannot call the published app

1. Open ADP

Site	Console	Control host	Agent SSE
Independent site	adp.tencent.com	`capi.adp.tencent.com`	`https://adp.tencent.com/adp/v2/chat`
Public cloud	adp.cloud.tencent.com	`adp.tencentcloudapi.com`	`https://wss.lke.cloud.tencent.com/adp/v2/chat`

Both sites complete against https://api.adp.cloud.tencent.com/chat/completions (no /v1). There is no api.adp.tencent.com.

2. Get SecretId / SecretKey

Public cloud — CAM AKID… key (36 characters):

Open CAM → API Key Management.
Create a key if the list is empty (root account access keys). Copy SecretId and SecretKey at creation time; SecretKey is shown only once after 2023-11-30.
Sub-accounts need ADP (formerly Large Model Knowledge Engine) read/write on the CAM role (FAQ). Collaborator accounts are not supported (122569).

Independent site — ADP console key (~26 characters, not AKID):

Sign in at adp.tencent.com.
Open Key Management and copy SecretId / SecretKey (API overview · independent site).

That pair signs control-plane calls (DescribeModelList, DescribeSpaceList, marketplace). It is not ADP_API_KEY.

3. Get the Tool Key (`ADP_API_KEY`)

Independent site: open Key Management and create a Tool Key in the upper section.
Public cloud: open Key Management and click Create Tool Key in the upper section.

The Tool Key is used for Hunyuan / DeepSeek completions, Hunyuan search, and API/MCP plugin calls.

4. Optional: AppKey

Publish the app.
Open App Publish → Service Status → API Management, or App Management → Invoke, and copy AppKey (104209, 105560).

5. Fill the DSH card

Run dsh web on loopback (127.0.0.1). Credential writes are loopback-only.
Settings → Plugins → Tencent Cloud ADP.
Choose Independent site or Public cloud.
Paste the Tool Key, SecretId, and SecretKey. Save. Values go through credentials.set into $DSH_HOME/.credentials.yaml.
After AKSK is stored, the card lists workspaces from DescribeSpaceList. Pick one. Public-cloud app and plugin calls need a real SpaceId; the patch default default_space is not a workspace on most accounts (control-plane 4510004). If the list is empty, paste a SpaceId from the ADP console (workspaces).
Paste AppKey if you will use ask tools. Save again.

What you get

Model picker — Tencent Cloud ADP group

Select adp:Hunyuan/hy3 (or another gateway model) and complete a tool-using turn. How catalog vs completions are wired: docs/seams.md.
web_search through Hunyuan AI search when this provider is selected (China-centric index).
Enable an API or MCP marketplace plugin via adp_plugin_list / adp_plugin_enable, or enabledPluginIds. Public-cloud plugin/app calls need the workspace chosen above.
Generated media links (~24h COS) are saved into the workspace as saved_files.
Skill plaza as a ctx.skills provider (entries without download URLs stay in list only).
Optional agents-adp provides adp_provision_agent and adp_ask / adp_ask_<slug>; manually load @tencentcloudadp/dsh-adp/agents when the legacy plain-tool mode is needed.
subagent_adp — run a published ADP app as a real DSH child Agent; reasoning, remote tool traces, and the final reply are projected into its native child session. Its AppKey defaults to TENCENT_ADP_APP_KEY; unless endpoint is explicit, every run follows the active adp-core site's SSE URL.
adp_list_actions / adp_call with allowMutating for App/Agent/Release CRUD. Mutating calls require approval.

Documentation

docs/credentials.md — where each key comes from and what breaks without it
docs/seams.md — contracts between this plugin and DSH
docs/pitfalls.md — known traps
docs/verification.md — manual checklist

Verify

pnpm test         # simulated HTTP; no secrets; CI gate
pnpm test:live    # real account; skips when env is absent

Contributing

Issues and pull requests are welcome on GitHub. Run pnpm test before opening a PR.

Adp

兼容性与来源证明

版本

Adp

README

@tencentcloudadp/dsh-adp

Install

Configure

1. Open ADP

2. Get SecretId / SecretKey

3. Get the Tool Key (ADP_API_KEY)

4. Optional: AppKey

5. Fill the DSH card

What you get

Documentation

Verify

Contributing

License

兼容性与来源证明

版本

README

@tencentcloudadp/dsh-adp

Install

Configure

1. Open ADP

2. Get SecretId / SecretKey

3. Get the Tool Key (ADP_API_KEY)

4. Optional: AppKey

5. Fill the DSH card

What you get

Documentation

Verify

Contributing

License

3. Get the Tool Key (`ADP_API_KEY`)

3. Get the Tool Key (`ADP_API_KEY`)