An open-source background agents coding system
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 77%
Response Time: -
First Timer Success: 54%
ColeMurray/background-agents has a recorded first-timer success rate of 54.2%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ColeMurray/background-agents 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 70.4 places ColeMurray/background-agents in the S tier.
The external contributor pull request merge rate for ColeMurray/background-agents is 77.2%, based on public PR activity from non-core contributors.
ColeMurray/background-agents currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An open-source background agents coding system
Highly welcoming maintainers in ColeMurray/background-agents. 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/ColeMurray/background-agents?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (35% approval). Keep your diff compact for rapid review.
Problem The Changes panel lets users inspect a selected file as a unified or split diff. For Markdown changes, users also need to see the rendered document to review formatting and readability without leaving the session. Add a Preview option for the selected Markdown file, alongside access to the existing text diff. Requirements Offer an accessible Preview option for Markdown files (including .md and .markdown, case-insensitively). Keep the selected repository and file identifiable, and allow returning to the diff without losing the selection or existing diff preferences. Other file types retain the current diff experience. Render the complete resulting document represented by the selected diff revision, including unchanged content—not the Git patch, only added lines, or the repository's latest committed version. Added and untracked Markdown files are included when their content is available. Deleted lines, Git headers, and hunk markers must not appear as document content. Support
Summary Sessions created by the GitHub integration (PR reviews and @mention actions) always run on the OpenCode harness, and there's no way to choose Claude Agent. The rest of the product already supports it: the web composer, automations, and child sessions all do. We want the GitHub integration to offer Claude Agent as an option operators can switch to. OpenCode stays the default, so existing behavior doesn't change unless someone opts in. Companion to #2034 (Linear) and #2044 (Slack). All three should end up with consistent behavior, especially for model/harness mismatches. Current behavior packages/github-bot/src/handlers.ts → createSession() posts the target, title, model, reasoningEffort and SCM identity to POST /sessions, but no harness. The control plane (routes/session-create.ts) then resolves getValidHarnessOrDefault(undefined) → DEFAULT_HARNESS ("opencode"). Four handlers create sessions this way: handleReviewRequested: the bot is requested as a reviewer handlePullRequ
Summary Slack-triggered sessions always run on the OpenCode harness, and users have no way to choose Claude Agent. The rest of the product already supports it: the web composer, automations, and child sessions all do. We want the Slack integration to offer Claude Agent as an option operators can switch to. OpenCode stays the default, so existing behavior doesn't change unless someone opts in. Companion to #2034, which covers the same change for the Linear integration. The two should end up with consistent behavior, especially for model/harness mismatches. Current behavior packages/slack-bot/src/sessions/control-plane-client.ts → createSession() posts the target, model, reasoningEffort and actor fields to POST /sessions, but no harness. The control plane (routes/session-create.ts) then resolves getValidHarnessOrDefault(undefined) → DEFAULT_HARNESS ("opencode"). Slack integration settings (slackGlobalSettingsSchema / slackRepoSettingsSchema in packages/shared/src/types/integrations.
Summary Linear-triggered sessions always run on the OpenCode harness. There is no way to choose the Claude Agent harness for them, even though the rest of the product already supports it: the web composer, automations, and child sessions all do. We want the Linear integration to offer Claude Agent as an option operators can switch to. OpenCode stays the default, so existing behavior doesn't change unless someone opts in. Current behavior packages/linear-bot/src/webhook-handler.ts → createSession() posts title, model, reasoningEffort and the target to POST /sessions, but no harness. The control plane (routes/session-create.ts) then resolves getValidHarnessOrDefault(undefined) → DEFAULT_HARNESS ("opencode"). linearBotSettingsSchema (packages/shared/src/types/integrations.ts) has no harness field. The resolved-config endpoint (GET /integration-settings/linear/resolved/:owner/:name) and the bot's ResolvedLinearConfig (linear-bot/src/utils/integration-config.ts) don't return one either
Summary Agents frequently include Mermaid diagrams in responses, but the session timeline currently displays mermaid fenced code blocks as plain preformatted text. Render these blocks as diagrams while preserving the existing behavior for other code blocks. This issue intentionally describes the required outcomes rather than prescribing a library or component design. Existing behavior Markdown is rendered by packages/web/src/components/safe-markdown.tsx using react-markdown, remark-gfm, rehype-highlight, and rehype-sanitize. The primary timeline call site is packages/web/src/components/session-timeline.tsx. SafeMarkdown is also used for pull request bodies and GitHub review feedback, which must not regress. Requirements Rendering Render fenced mermaid blocks as diagrams in assistant timeline messages. Support the diagram types provided by the selected renderer without introducing an application-specific allowlist. Preserve current syntax highlighting and styling for all non-Mermaid co
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 ColeMurray/background-agents, 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 ColeMurray/background-agents acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.2% were successfully merged into the primary branch.
ColeMurray/background-agents has a recorded first-timer success rate of 54.2%. 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 70.4 places ColeMurray/background-agents in the Elite tier.
The external pull request merge rate is 77.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ColeMurray/background-agents currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ColeMurray/background-agents 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.