Bridge Feishu/Lark to AI coding CLIs — Claude Code, Codex, Gemini, OpenCode… every DM, group or topic spawns its own live-streaming CLI session
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 75%
Response Time: -
First Timer Success: 68%
deepcoldy/botmux has a recorded first-timer success rate of 68.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in deepcoldy/botmux respond to incoming external pull requests in approximately 0.0 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 67.5 places deepcoldy/botmux in the A tier.
The external contributor pull request merge rate for deepcoldy/botmux is 75.0%, based on public PR activity from non-core contributors.
deepcoldy/botmux does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Bridge Feishu/Lark to AI coding CLIs — Claude Code, Codex, Gemini, OpenCode… every DM, group or topic spawns its own live-streaming CLI session
Strict review standards in deepcoldy/botmux. Ensure PR scope matches issue requirements closely before requesting review.
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/deepcoldy/botmux?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (94% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
背景 Botmux 已能识别部分 CLI 的 usage limit / rate limit，并在会话首次进入限额状态时由 daemon 主动通知用户。当前任务仍会暂停，用户需要手工改用另一个 Bot/CLI。 希望支持一种不依赖主模型继续生成文本的降级方式：主 CLI 确认额度耗尽后，由 daemon 直接通过飞书 API 在原会话位置发送一条预配置的固定消息，并原生 @ 一个备用 Bot。备用 Bot 再使用自己的 CLI 接手。 这个能力与 #1225 不同：#1225 是同一 Bot 内轮换 Provider/API Key；本需求是在飞书会话层把任务交给另一个独立 Bot/CLI。 需求 为单个 Bot 增加可选的「CLI 限额后自动交接备用 Bot」配置。字段名仅供讨论： { "quotaFallbackBot": { "enabled": true, "targetAppId": "cli_xxx", "kinds": ["usage", "rate"], "message": "主 Bot 当前额度已耗尽，请接手本话题并结合上下文继续处理。" } } 当当前 CLI 进入可信的限额状
背景 话题群里同时运行多个 Agent session 后，用户很难快速知道当前群还有哪些活跃话题，也需要在聊天列表中手动翻找原话题。 目前已有的能力： /dashboard sessions 可以查看全局会话，并通过详情里的「定位话题」找回会话；但它要求 Dashboard 管理员权限、结果发到私聊，且不是当前群视角。 Agent Workbench 可以集中查看会话并打开聊天；但对于只想在群里快速切回某个话题的用户，操作链路偏重。 /relay 会迁移会话，不适合“回到原话题继续聊”的场景。 希望增加一个面向群成员的轻量命令，在当前群内列出当前机器人拥有的活跃话题 session，并提供回到原话题的入口。 第一版范围（MVP） 新增 /sessions 命令： 仅查询当前机器人在当前群中的 session，不做跨机器人 / 跨 daemon 聚合。 仅展示 scope = thread 且状态非 closed 的 session。 每条至少展示： session
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 deepcoldy/botmux, 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 deepcoldy/botmux acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.
deepcoldy/botmux has a recorded first-timer success rate of 68.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 67.5 places deepcoldy/botmux in the Welcoming tier.
The external pull request merge rate is 75.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
deepcoldy/botmux 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 deepcoldy/botmux 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.