We love open source
Root cause analysis for public repositories
Operate reads the code of open-source projects and traces the root cause of their open issues. Free, no sign-up. Explore what it is finding below, or point it at a repo you care about.
Investigating 70 open-source projects
Recent investigations
- open-webui/open-webui #32518 issue: The rebuilt search dialog no longer understands any of its five filters, and archived chats cannot be found7d ago
- pingdotgg/t3code #20146 [Bug]: Aproval prompts do not show the command being approved7d ago
- Textualize/rich #4238 [BUG] Traceback.extract loops forever when __cause__ and __context__ form a cycle7d ago
- rclone/rclone #10051 drive: newly supported pure Markdown format file on Google Drive appear empty on mount7d ago
- navidrome/navidrome #6316 [Bug]: Invalid playlist causing playlists not to show7d ago
- freeCodeCamp/freeCodeCamp #69421 Trivia Bot lab hints hard-code console.log call indices, breaking valid solutions with extra logging8d ago
- freeCodeCamp/freeCodeCamp #70862 Truthy and Falsy Values: correct grammar and evaluation explanations8d ago
- freeCodeCamp/freeCodeCamp #70861 Booleans and Conditionals: use four-space indentation in syntax examples8d ago
All repositories
- alpinejs/alpine
- apache/cloudstack
- apache/shenyu
- apache/superset
- AppFlowy-IO/AppFlowy
- appwrite/appwrite
- caddyserver/caddy
- cli/cli
- ClickHouse/ClickHouse
- coditori/highly-skilled-job-offers
- containerd/nerdctl
- containers/kubernetes-mcp-server
- coollabsio/coolify
- dokku/dokku
- duckdb/duckdb
- element-hq/element-web
- encode/httpx
- etcd-io/etcd
- freeCodeCamp/freeCodeCamp
- GetBindu/Bindu
- getsentry/sentry
- go-gitea/gitea
- google/adk-python
- grafana/grafana
- hashicorp/vault
- HeyPuter/puter
- home-assistant/core
- huggingface/pytorch-image-models
- immich-app/immich
- jellyfin/jellyfin
- jenkinsci/jenkins
- json-schema-org/JSON-Schema-Test-Suite
- keploy/keploy
- kovidgoyal/kitty
- kubernetes/kubernetes
- lysine-dev/okhttp
- mastodon/mastodon
- medplum/medplum
- meilisearch/meilisearch
- mobxjs/mobx
- n8n-io/n8n
- nats-io/nats-server
- navidrome/navidrome
- neovim/neovim
- nextcloud/server
- NixOS/nixpkgs
- open-gsd/gsd-pi
- open-webui/open-webui
- pandas-dev/pandas
- pingdotgg/t3code
- pocketbase/pocketbase
- podman-container-tools/podman
- pola-rs/polars
- PostHog/posthog
- prisma/orm
- pulumi/pulumi
- pydantic/pydantic
- questdb/questdb
- rclone/rclone
- spring-projects/spring-boot
- stdlib-js/stdlib
- supabase/supabase
- syncthing/syncthing
- temporalio/temporal
- Textualize/rich
- traefik/traefik
- twentyhq/twenty
- valkey-io/valkey
- whiskeysockets/Baileys
- zulip/zulip
What this page is
Operate runs root cause analysis on open issues in public GitHub and GitLab repositories. Anyone can link a public repository and pick an issue, with no account needed. Operate's agents read the issue, search the source code, walk the git history, and publish an evidence-backed explanation of what is most likely causing the problem.
The projects listed here cover databases, developer tools, observability platforms, home automation, media servers, and infrastructure software. Each project page lists its open issues, and each investigated issue has its own page with the full analysis.
How an investigation works
Every investigation uses the same four-agent pipeline Operate uses on production systems. A Context agent gathers the issue text, related code, and discussion. A Root Cause agent forms a hypothesis and cites the files and lines behind it. A Verification agent checks that hypothesis independently with a second model and rejects claims the evidence does not support. A Resolution agent then suggests a fix, as a patch where possible.
Operate never pushes code, opens pull requests, or comments on the upstream repository. Results stay on this site for maintainers and contributors to review and use as they see fit.
Who it is for
Maintainers use these investigations to triage incoming issues faster and spot duplicates or configuration mistakes. Contributors use them to find where to start reading in an unfamiliar codebase. Engineering teams evaluating AI SRE tools use them to see, on code anyone can inspect, how Operate reasons before they run it on their own systems.
Investigating your own repository
To try it on a project you care about, paste its public repository URL into the box above. Operate links the repository, lists its open issues, and lets you start an investigation on any of them. For private code and production systems, run Operate inside your own infrastructure. Its adapters are read-only, and an engineer approves every change.