zlacker

Presumably they didn't want to sit there and monitor Claude Code doing this for each of the 14 things they want done. Using a harness around Claude Code (or its SDK) is perfectly sane for this. I do it routinely. You just automate the entire process so that if you change APIs or you change the tasks, the harness can run and ensure that all of your sets are correctly re-done.

Sitting there and manually typing in "do thing 1; oh it failed? make it not fail. okay, now commit" is incredibly tedious.

>>renewi+(OP)
They said they were copy/pasting back and forth. But regardless, what do you mean by "harness" and "sets"? Are you referring to a specific tool that orchestrates Claude Code instances? This is not terminology I'm familiar with in this context. If you have any link that explains what you are talking about, would be appreciated.

>>olalon+I3
Ah, it's unfortunate. I think we just lack a common language. Another time, perhaps.

You're correct that his "pasting the error back in Claude A" does sort of make the whole thing pointless. I might have assumed more competence on his side than is warranted. That makes the whole comment thread on my side unlikely to be correct.