Compared with other tools¶

← README · Security design · Questions and troubleshooting

What the issue assistant does differently from the tools that maintainers use for issues today, and when another one is the better choice.

Other tools cover parts of this; only GitHub Agentic Workflows, and the workflows built on it, share its design. Checked on 2026-10-13:

The issue examples of the Claude Code action let the AI set labels and post comments itself, with a token that writes to issues and no check of its answer before it is posted.
GitHub Agentic Workflows (gh-aw) has the closest design: an agent with a read-only token behind a firewall, and writes through limited safe outputs after a second AI pass looks for threats. It is a general framework in version 0.x, in which you write and compile the triage workflow yourself; reminders, duplicates that close and the closing with the release are not part of its triage.
actions/stale closes inactive issues without AI, by default 60 and then 7 days after the last activity. It writes no analysis, and limiting it to issues that wait for their reporter takes a label such as needs-info, which something else has to set.
Dosu is a hosted service for documentation now. Its labels and its stale bot became open-source workflows on gh-aw, which run with your own engine.
GitHub's duplicate detection, in public preview, suggests up to three similar issues while a reporter writes. It goes well with the assistant, which also finds duplicates of an issue that exists.

Feature by feature¶

Each cell names the sources of its tool, as of the day above; the column of the issue assistant is what this documentation describes.

	Issue assistant	Claude Code action examples	gh-aw issue triage	actions/stale	Dosu	GitHub's duplicate detection
A first analysis of a new issue	The likely cause with links to the lines of code, what to try and what is missing, in the reporter's language	No: the triage example only labels, and the duplicates example comments only on a duplicate¹	A comment that explains its label and how the issue might be addressed²	No³	Not in its open-source workflows⁴	No⁵
Labels	From the issue forms and from the analysis, each with its reason; labels as code	The AI sets them¹	One from an allow list²	Only its stale label³	auto-label, which learns from the corrections of maintainers⁴	No⁵
Duplicates	A notice for a sure duplicate of an issue that a maintainer opened or triaged, and closing after 3 days unless someone objects; other ones become suggestions	A comment and the label `duplicate`¹	Not part of the triage workflow²	No³	Not in its open-source workflows⁴	Up to 3 suggestions while the reporter writes⁵
Issues that wait for their reporter	`needs-info`: a reminder after 15 days, closing after 30, and an answer reopens; other days and exemptions are settings	No¹	No²	Any inactive issue: stale after 60 days and closed 7 days later by default, or only those with a label³	better-stale-bot, whose AI reads the thread first; 60 and 7 days by default⁴	No⁵
Fixed issues close with the release that ships the fix	Yes, with a link to the release; "still broken" reopens	No¹	No²	No³	No⁴	No⁵
The AI can write to GitHub	No: its token only reads	Yes: `issues: write`, and the AI applies labels and comments¹	No: a token that only reads, and separate jobs write its safe outputs²	No AI³	No: built on gh-aw⁴	Not an agent⁵
The output of the AI is checked before it reaches GitHub	By a job without AI: schema, labels and issues that exist; refused when it holds anything like a secret; mentions, images, HTML and foreign links removed	No¹	Limits for each kind of output, allowed labels, and a second AI pass that looks for threats²	No AI³	As in gh-aw, with the second pass⁴	Not an agent⁵
The network of the AI	GitHub's egress firewall with an allow list	Not limited in the examples¹	gh-aw's own firewall, a proxy with an allow list²	No AI³	As in gh-aw⁴	Not an agent⁵
Who receives the issues	Your runners and the vendor of the engine	Your runners and Anthropic¹	Your runners and the vendor of the engine²	Your runners³	The workflows: your runners and the vendor of the engine; the hosted service: Dosu⁴	GitHub⁵
Engines	Claude; another one can be added	Claude¹	GitHub Copilot, Claude Code, Codex, Gemini CLI and others²	None³	Claude Haiku by default, or Copilot or Codex⁴	Not stated⁵
Price	Free; the engine, $0.20 for a triage with Claude Opus 5.5 at the prices of the API, measured	Free; the engine¹	Free; the engine²	Free³	The workflows free, the engine about $0.10 a run with Haiku; the hosted service free for public repositories with 200 credits a month, Pro $16 a month⁴	Not stated⁵
Set-up	One `install` command; `check` in CI keeps the workflows equal to the templates	Copy a workflow, a command and two scripts¹	Write the workflow in Markdown and compile it with `gh aw compile`²	One workflow³	`gh aw` for the workflows, a GitHub App for the hosted service⁴	Built into the form of a new issue⁵
Status	Version 1, signed releases with provenance	Version 1¹	Version 0.x, to use "with caution, and at your own risk"²	Version 10 and later³	A hosted service and open-source workflows⁴	Public preview⁵

The tools one by one¶

The issue examples of the Claude Code action¶

The Claude Code action is the engine of the issue assistant too. Its issue examples are short starting points: in the triage example, Claude runs two scripts that list and edit labels; in the duplicates example, it gets GitHub's tools to comment on and edit issues. Both grant issues: write, and nothing checks what Claude writes. That is the pattern that PromptPwnd and Comment and Control attack: the text of an issue steers an AI that can write. The assistant runs the same action with the reading tools alone and leaves every write to a job without AI, as the security design shows.

Choose the examples to learn the action in a repository where only trusted people open issues; choose the assistant where anyone can.

GitHub Agentic Workflows¶

gh-aw, by GitHub Next, is a framework for agents in GitHub Actions, and its design is the closest to the assistant's: the agent gets a token that only reads, runs behind a firewall, and asks for writes as safe outputs, which separate jobs carry out within limits after a second AI pass looked for threats. Its issue triage is an example to adapt, with one label and a comment. gh-aw runs many engines and any task you describe, and it calls itself a 0.x project to use with caution.

The assistant is narrower and complete for issues: a schema for each task, checks without AI of every link, mention and issue number, duplicates that close, reminders, the closing with the release, and check, which keeps every repository on the templates.

Choose gh-aw for agents of your own design across many tasks; choose the assistant for the whole life of issues, with nothing to write yourself.

actions/stale¶

actions/stale closes what stays inactive, without AI and for issues and pull requests alike: by default it marks an issue after 60 days and closes it 7 days later, and a new comment removes the mark. It can't tell an issue that waits for its reporter from one that waits for the maintainer, unless something else sets a label such as needs-info for it to look at.

The assistant sets needs-info itself when a question waits for the reporter, reminds after 15 days, closes after 30 and reopens on an answer. Like actions/stale, it takes other days, exempts issues by label, assignee or 👍, and can lock issues closed long ago, as [lifecycle] in config.toml sets. Keep actions/stale for pull requests if you like; for issues, the assistant does its work.

Dosu¶

Dosu's hosted service keeps documentation up to date. Its pricing page says that labels and the stale bot are "not as hosted features anymore": both became open-source workflows on gh-aw. auto-label labels issues and pull requests with Claude Haiku by default and learns from the corrections of maintainers; better-stale-bot reads a thread before it marks or closes an issue. Both share gh-aw's design and run with your own engine.

Choose Dosu's workflows for labels alone or a stale bot that reads; choose the assistant for an analysis, duplicates and the closing with the release as well.

GitHub's duplicate detection¶

Since June 2026, in public preview, the form of a new issue suggests up to three existing issues that look the same while the reporter writes. It prevents a duplicate before it exists. The assistant finds the duplicates that are opened anyway, says why, and closes a sure one after three days unless someone objects. Use both.

Keeping this current¶

The cells were checked against the sources below on the day at the top of this page. Tools change; a correction is welcome as an issue or a pull request.

anthropics/claude-code-action: examples/issue-triage.yml with the command that it runs, .claude/commands/label-issue.md; examples/issue-deduplication.yml; the releases. ↩↩↩↩↩↩↩↩↩↩↩↩↩
GitHub Agentic Workflows: the home page for its engines and gh aw compile; Meet the Workflows: Issue Triage of 2026-01-13; Architecture; Safe outputs; Threat detection, which is on whenever safe outputs are; the README and releases of github/gh-aw. ↩↩↩↩↩↩↩↩↩↩↩↩↩
actions/stale: README. ↩↩↩↩↩↩↩↩↩↩↩↩↩
Dosu: pricing; the READMEs of dosu-ai/auto-label and dosu-ai/better-stale-bot. ↩↩↩↩↩↩↩↩↩↩↩↩↩
GitHub changelog: Detecting Duplicate Issues – Public Preview, 2026-06-18. ↩↩↩↩↩↩↩↩↩↩↩↩↩