An agent box: where your agent loops actually live
Loop engineering needs somewhere to live: an agent box on your server —an outbound daemon, your own worktree engine and access without opening ports.
Blog
Notes from real engineering work — Forward Deployed Engineering, AI-native vertical SaaS, domain immersion (accounting, finance), and the trade-offs we don't usually write down.
Loop engineering needs somewhere to live: an agent box on your server —an outbound daemon, your own worktree engine and access without opening ports.
When the agent absorbs execution, what sets you apart stops being your title —engineer, design, PM— and becomes your posture in the product lifecycle.
Loop engineering isn't 'design loops, not prompts.' It's three decisions: when to raise or lower a loop, how to let it go, and what tool it's missing to close itself.
When the domain generates its code with AI, reviewing it doesn't scale. The verification ladder: let the cheapest verifier check each claim.
Ramp evaluates its accounting agent against 237 tasks and 3,469 accountant-written criteria. Why the private domain benchmark decides more than the model.
An agent that reconciles invoices and posts to your ledger holds the keys to your bank. The four boundaries that decide whether a prompt injection can move money.
Aggregate pass@1 falls from 76% to 52% as tasks get longer. In an agent that posts to your ledger, that gap is mis-stated entries. Capability isn't reliability.
In 22 days, Phil Schmid published three deep dives — skills, MCP, subagents — that read together are the unwritten manual for building a serious agent in 2026.
Firefox found 13x more bugs, Zenith won 5 of 8 tasks at 43% cost, Eugene Yan shared his workflow. The signal: invest in your harness, not the model.