Anthropic may have forgotten to read their GitHub issues for two months

果物リン — Fri, 03 Apr 2026 16:30:29 +0000

TL;DR — four prompts, four answers

This entire investigation was four prompts I gave Claude (claude.ai, Sonnet 4.6) in Japanese. Here's the short version:

🇯🇵 Anthropic の claude code のリポジトリの Issue を巡回する公式 bot について質問させてください。Duplicated の検出や自動 Close について、いつからか止まっていませんか？
🇬🇧 "Has the duplicate detection bot in the Claude Code repo stopped working at some point?"
→ Yes. It went silent around January 27, 2026 and stayed down until ~April 1.

🇯🇵 その前後の Claude Code のバージョンと、大きな構造的な変化はありますか？
🇬🇧 "Were there any major structural changes around that time?"
→ v2.1.0 shipped on Jan 27 — 1,096 commits, npm deprecated, native binary. The bot broke the same day.

🇯🇵 このことを指摘している Issue はありますか？
🇬🇧 "Are there any Issues pointing this out?"
→ No. Nobody noticed publicly for two months.

🇯🇵 では、Github Issue 上ではなくブログポストではどうでしょうか？
🇬🇧 "What about blog posts?"
→ Nothing. You're reading the first one.

What happened between those prompts was a multi-turn conversation in which Claude Sonnet 4.6 performed the research — querying GitHub Actions logs, cross-referencing npm release dates, fetching the CHANGELOG, and building the timeline. The analysis, structure, and prose of this post are almost entirely Claude's work. I asked the questions; Claude found the evidence and wrote the article.

I'm publishing this as-is because the finding seems worth sharing publicly — and because it felt fitting that a post about Anthropic's AI-powered issue tracker should itself be AI-authored.

If you filed a bug report against anthropics/claude-code between late January and early April 2026 and wondered why you never got a "possible duplicate" comment — you weren't imagining it. The bot silently stopped for over two months.

It appears to have quietly restarted around April 1, 2026 — just days before this article was written. Here's what I found.

Background: how the repo manages 2,000+ issues per week

Claude Code is one of the fastest-growing developer tools in history. The GitHub repo has over 41,000 issues filed (issue numbers reach #43,000+ due to PRs and deletions). At roughly 2,000–2,500 new issues per week, manual triage is impossible. Anthropic built a suite of GitHub Actions bots to handle it:

Workflow	Model	Role
`claude-dedupe-issues.yml`	Claude Sonnet 4.5	Fires on every new issue, finds duplicates, posts a comment
`auto-close-duplicates.yml`	—	Daily sweep: auto-closes issues 3 days after a duplicate comment (unless the author thumbs-downed it)
`claude-issue-triage.yml`	Claude Opus 4.6	Labels every new issue (bug, invalid, needs-repro, etc.) — no comments
`sweep.yml`	—	Marks issues stale after 14 days, closes 14 days later
`lock-closed-issues.yml`	—	Locks closed issues after 7 days

The dedupe bot in particular is impressive in design: it launches 5 parallel sub-agents per issue to search for duplicates with diverse keywords, filters false positives, and posts a structured comment if matches are found. A significant portion of all issue closures in the repo have been bot-driven.

The anomaly: the dedupe bot went silent for ~20,000 issues

When I first investigated on April 4, 2026, the GitHub Actions page for claude-dedupe-issues.yml showed a clear gap: workflow runs referencing issues in the #21,138–#21,162 range, then nothing until the #42,200s.

That's a gap of roughly 20,000 issues — spanning late January to early April 2026 — during which the dedupe bot posted no duplicate-detection comments.

The workflow file never left the repo. The triage bot (label-only) continued to run on every new issue. But the dedupe bot — the one that posts comments and drives the auto-close cycle — was completely silent for over two months.

Update: The bot appears to have quietly restarted around issue #42,210 (approximately April 1, 2026). Issues filed after that point are once again receiving duplicate-detection comments. There has been no public announcement of either the outage or the restart.

When did it stop? Right as v2.1.0 shipped

Cross-referencing issue numbers with npm release dates (via mise-versions.jdx.dev) gives a precise timestamp:

Date	Event
Jan 23, 2026	Issue #20,302 filed — the last large batch of dedupe activity visible. v2.1.19 releases to npm.
Jan 27, 2026	v2.0.73 → v2.0.76 → v2.1.0 through v2.1.17 all released on the same day — a massive version restructuring. Dedupe bot goes silent around issue #21,162.
~Apr 1, 2026	Dedupe bot quietly resumes around issue #42,210. No announcement.

v2.1.0 was described by the community as bundling "1,096 commits" — the largest single release in Claude Code's history. The same day, npm installation was deprecated in favor of a native binary installer.

The coincidence is striking. Whatever broke, it broke exactly then — and whatever fixed it, it was fixed just as quietly.

Has anyone noticed? Not publicly

I searched GitHub Issues, Hacker News, Reddit, and tech blogs for any mention of the dedupe bot being inactive. I found nothing.

The closest thing is a March 14, 2026 community analysis (a GitHub Gist, written by Claude Opus 4.6 itself inside a Claude Code session) that analyzed the repo's issue tracker in depth. It described the dedupe bot as still actively "processing every new issue for duplicate detection" — which was factually incorrect at the time. The analysis was written 7 weeks after the bot stopped, but since the workflow file still existed and the cumulative duplicate-labeled issues still numbered over 10,000, it appeared operational.

The triage bot (label-only, no comments) kept running fine on new issues throughout. So new issues got labels. They just didn't get duplicate detection or the associated auto-close.

What this meant in practice

Before January 27, the flow for a new bug report was roughly:

New issue filed
  → Dedupe bot fires (5 parallel agents, ~4 min)
  → "Found N possible duplicates" comment posted
  → If no 👎 within 3 days → auto-closed as duplicate
  → Closed issue locked after 7 more days

From January 27 through early April:

New issue filed
  → Triage bot labels it (bug, platform:macos, etc.)
  → Issue stays open indefinitely
  → (Stale bot may eventually close after 28 days of inactivity)

The practical effect: duplicate issues that would previously have been auto-closed within a week accumulated as open issues. By early April 2026, the open issue count had grown to approximately 9,000 — and during the outage period, none of the new duplicates were being caught.

A note on the criticism that existed before

Ironically, the most vocal community criticism before the bot stopped was about the bot being too aggressive — not about it being absent. Issue #20302 (filed January 23, 2026, four days before the bot stopped) argued that the auto-close mechanism was harmful because:

The codebase is closed-source, so users can't verify whether their bug truly shares a root cause with the "duplicate"
Burden of proof falls on reporters to actively contest within 3 days — vacations, time zones, etc. cause valid bugs to be silently closed
The bot created circular duplicate chains — 32 cases where issue A was marked duplicate of B and B was marked duplicate of A

That issue is still open. Anthropic never responded to it.

What might have caused it

I can only speculate from public information:

The workflow hardcodes --model claude-sonnet-4-5-20250929. If that model string became invalid or the associated API key was rotated during the v2.1.0 restructuring, the workflow would fail silently.
The massive same-day release of v2.0.73 through v2.1.17 suggests a significant infrastructure reorganization — something may have been misconfigured in the process.
It may have been intentional — the community criticism was real, and Anthropic may have quietly decided to pause the aggressive auto-close mechanism without announcing it.

The quiet restart around April 1 adds another layer: if it was intentional, why restart without announcement? If it was accidental, the two-month gap suggests no monitoring was in place.

One thing I haven't been able to verify from public data alone: whether the bot was completely non-functional during this period, or whether it was partially operational — for instance, hitting a rate limit or quota that caused it to process only a fraction of incoming issues. The workflow runs page shows a clear gap, but it's possible that some issues were processed without leaving visible traces. A more thorough analysis — checking individual issues across the gap for any bot activity — would be needed to confirm a total outage versus a partial degradation.

Whatever the reason, there has been no public communication about either the outage or the restart.

The bigger picture

The bot is back now. But roughly 20,000 issues passed through without duplicate detection.

Among those 20,000 issues, there are genuine bug reports, feature requests, and pain points from real users who took the time to file them. Some of those reports may contain signal that Anthropic needs — reproducible bugs, edge cases, workflow friction that only shows up at scale.

The question isn't really about the bot. It's about those issues. Will Anthropic go back and process the backlog? Will someone review the issues that accumulated during the gap to ensure nothing important was lost in the noise?

If you filed an issue between #21,163 and #42,209, it may have been a duplicate — or it may have been the one report that captures a bug no one else described well enough. Right now, there's no way to tell, because the system that was supposed to sort them was offline.

I'd like to think the answer is yes — that Anthropic will find a way to retroactively triage that window. But there's been no public indication either way.

All data sourced from publicly visible GitHub Actions logs, npm registry history via mise-versions.jdx.dev, and the anthropics/claude-code repository. Workflow run counts, version dates, and issue numbers verified at time of writing (April 4, 2026).

DEV Community: 果物リン