Skip to main content
The BeeOS DeepSeek Harness adapter registers native Harness tools backed only by the public BeeOS OpenAPI. It does not embed ADB, device runtime protocols, or credentials.

​
Available tools

Only list and get operations are declared concurrency-safe. Write operations are deliberately not marked concurrency-safe and remain subject to BeeOS device leases and capability checks.

​
Build the adapter

The adapter has not yet been published as a supported package. Build the current source before testing:
The installable package is generated at dist/packages/deepseek-harness. Its Cordis patch registers @beeos-ai/deepseek-harness-plugin as beeos.

​
Configure BeeOS

Set credentials in the Harness secret configuration or inject them through the process environment:
The apiKey Harness configuration field is marked secret for host-side redaction. Use the staging OpenAPI URL when validating against staging.

​
Validate safely

  1. Load the generated adapter with your Harness package workflow.
  2. Confirm all seven tools register without schema errors.
  3. Call beeos_list_instances first.
  4. Run a reversible Agent task before allowing computer or mobile actions.
  5. Confirm task cancellation and terminal-state handling before automation.
This adapter is experimental until a released package passes the live BeeOS validation gate. Do not use a production phone for the first write test.
See BeeOS Skills, Task Lifecycle, and Instances and Devices.