I got bored and invented a new category of software nobody asked for
I did a dumb thing because I got bored.
I let Opus 4.6 + 5.2 High Thinking argue with me about architecture for way too long, then I basically went “ok prove it” and had Opus 4.6 build the core while a few Sonnet 4.6 agents handled side quests (SDK/CLI/scaffolding/docs).
End result: I accidentally started building what I’ve been calling an “OS for AI.”
Not “AGI in your BIOS” lol. More like: operating systems are built around humans (desktop, apps, clicking stuff). But agents don’t need a desktop — they need a way to run tasks, talk to each other, not crash constantly, and leave logs you can actually debug.
What it does right now (simple)
It’s basically a local control plane / supervisor for agent scripts.
Today you can use it to:
• run multiple scripts/agents/services under one daemon
• auto-restart them if they crash (with backoff)
• collect logs in one place
• check status through an API/CLI
• drive it from Python with a small SDK
So if you have “a bunch of scripts that kinda work” (scrapers, automations, agent experiments, local services) and you’re tired of babysitting terminals, it’s meant to make that less annoying.
Repo: https://github.com/JosephBerm/XKernel
The idea behind it
Everyone’s default move is “scale out” and make everything distributed. I had the opposite thought: scale down the moving parts, and scale up the intelligence.
Like: fewer microservices/pods/YAML problems, more “one box that reliably runs your agents and you can reason about it.”
Where I’m stuck / what I want advice on
I can take this two directions:
A) Keep it boring and make it actually useful
• rock-solid process supervision + logs
• simple plugins
• good dev workflow tool / local runtime
B) Lean into the “AI OS” framing
• stronger permissions/capabilities
• better IPC/message passing
• real memory subsystem
• more agent orchestration
I don’t want to build a spaceship nobody wants, so I’m asking early.
What should I do next?
1. Is “OS for AI” a dumb name and should I just call it an agent runtime/control plane?
2. What’s the most useful thing you’d want from this today?
3. If you were hardening this first, what’s priority #1? (logs? restarts? IPC? permissions?)
4. What benchmarks actually matter here? (spawn latency, restart recovery time, log throughput, etc.)
Be honest. If this is pointless, tell me why and what would make it not pointless.
Posted Mar 3, 2026, 11:45 AM UTC