When I say an agent system should learn, I do not mean the model is retraining itself or quietly rewriting its own rules. I mean organizational learning: a completed run captures what changed, someone reviews the pattern, an approved change improves instructions, tools, workflows, topology, or maintained knowledge, and the next run can benefit from…
One of the easiest mistakes in agent design is to treat every capable chat as a service. A chat can be thoughtful. It can have useful history. It can even complete a difficult task. None of that means another person or agent should depend on it as a standing part of an operating system. I…
Agent systems become hard to trust when every important thing goes into the same place. Put all state in a chat and the system becomes difficult to inspect or rebuild. Put it all in a request ticket and the ticket turns into an unsafe archive. Put it all in source control and you start pretending…
Most agent designs talk about creation. Real systems spend much of their life changing. You add a specialist. You move a public route. You split one overloaded role into two. You change the model profile. You discover that an old instruction caused a recurring failure. You replace a project layout that no longer fits the…
I’ve gotten closer to creating “agents” with Codex. It’s still early, and they aren’t bootable or portable digital coworkers, but they’re closer to something that behaves like a persistent operating system. The magic trick is Codex’s ability to create and message other threads while executing inside of a chat session. That allows us to create…