I prefer to use Claude code like a smart rubber ducky while I write most the code in the end. I added rules to make claude first explain what it want to do in chat (and code changes should only be implemented if I ask for it). I like it to talk about ideas, discuss solutions and approaches. But I am in control of it - in the end, I am the person repsonsible for the code.

Since I don't like it to automatically do changes to files, I copy&paste the code from terminal to the IDE. That seems slow at first, but it allows me to correct the bigger and smaller issues on the fly faster than prompting Claude to my preffered solution. In my opinion, this makes more sense since I have more control and it is easier to spot problematic code. When fixing such issues, I point Claude to changes afterwards to add to its context.

For me Claude is like a very (over) confident junior developer. You have to keep an eye on them and if it is faster do it yourself, then just do it and explain them why you did it. (That might be a bad approach for Juniors, but for Claude it works for me)

Btw, can we talk about that this blog post is written by the company that tries to sell the tool? So we should take it with a huge grain of salt... . Like all what these AI companies are telling us, should probably be ignored for 90 % of time. They either want to raise money or or getting bought by some other company in the end ...

Just keep it in plan mode and it won't change anything?

Unlike Gemini CLI which will just rush into implementation without hesitation :D