{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/96058cb46f264c20a8092d029f43c522\" frameborder=\"0\" width=\"1114\" height=\"835\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":835,"width":1114,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":835,"thumbnail_width":1114,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/96058cb46f264c20a8092d029f43c522-463107df557db822.gif","duration":76.255,"title":"Team Beacon: CLI for Risky Agent Behaviour","description":"This Loom explains how Team Beacon’s CLI helps analyze risky behavior from coding agents that run with inherited access to a user’s identity. Justin and Sovit describe the problem that agents can use your SSH keys, GitHub authentication, cloud credentials, and access your machine or the open network. In a live demo, they kick off a cloud session where an agent is asked to describe a repository and reverse engineer its architecture. The CLI captures and normalizes agent telemetry, applies detections and analysis to the agent’s trajectory, and then shows the results in their dashboard."}