<?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/9200a5ab7f214aa28fbbf7845ed4523c&quot; frameborder=&quot;0&quot; width=&quot;1756&quot; height=&quot;1317&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1317</height><width>1756</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1317</thumbnail_height><thumbnail_width>1756</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9200a5ab7f214aa28fbbf7845ed4523c-0beeb9b54625eaf5.gif</thumbnail_url><duration>660.417</duration><title>Qovery Agent Task</title><description>This Loom explains Covery’s agent cloud for running AI agents in production inside a team’s infrastructure rather than sending data and secrets elsewhere. It contrasts two options: exporting data to a third party or building and maintaining your own event receiver, scheduler, model wiring, and governance. The author demonstrates a “Build and Deployment Optimizer” agent that runs regularly, set to trigger every Monday morning, collects metrics, checks code, and proposes improvements via a pull request. The agent is configured with templates, model access (using Entropiq), Slack output webhook for a recap, and governance egress rules, then a PR link is shared after completion.</description></oembed>