AI Assisted Programming That Actually Ships: The Long-Running Agent Harness

If you are using ai assisted programming for anything bigger than a quick script, you have probably seen the same pattern: the agent starts strong, then a few sessions later it forgets what mattered, rewrites working code, marks things “done” without testing, or leaves you with a half-finished feature and no breadcrumbs. That is not a model problem as much as it is a harness problem. Long-running work is inherently shift work. Each new session begins with partial context, and most real projects cannot fit into a single window. The fix is to stop treating your agent like a one-shot best ai code generator and start treating it like an engineer joining a codebase mid-sprint, with a clear backlog, a reproducible environment, and a definition of done. In our experience building infrastructure for teams that ship fast, the most reliable setup is a two-part harness: an initializer run that prepares the repo for many sessions, and a repeatable coding loop that makes incremental progress while