dsh-cua-macos

DSH PLUGIN会话与消息

仓库 elfgzp/dsh-cua-macos

会话与消息 L4 · 沙盒安装通过 安全审查:低风险 可信度:银 可安装插件
安装这个插件

为 DeepSeek Harness 提供 macOS 计算机操作能力:读取辅助功能树、截屏并驱动真实桌面应用。

一句话选型结论

按资料字段整理

dsh-cua-macos 是会话与消息类的 DSH 可安装插件,验证等级 L4 · 沙盒安装通过,安全审查为低风险,列出 4 项功能,有可直接复制的安装命令。验证通过不等于安全:插件会读写文件、执行命令或联网,装前先到仓库确认它做了什么;涉及密钥或系统权限的,建议先在隔离环境试装。

分类会话与消息 收录类型可安装插件 验证等级L4 · 沙盒安装通过 安全审查低风险
验证等级 L4 L4 · 沙盒安装通过
GitHub 星标 0 复刻 0 · 未关闭 issue 未标注
最近更新 2026-11-02 创建于 2026-11-02
README 11.6 KB 正文体量,越大说明说明书写得越细

安装

可安装插件
在 DSH 里执行,装完用 dsh plugin list 确认已挂上;标了 L4 / L5 的命令已在沙盒里真实跑通
dsh plugin --profile web add github:elfgzp/dsh-cua-macos#v0.1.0
  1. 1
    确认版本与运行环境

    仓库没有标注兼容版本与 Node.js 要求,先确认你的 DSH 版本能装,再继续。

  2. 2
    执行安装命令

    在 DSH 里执行上面的命令;多包仓库要注意区分具体子包名,别装错包。

  3. 3
    确认已挂载

    用 dsh plugin list 查看列表里是否出现这个插件,出现即挂载成功。

  4. 4
    试跑并检查权限

    加载后跑一个最小用例,确认它能正常工作;同时看它申请了哪些文件、命令或网络权限。

兼容 DSH 版本未标注版本不匹配时安装会报错
Node.js 要求未标注来自仓库 package.json 的 engines 字段
前置依赖无需要同时安装的同级依赖
npm 包名未发布到 npm可用 npm view 查看包信息

能做什么

4 项功能
字段来自项目仓库与公开索引,中文说明由本站标注

dsh-cua-macos:为 DeepSeek Harness 带来 macOS 桌面操作能力

  • 读取 macOS 辅助功能树
  • 截屏并识别界面
  • 模拟输入驱动桌面应用
  • 注册 cua 工具供 Agent 调用

适用场景

视觉识别

上游标签

deepseek-harnessdshdsh-plugin

验证等级与安全审查

L4 · 沙盒安装通过
自动化流程结论,不是人工审核
验证等级L4 · 沙盒安装通过安装命令在隔离沙盒内真实执行成功,无依赖错误
安全审查低风险静态分析结论,未标注不代表已通过审查
仓库健康度活跃按仓库活跃度与最近更新时间给出
可信度银综合仓库活跃度与验证结果

上面的结论来自上游最近一次自动化验证(2026-11-10): 同一套检查会在插件发新版后重跑,页面显示的是最新一次的逐项结果。

逐项检查结果

L1 · 已找到 ✓ 通过
  • L1.0_DEFAULTED_FROM_L3 由 L3 推定 默认通过——L3 安装规范已通过(全库 L3 扫描策略)
L2 · 结构化 ✓ 通过
  • L2.0_DEFAULTED_FROM_L3 由 L3 推定 默认通过——L3 安装规范已通过(全库 L3 扫描策略)
L3 · 安装规范 ✓ 通过
  • L3.1_INSTALL_COMMAND_PARSED 安装命令已解析 方式:安装规范解析
  • L3.2_DSH_VERSION_DECLARED DSH 版本已声明 方式:DSH 版本声明
L4 · 安装已测 ✓ 通过
  • L4.1_INSTALL_EXECUTED_CONFINED 受限沙盒内执行安装 方式:沙盒安装执行
  • L4.2_INSTALL_SUCCESS 沙盒安装成功 方式:沙盒安装执行
  • L4.3_ARTIFACT_CONFIRMED 安装产物已确认 方式:沙盒安装执行
L5 · 运行已测 ✕ 未通过
  • L5.1_INSTALL_PASSED_SANDBOXED 沙盒安装通过 方式:沙盒安装执行
  • L5.2_WEB_BOOT_READY Web 启动就绪 插件目录树加载失败
  • L5.3_HTTP_SERVED HTTP 服务响应

风险详情

  • 结论说明 静态扫描 低;动态审计无结论(以下以静态为准)→ 总评级 低。
  • 风险计数 严重 0 / 高 0

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 验证等级 L4:在沙盒里真实装过,依赖能装上,不是纸面声明。
  • 静态安全审查为低风险,没有发现明显可疑行为。
  • 有可直接复制的安装命令,不用自己翻文档找入口。
  • 列出了 4 项功能,能直接看出它解决什么问题。

先想清楚的地方

  • 没有声明 Node.js 版本要求,版本不匹配可能装不上。
  • 验证通过不等于安全:插件会读写文件、执行命令或联网,装前先到仓库确认它做了什么。

更适合

  • 需要在会话与消息场景里给 DSH 补能力的人。
  • 想装完就能用、不想自己排依赖的人。
  • 能接受在本地装依赖、愿意自己确认权限的人。

不太适合

  • 只使用 DSH 官方内置能力、不接受第三方插件的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
插件验证等级安全审查星标兼容版本安装命令
dsh-cua-macos当前 L4 · 沙盒安装通过 低风险 0 未标注 有
dsh-desktop L3 · 安装规范通过 低风险 3.0 万 未标注 无
openpets L4 · 沙盒安装通过 低风险 1,274 未标注 有
deeptide L4 · 沙盒安装通过 低风险 1,104 0.1.1-rc.2 有
jingyun-dsh L3 · 安装规范通过 低风险 1,004 未标注 有
study-mate 未做沙盒验证 未标注 856 未标注 无

仓库档案

会话与消息
字段来自项目仓库与公开索引,中文说明由本站标注
作者 / 维护方elfgzp仓库 dsh-cua-macos · 默认分支 未标注
分类会话与消息desktop
收录类型可安装插件声明了 dsh.bundle、可用 dsh plugin add 安装的条目
开发语言Swift仓库主语言
许可证MIT商用或二次分发前请确认条款原文
星标 / 复刻 / issue0 / 0 / 未标注收录时的数值,非实时
创建 / 更新2026-11-02 · 2026-11-02最后推送 未标注
本站收录2026-11-05首次进入本站目录的时间

README 全文

11.6 KB
作者原文,中文版优先;只做安全转义,不改内容

dsh-cua-macos

macOS Computer Use for DeepSeek Harness:
the agent reads accessibility trees, captures screenshots and drives real desktop
apps — the same capability shape as Anthropic's computer use, as a DSH plugin.

> This is not an official DeepSeek package. The official bundle
> @deepseek-ai/dsh-cua-bundle exists, but it only ships on the 0.2.2-alpha
> channel and cannot be installed on a 0.2.1-rc.5 profile. See
> Why a local bundle.

Status

Platform macOS on Apple silicon or Intel, DSH Host only
DSH version 0.2.1-rc.5 (pinned; the alpha line needs 0.2.2-alpha.2)
Requires macOS Accessibility + Screen Recording permission for the DSH process
Tool name cua

Why a local bundle

The official @deepseek-ai/dsh-cua-bundle:

  • ships only on the 0.2.2-alpha channel, which requires cordis ~4.0.6-alpha.1
    while a 0.2.1-rc.5 profile runs cordis 4.0.5;
  • expects a prebuilt native helper that the published npm tarball does not carry
    ("installed packages must already carry their native payload" — upstream defers
    helper distribution to the packaged Desktop app).

The three component packages are published on both lines, so this bundle mounts
the same rows at the versions that match the shipped runtime, and builds the
missing helper locally.

Row Package Role
cua-provider-registry @deepseek-ai/dsh-computer-use the exclusive computer-use provider slot
cua @deepseek-ai/dsh-experimental-cua-macos macOS native provider: AX tree, screenshots, input

@deepseek-ai/dsh-cua is not mounted as its own row: at 0.2.1-rc.5 it
exports only CuaConfig and installCua, with no apply, so the Loader cannot
mount it as a plugin. The macOS provider imports it as a library and calls
installCua, which registers the cua tool and the model guidance. The
0.2.2-alpha line does export an apply and does need its own row.

@deepseek-ai/dsh-attachment and @deepseek-ai/dsh-user-questions are listed as
ordinary dependencies because @deepseek-ai/dsh-cua imports them at runtime and
the Loader resolves them from the profile, not from the DSH installation.

Install

git clone https://github.com/elfgzp/dsh-cua-macos.git
cd dsh-cua-macos
./reinstall.sh

reinstall.sh resolves the native helper, installs it to
$HOME/.dsh/cua/dsh-cua-native, packs the bundle and installs it into the
profile. Restart DSH afterwards and start a new session.

Xcode is only needed when no prebuilt helper is available: reinstall.sh
downloads the arm64 or x86_64 binary from the GitHub Release first and compiles
from source only if that fails. See Prebuilt helper.

The bundle must be installed as a tarball or a git spec. pnpm's link: protocol
does not install a bundle's own dependencies, so a linked checkout would leave
@deepseek-ai/dsh-cua unresolvable.

To install from this repository instead of a local tarball:

./reinstall.sh desktop github:elfgzp/dsh-cua-macos

The native helper

@deepseek-ai/dsh-experimental-cua-macos ships the Swift sources of the
dsh-cua-native helper but no binary, and the Loader only compiles inside a DSH
source checkout. reinstall.sh therefore resolves it, in this order:

  1. a helper already present under native/bin/-/;
  2. the prebuilt binary attached to a GitHub Release (see
    Prebuilt helper);
  3. a local compile:
xcrun swift build \
--package-path native \
--scratch-path native/.build/runtime-arm64 \
--configuration release \
--product dsh-cua-native \
--arch arm64

The result is copied to $HOME/.dsh/cua/dsh-cua-native, which is where
cordis.patch.yml points it through a !!js expression — so the patch itself
stays machine-independent.

Only step 3 requires Xcode or the Command Line Tools. The package declares
swift-tools-version: 6.0, but the vendored sources need Swift 6.3 or newer
to compile in the Swift 6 language mode; with an older toolchain the build stops
at sending 'self' risks causing data races in SharedHelperServer.swift. On a
machine without a recent enough toolchain, step 2 is what makes the install work.

Prebuilt helper

.github/workflows/build-helper.yml builds the helper in CI and attaches it to
the GitHub Release for a v* tag:

Asset Runner Build command
dsh-cua-native-darwin-arm64 (+ .sha256) macos-26 (arm64) swift build --arch arm64
dsh-cua-native-darwin-x86_64 (+ .sha256) macos-26 (arm64) swift build --arch x86_64

Both are cross-compiled on the arm64 runner, so the workflow does not depend on
GitHub's hosted Intel images, which are being retired; the x86_64 binary is a
real Mach-O 64-bit executable x86_64 and is exercised through Rosetta 2 in CI.
The image is pinned to Xcode 26.6 (Swift 6.3.3) because the Swift 6.2 toolchain
on the older macos-15 image rejects this vendored source with sending 'self' risks causing data races; the workflow fails with an explicit message if the
runner ever offers only an older Swift.

Each binary is ad-hoc signed (codesign --force --sign - --identifier dsh-cua-native), the same way a local swift build on macOS produces it, so the
CI artifact and a locally compiled helper are interchangeable.

The workflow also runs on workflow_dispatch and on every pull request; those
runs build and verify the helper but do not publish, so a broken build is
caught before a tag is cut. swift test is not part of CI: the suite drives real
Accessibility and ScreenCaptureKit APIs and needs a logged-in GUI session with
both permissions granted, which a hosted runner does not provide. CI instead
smoke-tests that the binary executes and can parse its command-line options,
which happens before any AX call.

reinstall.sh uses the release assets when it finds no local helper:

./reinstall.sh            # downloads dsh-cua-native-darwin- for this Mac

It picks latest by default; to pin a tag, or to skip the download entirely,
use the environment overrides:

DSH_CUA_HELPER_TAG=v0.1.0 ./reinstall.sh   # a specific release
DSH_CUA_REPO=you/dsh-cua-macos ./reinstall.sh  # a fork
DSH_CUA_NO_DOWNLOAD=1 ./reinstall.sh       # always compile locally

The download is verified with the published .sha256 and by checking the Mach-O
header against the host architecture. A missing release, a missing checksum or a
mismatch is reported explicitly and reinstall.sh falls back to compiling from
source — it never installs an unverified binary and never silently skips the
helper.

native/ is vendored from @deepseek-ai/dsh-experimental-cua-macos; see
native/upstream.json for the per-file provenance and native/LICENSE.cua-driver
for the upstream license.

System permissions

macOS asks the process that runs DSH for two permissions:

  • Accessibility — to read the accessibility tree and post input events.
  • Screen Recording — to capture screenshots.

Grant both in System Settings → Privacy & Security. At 0.2.1-rc.5 there is no
permission page in the Plugin Manager, so do it by hand; the 0.2.2-alpha line
adds a page with one-click navigation.

Per-application authorization is requested by the agent at first use and stored in
the profile's domain storage, so grants survive restarts.

How the tool reaches an agent

@deepseek-ai/dsh-experimental-cua-macos mounts at host level, so its
ctx.tools.register({ name: "cua" }) lands in the global tool layer rather
than an agent scope. ToolRuntime.view(scope) starts every agent scope's view
from layers.global.tools, and nothing in the agent, preset or permission
packages calls tools.restrict(), so the cua tool is visible to every new
session.

A session created before the plugin was installed keeps its recorded tool
scope, so it will not see cua; start a new session after restarting DSH.

What the agent can do

The cua tool exposes one method per operation:

Group Methods
Discovery getCapabilities, listApps, findApps, getApp, activate, show, listWindows
Observation getState (accessibility tree), screenshot
Interaction click, hover, typeText, pressKey, setValue, selectText, paste, scroll, drag, performSecondaryAction

Clicks and hovers accept either an element index from the last getState read or
a coordinate — absolute pixels from the last screenshot, or relative: true
thousandths of the window size. Actions return dispatched: true, verified: false, so the agent has to read fresh state to confirm an action landed.

Reading the accessibility tree

getState returns the tree for one application. Two things about its shape are
worth knowing:

  • The top-level windowId can be null. For an app without a normal
    window (Finder is one), the useful ids live in the windows[] array instead —
    pass one of those to screenshot. Windows with isOnScreen: false still
    capture correctly.
  • The tree is application-scoped, not window-scoped. For Finder that means
    the menu-bar items plus an AXScrollArea named "桌面" (disabled) that holds
    the desktop's own elements. Menu-bar contents are omitted unless you pass
    includeMenus: true.

Application approval

The first time a task selects an application, the Host asks the human:

> Allow Computer Use to launch if needed, read, capture, and control ?

with Allow for this task, Deny and Always allow (the last one only
when the app identity is persistable). The answer is per session unless it is
saved, and a saved grant lives in the provider's allowedApps config.

This prompt needs a human answerer, so it only works in a foreground session —
a delegated task (subagent, workflow agent) gets APP_APPROVAL_UNAVAILABLE
instead and must be handed back to the main task.

Quirks found in live use

Empty params objects. Some models (MiniMax M3.1-Flash among them) encode an
empty JSON object in a tool call as the string "{}". The cua schema requires
params to be an object, so those calls fail with:

[{"expected":"object","code":"invalid_type","path":["params"],"message":"Invalid input: expected object, received string"}]

params methods that require no arguments (getCapabilities, listApps) also
reject a non-empty object, because their schema is strict-empty. The way through
is a key that adds no own property: {"method": "getCapabilities", "params": {"__proto__": 1}}.
Models that emit proper JSON objects never hit this.

getApp needs a foreground task. Selecting an application triggers a
per-application authorization prompt, which is only available in a foreground
session. A delegated task (subagent, workflow agent) gets:

APP_APPROVAL_UNAVAILABLE: Application approval is unavailable in delegated tasks; ask the main task to perform this operation

So listApps, getCapabilities and the other read-only methods work anywhere,
but the first getApp for an app has to run in the main session.

Known limitations

  • Windows support is in development upstream; this bundle is macOS only.
  • No permission page in the Plugin Manager at 0.2.1-rc.5.
  • The committed artifact under native/bin/ is arm64 only; Intel Macs get the
    x86_64 helper from the GitHub Release, or compile it with ./reinstall.sh.
  • The cua tool is not scoped to a PTC preset at 0.2.1-rc.5. The alpha line
    moves it into the PTC generated SDK.

Attribution

Native helper sources are adapted from trycua/cua
(cua-driver-rs-v0.28.0), MIT licensed.

License

MIT — see LICENSE.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
dsh-cua-macos 怎么安装?

在 DSH 里执行 `dsh plugin --profile web add github:elfgzp/dsh-cua-macos#v0.1.0` 即可。

dsh-cua-macos 的验证等级是什么意思?

L4 · 沙盒安装通过。安装命令在隔离沙盒内真实执行成功,无依赖错误

dsh-cua-macos 安全吗?

低风险。静态扫描 低;动态审计无结论(以下以静态为准)→ 总评级 低。

dsh-cua-macos 装之前要先确认什么?

先看它会读写哪些文件、执行哪些命令、连接哪些网络地址;验证等级只说明装得上、跑得起来,不等于安全。涉及密钥或系统权限的,建议先在隔离环境试装。

dsh-cua-macos 用的是什么许可证?

上游标注为 MIT。商用或二次分发前请到仓库确认许可证原文。

dsh-cua-macos 有哪些功能?

读取 macOS 辅助功能树、截屏并识别界面、模拟输入驱动桌面应用、注册 cua 工具供 Agent 调用。

这条记录的数据可靠吗?

本站按仓库名去重后合并整理,字段以作者仓库与 npm 元数据为准;安装命令、仓库地址与 README 保持原文,带 L4 / L5 标记的安装命令已在隔离沙盒里真实跑通。

会话与消息
按星标排序,可作替代方案

dsh-desktop

dsh-desktop

为 DeepSeek Harness (DSH) 插件生态打造的现代化桌面端解决方案。万物皆「插件」,桌面本身也是「插件」。

L3 · 安装规范通过 3.0 万 星

openpets

openpets

L4 · 沙盒安装通过 1,274 星

deeptide

deeptide

L4 · 沙盒安装通过 1,104 星

jingyun-dsh

jingyun-dsh

井云 DSH 客户端插件,为 DeepSeek Harness 注入会员登录、订阅支付、算力管控与应用市场,让智能体和技能快速变成可交易商品

L3 · 安装规范通过 1,004 星

study-mate

study-mate

StudyMate 是 DSH 的「学习模式」预设与技能包,为数学、计算机科目定制学习路线、讲解课件与练习评估,跨科目共享记忆。

未标注验证等级 856 星

elfgzp 的其它插件

6 个

插件的元信息来自作者仓库;分类、验证等级与安全结论的中文说明为中文整理,最近核验 2026-11-10。