An agent fleet needs a new kind of OS, not a bigger harness
kgcgfva
13 points
5 comments
September 16, 2026
Related Discussions
Found 5 related stories in 93.3ms across 6,833 title embeddings via pgvector HNSW
- Agent Harness Engineering fagnerbrack · 32 pts · July 12, 2026 · 59% similar
- Show HN: HART OS – an open-source AI OS built so frontier AI needs no datacenter hevolveai · 18 pts · July 26, 2026 · 53% similar
- Headlong: A Microharness for Persistent Agents lbw1215 · 26 pts · August 25, 2026 · 52% similar
- Pion, an agent designed to run any company autonomously lukaspetersson · 356 pts · September 14, 2026 · 50% similar
- Show HN: OSS Cross-Harness self hosted registry and analytics for AI Agents haz3-jolt · 21 pts · July 21, 2026 · 49% similar
Discussion Highlights (2 comments)
softwarewright
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.
2001zhaozhao
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.