Anthropic is giving Claude its own browser. As the company announced on Wednesday, Claude on the desktop (Mac, Windows, and The post Anthropic’s Claude now has a browser of its own appeared first on The New Stack.
Anthropic is giving Claude its own browser. As the company announced on Wednesday, Claude on the desktop (Mac, Windows, and The post Anthropic’s Claude now has a browser of its own appeared first on The New Stack.
In context
- Topic: Inteligencia Artificial — IA aplicada al negocio: casos, límites, costos y gobierno.
- Source: The New Stack
- Published: 26/08/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
Every week there is an announcement that promises to change everything, and every week most organisations are still fighting the same battle: messy data, processes nobody documented, and expectations running faster than capability. This story reads better with that in the background.
The first thing I look at is not model capability but the data feeding it. Almost every project I have seen fail did not fail on the algorithm. It failed because the data lived in three systems with three different definitions and nobody wanted to be the one to fix that.
What usually goes wrong
The point where it usually breaks is the handover to operations. The team that built the pilot knows how to read the results; the team receiving it does not. Without training and written criteria, people start accepting everything the model says or ignoring it entirely, and both are equally expensive.
What to watch
- Which concrete process is touched and how it is measured before and after; with no baseline there is no result, only opinion.
- Who reviews the model outputs and how often — the point at which AI becomes auditable.
- Cost per query at real volume, not pilot volume: the variable that produces the most surprises.
How I read this entry
If I had to bring this into an organisation, I would start with a boring, measurable process — reconciliation, first-line support, document review — and get it running with a metric before touching anything flashy. The credibility for big projects is bought with a small result nobody can argue with.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
