What's this about?
machine0, a Y Combinator S26 company, launched with persistent CPU and GPU virtual machines you create and manage from the command line.
What exactly is the gap here?
There are two established options and an awkward space between them. Ephemeral cloud sandboxes spin up in seconds and vanish, which suits a single task but loses everything you installed. Renting a full cloud server gives persistence but drags in an entire console, networking model and billing structure. "Persistent VM from the CLI" targets the middle: a machine that stays exactly as you left it, created with one command. That middle has become more valuable as agents do long-running work, because an agent that has configured an environment over hours shouldn't lose it when the task ends.
Why is this worth noticing?
HN 64 points, 37 comments
- It's infrastructure shaped by agent workflows rather than human ones — the same premise as Cursor's cloud agents keeping warm environments ready.
- GPU access from a CLI-first product matters for the local-model trend: the people running Qwen 27B on laptops are the ones who occasionally need a bigger machine for an afternoon.