Meta is spending everything on AI agents nobody has yet

Mark Zuckerberg is telling investors that within five years, billions of people will have personal AI agents that understand their goals and work on their behalf around the clock. On Meta's Q2 2026 earnings call Wednesday, he framed it as the obvious future: agents handling finances, health, relationships, household management, the works. The first area that really took off was coding, he said, but engineers are technical and willing to fiddle. For agents to go mainstream, they need to just work out of the box for ordinary users.

Here's the part that's more interesting than the pitch: Meta is throwing a ridiculous amount of money at this bet. Second-quarter capital expenditures hit $31.1 billion, up 83% year over year. Free cash flow fell 91% to $784 million from $8.6 billion the same quarter last year. Meta raised its 2026 capex guidance floor by $5 billion to $130–145 billion and is working with BlackRock on a $14 billion data center in El Paso. Meanwhile Reality Labs lost another $4.6 billion this quarter—roughly $88 billion in total since 2021. The stock dropped almost 10% after earnings.

Source article image
Source image 1

There's a real tension here. Zuckerberg is betting that selling intelligence through personal agents will eventually pay better margins than selling compute or ads alone. But for now, Meta is eating almost all its operating cash flow on infrastructure, taking on long-term debt, and delaying buybacks. The agents are not shipping as a consumer product yet—business agents on WhatsApp and Messenger are rolling out globally, b

Source article image
Source image 2
ut the "personal agent" vision is still mostly a thesis dressed up as inevitability. That's fine if it comes together, but it's not exactly subtle: Meta is borrowing heavily against its ad business to build a future where everyone has a bot working for them, and Meta is running a big chunk of those bots. Question is whether the infrastructure and product delivery can keep pace before investors start treating this as an expensive distraction instead of a second-growth platform.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more