<?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/d044887130304d64b08eeab0eeee6f82&quot; frameborder=&quot;0&quot; width=&quot;2596&quot; height=&quot;1947&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1947</height><width>2596</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1947</thumbnail_height><thumbnail_width>2596</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/d044887130304d64b08eeab0eeee6f82-6bba6e1e9f9dd677.gif</thumbnail_url><duration>214.106</duration><title>Enhancing Provider Management with Default Settings 🛠️</title><description>In this screencast, I’m proposing a feature to add the ability to set a default provider, which would save us from specifying a non-standard provider every time. I’ve implemented a simple code solution that allows for a default providers hash, prioritizing more specific providers based on key length. I demonstrated how this works with examples, showing that if we set Bedrock as the default, it routes correctly unless a more specific provider like Anthropic is specified. I encourage you to consider this feature as it could streamline our workflow significantly. Let me know your thoughts!</description></oembed>