Effective September 1, 2026, Dosu's unlimited free tier for open source ends. Issue triage and Q&A move to our standard free tier. On the same date, Dosu retires hosted auto-labeling, label correction learning, PR size labels, the LGTM label, auto-merge labels, and milestone syncing. Dosu retired its hosted stale bot in August.
We partnered with Pullfrog and they built a handoff page for Dosu users to help you install Pullfrog in your repo. Dosu also published open source GitHub Actions workflows that preserve label learning, PR labels, and stale-issue automation.
Dosu feature compatibility#
| Dosu workflow | Pullfrog | OSS projects from Dosu | Worth knowing |
|---|---|---|---|
Answers when someone mentions @dosu on an issue | Mention @pullfrog in any issue or pull request comment | — | Pullfrog answers collaborators only by default. Update this in the repo's Mentions settings. |
| Auto Reply on new issues | Set Enrich issues to Custom with a prompt | — | Set this up as you configure Pullfrog. |
| Auto Draft, held on the Review page for your approval | Use Quick Links while Pullfrog's Enrich issues is off | — | Allows for manual approval before posting. |
| Answers in GitHub Discussions, in the categories you choose | No built-in equivalent; Pullfrog has read access to discussions but cannot post | — | You can continue to use Dosu. More below. |
| Hosted auto-labeling for new issues and pull requests, retired September 1 | Turn on Label issues, steered by free-text Labeling instructions | dosu-ai/auto-label | Both pick only from labels that exist in your repo. Pullfrog runs it as a hosted automation; Auto Label runs in your own Actions on a model you choose. |
| Label correction learning, retired September 1 | — | dosu-ai/auto-label | Auto Label stores corrections on a memory/auto-label branch in your repo, where you can read or reset them. |
PR size, LGTM, and auto-merge labels, retired September 1 | — | The dosu-ai/auto-label companion workflow | The companion uses PR metadata instead of a model, so it costs only Actions minutes. |
| Milestone syncing between pull requests and linked issues, retired September 1 | No built-in migration path documented | — | Manage milestones in GitHub or build a custom workflow for your repository. |
| Hosted stale bot, retired in August | — | dosu-ai/better-stale-bot | Better Stale Bot reads each thread before responding. |
| Issue answering and labeling have direct migration paths. Discussions, draft review, label learning, milestone syncing, and stale issues each require a choice about how your project will handle them. |
Decide how Pullfrog answers your community#
Enrich issues is the Pullfrog setting that starts an agent run on every new issue. It runs in Plan, Build, or Custom mode, and Custom is the mode that takes your own instructions. With Enrich issues off, Pullfrog posts a Quick Links comment on each new issue instead, and nothing runs until the issue author or a maintainer clicks one of its buttons. If you ran Dosu in Auto Reply, turning Enrich issues on gives you the same behavior. If you would rather decide issue by issue, leave it off and use the buttons.
The default that catches most maintainers is the non-collaborator gate. Pullfrog ignores triggers from anyone without repo access, which on a public repo is nearly everyone who files an issue. Turn on "Include issues from non-collaborators" under Enrich issues, and "Include mentions from non-collaborators" under Mentions to let them use @pullfrog. Pullfrog caps those runs at restricted mode with no override, so opening the gate gives the agent no write access.
Labeling is a separate toggle. Turn on Label issues and fill in Labeling instructions, something like "prefer specific labels over generic ones, use at most three." Those two settings replace Dosu's Auto-Label Issues.
Model choice matters less than it looks. A repo accepted into Pullfrog for OSS runs on the set Pullfrog funds, and the picker marks a recommended default. Take it. A repo outside the program pays for its own tokens, which the next section covers.
Three defaults govern what a community-filed issue can do to the agent. Pullfrog never puts an issue body in the prompt, so the agent has to fetch it with a tool and issue text cannot act as an instruction. Shell isolation stays on for public repos with no way to turn it off. GitHub tokens are short-lived, and Pullfrog revokes them when a run ends.
Model access#
Pullfrog runs in your repository's GitHub Actions, so model tokens are the only per-run cost. Point it at your own provider key, an existing Claude or Codex subscription, or Pullfrog Router.
Hand issue triage to Pullfrog#
Open the Agent in your Dosu dashboard and set Reply Mode to Mention. Dosu stops responding to new issues on its own and still answers a direct @dosu mention, so the two tools do not both reply to the same issue.
If you install replacement labeling workflows before September 1, turn off Auto-Label Issues and Auto-Label Pull Requests, along with Add Size Labels and Add LGTM Label, so two systems do not label the same item. Effective September 1, Dosu no longer runs these hosted automations and the controls disappear. Install dosu-ai/auto-label and its companion workflow to keep the behavior in GitHub Actions.
Leave the rest of Dosu in place. Discussions, Documents, and the pull request comment that proposes doc updates all keep working, and the Dosu GitHub App is what serves them. Removing the app would take those with it.
Gaps to plan for#
GitHub Discussions#
Dosu answers there in the categories you pick, defaulting to Q&A and Questions. Pullfrog's GitHub App has read access to discussions and no write access, so it can read a discussion but cannot post in one.
If your community asks its questions in Discussions, keep Dosu there. Run Pullfrog on issues, leave Dosu on Discussions, and Discussions traffic becomes the only draw on your Dosu credits. To build your own, GitHub fires discussion and discussion_comment workflow events, and the pullfrog/pullfrog action drops into any workflow as a step. Post the answer back with your workflow's own token.
Holding responses for review#
Dosu's Auto Draft queues an answer on the Review page for your team to publish, edit, or delete. Pullfrog has no equivalent queue. Quick Links is the nearest option, where the issue author starts the run instead. If review-before-posting is why you run Dosu in draft mode, start on Quick Links and read Pullfrog's output before turning Enrich issues on.
Label learning and PR labels#
dosu-ai/auto-label reproduces the hosted auto-labeler, including its correction loop. Corrections live on a memory/auto-label branch in your own repo, so each repo learns from its own history and you can read or reset the branch. A companion workflow handles size, LGTM, and auto-merge labels without a model. Its README covers migration from Dosu.
Milestone syncing#
Dosu no longer syncs milestones between pull requests and linked issues after September 1. Neither Pullfrog nor Dosu's OSS workflows document a built-in replacement. Manage milestones directly in GitHub, or add a repository workflow if your project depends on this synchronization.
Stale issues#
Install dosu-ai/better-stale-bot if you want to replace Dosu's retired hosted stale bot. Its migration guide maps Dosu's inactivity period, close delay, operation cap, and exempt labels to the GitHub Actions workflow.
Where to get help#
Pullfrog's team takes migration questions and OSS program applications at support@pullfrog.com.
Thank you for running Dosu on your open source projects. Maintainers were our first users, and the questions you asked helped us understand what you care about most regarding knowledge infrastructure. That work is focusing on the agentic era, the layer agents read from and write to as they work, and we are excited to continue building that future with you.