[BUG] Over 6k issues labeled with "has repro" have been auto-closed since March 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?

This query indicates that over 6k issues that are labeled with has repro have been auto-closed since the beginning of March 2026.

<img width="1551" height="431" alt="Image" src="https://github.com/user-attachments/assets/584198f1-87f2-4181-8d8b-35ab417417e1" />

<br>
<br>

This behavior of the github-actions Issue Sweep workflow is inconsistent with the repository maintainers explanation of the issue auto-closing process:

Issues here are auto-closed by a bot when they've had no activity for a while and are missing information needed to reproduce (usually a version and steps, or a /feedback ID). Nothing is triaged solely by counting.

The incorrect auto-close behavior is aggravated by the Lock Stale Issues workflow that locks closed issues that are inactive for 7 days. Because commenting on locked issues is not possible, this locking behavior is contrary to the explanation provided by the maintainers of this repo

If one of your issues was closed and is still relevant, commenting on it with the current version and a repro is enough — a maintainer can reopen it; you don't need to re-file.

What Should Happen?

1) Issues that require additional information from the author are not marked with has repro
2) Issues that are marked by has repro are not auto-closed due to inactivity (due to lack of fresh human comments)

The above two points are symptoms of the issue management process that does not correspond to the maintainers explanation.
The repo maintainers may implement a different issue labeling mechanism (see for example https://github.com/anthropics/claude-code/issues/21732 or https://github.com/anthropics/claude-code/pull/26360#issuecomment-3917183519), or a recent mechanims of labeling issues with reproduced. However, issues labeled with reproduced also appear to be subject to auto-closing due to inactivity.

The goal is to correct the bots behavior so it corresponds to the maintaners explanation: issues that contain reproduction steps are not auto-closed based on inactivity, and document the issue lifecycle process.

Error Messages/Logs

Steps to Reproduce

Determine that issues that don't collect at least 10 thumbs up and have no recent comments will be auto-closed.

1. Check the Issue Sweep workflow has these settings: 14 days for stale, additional 14 days for autoclose, with stale marking exemption for issues with 10 or more thumbs up:

https://github.com/anthropics/claude-code/blob/01f1617f14452ac78bf319cef2236d87c0fe05cb/scripts/issue-lifecycle.ts#L22-L38.

1. Verify the workflow does not exlude issues that contain information needed to reproduce (usually a version and steps, or a /feedback ID) from auto-closing.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.233 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Xterm

Additional Information

Some issues returned by the query may have incomplete reproduction steps, missing Claude Version or missing /feedback ID. Such cases should not be labeled by has repro, and instead the issue author needs to notified about the information that is missing. Currently there is no such notification due to https://github.com/anthropics/claude-code/issues/46083#issuecomment-5311671488.

In the comments and links below you'll find examples of issues that were (or were about to be) auto-closed due to inactivity despite containing reproduction information.