orbis
连接与集成icodesign/orbis
DeepSeek Harness 的移动端远程控制客户端，提供设备配对、端到端加密传输和多设备实时更新。
- dsh-plugin
验证与兼容性
这里展示目录实际采集到的证据；未声明的信息会明确标为未知。
- 当前版本兼容性
- 已在当前目录版本验证
- 声明的 Harness 范围
- 未声明
- 声明的平台
- 未声明
- 适用 Profile
- web
- 构建授权
- 未检测到需要
- 权限声明
- 未声明
- 外部服务
- 未声明
- 遥测声明
- 未知
这不是安全背书；安装前仍应查看源码、权限和配置。
查看证据与判定范围
验证仅覆盖标出的来源、版本和 Harness 环境，不代表未来版本仍然兼容。
@orbisapp/remote-dsh@0.2.7- 插件已在隔离环境完成加载检查。
README
Orbis
English | 简体中文
Orbis is a remote control client for Deepseek Harness (DSH).
The Orbis plugin provides device pairing, end-to-end encrypted transport, and real-time updates across multiple devices.
Getting Started
- Download the Orbis app. It is currently in beta. iOS: Join TesFlight. Android: Working in progress.
- Install the Orbis plugin into DSH.
npx @deepseek-ai/dsh plugin --profile web add @orbisapp/remote-dsh@latest
- Configure the plugin and pair your device from the DSH web plugin page (Settings - Plugins - Orbis tab).
Development
Install dependencies at the repository root, then use a single command to build the plugin, install it into your local DSH Web profile, and start the test page:
pnpm install
pnpm run serve:dsh
The page is served at http://127.0.0.1:3080 by default. Pass flags to change the port or
point at a specific test directory:
pnpm run serve:dsh --port 3090
pnpm run serve:dsh --workspace-root /path/to/workspace
pnpm run serve:dsh --help
Testing
pnpm run check:core # typecheck + tests for everything that builds from this repository alone
pnpm run check:dsh # typechecks and tests the plugin and client entry points against the public DSH SDK
CI runs check:core on every push and every pull request, and again before a release.
check:dsh uses the public @deepseek-ai/* SDK packages installed by the workspace.
Releasing
Releases are driven by Changesets. Ship every user-visible change with a changeset and commit it alongside the change:
pnpm changeset
Changesets maintains one draft release pull request containing all pending changesets. Keep that pull request open while changes accumulate. When the complete release is ready, review the combined version and changelog, mark the pull request as ready, and merge it to publish the release. Changes that do not affect a published package do not need a changeset.
Write release-level highlights and upgrade notes in .changeset/.release-notes/next.md, using
heading level 3 (###) or lower. The version script prepends that Markdown to the generated package
changelog, so the draft release pull request and final GitHub Release show the same notes before the
Changesets list. The release pull request consumes and clears the file for the next release.
Community
Wechat Group
