omni.

When you run agents across fifty-plus projects, the filesystem becomes your bottleneck. A three-type taxonomy. Seat, domain, system. Cuts orient-cost from O(n) to O(1).

I ran a fully autonomous AI agent workspace for twenty sprints with no human gates. It shipped 200 pages. The more valuable output was a four-item failure catalog.

A CLI orchestrator that turns AI agents into long-running workers against a GitHub backlog: a 3-layer master/workspace/project model with a vault-backed feedback loop.

The first unsupervised run of my agent orchestrator: 686 cycles, 11 merged PRs, 8 self-healed stalls, and 94% idle time. What worked, what broke, and why the failures were the point.

619 commits and two months in. An honest retrospective: state-in-the-filesystem and folder-as-config held under load; idle polling and handoff races broke.

619 commits in two months. The two load-bearing choices: Rust, because the compiler shortens the agent's iteration loop, and tmux, because agents are long-running processes that have to survive the laptop.

From single-prompt user to fleet operator: the eight components of a personal AI OS, and what shipping each one taught me.