Claude Code's GitHub page auto closes issues after 60 days

[dcreater]

Claude Code has over 5000 open issues. And this is after issues that are inactive for 60 days being auto closed. Such a policy is facetious to say the least. What is more perplexing is why they don't use Claude to triage the issues?

[sdwr]

I think the idea is that nobody will be using CC in 5 years. If anthropic loses, nobody will use it. If anthropic wins, still nobody will use it! The value is in the model solving problems, and CC is just the hacky vessel for that, not the end goal. If they believe in themselves, polishing the product is a waste of time.

[bmitc]

> What is more perplexing is why they don't use Claude to triage the issues?

I wonder if it's because of cost.

[assbuttbuttass]

Yeah, it only checks whether the last bot comment is older than 30 days, completely ignoring any human comment

    if (botCommentDate < oneMonthAgo) {
        // Close the issue - it's been stale for 60+ days

Hard to imagine how this got past code review...

https://github.com/anthropics/claude-code/blob/5e3e9408feea9...

[sunaookami]

>code review

This implies they do any. Every Claude Code release is full of regressions and new features that are released barely work or need hotfixes.

[raincole]

This is about some issues are closed incorrectly due to a bug.

But as for the policy itself, why not? If an issue is inactive for 60 days it's very likely to stay so forever.

[kingstnap]

Closing things just so you have less open issues is the worst kind of dashboard driven development / goodharts law style of process failure.

Many issues are evergreen and people will come around continue to comment on them as they get hit. The idea that no one comments on old issues is simply a false premise.

If you look up examples of stalebot feedback the only people who think its a good idea are people literally only caring about how many issues are open.

GitHub stale bot considered harmful | https://news.ycombinator.com/item?id=28998374

[SkiFire13]

What's the problem is such inactive issue stays open?

[rickcarlino]

Keeping an issue open is not going to force a maintainer to care. If they want to close the issue it is likely because they don’t care and getting them to care is not a UI/UX problem. Even if the issue is left open, it is likely not getting prioritized on internal roadmaps and discussions.

[wahnfrieden]

Meanwhile OpenAI Codex keeps my issues open for months, monitors their popularity and relevance, and updates me on them once they finally make it to development and release.

Has happened with over a dozen I’ve opened. What you’re saying may be true of Anthropic (and you've done a good job justifying it for them) but certainly not its competition.

They only manually close my feature request tickets if they've been open for a long time (several months) without "upvotes" from the community and aren't already planned. A senior engineer always explains why they're closing these.

[Terretta]

At scale this works: If the issue is affecting enough user base, the issue will still be in the list.

[SahAssar]

This is not true unless you want people to start spamming "+1" and "me too!" comments.

[DeepYogurt]

Ya, but when you're not at scale it's annoying