{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/273ecb75bbff4ff39ee194dea37b46ca\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/273ecb75bbff4ff39ee194dea37b46ca-7537a1678c568125.gif","duration":285.285,"title":"Demonstrating an AI Support Agent for GitHub Issue Resolution","description":"In this Loom video, I demonstrated an agent I kicked off about four minutes ago to address an unanswered GitHub issue in the post-doc-js-rate repo. The agent utilized 26 tools, including the post-hog mcp for customer telemetry and live documentation searches. It concluded that the issue is likely a reverse proxy or WAF configuration problem rather than an SDK bug, and it provided a draft response for the customer. I encourage you to review the agent's findings and the proposed response, which we can further refine or share via Slack."}