<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/db5bc6156c584e0998c7624821bd5272&quot; frameborder=&quot;0&quot; width=&quot;1658&quot; height=&quot;1243&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1243</height><width>1658</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1243</thumbnail_height><thumbnail_width>1658</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/db5bc6156c584e0998c7624821bd5272-3444e32fc3d9d232.gif</thumbnail_url><duration>131.606</duration><title>Use Any Provider Models as Advisors ✅</title><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.</description></oembed>