It's not that I disagree with you, at least not for your use cases! But it's not hard for me to think of cases where this would work.
First, a quick anecdote - I run a dirt cheap, crummy Windows server at home for pet projects. I've been doing this for well over a decade. Maybe two? Along the way, I wrote a basic web interface for editing files on the server. Basic upload, rename/move, edit text files kind of thing. For pet projects, I work on them infrequently, but sometimes an idea will strike me, or I become aware of a bug or typo, and I just want to get in and fix the issue. Now, these were simpler times - the most complex code was classic ASP or JavaScript! The toolchain was non-existent.
A use case for pet projects would be cloud-hosted, cloud-repository, cloud-pipeline, and now cloud-development. When an idea strikes you, rather than pull things locally, configure them for that particular project, with that peculiar set of frameworks and toolchains, you can load up your cloud IDE which is already configured to point to the repository, build and test in a container, deploy through a pipeline to the cloud host, and just focus on making the edits you want without all the work of getting things local.
As someone who spent a few hours the other morning working on a computer I don't usually work on just getting the git credentials and containers and runtimes working before I could start getting any work done, I could definitely see a use case for this cloud-based development paradigm.