deepseek-harness/docs/upgrade-guide/v0.2.2-alpha.2/cua-source-dev-helper/guide.md

kind, description

kind	description
upgrade-guide	Source-built Computer Use helpers use a separate development bundle identifier and need one new macOS permission grant.

Source-built Computer Use helper identity

English | 中文

Change

Source checkouts previously built DSH Computer Use.app with the release bundle identifier com.deepseek.harness.computer-use and an ad-hoc signature. They now build DSH Computer Use Dev.app with bundle identifier com.deepseek.harness.computer-use.dev. Accessibility and Screen Recording grants for the old entry do not apply to it. Desktop and npm installations are unchanged. Source builds still default to ad-hoc signing; developers generate and maintain fixed identities outside DSH home and select them through configuration.

Migration

1. Keep the default sourceSigning: ad-hoc for temporary signatures. To reduce repeated grants after rebuilds and across worktrees, follow the developer signing skill to generate or reuse a certificate, then write sourceSigning: { identity, keychain } into the DSH home’s cordis.patch.yml; keychain must be an absolute path.
2. Start DSH from the source checkout, call Computer Use, and grant Accessibility and Screen Recording to DSH Computer Use Dev in System Settings.
3. Confirm that getCapabilities reports both permissions as true. With a fixed signature, check again after changing and rebuilding Swift code and from another worktree. Remove an old DSH Computer Use entry only when no installed DSH uses it.
4. After the keychain locks, rerun setup as described in the skill to unlock and reuse the identity. To stop using it, select ad-hoc or remove the configuration, then remove the identity through the skill; deleting DSH home does not delete the developer keychain.