i love pi and built my harness on top of it. but while checking error rates on tool calls, I noticed even opus 5.5 was making mistakes, like calling bash when the tool was named shell, or sending old_str or new_str instead of old_text or new_text (basically using the names of the tools in claude code despite tool definitions being different in my harness. i added aliases to fix it, but it changed how i think about harnesses now.
models are being heavily rl'd on the lab's harnesses, so eventually claude works better in claude code than any other harness.
i'm moving my weird customisations a layer above to acp or building on the claude sdk, especially since they now allow using your sub w it.
the labs are making it clear that they want control of the harness as well
models are being heavily rl'd on the lab's harnesses, so eventually claude works better in claude code than any other harness.
i'm moving my weird customisations a layer above to acp or building on the claude sdk, especially since they now allow using your sub w it.
the labs are making it clear that they want control of the harness as well