I've never seen this beore today; it happened today and was quite clearly incorrect behavior. I prompted it to research considerations for a significant code architecture decision. It asked a pretty difficult question about which direction to take, something that would take way more than 60s to answer properly. While I was thinking about it, it timed out.

Some Github issues claim that adding

    "env": { "CLAUDE_AFK_TIMEOUT_MS": "86400000" }