Professional Antigravity Account Manager & Switcher. One-click seamless account switching for Antigravity Tools. Built with Tauri v2 + React (Rust).专业的 Antigravity 账号管理与切换工具。为 Antigravity 提供一键无缝账号切换功能。
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 68%
Response Time: 9h
First Timer Success: 61%
lbjlaq/Antigravity-Manager has a recorded first-timer success rate of 61.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in lbjlaq/Antigravity-Manager respond to incoming external pull requests in approximately 8.7 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.8 places lbjlaq/Antigravity-Manager in the A tier.
The external contributor pull request merge rate for lbjlaq/Antigravity-Manager is 68.3%, based on public PR activity from non-core contributors.
lbjlaq/Antigravity-Manager does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Rigorous architecture standards (80% critical review signals). Ensure PRs strictly follow guidelines before requesting review in lbjlaq/Antigravity-Manager.
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/lbjlaq/Antigravity-Manager?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (85% approval). Large PRs (>500 lines) take ~42 hours (31% approval). Keep your diff compact for rapid review.
[RFC / 技术探讨] 关于 IDE 自动切号的进阶思考：剖析我们本地补丁的缺陷，探讨真正的底层根治方案 一、 背景与交流目的 在 v4.8.0 推出“定向热切（仅重启 language_server）”后，主窗口闪退的问题已解决。 为了在通宵长跑和多 Agent 连续结对编程中实现“100% 无人值守”，我们在本地编写了一套外挂守护脚本（CPU 采样避让 + CDP 模拟点击）。实测中虽然解决了一定问题，但我们在实际工程压测中深刻体会到：外挂补丁存在严重的脆弱性与工程缺陷。 特此向作者梳理我们这套补丁暴露出的核心问题，并探讨如何从 AM 内部架构层面实现真正的根治，附上核心设计与代码，想听听作者的想法与规划。 二、 坦白复盘：我们本地外挂补丁存在的严重工程缺陷 我们在本地写的两层外挂补丁逻辑如下： 外挂补丁 1（Smart Drain）：外部脚本轮询采样 language_server 的
环境 Antigravity Manager: v4.7.13（官方 Docker headless，Ubuntu，--network host，上游 http://127.0.0.1:10808 自有固定出口节点） 账号池：7 个 Google AI Pro 账号，全部状态正常（在 Antigravity IDE 内可正常使用） 客户端：同一台 Windows 机器上同时跑 DSH（deepseek-harness）、Codex Desktop、Hermes（Nous Research） 现象 单个请求的上游 429 会被网关逐个记到池内所有账号上，导致整池进入 30 秒冷却，此后任何客户端的请求都会拿到： HTTP 503 【网关调度受限】… 调度详情: All accounts limited. Wait 16s. error_code: all_accounts_limited, upstream_error.detail: gateway_local_accounts_throttled 日志实证（v4.7.13，16:57:09→16:57:25，单个 req_103）： 16:57:09 ✓ Using account: citylord2026 → 429 → 轮换 16:57:10 ✓ Using account: taol88178 → 429 → 轮换 [Multi-account Round 1 (attempt 1/7): fast rotating (50ms)] 16:57:14 ✓ Using account: viswa
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 lbjlaq/Antigravity-Manager, 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 lbjlaq/Antigravity-Manager acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.3% were successfully merged into the primary branch.
lbjlaq/Antigravity-Manager has a recorded first-timer success rate of 61.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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.8 places lbjlaq/Antigravity-Manager in the Welcoming tier.
The external pull request merge rate is 68.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
lbjlaq/Antigravity-Manager 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 lbjlaq/Antigravity-Manager 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.