Orca is the ADE for working with a fleet of parallel agents. Run any coding agent with your own subscription. Available on desktop, mobile and remote runtime.
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 62%
Response Time: 6h
First Timer Success: 26%
stablyai/orca has a recorded first-timer success rate of 26.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in stablyai/orca respond to incoming external pull requests in approximately 6.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 71.4 places stablyai/orca in the S tier.
The external contributor pull request merge rate for stablyai/orca is 62.1%, based on public PR activity from non-core contributors.
stablyai/orca currently has 11 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Orca is the ADE for working with a fleet of parallel agents. Run any coding agent with your own subscription. Available on desktop, mobile and remote runtime.
Highly welcoming maintainers in stablyai/orca. Prompt code reviews with positive guidance for new contributors.
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/stablyai/orca?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 Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (78% approval). Large PRs (>500 lines) take ~29 hours (28% approval). Keep your diff compact for rapid review.
Operating system Windows Orca version 1.4.215 Details Environment Orca: reproduced on 1.4.212 and on the latest build (still broken after updating) OS: Windows 10 22H2 (19045) IME: Microsoft Pinyin (built-in; the only IME installed) 0804:{81D4E9C9-1D3B-41BC-9E6C-4B40BF79E35E}{FA550B04-5AD7-411F-A5AC-CA038EC515D7} Display: dual 4K monitors, both at 100% scaling Steps to reproduce Open a file in Orca's built-in file editor Switch to Microsoft Pinyin and start typing pinyin The preedit renders in the editor, but the OS candidate window never appears — not over the editor, not anywhere on either monitor Expected Candidate list shows up and characters can be selected, as in the terminal pane. Actual Composition works (preedit is visible), but the candidate window is never drawn. Typing Chinese in the editor is effectively impossible. Scope — what makes this interesting Surface Candidate window Orca terminal pane works Edge / Chrome web inputs works Orca file editor (Monac
Environment Orca 1.4.206, still present in 1.4.207 (the 1.4.207 bundle still calls retrieveUserQuota and never retrieveUserQuotaSummary/daily-cloudcode-pa) — Windows 11 Pro 10.0.26200 Antigravity CLI (agy) 1.2.9, model gemini-3.8-flash-high What happens Orca shows Antigravity quota as available while agy itself refuses requests with RESOURCE_EXHAUSTED (429): Individual quota reached ... Resets in 27h. The account's weekly bucket for the Gemini group was exhausted, but Orca never shows a weekly limit. What agy reports (source of truth) agy -p "/quota" --output-format json (no model turn, no quota spent) returns command.data.groups[].buckets[] with ids gemini-weekly, gemini-5h, 3p-weekly, 3p-5h, each with remaining_fraction, reset_time and disabled. In our case: gemini-weekly remaining_fraction 0 (reset next day), gemini-5h disabled, AI credits 0. What Orca appears to do (read from the 1.4.206 app bundle) Calls https://cloudcode-pa.googleapis.com/v1internal:retrieveUserQuota (pe
[Bug]: Qwen Code is never detected on Windows — node-launched agents need a script-path entry Summary On Windows, Orca never recognizes Qwen Code as a running agent, even though it is listed as a supported agent and launches fine. Every orchestration path that requires agent identity fails: orca orchestration worker-start --task <t> --worktree <w> --agent qwen-code → state: failed · stage: agent_readiness · lastError: timeout orca orchestration dispatch --task <t> --to <handle> --inject → runtime_error: "Cannot dispatch --inject to terminal <handle>: no recognized agent detected." The error message lists the detectable agents and qwen is in that list, so this is not a missing-agent problem — it is a detection problem specific to Windows. Environment Orca 1.4.192 (desktop, Windows) Agent runtime host (not WSL) OS Windows 11 Pro for Workstations 22631 Qwen Code 0.22.3 (official Windows installer) Node 24.14.0 The same setup works on Linux, which i
Operating system Linux Orca version v0.14.2 Details Summary When using Antigravity CLI (agy) to generate a commit message, Orca appears to pass --sandbox as the actual user prompt instead of the commit-generation prompt. Antigravity then responds with messages such as: The user request contains --sandbox Could you please clarify what you would like to do or build? Claude and Codex work correctly for commit message generation in the same Orca installation. Environment OS: Fedora Linux Orca: v0.14.2 Antigravity CLI: v1.1.12 Model: gemini-3.6-flash Effort: low Orca configuration Agent: Antigravity CLI arguments: --add-dir . --model gemini-3.6-flash --effort low --dangerously-skip-permissions Command template: {basePrompt} {stagedPatch} The issue also occurred before adding --add-dir and --dangerously-skip-permissions. Steps to reproduce Open a Git repository in Orca. Stage some changes. Select Antigravity as the Commit Message agent. Use gemini-3.6-flash with --effort low. Generate a
Operating system Windows 11 Pro 10.0.26200 (x64) Orca version 1.4.180 Details Summary On some OMP panes the sidebar agent status stays at working forever after the agent's turn has fully completed. The OMP process is alive and idle at its prompt (not exited-to-shell). The same Orca session shows other OMP panes completing correctly at the same time, so this is not a global hook outage. The distinguishing feature of every stuck pane I found is its ORCA_PANE_KEY: it is a reminted $$<base32-hash>:L$$ token instead of the normal <tabId>:<leafUuid> form. Panes with the normal UUID-form key report status fine; panes with the $$...$$ form never get a single hook event into agent-hooks/last-status.json, so the completion edge never fires and the persisted sleepingAgentSessionsByPaneKey record stays at state: working indefinitely. What is happening Orca mints a pane's identity in two ways: The normal path (makePaneKey(tabId, leafUuid) in src/shared/stable-pane-id.ts, used by pty:spawn / launch
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 stablyai/orca, 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 stablyai/orca acknowledge new external contributions in approximately 6 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.1% were successfully merged into the primary branch.
stablyai/orca has a recorded first-timer success rate of 26.5%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 71.4 places stablyai/orca in the Elite tier.
The external pull request merge rate is 62.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, stablyai/orca currently has 11 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for stablyai/orca 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.