I believe that “it’s about the harness” captures an important idea, but I also think it’s helpful to consider the harness and the procedure separately. The har

I believe that “it’s about the harness” captures an important idea, but I also think it’s helpful to consider the harness and the procedure separately. The harness provides the model with its tools, context, and environment for execution. However, I prefer not to have the model within that harness also bear the responsibility for remembering the process steps—like plan, implement, review, fix, and verify—deciding when to move from one to the next, and keeping track of the loop's state. For tasks that need to be repeated, I’ve been moving that part into a reliable, deterministic runtime. Inside it, Claude, Codex etc simply take on interchangeable roles. This setup makes changing models much simpler: the overall process remains consistent, and each role can be optimized independently. I’ve been developing this approach as ctx.traits, if you're interested, here are the docs: https://ctx.company/traits/docs/quickstart/example/ https://ctx.company/traits/docs/quickstart/example/