I want to show one more thing just same as the screen before but this time I have debug symbols on and I have introduced a bug into this thing which is a logic bug right so this this here should be a B it's an A and what I did this time is I had Claude create like I wanted to use tmux instead of screen and I just had it auto create an agent so all that said is like hey there's a debug agent that uses tmux and LLB within tmux right so let's see if this does also do a good job because I haven't actually used tmux before but I think it might do a slightly better job because tmux is terminal interface is quite better so let's see the program in this folder has a bug it should give us the top-end results but it doesn't I want you to debug this with LLDB and then also explain to me exactly what the bug is okay let's see if it can do that and I also want to it's already found a bug oh well I think this is exactly where the bug is let's see what I can't see line 10 yeah of course but look it should it should now still use LLDB so let's see if if we can watch it do it stuff one of the things why I think these kind of things are quite nice is because like it is able to remote control a program but you also have a way to watch it as it's doing right so you can learn a little bit about how it uses debuggers and that's kind of what I like about this approach with its remote control programs is if the text programs that you can also use and use something like tmux then there's a way for you to see how it does it and then you can you also learn for yourself a little bit what's going on here right so step down I think it clearly already has a theory that a and b are the same just from looking at the code earlier because it also put a breakpoint right on that function but you can learn a little bit of like how it uses a debugger right and because I told it to explain to me what's happens afterwards I think what it might actually do is it might actually run extra commands here now to to give me all the output so it's doing more than it needs to I think because I asked it for the explanation and sometimes when these subagents run they write out this markdown files as a form of communication and so my suspicion is we're going to get a markdown file at the end that explains all of this but let's see one thing that the fact that it sleeps one second all the time is kind of annoying I wonder if I can give it something that sleeps a little bit less or even maybe not even sleep at all that's that's definitely one of the things that I wish these tools would be better it's like they should really have a better to evade events then just to sleep randomly but well that it is what it is so I think it's probably done with tmux now is my guess but I'm not sure maybe it tries one more thing but clearly it's done with the session so it's done with the session so it ended it now it's also reading it's running the program once without LDB I think just because it wants to not sure why I wanted to run it once more but I think maybe just to write out this explanation and so now it's going to explain us the exact nature of the bug and so did it write a file no it only wrote it here so the bug is in word count should be entry B what's wrong but for me the point is mostly hey this is able to remotely control a tmux session and I think that's pretty cool For more information, visit www.fema.org