[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3iakvb6yx7v8w":3},{"code":4,"message":5,"data":6,"timestamp":41},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":37,"homepage":38,"updated_at":39,"history":40},"xmanrui\u002Fdsh-im",7,"通过扫码或机器人凭据把IM机器人接入DeepSeek Harness（支持飞书、微信、钉钉、企业微信、QQ、Slack、Telegram、Discord和WhatsApp）。 Connect IM bots to DeepSeek Harness via QR code or credentials (9 channels).","JavaScript",2433,247,357,71,[],"Connects DeepSeek Harness agents to nine-plus chat platforms so users talk to a local agent from their everyday messaging app.","## The problem\n\nRunning a local agent harness is one thing; getting anyone else to use it is another. The harness sits on your machine behind an IDE or a web UI, while the people who would benefit already live in Feishu, WeChat, Telegram or Slack. Wiring each platform's bot API — long connections, webhooks, message chunking, streaming replies — is a separate integration project per channel, and most teams never finish more than one.\n\nDSH-IM packages that wiring as a single DeepSeek Harness plugin: scan a QR code or paste bot credentials, and the local harness connects outward to the platform, with each bot keeping its own workspace, model and session bindings.\n\n## What's different\n\nThe usual route is to write a custom webhook server per platform, or to adopt a hosted bot gateway that sits between the messaging app and your model. The first is repetitive and fragile; the second hands message traffic to someone else. This project keeps the runtime local and treats channels as plugins — nine standard channels plus experimental Matrix, each with channel-specific reply behavior: AI Card streaming on DingTalk, native threads on Discord, edit-in-place progress on WhatsApp and Telegram, voice transcription on Feishu. Multi-bot-per-channel with independent sessions is a real differentiator against most single-bot glue scripts.\n\n## Who it's for\n\nDevelopers already running DeepSeek Harness who want to reach non-technical teammates, or themselves, through chat apps. It fits small teams and personal deployments where a local machine is acceptable. Those without a running Harness, or who need a centrally hosted, multi-tenant bot service, should look elsewhere — this is a client-side connector, not a gateway product. Anyone who cannot expose or maintain a long-running local process, or who needs iMessage on non-macOS, is out of luck.\n\n## Cost of adoption\n\nYou need Node\u002FJavaScript tooling, a DeepSeek Harness install, and per-channel developer credentials — QR flows cover some platforms, but Slack, Discord, Telegram and Matrix require creating apps and tokens. Several channels need persistent outbound connections and platform-specific permissions; the iMessage channel is macOS-only and depends on Messages.app. The Matrix E2E encryption feature is explicitly experimental and not for sensitive traffic. License is MIT. The README is detailed but dense, and there is no independent documentation beyond the repo.\n\n## Verdict\n\nThis is a brand-new project — created 71 days ago, 2.4k stars — and its momentum is real rather than residue: +344 stars in the week HotRepo observed it, landing at #8 on the JavaScript weekly board. That speed plus an official Harness sponsorship suggests genuine demand from an existing ecosystem, not a viral one-off. The risk is maturity: experimental encryption, dozens of fast-moving platform APIs, and a single maintainer. Adopt it if you are already inside DeepSeek Harness and want chat reach; wait if you need stability guarantees or operate at organizational scale.",{"slug":19,"name":20},"ai-engineering","AI Engineering",[22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"ai-agents","chatbot","cordis","deepseek","deepseek-harness","dingtalk-bot","discord-bot","dsh","dsh-plugin","feishu-bot","im-bot","slack-bot","telegram-bot","wechat-bot","whatsapp-bot","MIT",null,"2026-10-24T22:36:10Z",[],1792898586]