WEBVTT

NOTE Timing: local ASR word timestamp alignment. Review against audio before publishing.

00:00:00.000 --> 00:00:02.520
Let's prepare a small CLI change with two

00:00:02.520 --> 00:00:05.960
independent checks. Using Qwen three point six through

00:00:05.960 --> 00:00:08.560
Lite L L M, we'll delegate test planning

00:00:08.560 --> 00:00:11.200
and command-line review while the main agent keeps

00:00:11.200 --> 00:00:11.580
working.

00:00:12.250 --> 00:00:14.790
Give each subagent a clear task, the relevant

00:00:14.790 --> 00:00:18.450
files, and read-only permission. Both use our same

00:00:18.450 --> 00:00:21.170
Qwen model; neither is being asked to change

00:00:21.170 --> 00:00:21.430
code.

00:00:22.042 --> 00:00:24.922
Two background agents can work independently while the

00:00:24.922 --> 00:00:27.322
main agent checks a baseline and forms a

00:00:27.322 --> 00:00:30.302
plan. This is useful when the tasks don't

00:00:30.302 --> 00:00:31.602
depend on each other's results.

00:00:32.375 --> 00:00:35.315
Open an agent to inspect its progress. Separate

00:00:35.315 --> 00:00:38.175
conversations keep specialist detail out of the main

00:00:38.175 --> 00:00:40.595
thread, while still letting us look into the

00:00:40.595 --> 00:00:41.315
work when needed.

00:00:42.000 --> 00:00:45.000
Reports return to the main conversation, where we

00:00:45.000 --> 00:00:48.040
can compare the suggested tests and command-line checks.

00:00:48.940 --> 00:00:50.960
We don't need to copy each worker's full

00:00:50.960 --> 00:00:52.460
transcript into the main chat.

00:00:53.042 --> 00:00:55.602
Here the main agent combines both reports into

00:00:55.602 --> 00:00:59.582
an implementation plan. Subagents help with independent research

00:00:59.582 --> 00:01:02.302
and review, but they're not a substitute for

00:01:02.302 --> 00:01:03.542
checking the final change.
