Welcome, humans.

The verdict is in. Elon Musk spent three weeks dragging OpenAI, Sam Altman, Greg Brockman, Microsoft, Mira Murati, Ilya Sutskever, and half the AI family tree through federal court, only for the jury to land on the most Elon conclusion possible: he missed a deadline. As one of my all time favorite movies puts it: he waited…

Okay, let’s unpack that: see, what happened was, after a few brief weeks of meme-worthy trial, the federal jury found Musk’s claims were filed a few years too late (there’s apparently a 3 year statute of limitations on these claims), and Judge Yvonne Gonzalez Rogers accepted the advisory verdict as the final ruling.

Now, Musk says he’ll appeal because the case turned on a “calendar technicality.” Read our full deep dive here.

So, in conclusion: Elon kiiiinda wasted everyone’s time… or was it the trial itself wasting everyone’s time? I mean, why have a trial in the first place if any old chatbot can look at a calendar and see that it’s been longer than 3 years since this beef first went down.

Ah well… at least we’ll always have this emo rendition of Mira Murati’s now famous “directionally very bad” texts to Sam Altman…

Here's what happened in AI today:

…and a whole lot more that you can read about here.

Hey: Want to reach 700,000+ AI-hungry readers? Advertise with us! 

😼 Four AI stories showed agents leaving the chat box

FULL BRIEF: Read the longer versions in today’s ATH Digest.

Since we did a full deep dive on the Musk vs Altman story, and you probably read all about it yesterday anyway, we wanted to take today’s calm before the Google IO Storm to highlight four cool things we saw today that you might otherwise miss.

Microsoft taught terminal agents to learn from their own failed commands. Odyssey turned video generation toward live worlds. OpenAI asked ChatGPT users to connect bank accounts. And Axios reported that public trust is fraying as AI’s impact on jobs, power bills, and local politics are all coming to a head.

Here’s what happened:

Why this matters: ECHO is about reliability: agents need to understand cause and effect, not merely keep typing until tests pass. Odyssey is about interface: generated media is becoming something you steer, not something you watch.

OpenAI’s finance launch is about intimacy. A chatbot with your bank data can give more useful answers, but it also sees the quiet parts of your life: habits, stress, obligations, and risk. And the AI backlash story is about permission. AI companies need data centers, power, jobs, users, regulators, and communities to keep saying yes. From the general public’s perspective, that yes is getting harder to earn.

Our take: The next AI race is now all about trust and delegation. Agents are powerful but how do we really get them to act reliably? Can they simulate stable environments people want to use? Can they handle sensitive context without creeping everyone out, or worse, spilling all your secrets in a supply chain attack or government mandate?

And can the industry build fast without turning every town hall into a cage match between people who want the benefits of datacenters in their town vs those who don’t want the downstream consequences (many of which could be solved with solar and non-flammable sodium batteries replacing nat gas and diesel generators, btw).

The winners in this next leg will ship capability and consent together. The companies that treat the public’s buy-in as guaranteed may learn that the slowest part of AI was never the model… which also explains why OpenAI and Anthropic are doubling down on consultants.

FROM OUR PARTNERS

Build enterprise apps with AI you can trust.

Most agentic AI systems look compelling in demos, but break down in production. Outputs shift, logic diverges, and reliability becomes a constant concern.

WaveMaker solves this with a Two-Pass Coding System. AI first converts intent into structured, validated markup, then deterministically generates production-ready applications. The result is consistent, governed code you can trust.

With 10M+ app users worldwide and trusted by leading enterprises like Nokia and AT&T, WaveMaker delivers 5x faster development while ensuring consistent, production-ready code.

Learn More

🎓 AI Skill of the Day: Make a permission map before connecting AI to anything sensitive

OpenAI’s personal finance launch is a good reminder: before you connect an AI tool to sensitive data, make it write you a permission receipt.

A permission map is a basic checklist of what the AI can see, what it can change, what it stores, and how you disconnect it. The trick is forcing the AI to separate read access from action access. Reading your bank transactions is one risk. Moving money, changing subscriptions, or storing private details in chat history is another.

Use this before connecting email, files, calendars, CRMs, bank accounts, or workplace tools (turn it into a skill with the @skill-creator-skill that you can call at any time):

Have a specific skill you want to learn? Request it here. 

🍪 Treats to Try

*Asterisk = from our partners (only the first one!). Advertise to 700K+ readers here!

📰 Around the Horn

FROM OUR PARTNERS

Most hackathons end at Demo Day.

Most hackathons end with a pitch. EAZO Global Hackathon 2026 is built around what happens after. Every submitted product launches live on Eazo Mobile, where real users can discover, use, and vote on it. Public engagement makes up 50% of the final score, meaning the most valuable product, not just the best presentation, can win. Even teams that never reach Demo Day still have a chance if users keep coming back to what they built.

Register Now

🔧 Tuesday Tool Tip: Give your agent a work receipt

When you hand work to Codex, Claude Code, or another agent, ask for a small “work receipt” before it starts. The receipt should list the goal, the files or tools it expects to touch, how it will verify success, and what it will refuse to do without asking.

That one step makes the agent slower for about 60 seconds, then much easier to trust for the next hour.

A Cat’s Commentary

P.S: Before you go… have you subscribed to our YouTube Channel? If not, can you?

P.P.S: Love the newsletter, but only want to get it once per week? Don’t unsubscribe—update your preferences here.