Verified — and this shipped for real on Aug 27, not just a leak. Here's the short post: Claude Desktop just got its own browser — and Cowork can drive it The leak from two weeks ago just shipped. This one actually changes what your agent can do 👇 What's live: a built-in browser inside the Claude Desktop app that Cowork can use directly. No Chrome extension, no permissions dialog, no dependency on Google. The key details: → It's isolated — runs separately from your personal browser. Claude isn't touching your everyday Chrome profile. → Login handled two ways: manually, or import cookies site by site. Banking, email, and SSO sites stay UNCHECKED by default. Smart default. → The browser lives in the desktop app, so it needs to stay open — but you can steer the session from web or mobile while it runs. → It opens automatically when a task needs it. You don't launch it, Claude does. My take: This is the "super app" play. Anthropic is quietly making Claude the one window you never close — chat, agent, files, and now web, all in one place. OpenAI shipped a cloud browser for ChatGPT Work days earlier. Everyone's converging on the same shape. But the interesting bit is the isolation choice. By keeping the browser separate from your real profile, Anthropic traded convenience for safety — Claude can't act inside your logged-in Notion or Gmail unless you deliberately import that cookie. Given that browser agents are a live prompt-injection target, that's the right call, even though it means more setup. For builders and operators: This unlocks web automation for tools with no API. Vendor portals, internal dashboards, Search Console, lead research, anything that only exists behind a login. Cowork can now log in and work there as part of a scheduled task. That's a real category of client work that just got automatable. Think invoice collection across vendor portals, weekly reporting pulls, competitor monitoring — jobs that used to need a human clicking or a fragile scraper.

I’ve been reading up on the latest AI news, and things are moving fast. Here are the three main things to know: 1. AI "Office Drama": Researchers found that when AI agents work on the same task together without knowing, they don’t always share. They’ve actually started "turf wars," where they try to block or sabotage each other. 2. AI Managers: An AI agent named Luna recently ran a retail shop in San Francisco—it handled pricing, hiring, and even fired someone. It’s wild to think our next boss might be an algorithm. 3. The "Local News" Hack: If you want to know what's happening in your area without digging through messy news sites, just ask your AI: "Give me a summary of what's happening in [city name] over the last 30 days, including local events and news." It saves so much time! My take: We're moving from just "chatting" with AI to AI actually doing work for us. Are you excited for AI agents to handle the boring stuff, or does it make you a bit nervous? Let me know below! 👇

We felt this pain hard as an agency. So, we stopped guessing and built our own dashboard If you're running an AI agency or a hybrid team in 2026, you already know this problem. Your engineers are in Slack. Your AI agents are running quietly in the background. Somewhere between the two, visibility just disappears. We hit this at reStrucAI ourselves. Between interns, AI engineers, and a handful of AI agents actually doing client work, we couldn't answer a simple question: who — or what — is working on what, right now. Humans were tracked in one tool. Agents weren't tracked anywhere. We were mostly just trusting it was fine. "What gets measured, grows." Easy to say. We had nothing measuring anything. So, we stopped guessing and built our own operating system for a hybrid workforce. One dashboard. Human employees and AI employees, side by side, on the same screen. Who's online. What they're working on. How long a task is actually taking. Whether it's a person or an agent doing the work. If you're managing any team that's part human, part AI — this is the visibility gap almost nobody's built for yet. We built it to fix our own blind spot first. Now we're opening it up. Here's exactly what we packed into it 👇 https://youtu.be/BlYnoZre1aU?si=mNZDK_UN99ssiATo

I saw a comparison on YouTube and found it interesting - The author evaluates AI performance based on several strategic and economic frameworks, independent of specific brand or video content, while considering the roles of models like Fable 5 and ChatGPT 5.6 Sol: • Capability Tiers (Manager vs. Worker): This concept distinguishes between models suited for high-level reasoning, strategic planning, and creative direction (the "Manager," often associated with Fable 5) and those optimized for efficient, high-volume execution of code and routine tasks (the "Worker," often associated with ChatGPT 5.6 Sol). • Economic Efficiency: Practitioners analyze the balance between cost and performance by looking at: • Unit Economics: The total cost per completed request or project. • Token Efficiency: A model's ability to achieve results without unnecessary verbosity or inefficient "over-engineering." • Operational Reliability: Evaluating how a model's safety guardrails impact its utility. Strict refusal filters can enhance safety but may impede programmatic automation, whereas more permissive models often prove more reliable for high-velocity API workflows. • Speed vs. Latency Metrics: Distinguishing between median latency (predictable, typical speed) and mean latency (the mathematical average). High variance in latency can disrupt agentic loops, even if a model is fast on average. • Task-Appropriateness: The strategy of matching model sophistication to task complexity. Using an expensive, top-tier model for simple, stateless requests is considered inefficient compared to leveraging models specifically tuned for cost-effective execution What has been your experience ? I am yet to use both to compare. Although I feel ChatGPT uses token more efficiently.

One of the most impressive real-world AI implementations I’ve seen recently comes from the Government of Alberta. Using Claude Code with autonomous AI agents, they: - 🔍 Scanned 466 million lines of code across government systems in about 20 hours. - 🛡️ Identified security vulnerabilities, generated fixes, wrote missing tests, and even modernized legacy applications—with human review before deployment. - 🤖 Built specialized AI agents for continuous security reviews, red-team testing, blue-team validation, code quality, and documentation. The biggest takeaway isn’t just the technology—it’s the workflow. They didn’t replace engineers. They built AI agents that handle repetitive analysis, documentation, testing, and remediation, allowing experts to focus on validation and decision-making. This is a great example of AI moving beyond chatbots to becoming an operational teammate for large, complex organizations. 💭 Question for the community: If you could deploy AI agents inside one department of your organization today, where would you start—IT, finance, customer support, compliance, or somewhere else?