The task had been running a while on my remote box — one of those long, multi-step jobs I kick off and step away from — and I was somewhere else entirely when my phone buzzed. It was a Telegram ping from a small notifier I'd built, claude-code-notify, which reaches me whenever a Claude Code turn needs my input, finishes, or dies — so I don't have to sit and watch. This one was the first kind: Claude had hit a decision it couldn't make alone and stopped to ask.
I didn't catch the ping in time. When I finally saw it, I reached for my phone to answer the way I'd planned: this session had Remote Control turned on, so I should have been able to reply straight from the Claude app. But the session there was already disconnected — nothing to type into. So I went back to the VS Code extension panel on my laptop, reconnected, and the question wasn't there either. When the session picked back up it never asked again; it had quietly stepped over the gap where I was supposed to be and kept going. Not answered — gone, with no record in the history of what it had decided. The only proof the moment had ever existed was that notification still sitting on my phone — Claude needs you — pointing at a question that no longer had anywhere to be answered.
