Give cloud AI agents a real development environment on your own machines.
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 69%
Response Time: -
First Timer Success: 20%
yyjeqhc/webcodex has a recorded first-timer success rate of 20.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in yyjeqhc/webcodex 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 71.1 places yyjeqhc/webcodex in the S tier.
The external contributor pull request merge rate for yyjeqhc/webcodex is 69.2%, based on public PR activity from non-core contributors.
yyjeqhc/webcodex currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in yyjeqhc/webcodex. Prompt code reviews with positive guidance for new contributors.
Discussions in yyjeqhc/webcodex 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/yyjeqhc/webcodex?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (87% approval). Large PRs (>500 lines) take ~115 hours (31% approval). Keep your diff compact for rapid review.
中文｜背景与范围 类型：可靠性增强 / 设计简化（help wanted），不是已经证实的普通代码 Bug。 在现有真实 Host 对照中，独立 MCP App Probe v003 能在 ChatGPT Web 后台约 5 分钟后完成零点击自动续接；WebCodex 的 goal_workflow_stalled 恢复路径在另一轮后台实验中出现较大的额外延迟。源码显示一个值得改进的设计边界：Goal 停滞资格在 sync_goal_plan 时重检，同时要求上一条有效卡片观察处于 75 秒租约内；Goal 卡片的后台轮询目标却是 60 秒。 Agent Continuation 又维护独立的 Endpoint 心跳/租约。 目标是提高后台可靠性、解释性和实现简洁度，不是取消有意设置的“陈旧卡片不能触发 Wake”保护、绕过 Session/Window 身份检查，或承诺任意 Host/已卸载卡片都能无人值守启动模型回合。 本议题关注 WebCodex Goal stall attention + Agent continuation 的时序耦合；与 #1013 中 Codex Desktop 切换到
中文说明 背景 这个 Issue 是对 #1013 的后续跟进，也与之前调整 continuation 工具表面的 #772 直接相关。 #772 当时因为 ChatGPT Host / WebUI 行为变化，自动 fresh-turn continuation 变得不稳定，因此有意把 continuation presentation 工具从普通模型可见表面中隐藏： present_agent_continuation：Direct -> ModelHidden present_job_terminal_continuation：Direct -> ModelHidden durable Agent/Job continuation 状态、handler、authorization、MCP App resource 和协议实现都保留了下来 ToolDirectReason::Continuation 也特意保留，用于未来 Host 恢复支持后重新启用 最近的真实 ChatGPT MCP App 实验表明，这种 Host 能力很可能已经恢复，因此值得做一次窄范围、基于实测证据的恢复，而不是整体 revert #772。 我们已经观察到的结果 我们实现了独立的 MCP App probe：先挂载 continuation card，让当前模型 turn 正常结束，然后由服务器在指定时
Summary I'd like to request first-class WSL2 integration in WebCodex Desktop for Windows. WebCodex already supports Linux Runners and provides a WSL/Linux Controller. However, using a WSL2 development environment from the Windows Desktop application still requires separate CLI setup and manual Server/Runner configuration. It would be great if Desktop could handle this through a guided setup flow. Motivation My primary development environment is WSL2, while Windows is my desktop operating system. I would like to use ChatGPT through WebCodex to work directly with my Linux projects, shell, Git, and development tools without manually managing a separate WSL installation. Ideally, I could configure everything from the Windows Desktop application and continue using the same ChatGPT connection. Proposed Experience Open WebCodex Desktop on Windows. Select Add Environment → WSL2. Automatically detect installed WSL distributions. Select a distribution, such as Ubuntu. Click Set Up Runner. Desk
Help make WebCodex better WebCodex welcomes contributions from everyone who uses, explores, or develops the project. You do not need to be familiar with the entire codebase, and you do not need to start with a large feature. In fact, some of the most valuable improvements come from everyday use: something breaks, takes too many steps, is difficult to understand, feels slow, or simply could work better. If an Issue or Pull Request can improve WebCodex's quality, reliability, usability, developer experience, or overall product experience, it is a welcome contribution. What can you contribute? For example: Report and fix problems. Bugs, regressions, crashes, unexpected behavior, compatibility issues, and reproducible failures. Improve the experience. Confusing interfaces, unclear messages, awkward workflows, unnecessary steps, accessibility problems, and small interaction details. Make things more reliable and efficient. Performance, stability, error handling, recovery, diagnostics, reso
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 yyjeqhc/webcodex, 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 yyjeqhc/webcodex acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.2% were successfully merged into the primary branch.
yyjeqhc/webcodex has a recorded first-timer success rate of 20.0%. Repositories ranked Elite 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 71.1 places yyjeqhc/webcodex in the Elite tier.
The external pull request merge rate is 69.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, yyjeqhc/webcodex 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 yyjeqhc/webcodex 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.