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

2
00:00:03,282 --> 00:00:05,887
with three agents working one after the other.

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

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

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

6
00:00:16,753 --> 00:00:20,146
with three steps: analysis, fix and review.

7
00:00:20,146 --> 00:00:23,235
In the analysis, Claude reads the code, finds the cause

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

9
00:00:26,295 --> 00:00:29,915
In the fix, Codex follows that plan and changes the code.

10
00:00:29,915 --> 00:00:32,757
In the review, Claude checks what was done.

11
00:00:32,757 --> 00:00:35,783
Each step opens its own terminal and has its own role.

12
00:00:35,783 --> 00:00:39,483
The project rules apply to all three: answer in Portuguese,

13
00:00:39,483 --> 00:00:44,452
don't touch package.json without warning, and every change comes with a test.

14
00:00:44,997 --> 00:00:47,644
The Ready line says when each step is done.

15
00:00:47,644 --> 00:00:50,524
The analysis is automatic, the fix is only ready if

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

17
00:00:54,556 --> 00:00:57,593
I run the flow and go back to the Grid.

18
00:01:00,993 --> 00:01:03,573
The analyst is reading the coupon and the cart.

19
00:01:03,573 --> 00:01:06,568
When it wants to write ANALISE.md, it asks for permission,

20
00:01:06,568 --> 00:01:11,256
and the request shows in the terminal, on the card, in Attention and in the footer.

21
00:01:11,256 --> 00:01:14,993
In the request you can see which terminal and which step it came from.

22
00:01:14,993 --> 00:01:16,720
I answer in the terminal.

23
00:01:19,991 --> 00:01:24,493
ANALISE.md holds the cause, the plan and a case that reproduces the error.

24
00:01:24,493 --> 00:01:26,631
That is the file Codex will read.

25
00:01:26,740 --> 00:01:29,289
With the analysis ready, the fix starts on its own.

26
00:01:29,289 --> 00:01:31,739
I switch to Focus to follow Codex.

27
00:01:36,175 --> 00:01:39,058
It reads the analysis, changes the discount calculation in the

28
00:01:39,058 --> 00:01:43,478
coupon and adds a test for the two-item case.

29
00:01:44,500 --> 00:01:49,331
Now it runs npm test, and all the tests pass, including the new one.

30
00:01:50,536 --> 00:01:53,801
The step is only ready because npm test passed.

31
00:01:53,801 --> 00:01:56,281
It's not enough for the agent to say it's done.

32
00:01:56,281 --> 00:01:59,588
In View result you see the command, the output and the verdict.

33
00:02:04,318 --> 00:02:05,622
Then the reviewer comes in.

34
00:02:05,622 --> 00:02:09,254
It reads what changed and writes its findings to REVISAO.md.

35
00:02:09,254 --> 00:02:11,894
Before approving, I read the findings.

36
00:02:11,894 --> 00:02:13,214
If there were a problem,

37
00:02:13,214 --> 00:02:15,478
I would send it back to the fix with an instruction.

38
00:02:15,478 --> 00:02:17,150
This time, I approve.

39
00:02:17,150 --> 00:02:18,726
The Steps tab keeps the log,

40
00:02:18,726 --> 00:02:22,079
with the instructions sent and the time of each thing.

41
00:02:22,079 --> 00:02:24,125
The three steps are done.

42
00:02:24,125 --> 00:02:27,825
I stepped in twice, for the permission and for the approval.

43
00:02:27,825 --> 00:02:30,266
The agents did the rest on their own.