[BUG]

Resolved 💬 3 comments Opened Jan 7, 2026 by dwalend Closed Feb 21, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Bug processing in claude-code's issues tracker (right here) has a broken workflow.

I find a bug, search for duplicates, find a match that is closed. The closed ticket says it is closed due to lack of progress for a week, and to start a new bug instead of reopening the old bug.

So I put in the work to enter my bug - citing the old bug that you closed automatically without ever addressing.

A few moments later I get a note that says the new bug is a duplicate that will automatically be closed in 3 days - citing the closed bug - the one that said to open a new bug.

This is broken. This is pathetic. This is not acceptable for a product that costs money.

See https://github.com/anthropics/claude-code/issues/16636#issuecomment-3719618546 for an example.

What Should Happen?

You should fix your bugs. You should not close duplicates until the duplicate bug is fixed and verified as fixing the maybe-not-duplicate problem.

Error Messages/Logs

Steps to Reproduce

Find a bug, search for duplicates, find a match that is closed. The closed ticket says it is closed due to lack of progress for a week, and to start a new bug instead of reopening the old bug.

Put in the work to enter a new bug - citing the old bug that was closed automatically without ever addressing.

A few moments later you will get a note that says the new bug is a duplicate that will automatically be closed in 3 days - citing the closed bug - the one that said to open a new bug.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.76 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗