<?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/5de72ffb97d7409db292119aada1218b&quot; frameborder=&quot;0&quot; width=&quot;1114&quot; height=&quot;835&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>835</height><width>1114</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>835</thumbnail_height><thumbnail_width>1114</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/5de72ffb97d7409db292119aada1218b-6244858f6078dde0.gif</thumbnail_url><duration>138.353</duration><title>Collecting Telemetry From Cloud Agent Sessions</title><description>This Loom demonstrates how Asymptote’s open source AgentBeacon collects and persists telemetry from cloud agent sessions. Justin shows a Cloud Code environment (“Asymptote Tracing”) configured via docs with network allowlisting, Beacon-specific environment variables, object storage parameters, and a setup script that installs the Beacon binary. After running an agent prompt that reads the AgentBeacon README, executes commands, and summarizes the actions, he verifies the collected trace in a GCS bucket. He downloads and opens the trace execution JSON, noting it contains rich metadata such as the submitted prompt.</description></oembed>