Ross ROSS = Recommend OSS · open-source software intelligence for agents

ColeMurray/background-agents

An open-source background agents coding system observed · 2026-08-28

github.com/ColeMurray/background-agents · homepage · TypeScript · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

60/100

  • Activity 99
  • Release rhythm 35
  • Longevity 15

Flags: no_releases

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 220
  • days_rel: n/a
  • days_push: 7
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

2683 stars · 393 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

An open-source, self-hostable background coding agent system (Open-Inspect) inspired by Ramp's Inspect, where AI agents work on tasks in sandboxed dev environments and turn requests from Slack, GitHub, Linear, or web UI into pull requests. It supports multiple AI models, scheduled/cron triggers, parallel sub-task sandboxes, and real-time multiplayer sessions, designed for single-tenant deployment by trusted teams.

Use cases

  • turn slack messages into pull requests automatically
  • run coding agents in the background on scheduled tasks
  • let non-engineers like PMs and designers ship code changes
  • spawn parallel AI coding agents on separate tasks
  • self-host a background coding agent for my team
  • create PRs from linear issues automatically
  • collaborate with teammates in a live agent coding session

When to choose

  • your team wants an open-source, self-hosted alternative to hosted background coding agents
  • you want non-engineers to submit code changes as reviewable PRs
  • you need agents triggered from Slack, GitHub, Linear, webhooks, or cron schedules
  • you want to use your own AI model subscriptions (Claude, Codex, Grok)

When to avoid

  • you need multi-tenant deployment with per-user repository access control - the security model explicitly assumes all users are trusted
  • you want a fully managed SaaS with zero infrastructure to run
  • your organization requires strict per-user permission validation before agent sessions access repositories

Facets

service · maturity active

agent-framework llm-inference workflow-automation webhook developer-tools developer-tools large-language-models self-hosted self-hosted background-agents coding-agent slack-integration github-app linear-integration multiplayer-sessions sandboxed-environments pull-request-automation single-tenant ai-agents automation web-server docker nodejs typescript

2 sources

Member repositories

RepositoryRoleHealth v2
ColeMurray/background-agentsmain60

For agents

markdown · JSON · MCP: product_card(name="ColeMurray/background-agents")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem