If that's your goal, then yes. Invoking sub agents (with a fresh context) corrects most of these problems. Ask your harness to create a commit gate.

▲

dirkc 2 days ago | parent [-]

But why stop at rewriting in another language. Get another sub agent to invent a new language, create a database, query language and maybe another few DSLs. Then you've got an ecosystem!

You can now re-position your initial solution and sell the client access to some agents that will implement & configure the ecosystem to suit their initial needs!

And don't forget the agents that you'll need to train the customer to use the whole thing!

▲

qarl2 2 days ago | parent [-]

I know you're trying to be funny - but I'm offering a real fix for his problem.

If you don't want a million agents arguing about things, you simply don't ask for that. One agent is sufficient to solve most issues.

▲

dirkc 2 days ago | parent | next [-]

Sorry, I wasn't implying your advice doesn't carry weight. Was more just thinking about the things that (used to) happen when you introduce more parties to process of creating software.

▲

zzleeper 2 days ago | parent | prev [-]

I wonder if I would need a non-openai agent to enforce it.. I have tried so far with skills and agents.md and code stills end up over engineered to the moon.

Will ask OpenAI to write me that agent! Hope the agent is not over engineered or else unsure how to solve the bootstrap puzzle :D

	▲	qarl2 2 days ago \| parent [-]
		There's a misconception that a mistake one instance of a model makes will be repeated by other instances. In my experience most mistakes are just sampling noise, and having the same model (with empty context) check the work usually fixes it. It's super easy - just ask your agent to set up a code review commit gate.