{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/db5bc6156c584e0998c7624821bd5272\" frameborder=\"0\" width=\"1658\" height=\"1243\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1243,"width":1658,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1243,"thumbnail_width":1658,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/db5bc6156c584e0998c7624821bd5272-3444e32fc3d9d232.gif","duration":131.606,"title":"Use Any Provider Models as Advisors ✅","description":"In this tutorial, I show how to use any provider model as an advisor in Cloud Code. First, I define the main model and the advisor model, then I set a model group alias for the advisor because Cloud Code only allows Opus 4.6 as the advisor entry point. When I run an integration test, the request goes to Opus 4.6 and behind the scenes routes to the Gemini 3.1 group review. I also show where to view the advisor call results with Control O and how to check per request cost in the logs. No action was specifically requested from you."}