Skip to content

TtTRz/dsh-wecom

30Last commit Aug 14, 2026

dsh-wecom DSH plugin

dsh-wecom is an installable DeepSeek Harness channel plugin for WeCom AI Bot. It receives WeCom messages over the official long connection, maps conversations to persistent Harness agents, and provides access policies, media handling, turn controls, status APIs, and an optional web UI.

How to install the dsh-wecom DSH plugin

dsh plugin --profile web add dsh-wecom

Copying does not run this command. Review the repository and version before use.

Data source

Snapshot date: Aug 15, 2026

manifest-valid

What the dsh-wecom DSH plugin can do

  • Connects a WeCom AI Bot through its WebSocket long connection.
  • Creates or resumes one persistent Harness agent per direct or group conversation.
  • Mounts a configurable agent preset so conversations can use its tools and persona.
  • Handles images as model attachments when supported; places files and videos in the agent workspace.
  • Supports direct-message and group access policies with allowlists.
  • Deduplicates messages, queues work per conversation, caps global concurrency, and cancels timed-out turns.
  • Provides bot commands for ping, help, status, cancellation, and starting a new conversation.
  • Publishes a serializable wecomChannelStatus service and a GET /api/wecom/status endpoint.
  • Includes a web client with a sidebar action and floating connection-status panel.

Where the dsh-wecom DSH plugin fits

  • Operating a tool-enabled DeepSeek Harness assistant through WeCom direct and group chats.
  • Restricting a WeCom bot to approved group chat IDs or direct-message users.
  • Keeping separate persistent agent sessions and workspaces for WeCom conversations.
  • Monitoring WeCom channel connectivity from a Harness web dashboard.

Who the dsh-wecom DSH plugin is for

  • DeepSeek Harness users deploying WeCom AI Bots.
  • Teams using WeCom for internal assistant workflows.
  • Administrators who need controlled group or direct-message bot access.

dsh-wecom DSH plugin limitations

  • Requires a WeCom Bot ID and a secret stored through the Harness credential service or development environment.
  • Requires Node.js 22.19 or later.
  • Group access control is based on group chat IDs; direct-message access control uses user IDs.
  • Browser status UI and the status route are available when a Harness web server is present.
  • Image attachment behavior depends on the configured image mode and whether the model can view images.

Objective checks

These signals come from public metadata scans. They are not a security certification.

  • dependency counts

    package.json declares 2 runtime, 23 development, 11 peer, and 0 optional dependencies.

    info
  • dsh bundle declared

    package.json declares DSH bundle metadata.

    info
  • license declared

    GitHub reports the repository license as MIT.

    info
  • package manifest available

    A root package.json was captured and can be inspected by the registry.

    info
  • prepare script detected

    package.json declares a prepare lifecycle script that may run during relevant package installation workflows.

    info
  • source available

    Public GitHub source metadata is available for this registry snapshot.

    info

dsh-wecom DSH plugin alternatives

dsh-wecom DSH plugin questions

What is the dsh-wecom DSH plugin?

dsh-wecom is a project included in the current DSH plugin snapshot. This page organizes repository metadata and reviewed notes, but you should still inspect the upstream repository before running it.

How do I install the dsh-wecom DSH plugin?

The page shows the install command captured from the source record. Copying does not run it, so confirm the package, profile, and version against upstream documentation first.

Which DSH profile does dsh-wecom use?

The snapshot records web as the dsh-wecom profile. DSH conventions can change quickly, so verify the manifest and README before installation.

Is dsh-wecom compatible with the current DSH release?

The source data does not include a verified compatibility matrix. Check recent commits, releases, and DSH breaking changes, then test in a profile you can roll back.

What should I do if dsh-wecom fails to load?

Check the install command, selected profile, dependency logs, and Cordis startup output first. Keep the exact error string, then compare it with this site's fix pages and upstream issues.

What are the closest alternatives to dsh-wecom?

Related plugins on this page come from the current snapshot and are only candidates. Compare capabilities, maintenance activity, installation method, and limitations before choosing one.