Open-source control plane for AI coding agents. Run an AI engineering team: parallel Claude Code, Codex, and Gemini workers with a shared board, atomic tasks, schedules, loops, origin-stamped messaging, model switching, and self-healing recovery. One dashboard, or your phone. MIT, single Rust binary.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 60%
Response Time: -
First Timer Success: 75%
mixpeek/amux has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mixpeek/amux 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 66.2 places mixpeek/amux in the A tier.
The external contributor pull request merge rate for mixpeek/amux is 60.0%, based on public PR activity from non-core contributors.
mixpeek/amux currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source control plane for AI coding agents. Run an AI engineering team: parallel Claude Code, Codex, and Gemini workers with a shared board, atomic tasks, schedules, loops, origin-stamped messaging, model switching, and self-healing recovery. One dashboard, or your phone. MIT, single Rust binary.
Active maintainer team in mixpeek/amux welcoming community pull requests and bug fixes.
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/mixpeek/amux?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (78% approval). Large PRs (>500 lines) take ~23 hours (28% approval). Keep your diff compact for rapid review.
Objective: Explicit per-session capabilities the harness enforces outside the sandbox: filesystem read/write globs, shell allow/deny, network allow-hosts, secret exposure, and action gates (e.g. deploy_production: approval_required). The model gets freedom inside its sandbox; amux enforces the boundary. Fits the north star: amux owns isolation and safety. Don't rely on the model to remember what it may do — especially critical as the MCP tool surface broadens (tool poisoning, privilege escalation, auditability). Scope Per-session capability manifest + enforcement points (fs/shell/net/secrets/actions). Approval-required gates for high-risk actions. Depends on: pairs with the MCP broker and transactional side effects. Avoid: prompt-based "please don't" guardrails. Part of #46 (amux harness roadmap).
Objective: Every command to an agent/tool carries command_id / task_id / attempt / timestamps / result_hash so reconnects and crashes never duplicate steering, deploys, emails, or browser actions (generalizes today's send-dedup + steering settle). For risky/business side effects (send email, submit claim, CRM update, delete record, deploy, money movement): represent the action as a proposal → validate schema → check permissions → detect duplication → preview impact → approve if required → execute → record receipt, with policy by risk level. Fits the north star: amux owns execution and accountability. Boring infra that is exactly what lets stronger models act more autonomously without causing more chaos. Scope Idempotency keys + precondition checks + dry-run + compensation actions on side-effectful tools. Risk-tiered approval thresholds (read CRM = immediate; delete prod / move money = always approve). Depends on: capability-based permissions; event sourcing. Avoid: trus
Objective: The environment decides done, not the model. Board items carry machine-readable acceptance (commands, required/forbidden files, endpoint assertions, review-required). Before risky ops, auto-checkpoint (commit/stash + diff + task/db state). On failure, restore the pre-change checkpoint and retry a clean task with a structured failure bundle — not by stuffing the old conversation back into context. Fits the north star: amux owns verification and recovery. Generalizes the existing board done/verified gate into a reusable verification engine (tests, linters, browser assertions, deploy health, custom scripts). The model can improve indefinitely while success criteria stay external and deterministic. Loop: agent reports done → amux runs gates → failures become evidence → same/different model receives only the failure bundle → task can't advance until gates pass or a human waives. Scope Verification engine runners (shell/test/lint/browser/deploy-health/custom). Checkpoin
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 mixpeek/amux, 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 mixpeek/amux acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.0% were successfully merged into the primary branch.
mixpeek/amux has a recorded first-timer success rate of 75.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 66.2 places mixpeek/amux in the Welcoming tier.
The external pull request merge rate is 60.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mixpeek/amux currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for mixpeek/amux 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.