github
dokku/dokku
Pick an open issue and Operate will investigate its root cause.
This page lists the open issues reported on the dokku/dokku repository. For any issue, Operate's AI SRE agents read the report, clone the dokku source code, walk the git history and blame, and trace the failure back to the lines of code most likely responsible. Each investigation produces an evidence-backed root cause analysis that maintainers and contributors can review before writing a fix.
Investigations run through the same four-agent pipeline Operate uses on production systems: a Context agent gathers the relevant code and discussion, a Root Cause agent forms a hypothesis, a Verification agent independently checks it with a second model, and a Resolution agent suggests a fix. Nothing is pushed to dokku/dokku — results are published here for humans to judge.
23 open issues
- #9226 Support curl-based healthchecks in json cron entriesmerge-level: minor
- #9211 nginx plugin: support HTTP/3 (QUIC) listenerstype: enhancementmerge-level: minor
- #8938 Add a `releases` command for deployment history (à la `heroku releases`)merge-level: minorneeds: plan
- #8936 Add support for multiple TLS certificates on a given appmerge-level: minorneeds: planplugin: scheduler-k3s
- #8935 Add support for managing Gateway API resources for the k3s schedulermerge-level: minorneeds: planplugin: scheduler-k3s
- #8932 Run deploy-phase deployment tasks in the cluster rather than on the Dokku hosttype: enhancementmerge-level: minorneeds: planplugin: scheduler-k3s
- #8837 config: support atomically replacing an app's entire environmentmerge-level: minorstatus: has planplugin: config
- #8532 Add --group <name> feature to config:* similar to --globalmerge-level: minorstatus: has planplugin: config
- #8414 Internal links for old versions of docs are sometimes brokenneeds: investigation
- #8142 Add redirect support to nginx pluginView investigationmerge-level: minorneeds: investigationplugin: nginx
- #7604 Image cache not cleaned automaticallymerge-level: patchdifficulty: easystatus: has planplugin: buildersestimate: 2h
- #7544 Retain old images on deployView investigationmerge-level: minordifficulty: mediumstatus: has planplugin: buildersplugin: commonplugin: registryestimate: 8h
- #7396 Scale processes without restarting the appmerge-level: minordifficulty: easystatus: has planplugin: psestimate: 2h
- #5102 Docker Compose Supportmerge-level: minordifficulty: mediumstatus: has planplugin: buildersplugin: schedulersestimate: 10h
- #4489 Deployment Task on Failneeds: more infomerge-level: minordifficulty: hardstatus: has planplugin: app-json
- #3443 Move nginx config to `/etc/nginx/dokku.d`merge-level: minordifficulty: mediumstatus: has planplugin: nginxestimate: 8h
- #3116 Dockerfile multiphase build cache issuesmerge-level: patchdifficulty: mediumstatus: has planestimate: 3hplugin: builder-dockerfile
- #1878 Who uses dokku and for what purposes?needs: more infodifficulty: easy
How Operate investigates dokku/dokku issues
When you pick an open issue on dokku/dokku, Operate starts with the issue itself: the title, the description, the reproduction steps, any stack traces or log excerpts pasted by the reporter, and the discussion that followed. Those details become the starting evidence. From there the agents search the dokku codebase for the functions, modules, and configuration that the report points at, rather than guessing from the issue text alone.
Next, Operate looks at how that code got to its current state. It walks the git history and blame for the suspect files, so a regression introduced by a recent commit can be told apart from a long-standing limitation. A good root cause analysis answers three questions: what is failing, why it fails, and when the behaviour started. Git history is often the fastest way to answer the third question.
Each hypothesis is then checked by a separate Verification agent running on a second model. If the evidence does not support the claimed cause, the investigation says so instead of presenting a confident guess. The aim is an explanation a dokku maintainer can confirm in minutes by following the cited files and line numbers.
What you get from each investigation
A finished investigation links to the specific files and lines most likely responsible, summarises the reasoning that connects the reported symptom to that code, and notes how confident the agents are. Where it makes sense, the Resolution agent drafts a suggested fix as a patch. Operate never commits, opens pull requests, or pushes anything to dokku/dokku. Results are published on this site so people can judge them.
Maintainers can use an investigation to triage faster, deciding whether an issue is a real bug, a configuration problem, or a duplicate. Contributors can use it as a map of where to start reading before writing a fix. Reporters can use it to add the missing detail that makes an issue actionable.
How to read a root cause analysis
Treat every investigation as a well-argued lead, not a verdict. Start with the cited code and check that it does what the analysis says. Then compare the suggested trigger with the reproduction steps in the issue. If both line up, the analysis has probably found the cause. If they don't, the evidence section usually shows where the reasoning went wrong. That is useful too, because it rules out one explanation.
Issues that depend on a specific environment, such as an operating system version, a hardware quirk, or a third-party service, are harder to diagnose from code alone. In those cases, Operate says what it could not verify instead of filling the gap.
Why Operate investigates open-source projects
Operate is a self-hosted AI platform that teams run inside their own infrastructure to investigate production issues. Its production adapters are read-only, and an engineer reviews and applies any proposed change. Running the same pipeline in public on projects like dokku/dokku shows how it reasons on real code that anyone can inspect. It also gives back something useful to the maintainers whose work much of the industry depends on.