OpenBitFun combines a high-performance agent runtime written in Rust with a polished desktop application. It pairs the depth of a Code Agent with open, general-purpose capabilities for work beyond software development.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 18%
Response Time: -
First Timer Success: -
GCWing/OpenBitFun has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in GCWing/OpenBitFun 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 60.0 places GCWing/OpenBitFun in the A tier.
The external contributor pull request merge rate for GCWing/OpenBitFun is 18.4%, based on public PR activity from non-core contributors.
GCWing/OpenBitFun currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in GCWing/OpenBitFun. Reviews community pull requests with focus on project quality.
Discussions in GCWing/OpenBitFun 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/GCWing/OpenBitFun?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (23% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Problem / opportunity BitFun 内置的 Markdown 查看器/编辑器（打开 .md 文件时使用）不渲染数学公式，$...$ 与 $$...$$ 只显示为原始文本；而对话（chat）中的 Markdown 已经支持 KaTeX 公式渲染。两者渲染能力不一致。 对以 Markdown + LaTeX 记笔记的用户（如数学/理科笔记）影响较大：在 BitFun 内打开自己的笔记看不到公式渲染，只能借助外部编辑器，或自行编写 MiniApp 阅读器绕过。 根因（源码层面）：BitFun 内部有两套独立的 Markdown 渲染路径—— 对话渲染（已支持公式）：src/web-ui/src/component-library/components/Markdown/Markdown.tsx 通过 mayContainMarkdownMath() 检测 $$ / \( / \[ / 行内 $...$，命中后懒加载 MarkdownMathRenderer.tsx（react-markdown + remark-gfm + remark-math + rehype-katex）。 文件查看器/编辑器（不支持）：打开 .md 走 FileViewerScene → ContentCanvas → MarkdownEditor（src/web-ui/src/tools/editor/compon
Summary LLM 推理异常时，将工具调用指令（<tool_calls> 等 XML 标签）以纯文本形式输出到对话区。系统未做防护，将其识别为合法调用继续执行，形成递归循环，导致上下文在数秒内无限膨胀直至撑爆。 预期行为： 系统应检测这种泄露并中断循环，而非无限递归。 Area Desktop app Reproduction or evidence 复现步骤： 发起对话触发 LLM 调用 模型某次推理异常，输出中出现本应是工具调用指令的 XML 标签（如 <tool_calls>...）作为自然语言回复内容 系统解析输出时检测到 <tool_calls>，将其作为合法调用执行 工具返回结果 → 再次喂给 LLM → LLM 再次输出同样的 XML 标签 循环往复，上下文飞速膨胀 示例： <｜DSML｜tool_calls> <｜DSML｜invoke name="ExecCommand"> <｜DSML｜parameter name="cmd" string="false">Get<｜DSML｜tool_calls> <｜DSML｜invoke name="ExecCommand"> <｜DSML｜parameter name="cmd" string="false">Get-
在收缩左侧面板时，希望鼠标在悬停“展开”按钮时， 可以临时展开面板， 不用特意点击永久性展开
一个服务商可以添加多个key，用来轮询 有些服务商有 rpm 限制， 每分钟超过一定的请求会直接掐死， 大佬可以加强一下控制吗
背景 随着把外部 agent 通过 ACP 接入(opencode / claude-code / codex,以及 #963 新增的 omp),BitFun 已经是一个 ACP host/client。但目前实现的是 ACP V1 的一个可用子集,并非完整标准协议。本 issue 跟踪"补全到完整 ACP host"的差距与优先级。 相关:#963(omp via ACP)、#931(自定义多运行时方案,建议关闭、改走 ACP)。 现状基线(client 侧,ProtocolVersion::V1) 已实现: initialize + client_info session/new load resume prompt cancel close session/set_model agent→client 回调:session/request_permission(唯一实现的回调) 流式 session/update:AgentMessageChunk / AgentThoughtChunk / ToolCall / ToolCallUpdate / UsageUpdate 关键限制:InitializeRequest 传的是 ClientCapabilities::new() —— fs、terminal 能力均未声明(默认 false)。因此外部 agent 不会把文件读写 / shell 回调给 BitFun,而是在自己进程里直接执行(BitFun 仅把 cwd 设为 workspace)。stream.rs 也只处理上述 5 种 S
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 GCWing/OpenBitFun, 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 GCWing/OpenBitFun acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 18.4% were successfully merged into the primary branch.
GCWing/OpenBitFun has a recorded first-timer success rate of 0.0%. 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 60.0 places GCWing/OpenBitFun in the Welcoming tier.
The external pull request merge rate is 18.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, GCWing/OpenBitFun currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for GCWing/OpenBitFun 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.