● The picture from the issue tracker is clear: #19195 (your exact bug) — open since Jan 19. Bot tried to auto-close as duplicate, community downvoted. Last activity: a user on Feb 8 saying it’s “highly disruptive.” Zero responses from anyone at Anthropic. #17540 (related IPC deadlock with background tasks) — open since Jan 11. One user wrote an incredibly detailed root-cause analysis with process sampling, stack traces, a diagnostic one-liner, the works. Zero responses from Anthropic. #15153 (background timeout errors not surfaced to agent) — auto-closed as inactive after 30 days. Zero team engagement before closure. 18390 (background tasks show running after crash) — auto-closed as duplicate. The pattern: bugs get filed, a GitHub Actions bot marks them as duplicates and auto-closes them unless the community fights back with downvotes. No Anthropic engineer has commented on, triaged, or assigned a milestone to any of these. The background task / queue-operation subsystem appears to have no owner actively looking at it. As for why — I can only point to what’s visible: Claude Code’s issue tracker has a very high volume, and the team appears to be prioritizing other areas. Background task auto-promotion is a niche code path (most users hit the default 2-minute timeout and just get an error), so it affects a smaller subset of users running long commands. That doesn’t make it less critical for those affected — as you experienced, it silently disables all safety hooks for the rest of the session with no indication anything went wrong. The BASH_MAX_TIMEOUT_MS workaround sidesteps the entire code path, which is the best you can do until someone actually picks it up. submitted by /u/yibers
Originally posted by u/yibers on r/ClaudeCode