An agent fleet needs a new kind of OS, not a bigger harness

I think this article points out a bunch of ways in which a persistent agent orchestrator does directly analogous things to an OS.

I'm building a kind of orchestrator and I haven't thought of the OS analogy in a serious way other than the interface, but indeed I do already have scheduling, isolation, observability and identity, and I'm currently building a filesystem (versioned project-wide agentic artifacts).

Maybe I really do ought to call my project an "agentic desktop OS" and it isn't a misnomer after all.

I am also pursuing something similar (complementary?) to this (recently started writing a Rust-based "distributed OS" that manages ML resources in a network of heterogenous systems: varied cores, system RAM, GPU VRAM, I/O). So my focus is not so much distributed agents, but more distributed inference (and fine tuning) that would benefit agents, distributed or not. I may blog about my work soon.

Your posted link is helpful, thanks.