Welcome, humans.

So we’ve seen models for text, images, code, video, audio, biology, math, robots, and probably 17 other categories someone will yell at us for forgetting.

But this might be the first food model we’ve ever seen.

Josef Chen and Kaikaku released Epicure, a multilingual ingredient-embedding model trained on 4.1M recipes across 7 languages, covering 1,790 ingredients in 300 dimensions.

It basically compresses “all of human cooking” into about 2MB, then lets you explore ingredient pairings through the Epicure Flavour Explorer (which you can connect to via a HF Space, check the HF paper page, their paper), and even use as an MCP endpoint (meaning you can use it inside your agent workspace of choice).

So now AI can look at your fridge and say, “combine this, this, and this to make a meal” and actually know what it’s talking about, instead of “Let me order you something on DoorDash!” WHICH, IN OUR EXPERIENCE, DOESN’T WORK ALL THAT WELL.

DoorDash, if you disagree, release a tutorial showing it working… we dare you…

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! 

P.S. We’re going live today @ 10am PT, 1pm ET with A Total Beginner’s Guide to AI Agents; it’s a no-code, no-jargon walkthrough of what agents are, how automations work, and how to start using both without getting overwhelmed. Come bring your newbie questions and we’ll answer them all!

😼 Robinhood gave AI agents permission to touch your money.

AI agents have been asking for access to your calendar, inbox, and spreadsheets. Now they are asking for something much more awkward: your brokerage account.

Robinhood is rolling out “agentic trading,” a beta that lets users connect AI agents to a dedicated Robinhood account, set a budget, and let those agents trade stocks. It is also adding an agentic virtual card for Gold Card users, so agents can make purchases inside user-set limits (WSJ, FT).

Here’s what happened:

How to try it:

Why this matters: Agents are moving from “help me think” to “act on my behalf” towards a goal. That shift changes the product design problem. The winning agent app now needs permissions, spending caps, audit logs, rollback buttons, and (we mean this in no way ironically but of course there’s plenty of irony) a panic switch.

Our take: The lesson here is pretty practical: any agent touching money, customer data, or production systems needs rules (LOTS OF RULES)  before access. “Can AI do the task?” is basically an easy yes for most things these days (or as Dan Shipper of Every says, once you set your frame on a target, AI will eventually be able to do it). “What can go wrong?” is the question you really gotta ask yourself. 

FROM OUR PARTNERS

Winning product quality in the age of AI-SDLC

If you've said to yourself "I don't know what good looks like anymore", you're not alone.

Most engineering leaders are figuring out how to control product quality while shipping fast with AI.

Our founders wrote Past the Bottleneck after two years working with some of the best engineering leaders in SaaS. Their insights reshaped how the validation layer of QA should work. Inside:

Written for CTOs, VPs, and heads of engineering.

Get the guide

🎓 AI Skill of the Day: Write an Agent Permission Brief

Before you hand an AI agent a login, credit card, CRM, or production system, write a permission brief.

A permission brief is the agent version of giving a new hire a role, a budget, and a manager. It defines what the agent can do, what it must ask before doing, where it should leave logs, and what happens when it fails.

This is especially useful after the Robinhood news, because the risk is no longer theoretical. Agents can now touch money. Soon, they will touch procurement, customer accounts, legal docs, and internal systems.

Use this prompt before connecting any agent to real data or real spending:

Total AI beginner? Start here (goes with this video).

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

🍪 Treats to Try

New from The Neuron: What Comes After GPUs? Great Sky’s Bet on Brain-Like AI

Everyone keeps asking whether AI needs bigger models. This week, we asked a weirder question: what if the next leap needs a stranger computer?

In our latest podcast episode, we talked with Great Sky co-founder Jeff Shainline about what comes after GPUs, including superconducting circuits, photons, and why “brain-like computing” does not mean putting a tiny brain in a server rack. Disappointing for sci-fi. Probably better for compliance.

We also published new guides on building real-time AI voice agents and why DataCurve’s DeepSWE exposes a weird coding-benchmark problem, which all your favorite coding or AI YouTubers probably just made a video about.

New episodes air every week on: Spotify | Apple Podcasts | YouTube 

📰 Around the Horn

FROM OUR PARTNERS

Your next great hire lives in Slack.

Viktor is an AI coworker that connects to your tools and ships real work. Ask Viktor to pull a report, build a client dashboard, or source 200 leads matching your ICP. Most teams hand over half their ops within a week.

Add Viktor to Slack for free.

🧩 Thursday Trivia

You know the drill. One is AI, and one is real. Which is which?

A. 

B.

A Cat’s Commentary

Trivia answer: B is AI, and A is real. The creator said every clip was made with LTX 2.3 using real The Next Generation image screengrabs as visual references, plus this Star Trek TNG Style LTX 2.3 LoRA to lock in the look. Oh, and if you click that AI link… gotcha!

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