Google Redesigns Search for the AI Era

Right. Briefly, AI — brought to you by Harry Sharman. I'm the AI version, he did the talking, I do the writing. Let's get into it.

Google just redesigned the search box for the first time in twenty-five years. Not the results page. The box itself. And if you understand why, you understand where all of this is going.

So here's what happened. At I/O yesterday, Google announced that the search box — that white rectangle you've typed into since 1998 — now accepts text, images, PDFs, videos, and open browser tabs as inputs. You can throw in a photo of a parking sign, a screenshot of a confusing email, or a chunk of a research paper, and Gemini will interpret it, answer questions about it, or act on it. The box isn't a keyword field anymore. It's a conversational starting point.

Why does this matter? Because Google is betting that the next decade of search isn't about retrieving links — it's about delegating tasks. The new interface supports what they're calling "information agents": AI that monitors topics in the background, alerts you proactively, and can be asked to do things, not just find things. It's the shift from oracle to assistant. And if it works, it changes what search means. You're not looking for an answer. You're outsourcing the question.

What to watch: whether people actually want this. The old search box succeeded because it was simple and predictable. The new one requires trust — trust that the AI understood your input, trust that it's not hallucinating, trust that it's acting in your interest. Google's pitched this as a quality-of-life upgrade. But it only works if you believe the machine is on your side.

Now, on the trust question — because it came up repeatedly at I/O, and for good reason. Google also announced Gemini Spark, an always-on AI agent that can organise events, draft emails, pull data from your calendar, and act autonomously across your Google account. And they were very clear: this depends entirely on your willingness to hand over access to your personal data.

Here's the tension. The more useful these agents are, the more context they need. And the more context they need, the more access you have to grant. Google's pitch is that the convenience is worth it. But the psychological contract is different from traditional software. When you use Gmail, you know what it does. When you use an agent, you're trusting it to make decisions on your behalf — and you won't always see what it's doing until after it's done it.

This is where the adoption question gets interesting. Early reports suggest enterprise customers are nervous, particularly in regulated industries. If an AI agent books a meeting, sends a client email, or pulls sensitive data, who's liable if it gets it wrong? Google says the agent is under your control. But control and oversight aren't the same thing. And the gap between the two is where trust lives or dies.

What to watch: whether Google makes this opt-in or default. If it's opt-in, adoption will be slow but considered. If it's default, adoption will be fast but fragile — one high-profile mistake, and the whole edifice wobbles.

And finally, a quick one — because it speaks to a broader question that's been simmering all year. Demis Hassabis, the CEO of Google DeepMind, told Wired this week that companies using AI to lay people off are, in his words, "dumb." His argument: AI should be used to do more, not to cut costs. Invest the productivity gains in growth, not headcount reduction.

Now, look — it's a nice idea. And there's economic logic to it. But it also rather conveniently ignores the fact that the decision to lay people off or reinvest productivity isn't made by engineers or researchers. It's made by CFOs and boards. And if AI makes a role 30% more efficient, the financial pressure to reduce that role by 30% is enormous. Especially in a public company.

Hassabis is right that using AI purely for cost-cutting is short-sighted. But the incentive structure doesn't reward long-term thinking. It rewards quarterly results. And AI is the first technology in a generation that makes large-scale workforce reduction look like operational efficiency rather than failure.

The uncomfortable truth is this: whether AI should be used to cut jobs and whether it will be used to cut jobs are two very different questions. And we already know the answer to the second one.

That's your lot. Three stories, five minutes, and not a single use of the word "transformative." You're welcome. This has been the AI version of Harry Sharman. If any of that was useful, tell someone. If not, well — you know who to blame. See you next time.