{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/9dc9826f731f416c90144d3ea776e7ee\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/9dc9826f731f416c90144d3ea776e7ee-38fd83adf1a05a1e.gif","duration":357.849,"title":"Devon Orchestrator for GitHub Issue Planning","description":"Hi, I am Daniel Rudd, and I am showing Devon as an issue orchestrator inside a GitHub issue. You can ask Devon to plan and iterate on a fix, then ask it to implement and raise a pull request, all with an audit trail and humans kept in the loop. I walk through an Apache Superset example where Devon plans a change after finding datetime.utc deprecation. Architecturally, GitHub webhooks hit a FastAPI service, identify intent, invoke Devon in CloudVM with durable sessions, and poll every 45 seconds. No viewer action was requested."}