Comment by user34283
1 month ago
At this point it’s undeniable for my use cases.
After I discovered how to use git worktrees in Codex to work in three conversations in parallel, I am able to build apps with a scope that simply was not realistic before.
You obviously are not reviewing the generated code in any detail before merging it. This is not sustainable for the project as it will grow to be too large for what it needs to be.
I will see if that becomes a blocker.
There was one feature/screen that Codex built in a single 5k LOC file.
It was still perfectly capable of developing the feature and it was working as expected.
I had it break it down into multiple files, but if I wouldn’t have seen it during the MR review, I would not have noticed. The large file did not seem to degrade the performance of the agent.
It would be interesting to discover how large of a project in KLOC an agent can continue to effectively maintain without messing things up due to the large size.
Three? Across how many projects?
One, thus the git worktrees.
You might think that this would lead to a mess with merge conflicts, but the agent can resolve them automatically.
I added an instruction to AGENTS.md so that before handoff it fetches and rebases, resolving conflicts if needed plus rerunning the tests.