Loading player...

The BEST Way to Research with AI (OpenClaw) Claude

46 views
0
0
March 9, 2026
intermediateshorts

Summary

This video walks you through a powerful AI-driven research workflow using OpenClaw and Claude Code, showing you how to automate the heavy lifting of content aggregation and analysis. The setup pulls from over 170 live news feeds, summarizes the incoming data, and — most impressively — identifies angles and perspectives that are not being widely covered elsewhere. That last step requires genuine critical thinking, which is why the full process can take around 10 minutes to complete. You learn why that time investment is justified given the depth of analysis being performed. The video also covers a real-world debugging scenario: when a cron job fails to fire (in this case, a 6 p.m. scheduled report never appeared), you can rely on Claude Code to diagnose and fix the issue without manual intervention. The host demonstrates asking Loki — an orchestrator AI agent — to check the cron job status, and Claude Code identifies and resolves the problem automatically. A key insight here is the distinction between an orchestrator agent and a worker agent. Loki does not write the reports himself; he coordinates parallel sub-agents that do the actual work. The fact that the test report comes back high-quality is evidence that those sub-agents are running effectively in parallel, not that Loki is doing the writing. This architecture allows you to scale complex research tasks without bottlenecking on a single process. Overall, this video is a practical look at how to combine AI orchestration, automated scheduling, and multi-agent parallelism to build a research pipeline that surfaces unique insights — and self-heals when something breaks.

Transcript

The fact that it's 10 minutes, yeah, it can seem long, but hey, that's a lot of data that you're sifting through. 170 plus news feed on a live aggregate website, then you need to summarize that news. And the part that really takes a lot of time is to cover angles that no one is talking about, and that requires critical thinking. So, it makes sense that that task would take longer. Now, in case if your cron job isn't working, here's where you really need cloud code yet again. Okay, no glaze. I asked Loki when I first built this yesterday, the first crown job schedule didn't come out. My 6 p.m. report was not there. So I told Loki, can you check if the chronrop status is all right? And it sees the issue and it fixed it with cloud code. What's even impressive? And this is how how you know that they're actually using parallel sub agent is they're saying, yo, the test report is really impressive because remember Loki himself is not writing the reports. He's just the orchestrator agent.

Related Videos