Replies: 2 comments
|
The part that stands out to me is "Use openai compatible model and the latest version. Error.". That is usually where agent workflow routing starts to matter in practice, because the integration works at small scale but gets harder once real users, retries, and longer sessions show up. I would make provider/model choice explicit per agent step, then log usage and fallback reason for each tool loop. That makes it easier to move simple steps to cheaper routes while keeping stronger models for planning or final synthesis. I am testing an OpenAI-compatible multi-model API layer around official Chinese models, so this kind of agent workflow routing is directly relevant. For harness-sdk, would routing be configured per agent role, per tool call, or dynamically from runtime signals? |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
And the model answer normally at first. But when it calls the tool:
And I can't understand why this error occurs. Could you please help me with this? I would greatly appreciate any assistance. Thank you!
All reactions