Glancing at what it's doing is part of your multitasking rounds.

Also instead of just prompting, having it write a quick summary of exactly what it will do where the AI writes a plan including class names branch names file locations specific tests etc. is helpful before I hit go, since the code outline is smaller and quicker to correct.

That takes more wall clock time per agent, but gets better results, so fewer redo steps.

▲

irthomasthomas 2 days ago | parent [-]

Here is an example where the prompt was only a few hundred tokens and the output reasoning chain was correct, but the actual function call was wrong https://x.com/xundecidability/status/2005647216741105962?s=2...

	▲	jmalicki 2 days ago \| parent [-]
		I as a human have typos too - and sometimes they're the hardest thing to catch in code review because you know what you meant. Hopefully there is some of lint process to catch my human hallucinations and typos.