STARDUSTLC666/dsh-slack
DeepSeek Harness Slack plug-in: slack_notify/channels/inbox/reply four tools, Socket Mode free public network callback to receive messages, inbox queue + thread reply, supports custom slackA
Lets the agent communicate with Slack bidirectionally: slack_notify sends a Markdown message to a channel or thread (returns ts), slack_channels lists bot-visible channels (paginates conversations.list fully), slack_inbox reads Socket Mode messages (in-memory queue, up to 200, dedup + atomic markRead consumption), slack_reply replies in-thread to inbox messages. WebClient is cached per token+slackApiUrl and rebuilt on config change.
Install
dsh plugin --profile web add dsh-slacknpm package dsh-slack 0.2.3 (registry-verified 2026-08-25). dsh plugin --profile web add dsh-slack, then restart the dsh Web service — the four tools slack_notify / slack_channels / slack_inbox / slack_reply become visible to the model. Configure in the profile's cordis.patch.yml by id: slack (token supports env fallback DSH_SLACK_TOKEN / DSH_SLACK_APP_TOKEN).
Compatibility
DeepSeek Harness Web profile. v0.2 scope is two-way: agent → Slack notifications and Slack message → agent via Socket Mode (slack_inbox / slack_reply). RTM and interactive components (buttons/modals/slash-command replies) are out of v0.2 scope.
Details
- Repo: STARDUSTLC666/dsh-slack
- Category: Messaging & Communication
- Stars: 4
- Version: npm dsh-slack 0.2.3 (registry-verified 2026-08-25)
- Last push: 2026-09-18
- First seen: 2026-08-13
Recent updates
v0.2.3: slack_channels auto-pagination; slack_inbox dedup + drain atomic consumption; WebClient reuse per token+slackApiUrl; pagination cap; error mapping (not_authed/is_archived/msg_too_long/ratelimited).
FAQ
- What does v0.2 add over v0.1?
- v0.1 was one-way agent → Slack notifications. v0.2 adds Socket Mode for Slack message → agent: slack_inbox receives messages and slack_reply replies in threads.
- What tokens do I need?
- A bot token (xoxb-) for sending, plus an App-Level Token (xapp-) with connections:write when Socket Mode is enabled for receiving. Both support environment-variable fallback.
- What is out of scope?
- RTM and interactive components — buttons, modals, and slash-command replies — are not in v0.2 per the known-limitations roadmap.
Alternatives
imetn/dsh-lark-bridge · pgzxb/dsh-feishu · amlyczz/dsh-lark-link