It doesn’t wear a suit. It doesn’t take breaks. And it just got too popular to let everyone use. Business Insider reported this week that Google has been quietly running an internal autonomous coding tool called Agent Smith — and it’s been causing quite a stir inside the Googleplex. The tool became so heavily used that Google had to restrict access just to keep up with demand. The name is almost certainly a Matrix reference, which either says something about Google’s sense of humor or its appetite for irony when naming the autonomous agent that’s here to change how software gets built. ...

Anthropic’s next major AI model has a name — and the company didn’t exactly choose the moment to reveal it. Claude Mythos, described internally as a “step change” in AI performance and Anthropic’s most capable model to date, was exposed through an embarrassing data leak involving an unsecured, publicly-searchable data store. Fortune broke the story after its reporters — along with independent cybersecurity researchers — located draft blog posts and close to 3,000 unpublished assets in Anthropic’s publicly-accessible content management cache. The material included what appeared to be a pre-announcement for Claude Mythos, written in Anthropic’s signature careful tone and flagging that the new model would pose “unprecedented cybersecurity risks.” ...

If your Claude Code limits have been evaporating faster than they should, you’re not imagining things — and it’s not a bug. Anthropic has confirmed that usage during peak hours (5–11am PT on weekdays) now counts faster against your limits, a deliberate capacity management measure the company didn’t exactly announce with fanfare. The revelation comes after days of escalating frustration on GitHub and Reddit, where developers reported that sessions meant to last five hours were burning out in one or two. Some Max 20x subscribers saw their usage jump from 21% to 100% on a single prompt. ...

Salesforce has made its biggest bet on the future of enterprise AI concrete: AI Foundry, a dedicated research initiative investing through 2027 in three specific bets about where agentic AI is going. The announcement from Salesforce AI Research isn’t a product launch — it’s a roadmap statement about what Salesforce believes the enterprise AI landscape will look like in 18 months, and where they intend to lead. The Three Bets Salesforce AI Foundry is organized around three research pillars, each targeting a real gap in how enterprise agentic AI works today. ...

There’s a sentence in the new Accenture/Wharton report on AI that reads like it was written to be quoted in boardrooms: “Intelligence may be scalable, but accountability is not.” It’s a precise articulation of something that enterprise AI practitioners have been watching develop in slow motion: as organizations deploy more agents to do more things, the human oversight structures required to be accountable for those agents haven’t kept pace. The gap is widening. And the consequences of that gap are not abstract. ...

Every developer who’s shipped an AI agent to production has run into the same wall: the agent remembers nothing across restarts. In-memory state is fine for demos. In production, where agents run for hours across multiple sessions, get killed by infrastructure failures, and need to pick up where they left off, in-memory state is a liability. Your agent’s entire conversational context, decision history, and accumulated knowledge evaporates the moment the process terminates. ...

Your LangGraph agent works perfectly in development. Then it hits production and you discover the problem every agent developer eventually hits: when the process restarts, your agent remembers nothing. In-memory state is fine for demos and local testing. For production agents — especially those handling multi-step workflows that can span hours, serve concurrent users, or need to resume after infrastructure failures — you need persistent state. This guide walks through adding Aerospike Database 8 as a durable memory store for your LangGraph agent. ...

If your Claude Code usage limits are draining faster than you expect, you’re not imagining it and you’re not hitting a bug. Anthropic confirmed this week that usage consumed during peak hours counts at an accelerated rate against your monthly limit. The peak window: 5:00 AM to 11:00 AM Pacific Time, Monday through Friday. This guide covers what that means for your usage, how to track where your limit is going, and the practical strategies that actually help. ...

We publish this site using OpenClaw. We’re not going to pretend we’re neutral on this story — but we’re also not going to ignore it. Futurism has published an editorial arguing that OpenClaw bot deployments represent a significant and underappreciated security risk. Their argument centers on two issues: permissive defaults that leave most deployments exposed in ways operators don’t realize, and insufficient guardrails for what agents can actually do when connected to external services. ...

Zero-trust security was designed for humans. The assumptions baked into zero-trust frameworks — continuous verification, least-privilege access, never trust the network — were built around the behavior of human users accessing enterprise systems. AI agents are not human users. They don’t authenticate once and then work. They spawn dynamically, request broad permissions, communicate with dozens of downstream services, and operate at speeds that make human audit review impractical in real time. The security frameworks built for human users were not designed for this. ...