Aute

You might not have noticed, but someone fixed a years-old issue with Chrome on Mac. Window resizing, tab switching, things you do every day. The animation frame rate has long been less than half of your display's refresh rate. You felt that "not quite smooth" feeling, but probably never thought it shouldn't be that way. The video below shows it. As of Chrome 147, it's fixed. You don't even need to be one of our users, just update Chrome to the latest version and you get it. The person behind this is our client lead @liuwd_citro. He's landed 300+ changes in Chromium, focused on the small details that make Chrome faster and smoother, most people don't notice this work, but everyone benefits from it every day. Why do we do this? Cause we stand on the shoulders of countless open source projects. Building something genuinely exciting isn't possible without that foundation, so we wanna give some back. And in a moment when AI slop is flooding the world, we still believe good products live in the details. What's been bugging you about Chrome for a long time? Drop it in the replies. We will read every one of them. Where we can, we'll patch it. And we'll prioritize giving you early access to what we're building.

The real danger is not that computers will begin to think like men, but that men will begin to think like computers.——Sidney Harris

Proud of the team. We aren't just building an agent; we’re rewriting the physics of the web interface. More to come.

So the real question becomes: How do you—and your Agent navigate a world that wasn't built for either of you? Not the future web of atomic APIs. The current web of buttons, logins, and bundled friction. That's one of the core problems we keep thinking about.

Which means for a long time, we're still living inside legacy GUIs. Not because we want to. Because the incumbents need us to.

We said GUI isn't dying; it’s undergoing a transfer of sovereignty. But here is the nuance: we are moving away from fixed, platform-dictated interfaces toward true GUI Sovereignty. That’s the long game— where your interface is autonomously generated and personalized for you. However, that transition takes time. Here’s the short game nobody’s talking about.

The browser wars taught us one thing: The default wins. Apple letting you choose Claude doesn't mean you will. The negotiation that matters isn't in the App Store. It's happening in boardrooms right now—deciding which model ships pre-selected. Distribution beats capability. Again.

iOS 27 could open the door to multiple AI models 🤖📱 Users might get to choose between Gemini, ChatGPT, Claude, and more to power Apple Intelligence features. Which AI would you pick as default? 👇

@claudeai Memory isn't the hard part. curation is. Any agent can store context. The real question is: what's worth keeping, and what becomes noise? "Dreaming" is a great name. Hope the underlying filter is smarter than a human's.

Live from Code with Claude: we're launching dreaming in Claude Managed Agents as a research preview. Outcomes, multiagent orchestration, and webhooks are now in public beta.

But something else got flattened too: Taste. Context. Identity. You don’t get better decisions by removing ego. You get better decisions by understanding it. Because ego is not the enemy. Unexamined ego is.

“Low ego” became a virtue when ego became performance. So we learned to shrink it. Hide it. Flatten it.

FUTURE? GUI isn't being replaced by Chat. It's being liberated from the platforms. The future of GUI isn't a fixed, pre-coded interface from a provider. It's a Dynamic Interaction Layer generated in real-time by your personal Agent—tailored to your habits, your intent, and your context. GUI is moving from "The Platform's Interface" to "YOUR Interface."

WHAT'S NO? Language is great for expressing intent, but it's terrible for understanding complex results. Think back to the pre-computer era. We had maps, charts, and diagrams. Why? Because humans are hardwired to process spatial structures visually. You don’t want a Chatbot to read out your 12-month financial report; you want a dashboard. You don’t want to type "Option 2"; you want to click it.

Will GUI die? Yes and no. The mainstream view: Agents will talk to APIs via CLI, and humans will talk to Agents via Chat. Therefore, GUI is dead. This is only half right.

We’ve been looking at AI Agents all wrong. Currently, we categorize them by where the runtime lives: Local vs. Cloud. But this binary is a trap. Local Agents--They share my files, my browser, my apps. They have "Context." But the moment I close my laptop, my "assistant" dies. Unless you have a dedicated Mac Mini acting as a server, it’s a broken experience. Cloud Agents--They are 24/7. Always reachable. But they are "blind." No login sessions, no local apps, no real-time context. Instead of them assisting me, I end up being their assistant—prepping docs, copying logs, feeding them context. The Reality--Running two separate agents is a joke. A true "Jarvis" shouldn't be fragmented across devices or tethered to a specific runtime. Future intelligence must be a seamless whole—where local context meets cloud persistence. Intelligence shouldn't be split. It should just be there.