插件安装与启用
确认宿主平台、安装位置和启用步骤,再查看安装后增加的能力。
- 宿主平台
- 待补充
- 安装位置
- 待补充
- 安装步骤
- 待补充
- 启用方式
- 待补充
- 增加的能力
- 待补充
- 所需权限
- 待补充
- 限制与边界
- 待补充
先看适用边界
来源资料与任务效果分开判断。
- 适用平台
- DeepSeek Harness
- 任务实效
- 暂无任务实测结论
审核通过不等于官方出品。安装前请核对实际作者、所需权限、平台版本与运行成本。
The web GUI host's workspace-directory picker is a capability seam. The abstract `DirectoryPicker` service (`ctx.directoryPicker`) is its Service Definition. Its only method, `capability()`, returns a discriminated union describing how an operator selects a directory. Backends differ in user interaction, not just implementation: `{ kind: 'native', pick(signal) }` opens one native OS chooser on the host display ([`-native`](../directory-picker-native/README.md)); `{ kind: 'browse', list(path?), createDirectory(path, name) }` provides listing and creation operations for an in-app browser, which works for remote clients that cannot reach an OS chooser ([`-browse`](../directory-picker-browse/README.md)). Consumers switch on `capability().kind`; the union derives from the merge-extensible `DirectoryPickerCapabilities` map, and a new backend adds its variant there through declaration merging. For an unknown kind, consumers hide directory picking rather than fail. The capability object must be stable for the service lifetime. Each backend package also has a browser entrypoint that registers the matching interaction in ui-workspace's directory-flow slots, so one composition row selects both the host capability and the client flow. A composition that should choose at runtime mounts [`-auto`](../directory-picker-auto/README.md), which inspects the host once at boot and mounts the matching backend row.
能力
它能让 Agent / 使用者做什么。
- 适用 Agent:DeepSeek Harness
- 适配模型:DeepSeek
安装与获取
可复现安装方式。
@deepseek-ai/dsh-host-directory-picker
来源与核实
保留来源、时间与置信度,供回溯。
实效证据
来源可信不等于任务有效。
暂无通过审核、可复现的同任务 A/B 运行证据;本档案仅证明来源可信,不代表实测有效。