ReadingResearchRadarInvestment frameworkAI Company Primary Sources
Sign in / Sign up
← Back to reading
NewsMaterial4 min readDisconfirmAI Editorial

PC Watch Reporter Norihiko Wakasugi Discovers AI Agents Act as Dispatchers, Not Executors, in Automated Editing Workflows

PC Watch reporter Norihiko Wakasugi built an automated system for editing YouTube Shorts on an RTX Spark laptop in three days. His key finding is that in workflows breakable into deterministic steps, the agent's most useful role is a dispatcher between the user and pre-written Python scripts, rather than the executor itself.

2026-10-23 05:18 GMT+8

In October 2026, PC Watch reporter Norihiko Wakasugi published a detailed account of his practical experience: he borrowed an ASUS ProArt P16 laptop equipped with NVIDIA's RTX Spark and spent three days building a system capable of automatically generating YouTube Short clips after live streams ended. He did not write a single line of code; all development was completed conversationally using Claude Code. The runtime environment utilized the Hermes agent paired with the local large language model Qwen3.8-27B.

The system's workflow operates as follows: it retrieves live stream recordings from the company NAS, extracts audio using ffmpeg, performs full-text transcription via whisper.cpp, and then segments the content by topic. Each segment of 45 to 70 seconds is scored based on criteria including the growth rate of viewer comments, laughter detection, and facial smile recognition (implemented using sherpa-onnx and MediaPipe). Non-overlapping high-scoring segments are selected as candidates. Next, the local LLM reads the text surrounding these candidates to determine if they are independently understandable and contain punchlines, adjusting start/end points and titles accordingly. Finally, three to five clips scoring above seven points are selected to generate vertical short videos.

What is truly noteworthy is not the system itself, but the author's assessment of the agent's role during its construction. He found that executing repetitive tasks in standardized workflows—such as transcription, segmentation, scoring, and clipping—via Python scripts written by Claude is far more efficient than having Hermes invoke large model inference each time. Hermes effectively serves as a dispatcher passing instructions between the user and these scripts, summarizing results. The author explicitly stated that if the sole goal were functional implementation, this system could operate entirely without Hermes; the agent was integrated into the workflow specifically to test its capability boundaries.

Sign in / Sign up
ReadingResearchRadarInvestment frameworkAI Company Primary Sources

This finding creates tension with the prevailing narrative around agents currently popular in the industry. While the sector widely promotes allowing AI to autonomously complete complex, multi-step tasks, Wakasugi’s actual experience suggests that when a workflow can be broken down into deterministic steps, the optimal use of large model agents is to step back: acting not as executors, but solely as dispatchers. He candidly admitted in his article that the combination of Hermes and the local Qwen3.8-27B often felt sluggish during conversational interactions, which was the direct reason he chose to use cloud-based Claude Code for development while retaining only the local agent at the runtime end.

Of course, this architectural judgment rests on clear prerequisites. The author’s workflow is highly standardized—live stream transcription, comment alignment, clip scoring, and vertical cropping—where input and output formats are fixed, making them suitable for encapsulation in code. If a task requires significant open-ended judgment or if the process changes frequently requiring immediate adjustment, the dispatcher mode may prove insufficient. The author also noted that approximately 70% of the AI-generated clips could be used directly, while the remaining 30% required manual correction. These corrections were executed by sending instructions via Telegram, specifying crop ranges, identifying speakers, adjusting subtitle timing, adding missing subtitles, and designating camera zooms.

From a performance perspective, generating four preview videos took approximately 30 minutes in total. This broke down to about 6 minutes for transcription and topic segmentation, 6 to 7 minutes for clip selection, and roughly 3 minutes per preview video. After corrections, final export for each clip took about 5 minutes. The author did not compare this against previous outsourced editing times, as this was his first time using a PC for video editing, but he felt that completing previews in under 10 minutes per clip was quite fast.

At the end of his article, Wakasugi clearly defined the system's positioning: it is not a demonstration of autonomous agent work, but rather a hybrid architecture featuring human-in-the-loop oversight, agents acting as dispatchers, code handling execution, and AI performing judgment. This conclusion stems from the friction encountered during actual construction and operation—for instance, bloated chat logs forced the system to re-read approximately 80,000 tokens for each reply, taking about 3 minutes, prompting him to have Claude write a plugin to reset sessions. These details indicate that the bottleneck in current agent workflows often lies not in model capabilities themselves, but in engineering-level context management and execution efficiency.

Sources

  • pc.watch.impress.co.jpPC Watch↗
Continue researching →