I absolutely love reading thoughts and see the commands it uses. It teaches me new stuff, and I think this is what young people need: be able to know WHAT it is doing and WHY it is doing it. And have the ability to discuss with another agent about what the agent and me are trying to archive, and we can ask them questions we have without disturbing the flow, but seeing the live output.

Regarding the thoughts: it also allows me to detect problematic paths it takes, like when it can't find a file.

For example today I was working on a project that depends on another project, managed by another agent. While refactoring my code it noticed that it needs to see what this command is which it is invoking, so it even went so far as to search through vs code's user data to find the recent files history if it can find out more about that command... I stopped it and told it that if it has problems, it should tell me. It explained it can't find that file, i gave it the paths and tokens were saved. Note that in that session I was manually approving all commands, but then rejected the one in the data dir.

Why dumb it down?

> While refactoring my code it noticed that it needs to see what this command is which it is invoking, so it even went so far as to search through vs code's user data to find the recent files history if it can find out more about that command... I stopped it and told it that if it has problems, it should tell me.

TIL that there's an especially apt xkcd comic for this scenario: "Zealous Autoconfig"

https://xkcd.com/416/