AI Agent Hub
Back to plugins
🧰

dsh-gateway

Web Tools Updated 2026.08.26

Run the following command in DeepSeek Harness:

dsh plugin install aa2246740/dsh-gateway

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install aa2246740/dsh-gateway (source: https://github.com/aa2246740/dsh-gateway), then restart the DSH Host and reload the page, and finish Slack / Feishu pairing under Settings > Messaging.

About this plugin

You are already running a DeepSeek Harness agent in the terminal, but reaching for a laptop every time you want a quick chat adds up daily. dsh-gateway turns Slack DMs and Feishu DMs into full DSH sessions. You create your own Slack app and your own Feishu enterprise self-built app, paste the tokens into the local DSH settings page, and every credential stays on your machine. No shared public bot, no third-party relay.

Once paired, a phone DM carries the same tool calls, conversation history, and slash commands (/new, /compact, /model, and friends) as your desktop session. Feishu gets a dedicated reply rhythm: the first sentence lands immediately, the remainder stays in a single bubble, and approvals surface as interactive cards (Allow once / Deny). Slack keeps its plain-text tone and only responds when @mentioned in channels. An instance-lock mechanism guarantees that only one Gateway process on the machine holds write access, preventing duplicate-Host conflicts.

This plugin is for individual developers or small teams who already run the official DSH with a web profile, rely on both Slack and Feishu daily, want to carry their agent in their pocket, and prefer keeping every token local. All you need is a Slack workspace where you can install apps and a Feishu tenant where you can create an enterprise self-built app. No dshx, no extra middleware.

Use Cases

  • Drive your local DSH agent from a phone via Slack or Feishu DM
  • Approve or deny agent actions with one tap on a Feishu interactive card
  • Prevent duplicate Gateway write conflicts on the same machine via instance locking

Best For

  • Individual developers who rely on both Slack and Feishu daily
  • Small teams already running the official DSH web profile
  • Users who insist on local token storage and avoid shared public bots