Introduction

DSH extends external capabilities through plugins. To integrate Livis’s messages, file uploads, and result callbacks into a persistent DSH Agent, handling authorization, binding, connection status, and task idempotency separately would be fragmented. fyy99/dsh-livis-connector is a native Cordis plugin that integrates Livis into DeepSeek Harness. Authorization, Agent ID binding guidance, and connection status are all completed on the DSH settings page, and it does not depend on OpenClaw at runtime.

What is this

fyy99/dsh-livis-connector is an independent community connector maintained by fyy99, licensed under MIT. It addresses the issue of completing Livis account authorization and connection management on the DSH Web settings page, and reliably returning results after handing Livis messages to the persistent DSH Agent.

It is not affiliated with or represents DeepSeek, Li Auto, or Livis; related names belong to their respective owners.

Core Capabilities

  • Complete Livis account authorization and connection management on the DSH settings page
  • Generate and display the Agent ID, guiding the user to complete the setup within the Livis App
  • Hand Livis messages to the persistent DSH Agent and reliably return the results
  • Support cancellation, result confirmation, reconnection on disconnection, and job_id idempotency
  • Support whitelisted document uploads and restrict them to the configured directory
  • refresh token is only stored on the DSH Host and will not be sent to the browser page
  • Does not depend on OpenClaw at runtime

Requirements

  • Node.js: ^22.19.0 || >=24.0.0
  • DeepSeek Harness: 0.1.0-rc.6
  • DSH is still in developer preview; this plugin follows the evolution of its plugin API. Please check compatibility before upgrading DSH.

Installation and Enablement

The following steps describe the installation and starting of the Web profile. First, install the GitHub repository, then dump the current configuration, and finally start the Web profile.

  1. Install the GitHub repository using the DSH official plugin command:
dsh plugin --profile web add github:fyy99/dsh-livis-connector
  1. After installation, execute the configuration dump to confirm the plugin configuration has been entered into the current profile:
dsh --profile web --dump-config
  1. Start the Web profile:
dsh web

Connecting to Livis

The connection process is as follows:

  1. Open DSH and navigate to “Settings → Plugins → Livis”.
  2. Click “Start Authorization”, wait for the page to show that it is connected to DSH, and copy the generated Agent ID.
  3. Paste the Agent ID in the Livis App under “Me → Connections & Services → My Agent”.
  4. Send a test message from the Livis App to confirm the message enters the DSH Agent and receives a callback.

If authorization is interrupted or expired, simply go back to the same page to initiate it again; the plugin will not automatically start authorization upon page load.

Reproducible Deployment

When reproducible deployment is required, pin the GitHub dependency to a verified commit SHA instead of long-term following the default branch.

You can also first execute npm pack to generate a tarball, and then pass the tarball path to the same dsh plugin --profile web add command:

npm pack

Security and Considerations

  • Do not bind DSH Web to 0.0.0.0. The management RPC only allows loopback, but DSH Web itself does not provide user login authentication.
  • The Livis relay handles account tokens, devices and Agent IDs, messages, replies, and files explicitly uploaded by the user.
  • The three directory fields must use absolute paths.
  • Production endpoints force HTTPS / WSS; plaintext protocols are only allowed for localhost testing.
  • Remote text always enters the model as a normal user message and will not be executed as a DSH slash command.
  • The approval policy for the Livis Agent is fixed to never; operations requiring local approval will fail.
  • It is recommended to use a dedicated low-privilege API Key, do not use danger-full-access, and run DSH in a workspace without sensitive data.
  • The plugin runs under the permissions of the current dsh process; you should check the source code and the MIT license before installation.
  • If a security issue is discovered, report it privately via the repository’s Security Advisories; do not submit tokens, Agent IDs, message content, or local paths in public Issues.

Conclusion

The value of fyy99/dsh-livis-connector is to place Livis authorization, Agent ID binding, message callbacks, and upload restrictions into the DSH settings page, reducing manual configuration for external connections. It is suitable for use as a community connector under the DSH Web profile, but it requires maintaining version compatibility and low-privilege execution boundaries.

GitHub Repository: https://github.com/fyy99/dsh-livis-connector
Directory Page Link: https://www.skillhub.cn/plugins/fyy99/dsh-livis-connector (Not verified in this material, not to be taken as a confirmed fact)