DSH Marketplace

dsh-lark

omdsh-dev/dsh-lark

Lark/Feishu bot channel for DeepSeek Harness: each chat drives its own agent, and tool approvals, model questions, and plan reviews return as cards answered by a button or a reply. Switch workspace and model from the chat (`/cd`, `/model`, `/new`), and run several bots that keep separate sessions and can hand turns to each other in one group.

5515TypeScriptBSD-3-ClauseSource

Install

Add dsh-lark to DeepSeek Harness

via npm

Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.

via GitHub · npm package

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

What happened when we ran it

Installed cleanly when we ran it

Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 14d ago.

Show it in your README

install verified — dshmarketplace

For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.

Due diligence

Before you install dsh-lark

  • Source of record: omdsh-dev/dsh-lark — present in the community registry that DSH's own plugin market installs from.
  • Licensed under BSD-3-Clause.
  • A listing here is not a security review. Plugins run with your agent's permissions.

The AI take

What it is — DeepSeek Harness Lark/Feishu plugin: integrates chats to drive agents with card-based approvals.

Who it is for — Users collaborating multiple DeepSeek Harness agents in one Lark/Feishu group chat benefit from independent sessions and turn handoff. Users who do not use Lark or Feishu as integration channels can skip this plugin because they lack the chat environment.

Watch out — No public server or callback configuration needed. Tested and registered successfully in a new profile. No obvious issues found.

The verdict — I would install it because no public server or callback configuration is required.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What dsh-lark does

Separate chat streams pass through agent sessions, approval gates and workspace folders.

dsh-lark is a DeepSeek Harness plugin that connects agents to Lark or Feishu chats through a bot channel. DeepSeek Harness loads the plugin as a channel, where each chat, topic or sender scope can drive a separate agent session. The service uses a WebSocket connection, so it does not require a public server or callback URL. Messages start tasks; execution details, tool calls and results are sent back to the chat, while questions, plan reviews and tool approvals arrive as cards that can be answered with buttons or replies.

Commands such as /status, /ws, /cd, /model, /new and /stop control the active workspace, model and session. Incoming files are written to .dsh-lark/inbox/<timestamp>-<message-hash>/ in the current workspace; outgoing files can be sent back, with approval required in group chats. workspaceRoots, sessionScope, senderAllowlist, groupAllowlist and approvers constrain how the service is used. Additional bot instances keep separate settings, credentials and sessions, and can hand turns to one another in a group.

dsh-lark suits teams that want to operate DeepSeek Harness from Feishu or Lark rather than a terminal, including workflows requiring human approval during execution. It is a poor fit where chat-based access is unnecessary, where voice transcription is required, or where the documented Node.js and DeepSeek Harness version requirements cannot be met. It also duplicates some host commands, which are passed through to the DeepSeek Harness command runtime.

dsh-lark documentation

Configuring dsh-lark

DeepSeek Harness loads dsh-lark into a profile; the README shows dsh plugin --profile web add dsh-lark-channel for sharing a profile with dsh web. Start-up configuration is read once, so changes require a service restart. Relevant settings include:

Setting Behaviour
workspaceRoots Restricts directories selectable from chat.
sessionScope Selects chat, chat-thread or chat-sender session separation.
senderAllowlist, groupAllowlist, approvers Narrows who can use the bot or approve actions.
instance Names an additional bot instance; the first remains unnamed.
botPeers, botHops Restricts bot-to-bot conversations and their consecutive turns; botHops defaults to 6.
receiveFiles, sendFiles Enable file reception and delivery; both default to enabled.
attachImages Enables image attachments when the selected model supports vision.
maxReceiveFileBytes, maxSendFileBytes Set per-file limits, which default to 20 MiB.

Received files remain under .dsh-lark/inbox/ and are not deleted automatically. Group file delivery always requires an approval card.

Commands provided by dsh-lark

/status shows workspace, model and session state; /ws lists workspaces; /cd <name-or-path> changes workspace; /get <path> sends a workspace file; /model, /model use <provider/model> and /model reset select or restore a model; /new starts a session without changing workspace or model; /stop stops the current task; and /help lists commands. DeepSeek Harness also passes host commands such as /plan, /compact and /permission to its command runtime.

Requirements and operation

The service requires Node.js ^22.19.0 || >=24, DeepSeek Harness 0.1.0-rc.6 or newer, and a Feishu or Lark tenant. On macOS and systemd-based Linux, its user service can be managed with status, logs -f, restart and stop. The service reconnects its WebSocket with rate and back-off controls.

Known limits

Voice messages are stored but not transcribed. PDF, XLSX and DOCX files can be downloaded but not previewed in chat. A group can have at most three pending file approvals, and each file is limited to 20 MiB by default.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to dsh-lark

dsh-im

xmanrui

1.5k

Connect IM bots to DeepSeek Harness via QR codes or bot credentials (9 channels: Feishu, WeChat, DingTalk, WeCom, QQ, Slack, Telegram, Discord, and WhatsApp).

Installed cleanly when we ran it

npm packageJavaScript6d ago

AI review

dsh-im

What it is — dsh-im plugin for connecting IM bots to DeepSeek Harness via QR codes or bot credentials, supporting nine channels and enabling local Harness to connect to public AI Office.

Who it is for — When users need to handle AI Office tasks in enterprise IM such as WeChat or DingTalk and require Harness to connect outward it is suitable to install. It allows multiple bots per IM channel with independent binding of status, workspace and model. Not suitable for users who only run locally with no public network requirement.

Watch out — Tested successfully registered and enabled in a fresh profile with no obvious installation or usage issues found.

The verdict — I would install it because it solves the IM access pain point for Harness connecting to public AI Office without extra configuration.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Details

dsh-pocket

shaobeichen

1.4k

Remote phone access to the DSH Web UI: scan a QR code for LAN or public (cloudflared tunnel) access with real-time sync, a mobile-adaptive layout, and a settings tab.

Installed cleanly when we ran it

npm packageJavaScript19d ago

AI review

dsh-pocket

What it is — dsh-pocket enables remote phone access to the DSH Web UI via QR code scan for LAN or public cloudflared tunnel with real-time sync.

Who it is for — When you are away from your desk and want to monitor an agent task running on your computer, this plugin is suitable. Users in advanced mode on the desktop version may find it inapplicable as mobile access is temporarily unsupported.

Watch out — Sandbox testing passed in a fresh profile. The plugin installs with a single npm command. Session persistence requires the dsh web process to remain active, and public access requires agreeing to the disclaimer.

The verdict — I would install it because it provides real-time mobile access to the web UI, but only if the dsh web process stays running to maintain the session.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Details

openpets

alvinunreal

1.2k

Bridges DeepSeek Harness lifecycle status, errors, and approval requests to a locally running OpenPets desktop companion.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScript15d ago

AI review

openpets

What it is — Bridges DeepSeek Harness lifecycle status, errors, and approval requests to a locally running OpenPets desktop companion.

Who it is for — Users who want to bridge DeepSeek Harness lifecycle status, errors, and approval requests to a local OpenPets desktop companion can install this plugin. Users who do not run local OpenPets desktop companion can skip this plugin.

Watch out — Not sandbox tested. Static check indicates it will execute shell commands.

The verdict — I would install it if bridging to local OpenPets is needed, because it connects lifecycle status and errors directly.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

Connects DeepSeek Harness to Avernet's Bot Collaboration Network over WebSocket V2, with automatic onboarding, isolated agent sessions, tool-call events, and multi-bot routing tools.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourcePython11d ago

AI review

deepseek-harness-channel-bcn

What it is — This plugin connects DeepSeek Harness to Avernet's Bot Collaboration Network.

Who it is for — When you need to run multi-agent collaboration tasks with DeepSeek Harness. If your work involves only independent agents without needing the Bot Collaboration Network, you can use other approaches.

Watch out — Sandbox testing has not been performed. Static check indicates it will execute shell commands. No obvious issues found.

The verdict — I would install it if I need Avernet infrastructure integration, because it supports WebSocket V2 connection.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source
85

Desktop notifications for turn completions, with per-outcome controls and keyword rules.

Installed cleanly when we ran it

GitHub sourceJavaScript1mo ago

plugin-notify

whyihaveyou

57

IM webhook and local notifications on turn completion, errors, or approval (Feishu/WeCom/DingTalk/Slack/Discord/custom).

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceHTML5d ago

AI review

plugin-notify

What it is — Sends notifications via IM webhooks and local systems when turns complete, errors occur, or approvals are pending.

Who it is for — When using DeepSeek Harness for turn completion, errors, or approval notifications, users needing instant results should install this plugin. If not involving external IM integration, users can skip this plugin.

Watch out — This is a subdirectory plugin with no single command install. Manual allowance of shell script execution is required from source builds. It executes shell commands and requires API key or token. No sandbox testing was conducted.

The verdict — I would install it because it handles notifications for turn completion and errors in agent workflows, but only if external IM integration is necessary.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
2Details