Models will internalize the harness but it won’t disappear.
Compilers ate register allocation. We still write code.
What stays external: your repo state, incidents, and guarantees the model can’t self-enforce. A model can’t be both the actor and the check on the actor.
Exactly aligned with an excerpt from my open-source book "AI Agents in Depth": https://t.co/6VBSv9Mete
"Will models eventually eat the harness? Yes.
Each time a model reliably internalizes a capability, the corresponding layer of the harness can be removed. Look back at all the fallback logic piled into today’s harnesses: multi-stage context compression, retry loops, and permission checks that pessimistically default to “unsafe.” Every seemingly ugly pile of technical debt marks something the model still cannot do reliably.
When the next generation of models internalizes those constraints, the corresponding code can be deleted. And the reason models can internalize them is precisely that agents have already encountered these failure modes in real-world applications, turning those experiences into training signals for the next iteration.
Users bring real, difficult problems. The application layer uses a harness to compensate for what the model cannot yet do. And those compensations, in turn, become training signals for the model’s next generation."
@JulianGill2@ashebytes Interesting. You're describing a human-AI interaction problem rather than a model capability problem. AI should be able to infer intent from minimal signals and guide users through the cold-start phase.
@a1zhang@lateinteraction "As base models grow stronger through RL training, rules[harnesses] describing how
to code (style, formatting, generic process) are increasingly
internalized into model capabilities, while rules encoding
what not to do (project-specific scope constraints, safety
prohibitions)