Home / Blog / Claude Code Over 6k issues labeled with has repro have been…
Tech News

Claude Code Over 6k issues labeled with has repro have been auto-closed

. Claude Code Over 6k issues labeled with has repro have been auto-closed Why it matters for engineering teams What shipped and who is affected.

By Dillip Chowdary • Sep 28, 2026 • Source: HN Claude/Codex/Fable

Claude Code Over 6k issues labeled with has repro have been auto-closed
Illustration · Pexels

01What shipped

HN Claude/Codex/Fable reports: Claude Code Over 6k issues labeled with has repro have been auto-closed. Article URL: https://github.com/anthropics/claude-code/issues/87647 Comments URL: https://news.ycombinator.com/item?id=49697749 Points: 4 # Comments: 0

This query indicates that over 6k issues that are labeled with has repro have been auto-closed since the beginning of March 2026. This behavior of the github-actions Issue Sweep workflow is inconsistent with the repository maintainers explanation of the issue auto-closing process.

02What improved

The explanation was written by Claude, but posted by a human GitHub account: 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). The incorrect auto-close behavior is aggravated by the Lock Stale Issues workflow that locks closed issues that are inactive for 7 days (on a side note, that locking wokrflow is under a strain so it may experience delays #69470).

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

03What you gain

The repo maintainers may implement a different issue labeling mechanism (see for example #21732 or #26360 (comment)), or a recent mechanims of labeling issues with reproduced. See the full write-up from HN Claude/Codex/Fable via the source link for quotes and complete context.

However, issues labeled with reproduced are also subject to auto-closing due to inactivity, despite maintainers expressing the goal to keep the issues open. 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.

04How to get it

Moreover, document the issue lifecycle process so the users of this repo know what to expect from the process, including notifications when reported issues are fixed (see #21733 for an example suggestion how this can be handled). 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.

05What to watch next

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. See the full write-up from HN Claude/Codex/Fable via the source link for quotes and complete context.

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →