1
00:00:00,013 --> 00:00:03,242
In this video, I show a bug fix from start to finish,

2
00:00:03,242 --> 00:00:05,859
with three agents working one after another.

3
00:00:08,769 --> 00:00:11,085
The bug is in the first-purchase coupon:

4
00:00:11,085 --> 00:00:14,592
with two items in the cart, the discount is applied twice.

5
00:00:14,592 --> 00:00:16,819
To fix it, I use my usual flow,

6
00:00:16,819 --> 00:00:20,448
with three stages: analysis, fix and review.

7
00:00:20,448 --> 00:00:23,512
For analysis, Claude reads the code, finds the cause

8
00:00:23,512 --> 00:00:26,974
and writes a plan to a file, without changing anything.

9
00:00:26,974 --> 00:00:30,681
For the fix, Codex follows that plan and changes the code.

10
00:00:30,681 --> 00:00:33,512
For the review, Claude checks what was done.

11
00:00:33,512 --> 00:00:36,730
Each stage opens its own terminal and has its own role.

12
00:00:36,730 --> 00:00:40,548
The project rules apply to all three: answer in English, don't touch

13
00:00:40,548 --> 00:00:45,009
package.json without telling me, and every change needs a test.

14
00:00:45,048 --> 00:00:47,878
The Done when line says when each stage finishes.

15
00:00:47,878 --> 00:00:50,720
The analysis is automatic, the fix is only done if

16
00:00:50,720 --> 00:00:54,266
npm test passes, and the review waits for my approval.

17
00:00:54,266 --> 00:00:56,393
I run the flow and go back to the Grid.

18
00:00:59,547 --> 00:01:02,349
The analyst is reading the coupon and the cart.

19
00:01:02,349 --> 00:01:06,167
When it wants to write ANALISE.md, it asks for permission,

20
00:01:06,167 --> 00:01:08,017
and the request shows up in the terminal,

21
00:01:08,017 --> 00:01:11,152
on the card, in Attention and in the status bar.

22
00:01:11,152 --> 00:01:14,321
The request shows which terminal and which stage it came from.

23
00:01:14,321 --> 00:01:15,965
I answer it in the terminal.

24
00:01:18,529 --> 00:01:23,534
ANALISE.md has the cause, the plan and a case that reproduces the bug.

25
00:01:23,534 --> 00:01:25,417
That's the file Codex will read.

26
00:01:25,417 --> 00:01:28,557
With the analysis done, the fix starts on its own.

27
00:01:28,557 --> 00:01:30,739
I switch to Focus to watch Codex.

28
00:01:31,995 --> 00:01:34,951
It reads the analysis, changes how the coupon calculates

29
00:01:34,951 --> 00:01:37,914
the discount and adds a test for the two-item case.

30
00:01:38,324 --> 00:01:43,163
Now it runs npm test, and all the tests pass, including the new one.

31
00:01:43,246 --> 00:01:46,485
The stage counts as done because npm test passed.

32
00:01:46,485 --> 00:01:48,849
The agent saying it's finished isn't enough.

33
00:01:48,849 --> 00:01:52,060
View result shows the command, the output and the verdict.

34
00:01:54,956 --> 00:01:55,998
Then the reviewer comes in.

35
00:01:55,998 --> 00:02:00,037
It reads what changed and writes its findings to REVISAO.md.

36
00:02:00,037 --> 00:02:02,623
Before approving, I read the findings.

37
00:02:02,623 --> 00:02:04,133
If there were a problem, I'd send it

38
00:02:04,133 --> 00:02:06,341
back for correction with an instruction.

39
00:02:06,341 --> 00:02:08,166
This time, I approve it.

40
00:02:08,166 --> 00:02:09,579
The Stages tab keeps the log,

41
00:02:09,579 --> 00:02:12,811
with the instructions sent and the time of each step.

42
00:02:12,811 --> 00:02:14,593
All three stages are done.

43
00:02:14,593 --> 00:02:18,100
I stepped in twice, for the permission and the approval.

44
00:02:18,100 --> 00:02:20,039
The agents did the rest on their own.