
I Run a Dev Team of 3 AIs. Here's What Almost Broke It.
I built real software with Claude, Codex, and Grok — each with a different role, coordinated using RUP/SCRUM principles. It almost fell apart when Codex wrote 900 lines of GDScript where C++ should have been. Not because it made a mistake. Because I gave it the wrong context. The GDScript Incident The SML Parser for Forge4D was already ported to C++. Factor 15 faster than the original C# version. A good day. Then I ended the session. In the next session I told Codex to remove the old C# parser. What I forgot to say: the new C++ version already exists. In my mind, "remove the old" obviously implied "the new is there." In Codex's context window, it did not. Codex concluded: I need to write the SML Parser in C++. And it did. In GDScript. The logic was sound. The premise was wrong. Codex was not wrong. The context was wrong. The Rules That Came From This Rule 1: At the start of every new session, tell Codex what exists — not just what you want to build. Rule 2: Never assume "remove the old
Continue reading on Dev.to
Opens in a new tab

