让 bot 稳定可靠地读 YouTube

@scheemunai's first test for any new agent is YouTube: hand it a video and ask it to read the transcript, summarize, find a moment, or research across channels. Opening YouTube is easy - the question is whether the agent can work with what's inside the video.

With Grok Bot on browser control alone, it couldn't. The video played fine on its computer, but when asked to summarize it the Bot's caption API call was blocked from its IP, YouTube's transcript panel came up empty, and it fell back to scrolling the transcript one piece at a time. After several attempts and two nudges it gave up - and by then the entire Grok Bot trial had been spent on one video.

The fix is the TranscriptAPI plugin: it hands the Bot timestamped transcripts, YouTube search, channel browsing and playlists in a single request, instead of making it inspect-click-wait-scroll through YouTube's transcript drawer. To install it, send this to the Bot:

This is the clearest illustration of when a plugin beats browser control. Browser control is powerful, but reconstructing a transcript through the screen - inspect, click, wait, scroll, inspect again, guess whether it loaded - is exactly the kind of loop that quietly burns an agent's entire usage budget, and it can still come back empty when the caption API is IP-blocked. A transcript API returns the same thing in one request. The smart pattern the article lands on is to use both: let the plugin find the relevant timestamp cheaply, then let the Bot open that exact moment on screen when the visual frame actually matters. It turns "can my agent even read a video?" from a coin flip into a reliable primitive you can build morning briefs, research reports, and clip pipelines on top of.