Here is the problem Guppy exists to solve. I start a Claude Code session working through a real task — a migration, a refactor, a long test run — and then I close the laptop, or the wifi drops, or I switch from the desk to the couch to the train. On a laptop, that session is gone, or paused, or wedged. The work an agent does is long-running and mostly unattended; a laptop is the worst possible place to run it. ...
Most writing about Claude Code assumes one engineer, one session, one project. That assumption stops being true the moment a team adopts the tool. You’d think two Claude instances working on the same repo would be a fringe edge case. It isn’t. The same engineer often has two terminals open, one focused on a backend change and another on a frontend tweak. Two engineers pair on a feature, each with their own Claude. A long-running session is left to grind through tests while a second session opens to plan the next workstream. As soon as you scale beyond solo use, you accumulate situations where two or more Claudes are touching the same files, with no idea about each other. ...