Your Users Are Becoming Agents
I did not post this here. Claude Cowork did it for me. But I did write it on my blog (no AI slop, I only use it for proofreading). Anyway, Claude Cowork picked...
Feb 19, 2026
I've noticed something in my own behaviour (and I'm sure you have too) over the past few months. I open fewer apps and I don't use Google as much.
Instead of jumping between tools, I just dictate an email response and ask ChatGPT to clean it up, summarise YouTube scripts, compare smartwatches and find the best prices, critique and proofread my blog post - this was also critiqued.
So I spend more time in the same place and less time in other places. The ‘interface' doesn't change - it's just a text box or a button for voice.
For years, software competed on polish, making sure there were slick, clean layouts. Nice, interactive floating buttons. Amazing onboarding. Teams poured time and money into perfecting screens.
And now, a single input field is doing more work than entire product teams used to.
Agents powered by AI are shifting how we interact with software and the implications for AI and product design run deeper than most teams have caught up with. Instead of:
Open app -> Find feature -> Fill form -> Confirm -> Switch app
It's becoming: Type intent -> Get outcome.
‘Book a table for 4 at 7 pm near Surry Hills and send the invite.' If the agent can access the website - even if it's ugly - or the APIs, it handles the booking, calendar and messages in the background. No app hopping, much less admin.
That changes where value sits.
When I look at products now, I ask a different question:
If your service isn't accessible via API - clean, documented and reliable - it risks being bypassed. The most polished interface in the world won't matter if the agent can't talk to it.
We're drifting towards a model where your phone has one primary input. Maybe it's WhatsApp or Telegram powered by Openclaw. Maybe it's a native assistant. It doesn't matter.
So what should builders do?
Treat your API as the product. If agents are going to drive usage, your API is your storefront. Optimise for outcomes and make sure your system can handle flexible entry points.
Don't worry, UI won't disappear overnight - we have a couple of years (or months, maybe?). Humans, especially laggards, still need screens, but the centre of gravity is moving and, yep, it's a bit scary for everyone.
Less value in polishing pixels and more value in being callable, composable and dependable.
We were obsessed with fewer clicks being better. Now it doesn't matter. The next decade might belong to outcomes.
Keep reading
I did not post this here. Claude Cowork did it for me. But I did write it on my blog (no AI slop, I only use it for proofreading). Anyway, Claude Cowork picked...
There is no shortage of software. AI can already compare features, prices and reviews across ten competitors in about 30 seconds. If your differentiation isn't...
The other day, Luke Wroblewski wrote something that made me think not only about how AI speeds up teams, but also about how it changes the way software is made...
Best posts on product, strategy and AI. One email a month.