google search returns "(empty)"

[xavieryin]

autocli 0.3.8; extension 1.5.6

$ autocli google search AutoCLI --verbose
(empty)
Elapsed: 3.26s | Source: google search

I was quite confident that with real browser operation AutoCLI should be reliable search ability for my local agent, and this once worked well. I haven't searched with my agent for a while, and I happened to notice this today.

Is Chrome extension behavior actually somehow distinguishable and thus being blocked by Google?