As he says a tool's ownership shouldn't affect it's status of a tool.

You do not control the tool either.

You cannot manually train it for your case.

You cannot tell it to not touch particular parts of your project either. It will stomp over all of the code.

You cannot even easily detect this tool has been used except for typical failures.

The tool may also leak your secrets to some central database. You cannot tell it to not do that.

(If you try either tack of those, it will lie to you that it complied while actually not doing that at all.)

When your networking fails, the tool does not work. It's fragile in all cases.

You control the prompt and the system prompt. No, it's not hyper specialized yet on the training side, but that doesn't matter. You can explicitly control the files it reads in Cursor, and I'm sure Roo and Aider can as well. If you self host, you can control exactly where your data is stored.

I've never seen so many false assumptions in one place.

and my comment said "own and control" and later focused on "control".