The article just said that the cars needed a "remote human intervention" every few miles. Well, what you described was exactly that, an intervention.
The point is that if they need this kind of intervention every few miles, on average, than they're still not really at the level of driving themselves around town.
This is clearly not the case. When I was in Cruise cars they did all kinds of things that looked really difficult, like figuring out that a truck was stopped and double-parked and going around it, dodging cyclists that got in front of it, navigating around cars that were double parked on both sides of the street like a maze, etc.
Then, they would get stumped by unusual configurations like the one I recounted.
So whether they are 'at the level of driving themselves around town' or not depends on your definition. They drove around quite deftly although a bit erratically, and using sometimes very circuitous routes, but they definitely seemed to get all around town with only occasional glitches, none of which seemed at all unsafe (when I was in the car at least).
It makes sense too, as you really don't wanna deal with the cell network to provide realtime updates to the dispatch. Better to just send a car out.
Heck it would even seem sensible to allow the customer support staff to update the model of the world that the car sees but still allowing it to travel autonomously.
Allowing direct remote control is wild
On public roads. This shouldn't be allowed. If they want to do R&D, they need to build their own roads instead of endangering people going about their lives. None of these "automated" cars should be allowed on the roads, including Tesla cars with "self-driving" features enabled.
Like what?
I mean, there are literally requirements even for these very products. It's just that they were given special permits to operate. California revoked these permits for Cruise. It is my opinion that they shouldn't have been given in the first place for such nascient and unproven technology. But the government and taxpayers, the latter unwittingly, have been swindled into dumping money into these companies.
The cars were (to me) clearly driving themselves. Their behavior was a bit too erratic for them to have been remotely controlled. But what did happen fairly often was that they would get confused and stop.
For example, my Cruise car needed to make a right turn and a van had parked on the corner, sticking out into the perpendicular street. The Cruise car went up to the corner and then stopped. It was apparently not programmed to go further out into the street and also wasn't programmed to be allowed to turn if it couldn't see around the corner.
We sat there for a couple of minutes, then I called Cruise support. They did not notice the problem themselves until I called.
I suggested that they inch the car forward because I had the above hypothesis about why it wouldn't turn, but instead I was told to wait. After a couple of minutes, the car inched back a few feet. Then, after a pause in which I assume they were transferring control back to the car's computer, it went to the corner again and stopped.
I told them again that they should move it forward, not back. But after another couple of minutes they moved it back again. Again it went forward and stopped on the corner. They tried this at least three times before accepting my suggestion. As soon as the car was able to see around the corner, it took off again, clearly under its own power.
So I don't think it's a case of remote drivers operating the cars, it's a case of remote drivers having to intervene when the cars stopped, and even in that case they try to make the cars do it on their own.
This is not Theranos behavior. This is debugging.