DEV Community: Dishant Sharma

Vercel's UI SDK Hands Agents Behaviors, Not Components

Dishant Sharma — Sat, 14 Nov 2026 13:38:33 +0000

There's an open issue in the UI SDK repo, number 534, that says FieldError is not a live region. A validation error that appears after the page loads never gets announced to a screen reader.

Zero comments on it. No fix yet.

That issue sits inside a library whose entire pitch is accessible behaviors for agents. Vercel Labs shipped it on November 12, 2026, built by shadcn, Apache-2.0, still beta.

The repo went from nothing to 4,239 stars in nineteen days. The announcement post pulled thousands of likes. And the Hacker News submission got 7 points and zero comments.

So which is it. A new layer of the web, or a launch video with good typography.

what it actually is

Most tutorials will tell you UI SDK is a component library. It isn't. It's the layer underneath one.

Instead of handing you a Select, it hands you createPopup, createSelection and createTypeahead. The agent wires them together.

Then you get a Select. Or an autocomplete. Or something nobody has designed yet.

Here's the shape:

definePrimitive declares state, an api and slots
slots attach attributes, events and behaviors to DOM parts
createParts renders the same primitive in React, Vue, Svelte, Solid or Web Components

One behavior definition, five frameworks. That part is real, and it works.

There are 50+ behaviors in the core package, grouped into ten categories. Focus, keys, selection, popups, dragging, lists, trees, transitions, canvases, utilities.

The README has a line that stopped me cold: "Don't worry, you don't need to learn how to write this. Your agents will."

I don't know how to feel about that. It's honest about the bet. It's also a strange thing to print in a library README.

the first time an agent builds one

the first time i tried this, i asked for a teammate picker. Small thing. Button opens a list, you pick a person, it closes.

The agent reached for createPopup and createSelection. Then it skipped createListbox and wired arrow keys by hand.

The result looked fine. Then i tabbed into it and focus vanished into the popup with no way out.

That's the trap. Behaviors are composable, which means they're also omittable.

Here's what the docs push instead:

Pick the behaviors that match the interaction
Define the primitive with state, api and slots
Render with createParts in your framework
Run the testing kit on keyboard, focus and ARIA

Step four is the one people skip. And it's the one that catches my broken picker.

My coworker tried the same prompt a day later and got a cleaner result. Same model, same package, different phrasing. He said "use createListbox for arrow keys" and it listened.

So the skill isn't a compiler. It's a nudge. The quality of what you get still depends on how well you describe the interaction you want.

That's not a flaw exactly. It's just not the hands-off thing the demo implies.

the agent half

i used to think the "built for agents" label was marketing. Then i read the docs.

Every package ships llms.txt and core.md matching the version you installed. There's a skill you add with one command. And there's a bridge.

const agent = createAgent()

After render, agent.snapshot() returns components, their state and their actions. Then agent.act() calls setValue on an input by label.

No screenshots. No clicking coordinates.

That's a different thing from browser automation. It's the gap between reading a form and guessing where the text box lives.

Vercel ran a benchmark on one settings screen. Browser tools versus the bridge:

	Browser tools	UI SDK bridge
Tool calls	16	5
Text read	39.8k chars	6.8k
Time	41 s	16 s

That's 69% fewer tool calls and 61% faster, self-reported.

And here's where i get skeptical. It's one task. Three runs.

The browser side used a different component library. Vercel doesn't name the Sonnet version.

a benchmark with one task is a demo, not a result.

is this AGI

No. Not close. And the framing around the launch did not help.

Guillermo Rauch called it "the x86 instruction set for agents to build new UI components spontaneously." He also said agents are the new design engineers, and that rigid component libraries are "kryptonite."

Good line. It's also a hardware metaphor for a TypeScript package.

What UI SDK does is narrower and more useful than that. It gives a model a small, named vocabulary for interaction.

Popup. Selection. Typeahead. Roving focus.

Models are decent at picking from a vocabulary. They are bad at inventing keyboard semantics from scratch.

So the real claim is boring. Structured primitives beat freeform generation. That isn't AGI. That's a schema with good docs.

why anyone needs it

here's a question people always ask. We already have Radix, React Aria and Base UI. Why another one.

Fair. React Aria already splits behavior from markup. Ark UI runs on Zag.js state machines.

Both are solid, both older, both battle-tested.

The difference is the agent layer. The skill, the bundled docs, the runtime bridge. None of that exists in the older libraries, at least not openly.

But the cost is real. React 19 is the floor. Vue 3.5, Svelte 5.33, Solid 2 RC.

That's a narrow door for teams mid-migration.

And the repo has 80 open issues. Many with zero comments.

a nested dialog rendering beneath its parent
IME digits never becoming a value
a Select listbox with no accessible name

Those aren't glamorous bugs. They're the ones that decide whether real people can use the thing.

Somebody on X posted a periodic table of UIs after the launch. Every element a component. It pulled hundreds of likes.

i have a folder on my laptop called components-v3. It holds four half-built design systems. Each one started right after a launch like this.

The poster and my folder are the same disease. We like the idea of a system more than we like finishing one.

And honestly, a periodic table is a perfect artifact for this moment. It makes a library feel like chemistry. Like the pieces were always there and somebody just labeled them.

They weren't always there. Someone wrote the focus trap.

There's a specific comfort in a new library. Everything is possible and nothing is broken yet. The bugs arrive later, and so does the real work.

Real talk. Most people don't need this.

If you ship three forms a year, use shadcn/ui and go outside. It's stable, it's boring, and your agent already knows it.

If you're on React 18, skip it. The peer range will fight you for an afternoon.

And if your team has no accessibility testing, a behaviors library won't rescue you. Issue 534 is the proof. A primitive is only as good as the person checking it.

Where it earns its keep is narrower. Teams building agent-operable products. Admin panels, dashboards, internal tools where an agent does the clicking.

That's a real market. It's just smaller than the launch video implied.

i keep coming back to that gap. 4,239 stars, thousands of likes on the announcement, and a Hacker News thread with zero comments.

The hype is real, but it's concentrated. It lives where people share videos, not where people file bugs.

Which is fine. Every layer of the web started as a demo. React did too.

The only question that matters now is whether anyone sticks around to fix 534.

OpenAI's ChatGPT Wallet Lets Agents Buy Things. One Bought a Potato

Dishant Sharma — Fri, 13 Nov 2026 20:08:59 +0000

A guy on r/wallstreetbets put $200 into an AI shopping agent and let it buy his groceries. It ordered two of something. It picked the wrong variation of something else.

And once, with no explanation, it bought a single potato.

i read that comment three times. Not because it was funny, though it is funny. Because one potato is the clearest summary of this whole product category i have seen so far.

The agent did not fail in a dramatic way. It did not empty his account or buy a boat. It just quietly decided that one potato was the right amount of potato.

That comment landed hours after OpenAI announced ChatGPT Wallet on November 13. The wallet lets agents in dots, ChatGPT Work, and Codex pay for things on your behalf. It was built with American Express, Mastercard, and Visa.

Right now it only runs in dots, for ChatGPT Pro subscribers in the US, 18 and up, with a US-issued card and a US billing address.

OpenAI is selling this as trust infrastructure. The card gets tokenized. You approve every purchase with Face ID or a fingerprint.

The agent never sees your number.

All of that is true, and none of it is the interesting part. The plumbing works. The question is whether the agent knows what you actually want.

How the token thing actually works

here's a question people always ask when a card gets involved: where does my number go?

It doesn't go anywhere. The flow is short:

You save a card once.
Your dot finds the item and shows you the merchant, items, total, and card.
You approve with Face ID or a fingerprint.
The network issues a token with its own number, code, and expiry.

That token is what the store sees. Your real card stays hidden from both the merchant and the agent.

Your rewards still apply. Your dispute protections still apply. If the sweater shows up with one sleeve, you call the merchant, not OpenAI.

But here's the line from OpenAI's own release notes that made me stop scrolling:

approval alone doesn't confirm an order. check the merchant's confirmation after checkout.

So the agent can take your Face ID, get a token, and still not have bought anything. The approval is a permission slip, not a receipt.

The stores are the real story

what actually happens is that half the internet does not want your agent there.

United Airlines changed its contract of carriage on November 11 and blocked third-party AI agents from booking flights. Amazon has been blocking outside shopping agents, including Meta's Muse and Perplexity. eBay blocks them too.

OpenAI admits this in the announcement. Some sites "may unintentionally block purchases."

That word is doing a lot of work. Much of it looks intentional.

So OpenAI shipped a playbook for merchants. Claim your business in ChatGPT. Allow signed requests through Web Bot Auth.

Then ask your fraud vendor to stop flagging agent traffic. They name Forter, Riskified, Sardine, Signifyd, Adyen, Checkout.com, and Stripe as partners already working on it.

Read that list again. OpenAI is asking retailers to reconfigure their fraud stack so a robot can check out.

That is a big ask, and it is the actual bottleneck. Not the card. The permission.

Who	What they want
OpenAI	Agents to complete checkouts everywhere
Merchants	Traffic they can see, price, and control
Networks	Transactions that do not look like fraud

Follow the money

most coverage skipped the fee question. CNBC reported OpenAI takes no cut of Wallet transactions at launch.

No cut, for now. That phrasing is doing work too.

OpenAI already charges merchants a 4% fee on sales through its Instant Checkout flow, which has been live since early 2026. Wallet is a different pipe, but it feeds the same machine. Free at launch usually means free until the habit forms.

And the incentive is obvious once you see it. If OpenAI owns the checkout, it owns the last step before money moves. That is the most valuable square on the board.

Reddit noticed faster than the press did.

"This is just a way for them to take a cut isn't it?"

That was the top-voted take in r/technology. It got there in about an hour.

What it costs

Wallet itself is free. Getting access is not.

ChatGPT Pro now comes in three tiers: $100, $200, and $500 a month. Wallet rolls out to Pro subscribers first. So the real entry price for letting your dot buy groceries is a hundred dollars a month.

And dots are the only place it works right now. Not the regular ChatGPT chat. Not Codex yet, even though OpenAI's own marketing copy mentions Work and Codex in the same breath.

The blog post says dots. The tagline says more. Trust the blog post.

Approval is not the hard part

The obvious criticism is the one i keep seeing. Who is this for?

If you can buy something in two taps on your phone, why would you ask an agent to do it and then approve it with your face anyway?

The answer is that per-purchase approval is training wheels. OpenAI says the quiet part in the announcement. Over time, they expect users to hand over purchases entirely, with spending limits, categories, and time windows set in advance.

That is the product. Not "approve every purchase." Approve the rules once and stop looking.

Which brings back the potato. An agent with a spending limit and a grocery category does not need your face to buy one potato. It needs judgment.

And judgment is the thing that failed.

A short detour about onions

i once ordered twelve kilos of onions because i misread a recipe that said two. My fridge smelled like a crime scene for a week. i made soup for six days and still threw half of it out.

So i have no room to judge a machine that buys one potato. We are both bad at this in different directions.

Every grocery store near me also replaced six humans with four machines that yell at me about bananas. You put a banana on the scale. The machine says unexpected item in bagging area.

You move the banana. It says the same thing. A teenager with a keycard walks over, sighs, and fixes it.

We spent a decade teaching machines to take payments and we still cannot weigh a banana correctly. Now we are handing those same machines a credit card and a shopping list.

Real talk

Most people should not touch this yet.

If you live outside the US, you cannot. If you are on Plus, you cannot. If you buy things the normal way and it takes thirty seconds, you are not the customer.

This is for people who already pay for Pro, already run dots, and already lose an hour a week on repetitive purchases. Maybe restocking the same five items. Maybe rebooking the same flight.

And even for them, i would wait a month. The blocklist problem is real.

A wallet that works on six sites is not a wallet. It is a demo with a Visa logo on it.

The ending

The part i keep thinking about is not the partnership or the token architecture. Those are solved problems. Payments people have been doing this for forty years.

It is the potato.

Somewhere a model looked at a household, a list, and a budget, and concluded that the correct number of potatoes was one. Nobody wrote a rule against it. There was no error message.

The system worked exactly as designed.

That is the thing about handing your card to something that thinks. It will not always be wrong in ways you can predict. Sometimes it will just be wrong in a way that is small, cheap, and completely inexplicable.

i would still try it. But i would check the bag.

Expo Simulators ships cloud phones for agents at $6 an hour

Dishant Sharma — Fri, 13 Nov 2026 09:54:16 +0000

Expo shipped cloud simulators for coding agents and the Hacker News thread got 24 points.

Twelve comments. One of them, word for word: "wow this is awesome !" with a space before the exclamation mark. Another says "my agents are going to love this."

The whole thread reads like people being polite to whoever posted the link.

That got under my skin. Not because the product is weak. Because this is the missing piece for agentic mobile work, and the room yawned.

On November 12 Expo made Expo Simulators generally available. It hands your agent a cloud iOS Simulator or Android Emulator on demand. No Mac, no nested virtualization, no seven simulators chewing through your laptop's RAM.

The agent installs a build, taps through the app, and comes back with a recording.

And it bills at $0.10 a minute. That number is most of the story, and i'll get to it.

What you actually type

npx eas-cli@latest simulator --platform ios

That one line starts a session and prints a link to a live view. You can also hand your agent a skill and let it work out the flags:

npx skills@latest add expo/skills --skill eas-simulator

The agent drives the remote device with the same commands it uses locally. agent-device is the default controller. argent and appium are options too. If you only want to look at a build yourself, --type web-preview-only gives you a stream with no controller attached.

i expected this to be the hard part. It isn't. The hard part is everything after.

Why local simulators fall apart

i used to think running agents locally was fine. It is, until you run more than one.

Two agents on the same machine fight over the same simulator. One reinstalls the app while the other is mid-test. You get a failure that has nothing to do with the code.

Expo names this directly. Each session gets its own VM, so parallel agents never share a device.

The comment i keep coming back to is from colinhunt on that thread: "Agents on my computer were fine to run in a normal dev loop but I really needed this for the background agents."

That's the real use case. Not your laptop. The agent in a cloud sandbox at 2am that has no device at all.

What the first session looks like

You run the command and it prints a URL. You open the URL and there is an iPhone, already booted, inside a browser tab.

No Xcode download. No 40-minute first launch. No spinning wheel while your fans ramp up.

I haven't run a session myself yet, so take the rest of this as what the docs and the demo show. The session page keeps a timeline of the agent's actions. Tap here, type there, wait three seconds.

Here's the question people always ask: does it replace a real device? No. Simulators never do. They miss push notifications on a locked screen, camera quirks, and anything that depends on a real network handoff.

But it replaces the part where you build the app yourself just to look at it. That's most of the time.

The Mac claim is half true

Someone asked if they could now build iOS apps from Linux. The reply came back cheerful: yes, your Linux agents can verify against a remote iOS simulator.

Then lukisk asked the obvious question. How do you build an iOS app without macOS and Xcode? Vendor lock, right?

He's right, and the thread moved on without answering him.

you still need a Mac somewhere, or EAS Build, to produce the .app in the first place.

Expo Simulators removes the simulator, not the compiler. That's still a big deal. It's just not the thing the headline implies.

What a session actually keeps

This is the part that sold me, and it's buried under the infrastructure talk.

Each session records:

video of the whole run
screenshots at any point the agent takes one
app and native logs
network traffic
CPU and memory usage

Artifacts stay for 30 days. Your agent can read its own logs and attach screenshots straight to the pull request.

That changes review. Instead of 500 lines that look about right, the reviewer watches a 40-second clip of the thing working. Nobody pulls the branch. Nobody builds it locally.

Expo's own demo is an agent that ran the app at the largest text size, saw labels overlapping, fixed the layout, and attached before and after shots. A real accessibility check, done without a human opening Xcode.

The pricing math

Here's where i stopped nodding.

$0.10 a minute is $6 an hour. For one verification run, that's nothing. Cheaper than your time.

But the entire promise is that agents check their own work. Constantly. A loop that verifies 40 times in an afternoon is $24. Spread that across a team and a CI pipeline, every day, and the meter adds up.

	Expo Simulators	Limrun	VibeView
Per minute	$0.10	~$0.08	$0.06
Entry plan	$19/mo	$20/mo	$19/mo
Free tier	none yet	120 credits	30 min

Paid plans include 60 simulator minutes a month until 2027. Sixty. That's ten hours of agent time per month, which is roughly two afternoons of a busy agent.

There's also a cap. The blog says no session runs longer than two hours. The pricing page says 115 minutes. Small gap, but you notice it when you're building a budget.

A short detour about the phone drawer

Every mobile team has a drawer. Old iPhones, a Pixel with a cracked screen, a tablet nobody remembers buying. It's the QA department, held together with tape and hope.

You know the one. Somebody's old phone, still charged, still on the wifi, labeled with a sticky note that says "do not reset."

The drawer exists because simulators lie. They're fast and clean and they never have a low battery or a notification covering your button.

Cloud simulators don't fix that. They just move the lie to a machine you're renting.

Who should skip this

If you have one agent, on your own Mac, in a normal dev loop, you don't need this.

Local simulators are free and already on your machine. Expo says so itself, near the bottom of the announcement.

The second group that should wait: anyone on the Free plan. Simulator minutes there still say "coming soon." Access starts at Starter, $19 a month. There's no free tier to try it, so you pay to find out if it fits.

And if your app is a simple form over a REST API, the agent can verify most of that without a device at all. You're buying a screen recorder for bugs you don't have.

The thing i keep thinking about

Twenty four points.

Expo built infrastructure that a dozen agent startups will end up depending on, and the internet replied with a shrug and a typo.

Maybe that's just Hacker News now. Launches don't get a reception anymore, they get a log line.

But i keep thinking about that Linux question nobody answered. The person asking wanted to build iOS apps without a Mac. What they got was a way to test them.

Half a product is still a product. It's just not the one the headline sold.

Claude Joined My Meeting And Microsoft Lost 2.26 Percent

Dishant Sharma — Thu, 12 Nov 2026 08:45:04 +0000

Microsoft closed down 2.26 percent at $521.12 after Anthropic showed off a spreadsheet.

Not a new model. Not a benchmark. Tabs and formulas.

i was half watching the announcement while doing something else, and that number is the part i keep coming back to. A company worth trillions lost billions in market cap in a single session because a competitor shipped cells.

Then i read the actual product list.

Claude Meetings, joining calls as a participant
Claude Whiteboards, shared boards that build during the call
Claude Sheets, spreadsheets with tabs and formulas
Claude Data out of beta, plus connectors into Adobe and Salesforce

All in one event.

The pitch is simple. Claude joins your Google Meet as a visible participant and follows the conversation.

Then it starts building the thing you are describing, while you are still describing it. A plan gets drafted. A timeline lands on a whiteboard.

Someone asks a question in chat and Claude answers it. The call ends and the notes, action items, and artifacts are sitting in claude.ai.

Anthropic's own line is that work normally starts after everyone hangs up. They want it to start at minute four.

And the timing is not subtle. This landed the same week as Anthropic's IPO roadshow.

Why care? Because every meeting tool you have used so far has been a stenographer. This one is trying to be a coworker.

What it actually does

here's a question people always ask about meeting bots: is this any different from Otter, or Granola, or the Copilot thing in Teams?

Yes, in one specific way. The others record and summarize. Claude is supposed to produce artifacts during the call.

Tool type	When it works	What you get
Transcript bots	after the call	summary, notes
Copilot in Teams	during and after	summary, chat answers
Claude Meetings	during the call	draft plan, whiteboard, tasks

That last column is the whole bet.

A reddit user on r/artificial made the case better than the marketing did:

"It would be useful to get work done while we discuss what and how to do something. Otherwise we have to work after hours to finish the work because we are sitting in meetings all day long."

That is the real pain. Not note taking. The gap between deciding something and doing it.

But.

The part that made me wince

Claude Sheets is in beta, and the early read is not flattering. Analysts flagged that it has no pivot tables, no macros, no VBA, no Power Query.

It does make tabs, formulas, formatting, and dropdowns. It edits cells alongside you and outlines each change so you can see what it touched. For a hiring budget or a campaign tracker, that is fine.

It is also nowhere near Excel.

And the r/myclaw thread nailed why that matters:

"There's like 30 years of excel having its claws into everything. Probably won't make a dent."

Another commenter went harder. If you cannot guarantee a spreadsheet reports the same number today as it did yesterday, no business signs the purchase order.

That is the wall. Not features. Trust.

i think that comment is right and also misses something. Claude Sheets does not need to replace Excel. It needs to be good enough that the tracker never leaves Claude in the first place.

The awkward social bit

what actually happens when a robot joins your standup?

Claude identifies itself and drops a notice in the meeting chat. That part is handled well. It will not join calls with external guests unless an admin allows it, and it leaves automatically if an outsider joins.

That auto-leave behavior is the detail i did not expect. It tells you Anthropic knows the room gets strange when clients are on the call.

The top comment on r/artificial was pure dread: "You're not getting a co-worker, you're getting replaced."

i don't buy that for meetings. Someone still has to decide what the meeting was about, and Claude cannot want anything.

But i get the feeling. There is something different about an AI that answers in chat versus one that produces a plan.

The first is a tool. The second has opinions in public.

The pile of summaries problem

the first time i used an AI notetaker, i loved it for two weeks. Then i had forty summaries and no system.

That is the failure mode nobody demos. Live drafting makes more artifacts, not fewer.

A plan, a board, a task list, a doc, a slide deck. Every one of them needs a human to read it.

One r/artificial commenter said the value is not another voice in the meeting. It is making sure decisions turn into work.

The reply under it was just "Well. Shit."

my coworker tried the opposite approach. She banned notetakers for a month and asked people to just talk.

Two things happened. The meetings got shorter. And nobody could remember what was agreed by Friday.

That is the actual tradeoff. Capture costs attention. No capture costs memory.

So the honest question is not whether Claude can draft a plan mid-call. It probably can. The question is whether your team reads the plan on Thursday.

i have a theory about calendar blocks. The default is thirty minutes.

Nobody in the history of work has needed exactly thirty minutes for anything. You either need eight or you need ninety.

We keep the thirty because it divides evenly into a grid. That is the entire reason. A software decision made by a calendar widget in the nineties, and we have all been living inside it since.

Which is why i laughed at the pitch. Anthropic is selling real time work inside a meeting that probably should not exist. If the call is thirty minutes of status updates, an AI that drafts the follow-up during it is solving the wrong half.

But if the call is the one where three people finally agree on scope, then having the plan appear while they talk is worth something. That meeting is rare. It is also the one that matters.

Where this is overkill

Most teams should not touch this yet.

Claude Meetings is beta. It is Team and Enterprise only, and it works with Google Meet at launch and nothing else.

If you are on a free plan or a small shop, you are not the customer this week.

And if your meetings are mostly alignment, mood, and unspoken politics, a live document is noise. Some calls exist so people feel heard. Claude cannot help with that and should not try.

The honest limit is smaller than the announcement suggests. This is a tool for teams that already decide things in calls and already write things down. Everyone else gets a nicer pile.

The bit i keep thinking about

The stock drop is the story everyone will write. i keep thinking about the auto-leave.

Someone at Anthropic sat in a room and asked what happens when a client dials in. The answer they shipped was: Claude gets up and leaves.

Quietly. No drama.

That is a small, unglamorous decision. It is also the kind of decision that tells you whether a company has actually used its own product with real humans.

i still don't know if i want a participant in my meetings. But i know i want the people building it to have thought about the awkward exit.

Nod From n8n Labs: Great Demo, 14 Minute Wait on Day One

Dishant Sharma — Wed, 11 Nov 2026 17:56:17 +0000

Emer McArthur posted on the n8n forum on launch day, excited to get Nod set up. Then the Claude Premium plan wouldn't connect, because Nod wanted an API key and credits instead.

So the free Gemini tier got a turn. The first question took 14 minutes to answer.

Fourteen minutes. That is longer than doing the errand yourself.

I read that post three times. Not because it's dramatic. Because it's the exact shape of every agent launch i've watched this year.

The demo is a browser opening tabs at triple speed. Day one is someone staring at a spinner, wondering if they broke the config.

Nod is worth writing about anyway. It shipped on November 10 from n8n Labs, the experimental arm inside n8n.

Apache 2.0 license. Runs on your Mac or Windows PC. It brings its own sandbox and its own Chromium.

You hand it a job. It goes and does the job on real websites.

That's the whole pitch, and it's also where things get messy.

What it actually is

Most AI tools with a browser are a chat window with a plugin bolted on. Nod is not that. The app spins up a Linux sandbox on your machine, runs a Chromium inside it, and lets the agent click around like a person would.

The stack is boring in a good way. One Node process, a few Docker containers, PostgreSQL, and the Pi agent runtime. Everything sits on the box you installed it on.

That matters because of what it lets Nod do. It can log into a supplier portal that has no API. It can read a dashboard with no export button and type the numbers into a spreadsheet.

It can also sit on a checkout page and wait for you to say go.

I've used tools that claim this. Usually they mean "we have a screenshot tool and a lot of confidence."

Nod actually drives the browser. Whether it drives it well depends on which model you point at it.

And the model choice is not a small setting. Point it at a cheap model and watch it fumble a login form for six minutes. Point it at a good one and your token bill shows up before your invoice does.

The 98% problem

The headline number is 98% task completion across 226 errands, run three times each. Zero unsafe actions in 678 runs. Memory recall at 93.2% on LongMemEval.

Those numbers are good. They also come with a footnote the page does include: GPT-6.1 Sol, October 2026, in simulated accounts and websites.

Simulated. That's the word to sit with.

A simulated supplier portal doesn't have a cookie banner covering the submit button. A simulated bank doesn't log you out mid-flow because your session looked weird. A simulated checkout doesn't throw a 3D Secure prompt at you and wait.

I'm not saying the benchmark is fake. I'm saying the gap between 98% in a test setup and 98% on a Tuesday afternoon is where products die.

The other thing to know is who Nod is for. n8n's own framing is sharper than most launch posts:

Tool	What it's for
Chat assistant	Where you think and write
n8n	Shared processes a team runs
Nod	The ongoing jobs that are yours alone

That's a clean split, and it's the reason Nod is a separate app instead of a new tab inside n8n. You don't need an n8n account. If you have one, you can connect it and Nod will build and test workflows there.

It remembers, and you can check

Here's a question people always ask about personal agents. Will it remember that my accountant is Anna and not Bob?

Nod's answer is a visible memory store. Every note shows the message it came from. You can read it, edit it, or delete it.

It also learns your email style from sent mail, with names and numbers stripped out first.

The 93.2% recall number is the one i believe most, because memory is a solved-ish problem next to browser automation. Retrieval is easy. Knowing which fact is still true is hard.

Nod handles that with a tell-it-once rule. Say something changed and it uses the new version from then on.

Small thing. But it's the difference between an assistant and a stranger you re-brief every morning.

The laptop dies, the job dies

Most tutorials tell you to install it on your laptop and forget about it. That works right up until you close the lid.

When the machine sleeps, Nod stops. Scheduled jobs stop with it. The morning brief doesn't arrive because the laptop was in a bag on a train.

n8n knows this. Their blog says some testers keep it on an always-on Mac mini or a server, and a hosted version is on the roadmap.

The comment that stuck with me came from a Redditor who tried the always-on route. Their Mac rebooted for an update, sat at the login screen, and every scheduled job stayed dead for eight days before anyone noticed.

Eight days. No error. No alert. Just silence.

So the honest setup looks like this:

Install on the laptop to try it.
Move it to a box that never sleeps.
Add a check that texts you when a job didn't run.

That's three pieces of infrastructure for a tool that's supposed to remove work from your week.

Local is not offline

"Local" is the word doing the most work in the launch posts. Your files, memory, and saved logins stay on your machine. True.

But local isn't offline. Your chosen model provider gets the conversation, the pages Nod reads, and screenshots. App connections route through a connection service that n8n hosts by default.

Usage analytics are on by default, and the docs are unusually clear that a fresh install can fire an event before you even reach the privacy switch.

I like that the privacy page exists and reads like a person wrote it. It shows you a scrubbed trace where "Jordi" is still sitting there in the text, because name detection by shape doesn't catch every name.

That kind of admission builds trust. Most vendors would have deleted that paragraph.

And the permission check is itself a model. n8n says so plainly. It can make mistakes, which is why anything your words don't cover waits for your yes.

Small tangent. I have a friend who self-hosts everything. His photos, his notes, his calendar, a wiki he keeps for his own recipes.

He once spent a Saturday migrating a to-do app because the maintainer changed the license.

I asked him why. He said he didn't want to wake up one day and find his stuff gone.

I used to think that was paranoid. Now i keep a folder called exports where i dump a copy of everything every few months, and i feel calmer for it.

The catch is that self-hosting is a hobby dressed as a setting. Every service you run is a thing that can break at 2am while you sleep.

He knows this. He has alerts.

Most people don't want alerts. They want the errand done.

And that is the honest pitch for Nod. Not automation. A list on your phone that finally shrinks.

Mine has eleven items on it and the oldest one is from last December.

The real talk

Most people don't need this. If your week has no recurring logins and forms, Nod is an elaborate way to send an email.

If you're not comfortable pasting an API key into a settings screen, wait. Setup is about ten minutes when nothing goes wrong, and day one suggests things go wrong.

If a job has to run at 6am while your laptop is shut, this is not the product yet. Use a hosted agent or a plain n8n workflow on a server.

And if money is tight, watch the meter. n8n admits early testers found tasks cost more than they expected. The $5 check-in exists because someone got surprised.

The software is free. The errands are not.

What i keep coming back to

The 14 minute Gemini reply is the detail i can't shake. Not as a knock on Nod. As a reminder of what day one actually feels like.

You read the launch post. You picture the version where the browser opens, the invoice downloads, the refund lands. Then you spend your first evening debugging model access instead.

That gap closes or it doesn't. n8n is calling this a research preview and telling people to expect rough edges, which is more honest than most launch copy.

I'll keep my install. The list is still there. The oldest item is still from last December.

e-means Is 10x Faster. The Comments Are Better Than the Paper

Dishant Sharma — Wed, 11 Nov 2026 17:48:15 +0000

A first-year PhD student at Meta FAIR shipped a drop-in replacement for k-means into FAISS, then spent two days answering every person who called it overhyped. That is the part of this story i keep coming back to.

The algorithm is called e-means. It hit Hacker News at 495 points and 78 comments. The paper claims it reaches the loss that Lloyd's k-means needs 25 epochs for in 1.4 to 2.6 epochs.

Faster on GPU by 10x to 45x against Flash-KMeans. Faster on CPU by 8x to 15x against the old FAISS implementation. And you tune nothing except k.

I have a clustering job in a side project that takes about forty minutes on a rented GPU. Forty minutes where i stare at a terminal and pretend to do other work. So yes, i clicked.

But the comments were better than the paper. Half the thread was praise. The other half was people who clearly run this stuff in production, poking holes.

And the author was down there in the replies, taking every punch.

That mix is the actual story. Not the speedup. The argument about whether the speedup means anything.

What the update rule actually changes

Every k-means variant stores two numbers per cluster: a sum S and a count N. The centroid is just S / N. All the variants differ in how they change those two numbers.

Lloyd throws them away each pass and rebuilds from the whole dataset. MacQueen's rule from 1967 keeps adding to them forever, so stale points never leave. e-means multiplies the old value by (1 - alpha) and adds the new batch scaled by alpha.

S = (1 - alpha) * S + alpha * s
N = (1 - alpha) * N + alpha * n

That is it. That is the algorithm. An exponential moving average on the statistics instead of a full recompute.

I used to think mini-batch k-means was the fast, sloppy option and full-batch was the careful one. Then i read the local minima section and had to sit with it for a minute.

The sloppiness was the point. Noisy updates wander out of bad starting positions. Lloyd's loss only goes down, so it gets comfortable in whatever ditch it lands in first.

The toy examples in the blog post are brutal about this. Five blobs in a line, k=5. Lloyd leaves a whole blob with no centroid and gives an end blob two.

Across 200 random starts it stayed stuck 46% of the time. e-means, same starts, stuck 0% of the time.

Lloyd doesn't find the optimum. It finds a local minimum and stops.

That one line reframed the whole thing for me. Everything i had read about k-means treated it as a solved problem with a quality ceiling. It has a quality ceiling, and nobody was measuring how low it sits.

The hyperparameter thing is the real flex

Here's a question people always ask about mini-batch methods: how do you pick the batch size?

The honest answer used to be "sweep it and pray." Batch too small and the gradients are noise. Batch too big and you waste a pass. Most teams pick 1024 because a tutorial said 1024.

e-means fits two equations to set batch size and starting step from n, k, and T. The paper reports median regret of 0.07% on datasets held out from the fit, and one left-out problem size predicted at 0.07% and 0.06%. Then alpha decays on a cosine schedule from its starting value down to a tenth of it.

What you tune	Lloyd	Mini-batch (Sculley)	e-means
clusters	`k`	`k`	`k`
batch size	none	yes	law
step size	none	yes	law
epochs	20 to 50	yes	5 default

So the honest pitch is not "faster." It's "same API surface as the thing you already use."

And that is why it landed in faiss.contrib.e_means with a two-line call instead of a research repo with a broken README.

Dead clusters are the boring problem nobody blogs about

The problem isn't what you think. The hard part of large-codebook clustering isn't speed. It's clusters that die.

A centroid drifts away from every point, gets nothing assigned in the next batch, and becomes a permanent zombie. Your codebook says 16,384 entries. Reality says 12,000, and the rest are decorative.

On the DEEP dataset at k=16,384, the paper measured 26.3% dead clusters with revival turned off. Random resampling from the batch, the trick EnCodec uses, got that to 14.3%. Splitting a large cluster in two, borrowed from FAISS itself, got it to 0.3%.

Forty-seven dead clusters instead of 4,313. Same data, same epochs.

That detail matters more to me than the wall-clock numbers. Dead clusters silently wreck the recall of any IVF index built on top of them, and you find out months later when a search returns something obviously wrong.

A short detour about naming

"e-means" is a bad name and i mean that with affection.

It sounds like email. Or e-commerce. Or one of those 1999 startups that raised 40 million to sell pet food online.

The e stands for exponential moving average, which is a fine thing to name a variable after. It is a strange thing to name a decade of work after.

Compare it to the competition. Lloyd's algorithm is named after a person. So is MacQueen's rule, Elkan's algorithm, Hartigan-Wong, Sculley.

Entire careers reduced to a possessive.

Then along comes a letter. It's like naming your kid "Q."

And yet it's growing on me. It's short, it types fast, and it makes the pip install obvious.

Maybe the era of naming algorithms after people is ending. Everything now ships with a landing page and a playground, so the name has to work as a domain.

e-means.github.io is a nicer URL than bessa-2026-emeans.github.io. So the letter wins.

Where this does not help you

Most people don't need this.

If your dataset is under a few hundred thousand points, Lloyd in scikit-learn finishes before you can alt-tab. The speedup is real and it is also irrelevant to you. Don't migrate anything.

If your k is small, like ten or twenty, the mini-batch machinery buys you very little. One commenter in the thread tried e-means for relaxing a mesh on a sphere and found it slower and noisier than Lloyd, because there was no dataset to sample, just geometry.

And if your pipeline is seeded with k-means++ and run five times to pick the best of five, you have a different bottleneck than the one this fixes. One person asked about that in the thread and i don't think got a clean answer.

The other caveat is duller. The authors wrote the baselines, the authors ran the benchmarks, and the authors are FAISS contributors.

That doesn't make the numbers wrong. It makes them unverified by anyone with an incentive to find the flaw.

What i actually took from it

The 45x number will get quoted everywhere and it will be wrong for most readers. That is fine. Numbers always are.

What stuck with me is a 1967 update rule still sitting inside the mini-batch clustering code that half the vector search world depends on. Nobody replaced it for fifty-nine years because it was good enough and because clustering was never the interesting part of the pipeline.

Then someone looked at it properly, wrote down two equations, and made the old thing obsolete in a weekend.

I still have that forty-minute job. I'm going to try the two-line swap and see if it gets shorter. And if it doesn't, i'll know why, which is more than i knew before i read the thread.

Reddit Reviews Landed With 161 Comments and Zero Upvotes

Dishant Sharma — Wed, 11 Nov 2026 05:05:53 +0000

Reddit's announcement post for Reddit Reviews is sitting at zero votes. The comment section under it has 161 replies.

That ratio is the review. Zero up, 161 down.

And it was written by the people who actually run the site's communities.

The feature is simple enough. Reddit used AI to pull product talk from across subreddits and pack it into about 10,000 product pages. Electronics, health and beauty, home and garden, apparel, US only.

You search a product, and you get a "what people are saying" block. Positive, mixed, negative split, plus topic filters.

And every summary links back to the original threads.

Fine idea on paper. Reddit has been the place people go to ask whether an air fryer is worth it for a decade. This just puts a label on it.

Then you read the comments.

The top one, at 114 points, is from a user called judasblue. "Yeah, this definitely isn't going to lead to even more fake account stealth marketing efforts across the site."

The second one is worse.

"Oh those advertising spam accounts are giving you consistent issues? What if instead of dealing with them we intentionally built them features to make THEIR jobs easier?"

That is the mood. Not curiosity. Not "cool, shopping."

Just a long tired sigh from people who spend their evenings deleting bots.

What the page actually shows

i went looking for the beta timeline first, because it explains a lot. Reddit tested this since February with a small group of US users in electronics, video games, and health and beauty.

And in September it added home and garden plus apparel. Now it is open to every US user.

The page has five parts:

a summary of what people are saying
a sentiment split, positive, mixed, negative
themes like durability or ease of use
a filterable list of mentions with links to the source
a list of communities where the talk happened

There is also product info with images, prices, and where to buy links. Reddit says that data comes from brand and retailer catalogs. The early testing ran in places like r/espresso and r/skincareaddiction, where people already argue about grinders and moisturizer for free.

That last part is what nobody in the thread liked. Price and buy links turn a conversation into a store shelf.

The definition problem

brandy_mcstyle from Reddit's product marketing team answered concerns directly in the thread. The defense has two parts.

Reddit excludes comments from accounts labeled as apps. And it defines a "review conversation" as a comment that appears to describe personal experience with a product.

A user named DeltaJesus replied with the obvious thing.

"So exactly what these bots are already doing now?"

He is right. Astroturfing has never looked like a press release.

It looks like a person saying they owned the thing for six months and it changed their life. Filtering for personal experience filters for the exact shape of a paid comment.

Reddit's answer to fake reviews is a detector tuned to copy the fakes.

The opt out question

Four separate mods asked how to turn this off for their subreddits. Beeb294, Sillvaro, SecureThruObscure, and LindyNet all wanted an off switch. None of them got one.

judasblue asked the sharper version. If Reddit is not making money from this feature, why not let non commercial subs opt out? He called the absence of a switch "sus," which is about as polite as that thread gets.

CouncilOfStrongs, a mod of over ten years, put the trust problem in one line. "There has been zero noticeable reduction in spam volume in the over 10 years I have been a moderator on this platform."

And WalkingEars added the detail that stings. Subs without aggressive moderation are now full of "insipid LLM posts that read more like LinkedIn than Reddit."

Why this shipped now

Follow the money, or the missing money. Reddit's shares dropped 29% after investors got spooked about Google's AI Overviews eating referral traffic from search. The company is also moving toward a logged in experience, which keeps people on site instead of letting search engines index everything for free.

Reddit Reviews lands weeks later, right before holiday shopping. That timing is not subtle.

What Reddit says	What it looks like
no paid placement	ten thousand pages with buy links
built with mod feedback	no opt out for mods
organic and community shaped	shipped before the holidays

Reddit also says it earns no commission on those buy links. Maybe true today. A shopping surface with 130 million daily users and live price data does not usually stay commission free for long.

The circular pitch

The line that stuck with me is buried in the announcement. Half of US shoppers say they come to Reddit to validate AI recommendations.

Read that twice. People ask a model for advice, then come to Reddit to check whether the model lied. Reddit's new feature hands them an AI summary of the human answers they came for.

The loop closes on itself. Ask a model, verify with a model that read people, then buy.

i do not think Reddit is evil for this. i think it is a company with a traffic problem building a shopping product, because shopping products make money.

But the packaging is what annoys me. This is not a community tool. It is a storefront wearing a community tool's jacket.

Random break

Somewhere in the middle of all this i remembered my own review habit. i read the two star reviews first, always. Not the one stars, those are people having a bad day with a delivery driver.

The two stars are where the real complaints live. The hinge that loosened after four months. The app that stopped syncing.

And i once spent forty minutes in a rice cooker thread because one commenter had measured the actual temperature variance across three units with a probe. No brand. No affiliate link.

Just a guy with a thermometer and a grudge.

That is the thing Reddit Reviews cannot summarize. The grudge. The guy who measured.

A summary keeps the verdict and throws away the obsession that made it worth reading.

Real talk

If you already search Reddit by adding "reddit" to your Google query, this feature is not for you. You will find the thread anyway, and you will read the messy parts that a summary flattens.

If you are the kind of shopper who reads one product page and calls it research, this will feel like a shortcut. And it mostly is one, for better and worse.

The people who should actually care are the mods. They get the spam risk, the extra moderation load, and no switch to turn any of it off. The feature benefits the shopper who never opens Reddit and costs the volunteer who keeps it usable.

That trade is bad. Not complicated. Just bad.

Ending

The comment i keep coming back to is from TGotAReddit, replying to Reddit's claim that nobody pays for placement. "Well if you don't benefit and the advertisers don't benefit, who does this benefit? Because it's not gonna help mods or users."

Nobody answered that one.

i keep thinking about the zero votes. Reddit built a review machine for ten thousand products and its own users could not bring themselves to click the up arrow on the announcement.

Maybe that is the most honest review on the page.

Muse Ember Is Cheap. The Pelican Test Told Me Something Else.

Dishant Sharma — Tue, 10 Nov 2026 21:12:39 +0000

Simon Willison ran a pelican test on it. That is the first thing I saw about Muse Ember, before I saw a single benchmark number.

He asked the model to draw a pelican riding a bicycle at all six reasoning levels. It returned five pelicans. The high setting did not produce a complete SVG at all.

Then he said something that stuck with me. The pelican test usually tracks reasoning effort. More thinking, better pelican.

This time the correlation broke. minimal came back with about ten reasoning tokens and, by several readers' judgment, the best bird of the set.

Meta Superintelligence Labs shipped its smallest model on November 9. The top comment thread on Hacker News was about whether the pelican had a fish in its basket.

I read 139 comments. Maybe six were about the pricing.

What they actually shipped

Muse Ember is a small multimodal model built for the boring part of agents. Tool calls, routing, extraction, coding subtasks, long document parsing. The stuff an agent does four hundred times while you watch a spinner.

The pricing is the headline, and it is genuinely low:

$0.10 per million input tokens
$0.004 per million cached input tokens
$0.50 per million output tokens

That cache number is the one people keep missing. It is 4% of input. Luna and Haiku charge about 10%.

In agent loops, cached input is most of the bill.

Meta's pitch is simple. A big model plans, this one does the volume. Their line: Muse Wonder plans, Muse Ember handles the volume.

The benchmark story, and the number that does not match

Artificial Analysis puts it at 36 on the Intelligence Index for $0.14 per task. Claude Haiku 5.5 hits the same 36 and costs $0.41. That is nearly three times more for the same score.

Model	Index	Cost per task
Muse Ember max	36	$0.14
Claude Haiku 5.5 max	36	$0.41
GPT-6 Luna max	28	$0.15

And it beats DeepSeek V4.1 Flash on cost, which is the part that made people sit up. DeepSeek was supposed to own cheap.

But here is the thing I could not stop poking at. Meta's own launch page lists AutomationBench-AA at 37.8% for Ember. Artificial Analysis wrote 68.1% for the same benchmark in the same week.

I do not know which test setup produced which number. Neither page explains the gap.

That is not a scandal. Benchmarks get re-run, versions drift, runners differ.

But it does mean you should not quote either figure like it is carved in stone. I have been burned by this exact thing before.

"Smallest" is doing a lot of work

Everyone asked the same question in different words. Small compared to what? How many parameters?

Can I run it?

The answer is no. There are no weights. Muse Ember is API only, muse-ember-1.0, on Meta's Model API and Muse Code.

One commenter put it better than I could: what is the point of bragging that it is small if it always runs on someone else's datacenter?

Fair. Though the "small" claim is not really about your laptop. It is a signal that this competes with Haiku and Luna, not with Wonder.

Meta is telling you where to slot it in your agent stack.

The open weights crowd is still annoyed. Muse Spark Open shipped at 816B parameters, which is not a thing most people can run either. And the open version came with extra safety training that several users described as being lobotomized into announcing it is Muse Spark regardless of the system prompt.

There is a running joke in that thread about whether the open releases are distills wearing a safety hat. Nobody proved it. But nobody disproved it either, and Meta has not published the parameter count for anything closed.

So the pattern is clear. Meta releases the closed good one, then a heavier, more restricted open one later. Ember fits the pattern.

The trick that keeps it honest

Here is the detail I actually respect.

On AA-Omniscience, Ember scores 21.1% accuracy. That is the lowest of its comparison group. Haiku gets 34.7%.

But it declines to answer 64% of the questions. And that keeps its hallucination rate at 17.4%, half of Haiku's.

So the model is not knowledgeable. It just knows when to shut up.

I have wanted this from every model for two years. A model that says "i don't know" instead of confidently inventing a citation is worth more to me than one that scores twelve points higher and makes things up. For an agent doing extraction at volume, a wrong value in a database costs real money.

It is also the least glamorous thing a model can do. Declining to answer looks like weakness on a scoreboard. In production it looks like not paging anyone at 2am.

The catch is obvious. If you need it to know things, this is not your model. It is a doer, not an encyclopedia.

The pelican thing is not a joke

I keep coming back to the birds.

Every model now draws the same pelican. Same red scarf. Same fish in a front basket.

Same three motion lines, same yellow sun, same dashed lane markings. One commenter called them ley lines, the paths a model walks when you leave a prompt vague.

That is not really about Muse Ember. It is about all of them. A short prompt makes the model fill the gaps from training associations, and the associations are now shared across every lab.

Which means the pelican test stopped measuring reasoning a while ago. It measures how much a model is willing to wander. And when a launch thread spends its energy there instead of on the pricing, that tells you something about what people actually do with these things all day.

The honest part

Most people do not need this model. If you are building a chatbot that answers twenty questions an hour, the price difference is noise. Use whatever you already have wired up.

And the benchmaxxed complaint is real. One user who had actually used the Muse line said the models read as frontier on bench cards but feel less useful in real work.

Another said Spark was their daily driver for weeks and got quietly outclassed. These are people with opinions formed by using the thing, not reading about it.

Also, no batch API at launch. One commenter's entire review was three words: "No batch. Pass."

If your workload is bulk and offline, that matters more than any index score.

Where this lands

The pelican with the fish is the one I remember. Not the 36.

Meta built a model that is cheap, quiet when unsure, and good at the repetitive middle of agent work. That is a real product decision, and a smarter one than chasing the top of the leaderboard.

But the launch told me something else too. We have gotten so used to benchmark charts that a genuinely low price barely registers, while a bird on a bicycle gets 300 upvotes.

Next time i run an agent loop that burns forty thousand tokens on nothing, i will think about that pelican. And i will check the cache price before i check the index.

Claude Fable 5.2: Faster, Cheaper, and Still Hard to Justify

Dishant Sharma — Tue, 10 Nov 2026 05:14:25 +0000

Someone posted a screenshot of Anthropic's own benchmark chart on r/ClaudeAI and asked the only question that mattered.

"So you move from Fable Xhigh to Max, and it thinks longer, costs more, and performs worse?"

That comment pulled 328 points. It sat at the top of a launch thread with 395 replies, and it set the tone for the whole day.

The chart was real. On FrontierCode 2.0, Claude Fable 5.2 at Xhigh effort scores 49.1%.

Crank the dial to Max and the score drops. You pay more and get less.

i read that around midnight and laughed. Then i read Anthropic's own announcement and laughed differently.

The post says, in plain text, that for most coding and knowledge work you should start with Claude Opus 5.5, their "strongest daily driver," and move up to Fable only when a task demands it. So the flagship shipped with a manual that says don't use this.

Fable 5.2 and Mythos 5.2 landed on November 9. The IPO roadshow starts the next day.

The company is reportedly chasing a $1.5 trillion valuation and investors are already calling that number overpriced. This is not a research paper. It is a pitch deck with a token price attached.

And the pitch is odd. Faster, cheaper, and harder to justify than the model it replaces.

The price cut that isn't a price cut

The headline number is $8 per million input tokens and $40 per million output. Down from $10 and $50. That reads like a 20% discount.

Then you look at tokens per task.

One commenter on Hacker News did the math against Artificial Analysis data. Output tokens per task went from 118,000 on Fable 5.1 to 274,000 on 5.2. The reasoning portion alone nearly tripled, from 71k to 192k.

So the per-token price fell 20% and the per-task cost roughly doubled.

That gap is the whole story of this launch, and almost nobody caught it on day one. The top thread on r/ClaudeAI was literally titled "WTF Fable 5.2 Cost per task is Insane." It hit 369 points.

Then something funny happened. The subreddit's mod bot posted a sticky summary correcting the thread. The consensus, per the bot, was that people were benchmarking wrong. Comparing models only at Max effort is "a classic rookie mistake."

The effort dial is the product

Here is the advice buried in that sticky:

Setup	Score	Cost per task
Fable 5.2 High	62	$9.08
Opus 5.5 Max	59	$10.04

Fable at High is cheaper and smarter than Opus at Max. Same data, opposite conclusion, one notch down the dial.

The default in Claude apps and Claude Code is Medium. Anthropic says Medium on 5.2 handles hard tasks with fewer tokens than 5.1 did. One early tester stayed on Medium all evening and never felt the need to move up.

max is the philosophical crisis setting, not the get work done setting.

So the model is fine. The interface is the problem.

You ship a five-position effort slider, you print benchmark numbers at the top position, and you let people assume more means better. Then a bot has to explain your own product back to your users. One commenter, sitting on 206 points, asked for a permanent sticky about it.

What it actually does that 5.1 couldn't

Strip out the pricing fight and there are real numbers.

RoboDojo Sim: 64.9%, up from 27.6% on Fable 5.1
Terminal-Bench-Science: 74.6% vs 52.6%
Remote Labor Index: 41.3% vs 17.9%
OSWorld 2.1: 89.3% vs 83.5%

The robotics jump is the one that stopped me. More than doubling on a simulation benchmark is not a rounding error.

And the demo stories are absurd in a good way. Fable 5.2 solved two open problems in black hole physics. It formalized a proof of Fermat's Last Theorem in 30 hours.

One engineer pointed it at an empty folder and it coordinated over 1,000 subagents for eight days. The output boots on a laptop with drivers, a login screen, and an installer.

A commenter called postalcoder said something i keep coming back to. Fable's ability to render images in JavaScript made him question whether dedicated image models are worth it anymore. That is a strange sentence to read about a coding model.

The half of the launch nobody covered

Fable and Mythos are the same model. Fable has cyber and biology safeguards bolted on and goes to everyone. Mythos is the same weights with the guardrails loosened, and you need verification through Anthropic's Cyber or Life Sciences program to touch it.

That second half is arguably the more interesting release.

Mythos 5.2 found 10.2% more vulnerabilities than Opus 5.5 on Anthropic's internal CVE benchmark. A security company reported that one in six confirmed bugs it found were missed by every other frontier model they tested. Mozilla said it roughly doubled their vulnerability discovery numbers versus Mythos 5.1.

Most of us will never see that model. Fable's safeguards block most security work outright. So the best capability in the launch is locked behind a verification form.

What the room actually said

The mod bot's summary of the main thread used the word "whelmed." Not underwhelmed. Whelmed.

The top replies were variations on one idea: i cannot tell this apart from Opus 5.5 on normal work. A few people went further. One thread declared the model "LOBOTOMISED and unusable." Another called it a major downgrade for 3D work, which sits awkwardly next to Unity's public quote about how good it is at building 3D scenes from scratch.

And there is the reset situation. Paid plans got one, two, or three usage resets this week depending on how long you have been subscribed.

But the reset only refills the Fable meter. If your weekly limit is already gone from Opus, the gift does nothing. A thread titled "The most useless reset?" hit 239 points.

The API string is claude-fable-5-2, if you want to try it yourself.

The naming is what gets me.

Anthropic used to name models after poetic forms. Opus, Sonnet, Haiku. Three sizes, one metaphor, clean.

Now we have Fable and Mythos. Story forms.

And i keep wondering who signed off on that. A fable is a short moral tale, usually with an animal that learns something. A myth is a sacred story about how the world came to be.

Those are not the same thing, and they are not a size tier. They are a mood. Someone in a room decided the flagship should sound like it belongs on a shelf next to Aesop, and the gated security model should sound like it invented the universe.

i do not have a point here. It just seems like a lot of confidence for a product line that shipped two versions in one year and told everyone to keep using the old one.

Who should actually skip this

If you write for a living, do not buy Fable for that. The gains are in long agentic work, big codebases, science, and vision. Prose is not where the benchmark spread lives.

If you are on a Pro plan and mostly use Sonnet, you have a week of access and nothing urgent to spend it on. Rerun one task that 5.1 got wrong and compare. That is the honest test, and it costs an afternoon.

And if you are running under a few thousand requests a day, the per-task cost conversation does not apply to you. Use Opus 5.5 at Medium and stop reading benchmark charts.

The one group that should care is anyone doing security work inside a verified org. Mythos 5.2 is the real product here. The rest of us got the consumer edition of a launch built for enterprise buyers and IPO investors.

The part that stays with me

That $1.5 trillion number is the thing i keep chewing on.

A company worth that much shipped its best model, and its own blog post recommended the cheaper one for daily work. The top comment on the launch thread was a person asking what the model is even for. The second was a complaint about cost.

That is not a failure. It might be the most honest launch Anthropic has done. They built something that only pays off if you hand it a genuinely hard problem, then said so out loud instead of hiding it.

i still have not found a task worth spending a Fable reset on. Ask me again on Thursday.

Expo's Exact Wants Agents to Write Your App. I Have Doubts

Dishant Sharma — Tue, 10 Nov 2026 04:59:29 +0000

Expo put Exact on GitHub and eight days later it had 1,178 stars. One of the first comments on Hacker News, from a user called prmph, was two words: "Is this satire?"

I understand the question. Exact is a cross-platform app runtime written in Rust. You describe the interface in a small declarative language called Contract.

The data logic goes in TypeScript or Rust. It runs natively on the web, macOS, iOS, and Linux.

And the whole thing is built on the assumption that an AI agent will write most of the code.

That is what made the thread strange. People were not arguing about frame times. They were arguing about whether a framework designed for agents is a framework for humans at all.

What Contract actually is

Most tutorials tell you a DSL saves you boilerplate. Contract goes further. It removes the ability to write arbitrary code in the view at all.

No JavaScript in the markup. No I/O. Expressions have no side effects.

Effects only happen inside actions, as assignments, sends, or commands like focus(…).

The todo app in the README fits on one screen. Shapes, components, state, derive, resource, mutation, action, view. A bare node behaves like a bare div: display: block, box-sizing: content-box, flex-direction: row.

The compiler refuses CSS aliases and hands you the web's spelling instead. font-size, not size. background-color, not the background shorthand.

That last detail tells you a lot about who they are writing for. They are optimizing for a reader that will not remember the alias.

Now the honest part. A commenter called btown, who clearly reads compiler internals for fun, said his reaction to any DSL that has to carry "arbitrarily complex mathematical expressions" is "why???" He poked at the syntax crate and did not think it would scale to what real UIs demand.

That is the sharpest criticism in the thread. Nobody answered it well.

The speed claim

Here is a question people always ask about anything Rust-shaped. Is it actually faster, or does it just feel faster because it is new?

The README has numbers. Cold start to interactive first frame: 100 ms p50. Edit to present: 100 ms p50.

On the RealWorld Conduit benchmark, Exact's runtime was up about 300 ms before the React SSR build had hydrated. It used 26 KB of code against React's 81 KB.

Against Electron the gap is not subtle. Electron ships a browser. Exact on macOS draws with AppKit and a Rust layout kernel, and the app's JavaScript loads after the first pixel.

But the fair comparison is React Native, not Electron. React Native does not ship a browser either. Its real cost is the bridge and the reconciliation work, not download size.

	Exact	React Native	Electron
UI rendering	Compiled plan, native views	JS tree reconciled to native	Chromium
Web runtime	~20 KB	n/a	Chromium
First pixel	Baked data, no JS	JS boot	JS boot

I could not find a single head to head benchmark against React Native. I looked. The speed story right now is architectural and self-reported.

The clock belongs to the agent

Here is the design decision i did not expect to like.

Exact exposes ten operations to an agent, the same on every host: tree, screenshot, tap, type, state, layout, logs, clock, prefer, perf.

The README explains the count: "There are ten on purpose: an agent API grows one reasonable addition at a time until no one can hold it in mind."

That sentence is the best writing in the whole repo.

And then the clock. Between two operations nothing moves.

Instead of sleeping until an animation finishes, the agent says clock +60000 or clock settle and reads the result. No timing flakes. No waits.

A test that needs a sleep is a test that will fail on someone else's laptop.

The evidence is thin but real. The README says a fresh agent built a todo app in about 57 minutes on a clean clone, and its tests passed on web, macOS, and the iOS Simulator. About 25 of those minutes were first builds.

Jayesh, writing on Medium, built a calculator with Cursor in 15 minutes, spent 2 minutes on tests, then got 10 seconds per UI change on a simulator. His first hour went to installing Rust, Bun, and an iOS simulator target. The app work was the short part.

What breaks

The first hour is setup. Rust, Bun 1.4.2 pinned exactly, Chrome, Xcode, Hermes. A first native build takes ten to fifteen minutes.

The open issues on the repo are more useful than the screenshots. Setup leaves Chrome marked MISSING on a Mac that has Chrome installed. A worktree in a folder with a different name fails native builds. Android compiles and runs, but "delivery and store packaging don't exist yet."

And this, stated plainly in the README:

Exact is pre-1.0 and changes daily. There is no API stability, no backwards compatibility, and no migration guide, by design.

"By design" is doing a lot of work in that sentence.

I keep a note file called frameworks i will not learn. QML is on it. Every year someone tells me QML is actually good, and every year i open a file, see the property bindings, and close it.

So when a commenter compared Contract to QML and said Qt "proven this approach works," my instinct was to disagree on principle.

Then i read the todo app again. Contract is much smaller than QML.

No property binding graph to reason about, no signal and slot machinery to learn. Just shapes, actions, and a view tree.

I still have not installed it. But i moved the note file.

The real talk

If you ship to the App Store next quarter, do not use this. No migration guide is a real cost, and you will pay it.

If you are a React Native shop with a working app, this is a research toy. It is not a migration path.

And if you think the "agent native" label is nonsense, you are not wrong to be suspicious. One commenter said the trend makes him "sympathize with the Butlerian jihad," which is the funniest sentence written about this release.

But agent native does not mean you cannot write it by hand. It means the docs, the compiler errors, and the test setup are built for a reader that never gets tired.

Whether that is good depends on who you think writes your code in two years. I genuinely do not know. I have been wrong about this twice already.

The part i keep thinking about

The 57 minute number is not what stuck with me. It is that a machine built the same app three times, checked it three times, and nobody had to sit and watch.

My first cross-platform app took a month and it still looked wrong on Android.

I do not know if Exact wins. The math expression criticism might sink it. And a framework that changes daily is not a framework you build a business on yet.

But someone finally built the boring part. The part where the tool can see its own work. That part is not going away.

Discord Swapped Electron for Rust. The 290MB Claim Needs a Caveat

Dishant Sharma — Mon, 09 Nov 2026 05:58:14 +0000

Stanislav Vishnevskiy posted a 15 second clip of two ThinkPads side by side, and the left side is the part that got me.

That's the Discord you and i have installed right now. Black window for about three seconds. Then a loading tip: "In the ancient days, Discord started as a browser-only app."

The joke writes itself. The app is still shipping a browser engine while telling you about its browser-only past.

The right side is the new client, codenamed Phoenix. It gets double clicked a second and a half later. Window fades in within a second.

By the time the Electron app finally shows its interface, the Rust client already has the friends list loaded.

The old app still says "There are no friends online at this time" while the new one is done.

The clip hit 2.3 million views. People asked if it was a tray launch.

Coral, who leads audio and video at Discord, said both were cold starts. Travis, who filmed it, pointed out that a tray launch would mean the friends list was already loaded.

Then came the number. 290.2MB of RAM. With two accounts signed in at once.

A Discord employee said in December 2025 that normal usage sits under 1GB, and the company tested auto restarting the app at 4GB. So 290MB is roughly 70% below the normal mark.

One reply called 290MB "still vile" for a chat app. Vishnevskiy answered: "Those 4k avatar decorations gotta render somewhere ;) but joking aside this client is actually running 2 accounts concurrently."

That reply is where i stopped scrolling and started taking notes.

What GPUI actually is

Most people guessed Tauri. Tauri uses Rust for app logic but builds the interface in HTML and CSS inside the system webview. Discord didn't do that.

They went with GPUI, the framework from the Zed editor team. It draws the interface on the GPU with no HTML at all. Rust handles memory without a garbage collector.

Tech	What it is	Role
Rust	Systems language	New client and shared code
GPUI	Rust UI framework from Zed	Draws the desktop app
Electron	Chromium plus Node	Current app, being removed
Tauri	Rust plus system webview	Not used

So the chat app stopped being a website wearing a coat.

The mobile apps drop React Native and share the same Rust core. The browser version keeps rendering HTML but moves its logic to WebAssembly. Web tech stays for the things that need it, like YouTube embeds and Activities.

The 290MB number is a screenshot

Here's what the headlines skip. That number came from Task Manager on a ThinkPad, not a benchmark. Discord hasn't published a like for like test of both clients.

And the 4GB figure was a restart threshold Discord set for itself, not typical usage. Normal was under 1GB. So "4GB to 290MB" compares a ceiling to an idle snapshot.

That's not a knock on the client. The thing genuinely looks fast in the clip. But the math in the headline is doing a lot of work.

i had Discord open the entire time i was reading about this. Activity Monitor said 1.4GB. i closed it and opened it again out of spite.

A cold start comparison is real evidence. A single Task Manager screenshot is a claim.

The real reason this is happening

i used to think the case for Electron was settled. One codebase, every platform, ship it. The cost of writing native UI three times was the whole argument.

A commenter on r/rust named its_lukebond put the shift better than any article did. GPUI maturing, plus AI writing most of the platform glue, is making that cost argument fall apart.

That's the story people are missing. Not the RAM. The price of not using Electron went down.

Which is also why this is bigger than Discord. If a company with a decade of React investment can walk away, the next one has less excuse.

The accessibility question

here's a question people always ask when a web stack gets dropped. What happens to screen readers?

On Hacker News, a legally blind user said per app UI zoom in the web stack made their life easier. Someone else pointed out that Windows apps had accessibility before computers had 25MB of RAM total.

Both true. Which is the annoying part.

But a developer who built on GPUI, zac_attack_ on Reddit, said the crate's README still had a broken 404 link for "Accessibility." He also hit rendering bugs and rough edges.

The framework's own docs couldn't find the accessibility page.

Discord's VP of Engineering says accessibility and security matter as much as performance. i want that to be true. i also want to see the commit history.

Where this gets messy

the first time i tried this kind of thing, it was a small tool, not a chat app with millions of people. Immediate mode UI gets harder as the tree grows.

A commenter, Grollicus2, worried about exactly that. Thousands of chat messages in one component tree, all needing diffing on every change.

That's the risk specific to Discord. Zed mostly renders editor panes. Discord renders a firehose.

And modded clients probably die. Disconsented pointed out that client mods like BetterDiscord and Vencord depend on the Electron shell.

Blocking already misbehaves with ghost notifications. A rewrite is a clean place to close that door.

A short detour about codenames

The build is called Phoenix. Which is a strange choice for a company that already rose from a browser.

Every big rewrite gets a codename like this. Phoenix, Nova, Atlas, something with a bird or a star. Nobody ships a rewrite called "Project Dave."

i once worked somewhere that named a migration after a Greek god. The migration failed twice and the name stopped being funny. Nobody says "Zeus is down" without sounding like they've lost it.

Phoenix is at least honest. It implies the old thing has to burn first.

Who should not care about this

If Discord runs fine on your machine, none of this changes your week. You will get the update eventually and it will feel slightly snappier. That's it.

The 290MB number also won't hold. As accessibility, features, and years of patches land, that figure creeps up.

Chrome used about 25MB per tab in 2010. It's often 500MB now. Every app gets heavier once real users show up.

And if you run a modded client, this is bad news dressed as good news. Performance you didn't ask for, at the cost of the thing you actually use.

Discord hasn't shipped a public date. Private testing starts soon, and the company says it's taking its time on stability and security. Believe that when the build is in your hands.

What i keep coming back to

The part that stuck with me wasn't the RAM. It was Vishnevskiy thanking Travis for "finding these janky old laptops."

ThinkPads with a Copilot key. Machines from 2024. He called them janky.

That's a person who has been staring at this problem for years, finally watching the old thing lose to the new thing on hardware he clearly doesn't respect. There's something honest in that.

i still have the Electron app installed. i'll probably keep it until the day it updates itself into something faster. And i'll open Task Manager that day, out of habit, and judge the number.

OpenCode Browse Hands Your Agent the Logged-In Browser

Dishant Sharma — Sun, 08 Nov 2026 05:19:19 +0000

The top reply under opencode's launch post for Browse reads: "it's basically just giving a toddler access to my banking app."

The post itself pulled 4.9K likes in a day. So a few thousand developers looked at a browser agent and immediately pictured their savings account draining.

That reply is the whole story in one line. opencode shipped something well built, and the first reaction was fear.

Browse is an MCP server plus a Chromium extension. Your agent gets Playwright control over the browser you are actually signed into.

Your tabs. Your cookies. Your 1Password icon sitting in the corner.

No fresh headless Chrome, no logging into Gmail again, no replaying auth flows.

i installed it expecting a toy. Then i read the security page and realized they had thought about the toddler problem harder than the people joking about it.

And that gap, between the joke and the engineering, is the most interesting thing about this release.

What actually runs when you type a prompt

Three pieces. The MCP server, talking over stdio.

A relay listening on 127.0.0.1:19988. The extension, connected to that relay over a WebSocket, driving your tabs through chrome.debugger.

The agent never talks to Chrome directly. It talks to a local server that pretends to be a Chrome DevTools endpoint.

That indirection is the whole design. The relay holds named sessions, recordings, network capture and a journal. The extension only has to execute commands, not reason about them.

Most tutorials tell you the hard part is the model. It isn't. The hard part is state.

An agent that clicks something and then reasons from a screenshot taken two seconds earlier is guessing. The relay keeps the page and the agent in sync, which is why execute can run real Playwright code instead of forty separate tool calls.

i used to think the tool count was a detail. Then i watched a different MCP server dump a whole accessibility tree into context for every single click.

Your tabs, and the 10 minute rule

Agents open their own tabs in the background of the window you last used. Grouped together, collapsed unless you are looking at one.

They cannot steal focus. They cannot raise a window over your work, because page.bringToFront() is refused at the protocol level.

Tabs nobody touches for 10 minutes close themselves. Never while a script is running on them.

Then there's the handoff. When the agent hits a login, a 2FA prompt or a payment page, it hands the tab back with a small card showing the site's origin.

You do the human part, click Continue, and it picks up again.

Here's the detail i didn't expect: only a real click on that card or the toolbar button finishes a handoff. A page cannot fake it.

There's also a flight recorder. It keeps the last minute of video and saves it when something breaks.

i have debugged enough flaky UI automation to know that feature came from someone's actual bad afternoon.

Where it sits next to Claude and Codex

	OpenCode Browse	Claude in Chrome	Codex for Chrome
Works with	any MCP client	Claude plans	OpenAI stack
Model	whatever you point it at	Anthropic	OpenAI
Source	open	closed	closed

Claude's version is the polished one. Site level permissions, confirmation prompts, tight hooks into Claude Code.

Codex's version leans on the ChatGPT desktop app, uses your signed-in sessions, and covers Chrome, Edge, Brave, Opera and Vivaldi.

Both are tied to a vendor. Browse isn't, and that's the pitch.

But that freedom has a price. You can point it at a local model, and nothing leaves your machine except what your agent sends to its provider. You also own the setup, the updates and the bad afternoons.

The r/codex answer to "which is better for browser use" was blunt: "Codex is far faaaar better :) nothing beats codex in computer use."

Fair enough. Different tool, different job. Browse is for the person who already has an opencode setup and wants it to stop fighting a login wall.

The page that earns respect, then hands it back

Pairing uses ECDH. Each browser gets its own key. Both sides prove they hold it, over fresh nonces, on every connection.

The pairing code is XXXX-XXXX, works once, expires in ten minutes. Five wrong codes in a row void every pending one.

Domain allowlists resolve names first, then check the document's real remote IP, which covers DNS rebinding. Site secrets get typed into a field only after the frame URL is checked against the secret's origin.

The value never enters the execute realm. It doesn't land in logs, journals or HARs.

Real crypto. Real care. And then, a few paragraphs in:

It shares the relay's process, so it is not a security boundary: treat code an agent runs as code running as you.

i read that twice. They built the wall and then told you it's made of paper.

The part that's a race, not a fix

execute runs on Patchright, which hides navigator.webdriver and the Runtime.enable leak. Input moves on curved mouse paths with paced typing.

The extension adds nothing to the page except the handoff card and an optional ghost cursor, both inside a closed shadow root.

Then the docs say the quiet part out loud. This makes an agent hard to spot, not impossible.

The browser still shows its "started debugging" bar while the debugger is attached. Focus emulation keeps background agent tabs looking visible. And fillInput falls back to synthetic events, which it warns you about.

i appreciate that honesty more than i appreciate the feature. Every anti-bot claim in this space is a snapshot, and they wrote it like one.

They also refuse to solve captchas. After a navigation, execute reports Cloudflare, Akamai, DataDome, PerimeterX, Imperva and AWS WAF walls, waits up to 15 seconds for the ones that clear themselves, then tells the agent to hand it to you.

Somewhere in the middle of reading all this, i looked at my own tab strip. Forty one tabs. Three of them are the same docs page opened at different times because i forgot i already had it.

The 10 minute idle close is the first feature in years that would actually fix that for me. Not a tab manager, not a snooze extension. Just an agent that opens a tab, uses it, and quietly lets it die.

i have installed four tab managers. None of them survived a week.

The real talk

If your daily browser has your bank, your work SSO and your personal email in it, don't run this there. Not because the code is bad. Because that's one session with an LLM holding the steering wheel.

Make a separate profile. Turn on an allowlist. Read the section on OPENCODE_BROWSER_ALLOW_NODE before you flip anything, because that flag hands execute full Node access.

And be honest about the use case. If your agent just needs to read a page, a fetch tool does that for free and cannot click "Confirm transfer."

Most people don't need this. The ones who do will know within an hour.

Closing

The toddler joke is right, but not for the reason people mean it. Toddlers are not malicious. They are just extremely literal and very fast.

That's a decent description of an agent with chrome.debugger access to your logged-in life.

The fix was never a smarter toddler. It was a playpen, a badge that says RUN, and a button that always takes the tab back.

They shipped all three. Then they told you the playpen has a gap in it.

i respect that more than a marketing page claiming otherwise.