通过扫码或机器人凭据把IM机器人接入DeepSeek Harness（支持飞书、微信、钉钉、企业微信、QQ、Slack、Telegram、Discord和WhatsApp）。 Connect IM bots to DeepSeek Harness via QR code or credentials (9 channels).
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 57%
Response Time: 4h
First Timer Success: 44%
xmanrui/dsh-im has a recorded first-timer success rate of 44.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in xmanrui/dsh-im respond to incoming external pull requests in approximately 4.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 63.6 places xmanrui/dsh-im in the A tier.
The external contributor pull request merge rate for xmanrui/dsh-im is 57.5%, based on public PR activity from non-core contributors.
xmanrui/dsh-im does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
通过扫码或机器人凭据把IM机器人接入DeepSeek Harness（支持飞书、微信、钉钉、企业微信、QQ、Slack、Telegram、Discord和WhatsApp）。 Connect IM bots to DeepSeek Harness via QR code or credentials (9 channels).
Highly welcoming maintainers in xmanrui/dsh-im. Prompt code reviews with positive guidance for new contributors.
Discussions in xmanrui/dsh-im focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/xmanrui/dsh-im?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (72% approval). Large PRs (>500 lines) take ~20 hours (26% approval). Keep your diff compact for rapid review.
背景 目前 dsh-im 没有实现 /clear 命令。用户在飞书发送 /clear 后，消息会进入普通对话流程，模型回复“没有这个能力”，但上下文并没有被清空。 当前已有 /new（解除当前聊天的 Session 绑定，下一条普通消息创建新会话）和 /compact（压缩上下文），缺少明确的清空上下文入口。 功能需求 新增 /clear 文本命令，由插件识别并执行，不再作为普通消息交给模型。 建议语义：清空当前聊天所绑定 Session 的模型上下文，让后续对话从空白上下文开始，并保留当前 Session 绑定；与 /new 创建新会话、/compact 保留摘要的行为明确区分。实现前需核实 Host/Harness 的清空能力，并在帮助中说明实际清理范围及历史记录的保留方式。 实现要点 优先复用 Host/Harness 提供的清空能力；若当前版本不支持，返回明确提示，不得假报成功或静默改为 /new。 将 /clear 纳入共享命
背景 目前可以在机器人卡片中设置工作区，但无法直接为机器人指定模型。希望将模型作为机器人级配置，方便不同机器人使用不同模型。 需求 在每张机器人卡片中新增“设置模型”功能； 入口放在“设置工作区”下方； 展示当前模型，并允许从 Harness Host 的可用模型中选择； 提供“跟随 Host 默认”选项； 模型选择按机器人独立保存，刷新页面或重启后仍保留； 设置只影响该机器人之后新建的会话，不修改已有会话或正在生成的回复； 已保存的模型不可用时，明确显示不可用状态，并允许重新选择或恢复为 Host 默认； 各 IM 渠道的机器人卡片保持一致行为。 验收标准 “设置模型”位于机器人卡片“设置工作区”下方； 不同机器人可以保存不同的模型设置； 新会话使用该机器人设置的模型； 删除机器人时同步清理对应模型配置； 模型目录
背景 目前 dsh-im 已支持微信、飞书、钉钉、企业微信、QQ、Slack、Telegram、Discord 和 WhatsApp，希望进一步增加 iMessage 渠道，让使用 Apple 生态的用户也能通过 iMessage 与 Harness 交互。 此前曾在 #55 中简单提出过这个想法。由于目前缺少稳定、方便的 Apple 设备与 iMessage 测试环境，想在这里诚邀熟悉 macOS、Messages.app 或相关 iMessage 接入方案的朋友一起讨论并协助实现。 期望的首版范围 建议先以一个可验证的 MVP 为目标： 支持接收和发送文本消息； 沿用现有渠道适配器结构，并保持机器人、工作区和会话映射相互独立； 凭据或本机授权信息只保存在本地，不通过前端接口回传敏感内容； 提供必要的安装、授权、运行环境和测试说明； 在条件允许时补充连接状态、错误提示和基础自动化测试。 图片、文件、引用回复、主动投递、群聊等能力可以根据所选
背景 感谢 PR #32 为 Telegram 机器人加入原生命令菜单和菜单按钮。这个功能让用户点击菜单按钮或在输入框键入 / 时，就能看到机器人支持的命令，使用体验很好。 随着项目继续增加命令，目前出现了一个可维护性问题：PR #32 引入的 TELEGRAM_COMMAND_MENU 在 src/channels/telegram/telegram-runtime.mjs 中单独硬编码，后续每新增一条共享命令，都还需要人工同步修改 Telegram 的清单。只要漏掉这一步，命令本身和 /help 已经可用，但用户输入 / 时仍看不到它。 当前已经可以观察到这种差异，例如 /history、/reasoninglist、/reasonings 和 /reasoning 已被共享命令层及 /help 支持，但未出现在 TELEGRAM_COMMAND_MENU 中。未来新增的命令或别名（例如 Issue #88）也容易再次遗漏。 期望目标 希望 Telegram 命令菜单能够从统一的命令定义中自动生成，而不再维护一份容易失去同步的独立硬编码清
背景 /workspacelist 和 /workspace 含义清晰，但命令较长，在手机端或高频使用时不太方便输入，也容易记混。希望在保留现有命令、确保完全向后兼容的前提下，为它们增加几个更短、更直观的别名。 新增别名 新命令 等效命令 /wsl /workspacelist /workspaces /workspacelist /ws /workspace 例如： /wsl /workspaces /ws /Users/alice/projects/my-app 期望行为 三个别名应调用对应原命令的同一套实现，不复制工作区业务逻辑。 参数、大小写、首尾空白、校验、错误提示和成功结果应与原命令保持一致。 /wsl 和 /workspaces 与 /workspacelist 一样不接受额外参数。 /ws <参数> 应完整继承 /workspace <参数> 当前及后续支持的能力，包括 Issue #87 提议的按序号切换工作区；请避免为别名单独维护一套参数规则。 原有 /workspace 和 /workspacelist 必须继续正常工作。 在存在特殊命令路由的渠道
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to xmanrui/dsh-im, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of xmanrui/dsh-im acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.5% were successfully merged into the primary branch.
xmanrui/dsh-im has a recorded first-timer success rate of 44.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 63.6 places xmanrui/dsh-im in the Welcoming tier.
The external pull request merge rate is 57.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
xmanrui/dsh-im does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for xmanrui/dsh-im are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.