AI Daily — Mar 10, 2026

Today's thread is control — and who's grabbing it. Microsoft is quietly deciding which AI model answers your questions, Meta just bought the identity layer for AI agents, Amazon is pulling the emergency brake on AI-written code, and an open-source project told LLMs to stay out entirely. The companies building AI and the companies deploying it are racing to own the plumbing between models, and the decisions being made this week will shape who has leverage for years.

Meta acquired Moltbook today, and the deal is weirder than it sounds. Moltbook isn't a social network for people — it's a platform where AI agents verify their identities, connect with each other, and act on behalf of their human owners. Think of it as a phonebook and passport office for bots. Its code was written almost entirely by an AI assistant, its security was porous enough that humans could impersonate bots, and some of its most viral moments were staged. None of that was disqualifying.

What Meta actually bought is the identity infrastructure underneath. An internal Meta post described the acquisition as gaining "a registry where agents are verified and tethered to human owners" — not a quirky social experiment, but the plumbing you'd need before embedding agents across WhatsApp, Instagram, and Messenger. Moltbook's founders, Matt Schlicht and Ben Parr, are joining Meta's Superintelligence Labs. Meanwhile, OpenClaw's founder — the creator of the agent communication protocol that powered Moltbook — was hired by OpenAI last month.

Both halves of the same experiment are now inside the two largest consumer AI companies. Academic teams have already published preprints dissecting Moltbook as a "silicon society" — documenting spam floods, emergent cliques, and learning behavior among 20,000+ agents. That dataset is now Meta's. The question isn't whether agents will have social networks. It's whether Meta just locked up the identity standard.

Letting AI write production code has consequences, and Amazon just found them. Following a series of high-impact incidents — including a multi-hour outage — linked in internal notes to "Gen-AI assisted changes," Amazon now requires senior engineers to manually approve any AI-assisted code before it goes live. Internal briefings reported by the Financial Times tied root causes directly to AI-assisted edits, and The Register's coverage today confirmed the new approval processes.

This is one of the first high-profile cases of a tech giant publicly admitting that AI developer tools create real operational risk. The pattern is straightforward: AI generates plausible-looking code, junior engineers ship it, and nobody catches the subtle errors until production breaks. Amazon's fix — senior sign-offs with tighter blast-radius rules — is practical but expensive. Expect every large engineering shop running Copilot or similar tools to quietly adopt the same approach within months. The era of "just let the AI commit" lasted about eighteen months.

Most AI models need a data center. Google's Gemma 3n, released today, is designed to run on your smartphone — summarizing texts, drafting emails, even generating images without a cloud connection or significant battery drain. If that sounds incremental, consider what it means for privacy: your data never leaves your device.

Real-world performance tests are just starting, and the r/LocalLLaMA community is already buzzing about inference optimizations that claim leaderboard-topping results on consumer GPUs. If those optimizations translate to mobile chips, Gemma 3n's promise becomes very real very fast. On-device AI has been a talking point for years; this is the first model from a major lab that seems built to actually deliver it at scale. Watch user feedback this week — it'll tell us whether "AI in your pocket" is finally more than a slide deck.

An update rolled out today makes Microsoft's Copilot something more than an AI assistant — it's now a multi-model router. Instead of relying on a single AI, Copilot picks which model answers your query based on the task: one for code, another for analysis, a third for creative writing. Think of it as a switchboard operator deciding which expert takes your call.

The strategic implications are significant. If Copilot becomes the default interface for hundreds of millions of Office users, Microsoft controls which models get traffic — and which don't. That's a different kind of power than building the best model. It's the power of distribution: owning the layer between users and AI. Developers and competitors should be watching closely, because interface control may matter more than model superiority in the long run.

X quietly shipped a "block modifications by Grok" toggle in its iOS app — the kind of fix regulators have demanded since the Grok deepfake scandal went global in January. Independent testing found it's mostly theater. The toggle stops other users from tagging @Grok in replies to your photo, but it doesn't prevent the bot from processing or editing images when they're re-uploaded, saved, or imported through other paths. The gap between what the setting promises and what it delivers is wide enough to drive a regulatory truck through.

The timing is brutal: Elon Musk and X executives face a European regulatory hearing scheduled for April 20 over Grok's deepfake and misinformation issues. Regulators are unlikely to be impressed by a cosmetic UI toggle that wasn't properly validated. This is shaping up as a test case for whether platforms can satisfy safety requirements with surface-level controls — or whether they'll be forced into verifiable, auditable safeguards.