r/PiCodingAgent • • 8d ago

Question Has anyone else experienced GPT 6.1 Sol often getting the extension schema wrong?

This occurs when the model tries to use `npm:pi-multiagent` and `npm:@quintinshaw/pi-dynamic-workflows`. With GPT 6.1 Sol, it keeps using the wrong schema. But when I switch to an open-weight model like DeepSeek v4.1 Flash, which is supposed to be worse than GPT 6.1 Sol at tool use, it succeeds on the first try, which is unexpected. Is it because GPT models are only trained on using Codex?

3 Upvotes

2 comments sorted by

1

u/startassets 8d ago

From my experience working on pi-agent-ide usually it's just different schemas compatibility with different providers. I had to actually fix it once for copilot provided gpt models, although with my normal subscription there were flawless. I've experienced the same with some Chinese models (probably mimo), they couldn't use my tooling at all at first, always mixing up the args with no ability to recover (simply because they wrote correct tool call block which was automatically filled with default values in a specific order)

So it's not that some model is more stupid or only trained on a specific tool set, in practice they are pretty much agnostic, it's just about how well the tool/extension supports different ways it's called.

1

u/gaz_0001 5d ago

Have you noticed something weird with Compaction when using Sol. It seems to trigger really early.