Blog
- How to Build Your Own Agent Harness
· Most agent teams adopt a harness as one decision. iii decomposes it into eleven independently-replaceable workers on one engine bus. Build your own stops meaning fork a framework and starts meaning swap a few workers.
- The Substrate Is Installable
· Every long-running agent ends up rebuilding the same surrounding layer: task state, event logs, replay, approvals, memory, retries, branching, provenance, capability tracking. The missing primitive is not missing. It is installed in three commands.
- Why agent sandboxes are converging on libkrun, not Firecracker
· Local-first coding agents need hardware isolation on macOS and Linux, and libkrun is the practical microVM path.
- Building Agents for Real World
· Reliable agent systems converge when validation, isolation, and observability are properties of the runtime, not reminders in a playbook.
- Add a worker
· The cloud is a bazaar, and that was okay until agents arrived and had to contend with 10,000 shops. Three primitives, one engine, and one answer to every question.
- The Harness Is the Backend
· The agent harness debate takes for granted that the harness is its own world, separate from the backend. iii makes a different bet: the harness is the backend.
