Developers wanted to resume Claude Code sessions so badly they built their own tooling for it. Shell hooks that save the session ID on exit. A published Ruby gem for bookmarking sessions by name. Custom zsh functions passed around like recipes. All of that engineering existed to preserve a single string. The sessions were never lost, which is what makes this a great product lesson. Claude Code stores every conversation as a JSONL file on disk, and the CLI could always resume them. The desktop app just couldn't see them. A GitHub issue back in April called it mostly a surfacing problem. So for months, users filled the gap themselves. A SessionEnd hook here, a bookmarking tool there, each one a tiny patch over the same hole. That's the strongest demand signal in software. A feature request costs the user 30 seconds. A workaround costs them hours, and they maintain it. When people start publishing packages to route around a missing feature, they've stopped asking and started paying with their own time. The best product teams read this signal deliberately. Upvotes tell you what sounds nice. Workaround tooling tells you what people already can't live without. And the reason this feature earned that level of desperation is worth sitting with. An AI coding session carries hours of accumulated context. Decisions made, constraints explained, dead ends ruled out. Losing it means paying that cost again. The session is quietly becoming the durable unit of work, and it just learned to travel.