DEV Community: Dishant Sharma

DeepSeek V4.1 Flash 1017: The Hype vs What Shipped Friday

Dishant Sharma — Sat, 17 Oct 2026 17:20:31 +0000

The most upvoted comment on the Hacker News thread wasn't about a benchmark. It was about a sentence on the model card.

"DeepSeek-V4.1-Flash-1017 is a minor update to DeepSeek-V4.1-Flash, delivering substantial improvements across reasoning, coding, agentic tasks, and visual benchmarks."

One user called it hilarious. Someone replied that it shows the team is more engineers than marketers. And they're right. A patch-level version number, a Friday drop with no event, no livestream, no demo reel. Meanwhile Terminal-Bench 4.0 went from 31.2 to 42.3.

I read that and sat there for a minute. Because that's not how anyone else ships a model anymore.

No countdown. No keynote. No carefully seeded leaks.

Just a checkpoint, a table, and a Friday.

What 1017 actually is

Here's the boring truth first. 1017 is a post-training checkpoint, not a new architecture. The base is still V4.1-Flash from September: 552B backbone parameters, 196B Engram parameters, a sparse MoE that activates 8B parameters on input and 16B on output.

The version number matches the date. October 17. That's it.

What changed is the RL pass. DeepSeek says it used reinforcement learning with self-feedback to push end-to-end project work. Game creation, 3D modeling, long agent runs. Same weights structure, better behavior.

Same model. Same price. Much better scores.

And the price stayed flat. deepseek-flash still serves it at $0.15 per million cache-miss input tokens off-peak, $0.60 per million output. Peak doubles that. The legacy names deepseek-v4-flash and deepseek-v4-flash-vision-exp quietly point at 1017 too.

The benchmark table, and why it annoyed me

Benchmark	1017	V4.1-Flash
Terminal-Bench 4.0	42.3	31.2
DeepSWE v1.1	77.0	74.2
ProgramBench	29.1	20.3
HLE (no tools)	42.6	36.8

Every row moves. Terminal-Bench gained 11.1 points in five weeks.

Here's what annoyed me. On DeepSWE, 1017 scores 77.0 and Claude Opus 5 scores 74.0. That number floated around Twitter all day. But on HLE without tools, Opus 5 hits 56.3 and DeepSeek gets 42.6.

So the model wins on agentic coding and loses badly on hard reasoning. Both facts live in the same table.

That's not a scandal. It's just what a cheap fast model should look like. But the people reposting the 77.0 left out the 42.6.

The cache thing nobody talks about

What actually happens under the hood is more interesting than the scores.

V4.1-Flash uses a Causal Encoder-Decoder setup. The decoder's global KV cache gets projected from the encoder's final hidden states. Add Compressed Sparse Attention 2 and an FP4 main KV cache and you land at 890 bytes per token.

For context: that's roughly a quarter of the previous Flash generation's cache. Persistent KV shrinks to about an eighth.

Why care? Because agent harnesses re-send huge prompts constantly. Codebases, tool outputs, chat history. OpenRouter shows DeepSeek's own endpoints running a 95.2% cache hit rate. That's where the real bill lives.

A price sheet looks cheap per million tokens. The invoice is really about how many of those tokens you pay full price for.

Most of them, for most people, are cached.

The first time i tried to reason about this, i got it backwards. I assumed smaller cache means you lose context. It doesn't. You keep the same 1M window and just pay way less to hold it there.

The hype, honestly

The reaction split cleanly.

On Hacker News, one person wrote that it passed their threshold for caring about new models back with DS4. Another said announcements in the series feel like obsessing over patch releases of software that already solved the problem.

On the other side, someone said they get far more done with $20 of DeepSeek API spend than with a $20 ChatGPT Plus plan. Another called it their favorite model.

Then there was the theory about why Chinese labs never bump major versions. One commenter claimed certification rules push companies toward calling things minor updates. Someone asked for a source. The answer was a paywalled podcast. Take that one with a grain of salt.

The disagreement isn't about the model. It's about what people expect a release to feel like.

Open source, sort of

The weights are on Hugging Face under MIT. That sounds like the headline until you read the size.

763B parameters. FP8 tensor types. Thirteen quantizations already, two finetunes. Someone in the threads did the math: at 2-bit you land around 175GB, which leaves room for KV cache on a 256GB machine.

So yes, you can technically run it. No, almost nobody will.

The people who do will spend a weekend on it and post a screenshot of 4 tokens per second. I respect that, but it is not a workflow.

The people who actually benefit are the ones hitting deepseek-flash through an API and not thinking about it.

Why the search API matters more

Buried under the benchmark table is the thing i keep coming back to.

DeepSeek opened their in-house Search and Fetch APIs to everyone. $0.75 per 1,000 successful calls. Empty results are free.

And if you call it through DeepSeek Harness, Claude Code, or Codex, the server-side tool calls are free until November 1.

A cheap coding model plus a first-party web layer under one key.

That's a different kind of move. Search at $0.75 per thousand is not the most interesting price in isolation. But it means an agent can loop over web results without you wiring up a second vendor and a second bill.

The random part

I spent twenty minutes of research time on the wrong thing entirely.

While digging for reactions, i went down a thread where a developer had a USB-C port that wouldn't charge. They used a smarter model to reverse engineer the controller firmware, built an emulator, and found a debugging buffer. On a laptop. For fun.

The whole time i was reading it, my own laptop was on a cable that only works if you insert it the right way up.

A USB-C cable. Cursed physics. At least both ends look identical, so i have that going for me.

I closed the tab and sat with that for a bit. The tooling matters less than the person who keeps pulling on the thread.

The real talk

Most people don't need 1017.

If you're writing a cron script or summarizing emails, the model you used last month is fine. The jump from 31 to 42 on a terminal benchmark does not change your week.

The model is also not a reasoning champion. Opus 5 still beats it on HLE, on ProgramBench, on NL2Repo. If your work is one hard ambiguous problem, pay for the smart one.

And if you're on a machine that just barely fits a 200B model, stop reading. This is not your release. The local story is still rough, and nobody should pretend otherwise.

The thing that stuck

DeepSeek shipped this on a Friday, with a model card that called its own big improvement "minor," and no launch event at all.

The score chart is real. The cache math is real. So is the gap on pure reasoning.

I kept wondering what a launch would look like if they actually tried. Maybe that's the point. Once the model is good enough and cheap enough, the theater starts to feel like overhead.

I still think the word "minor" is doing a lot of work there. But i'll take an honest table over a staged one.

Anthropic Replaced Git With Scion. Here's What Actually Happened

Dishant Sharma — Wed, 14 Oct 2026 16:01:17 +0000

Anthropic merged over 30,000 code changes a day in September. Five months earlier, that number was around 2,500. And somewhere in between, git stopped being able to keep up.

That is not a benchmark. It is a company admitting its own tooling broke. The same Claude that wrote the code also broke the thing that stores it.

I keep coming back to one line from Anthropic's engineering post: "the latent demand for merging code is practically infinite." That sentence is either the most exciting or the most terrifying thing I have read this year, and I genuinely cannot decide which.

Here is what happened. Anthropic's monorepo hit a wall. The main branch history is nearly 100 GB. A compressed working copy is over 25 GB. They run about 25 million code checkouts a day for CI alone, before you count agent sandboxes and developer machines. Fetched normally, that is over 600 PB of git traffic per day.

So they built Scion. An in-house version control system. Seven engineers. Five months. Migrated the whole monorepo off git.

What Scion actually is

Strip the framing away and Scion is a centralized system wearing a distributed system's clothes. It looks a lot like Subversion with better marketing, and I mean that as a description, not an insult.

The core idea is simple. Git assumes clients are offline and self-contained. Every clone is a full repo. Every dev can diff, blame, and check out without a network.

nearly all of Anthropic's clients are agents, and agents are always online.

So they threw out the assumption. In Scion, the server does the real work. It creates commits, computes diffs, finds merge bases, runs blame. The client just lays files on disk and asks for what it needs.

The unit of work is a "changeset," not a commit. A changeset only records what changed relative to its parent, plus pointers to compressed file contents in blob storage. No packfiles. No pushing. Every commit and rebase happens server side.

Here is the part I did not expect: the working copy is optional.

A CI job that only needs a diff never has to check out the repo. It asks the server for the diff and moves on. When files on disk are unavoidable, the client does sparse or virtualized checkouts, paying only for what it actually reads.

That is a real design decision, not a slogan. It is also the entire reason their checkout count is survivable.

The numbers

Metric	Before	After
Daily merges	~2,500 (May)	30,000+ (Sept)
Infra footprint	several hundred mirrors	200x smaller
CI checkouts	minutes	seconds

The 200x is the number everybody quotes. I care less about that and more about what it says about their old setup. They were running several hundred git mirrors just to survive. That is not a system. That is triage.

And the fixes did not scale either. Seeds drifted behind main between refreshes. Shallow clones and promisor remotes made history-dependent work, like diff and blame, fragile. Every workaround created a new thing to babysit.

Scion's answer: no fully materialized copy of the repo exists anywhere. Not even on the server. Data is distributed, content-addressed, and cached freely because a stored object never changes.

That last detail matters more than it looks. It is why the whole thing scales horizontally without everyone coordinating all the time.

The most honest paragraph Anthropic wrote

Buried in the reporting, not the headline: Anthropic's own engineers admit Claude writes better code than they do.

Then comes the actual job. From their post: "Very often, we found that the role of the engineers was to tell Claude 'no.'"

That is the whole shift in one sentence. The humans are not writing the code. They are the constraint layer. The seatbelt.

Agents will sometimes violate core system constraints to satisfy a pattern that should never have been allowed in the first place.

I have run into a smaller version of this. The agent does exactly what you asked, in a way you would never have permitted if you had thought to say no in advance. It is fast and it is confident and that is precisely the problem.

Being the person who says no is not a demotion. It might be the most important job in the building.

A tangent about naming things

While reading all this I got stuck on the names. Scion. Antique. Two tools, same launch, and neither name tells you anything about what it does.

A scion is a descendant, an heir, the young shoot grafted onto an older plant. Cute if you already know it replaces git. Useless if you do not.

Antique is worse. It is the code review surface. You named the thing humans stare at all day after the word for "old."

I have shipped bad names. Everyone has. But naming an internal dev tool is one of the few places you get to just say what the thing is and move on. Scion could have been called Monorepo VCS and nobody would have blinked.

This is not a real problem. It just lives in my head rent free now.

Real talk

Most of you do not need this. I mean that.

If your team merges a few hundred changes a day, git is fine. Great, even. Git is not broken. Git is optimized for a world where humans write code slowly and work offline, and for almost everyone that world is still here.

Scion exists because Anthropic hit a load roughly nobody else has hit yet. They said so themselves. This is not for general use. There is no open source release, and there will not be one.

And the 200x number deserves a caveat the headlines skip. It is 200x versus running several hundred mirrors. Your git setup is not several hundred mirrors. Your comparison is not their comparison.

I also want to flag the uncomfortable reading. A tool this expensive to build only makes sense if you have venture money to burn on writing your own infrastructure. That is fine, but it means the story is really about scale and budget as much as it is about clever engineering.

The genuinely useful thing here is not Scion. It is the warning. Anthropic thinks other teams will hit this in the next few months. Believe them or do not, but the checkouts, the merge rate, and the agent count are all moving in one direction.

I still think about that line about infinite demand for merging code. It sounds like a boast until you remember who wrote it. A company that just spent five months and seven engineers cleaning up after its own success.

They also told GitHub and GitLab to go solve the general version of this problem. Which is a very polite way of saying: this is your problem now.

The part I cannot shake is the engineers saying no. Not as a joke. As the actual description of the job. Six months ago that would have sounded like a punchline about AI taking work. Now it reads like a job posting.

Fish Audio Drama 3: The Hype, the Reactions, and the License Catch

Dishant Sharma — Wed, 14 Oct 2026 09:37:35 +0000

A guy on r/TextToSpeech got his weights running on two used RTX 3090s. Not through some clean installer. He watched the setup log write custom GPU kernels it needed just to boot the thing, and he admits he understands none of that code.

His take at the end of the comment is the one that stuck with me: "After getting banned on Eleven Labs three times, I'm so happy something like this is finally open weight."

That is the whole Drama 3 story in one line. Fish Audio dropped their new speech model on October 13, 2026, made it 35 billion parameters wide, put the weights online for anyone to grab, and then watched a crowd of people who had been burned by closed platforms lose their minds over it.

what actually shipped

Fish Audio calls it a 35B mixture-of-experts model. About 3 billion parameters fire per token, so it is not as heavy as the number sounds.

It hits No. 1 on Artificial Analysis' Pronunciation Robustness benchmark at 93.2%. The old S2.1 Pro sat at 88.1%. On exact sequences like file paths and email addresses, it jumped from 79.4% to 86.3%.

And the part people will not shut up about is the directing. You stop guessing at [whispers] tags. You write what you want like you are briefing an actor.

[barely holding it together, forcing a smile] I'm fine. Really. Go on without me.

That is a real example from their docs. You can drop a [shaky breath] or a [small laugh] exactly where it happens. You can write the direction in Chinese while the line stays English.

The direction can be in a language the script is not even written in. That broke my brain a little.

I have wasted whole afternoons on this exact problem. You want a line to sound sad but not crying. You type something like [sad] and the model gives you a funeral. You try [a little sad] and you get nothing. There is no dial, only a light switch. So you regenerate eleven times and settle for take seven.

The Drama 3 approach is different. You describe intent the way you would to a person. "Tired but pretending not to be." "Reading a text she has already decided to ignore." No syntax to memorize, no tag list to scroll through.

the feature nobody expected

Here is the one that surprised me most. Word-level inpainting.

Picture a five-minute audiobook chapter. One word comes out wrong. In the old world you regenerate the whole take and pray the emotion lands the same way twice. With Drama 3 you swap out the single word. The model listens to the audio on both sides and pieces the fix in without touching the mood or the rhythm.

I used to think editing audio meant that was impossible. You cannot surgically replace one word mid-sentence without a seam. Except they apparently did it.

Multi-speaker scenes work the same way now. You pass one voice ID per character, tag each turn, and get a whole argument in a single request.

narrator voice
the tired captain
the engineer who is about to panic

The docs show a scene where the engineer says the reactor is "not great" and the captain replies, "Define not great." The engineer's voice breaks on the word blow. One prompt. That is genuinely cool.

And you can switch languages mid-line. Wrap a phrase in a <french> or <japanese> tag and only those words change language. Fish Audio marks this experimental and warns it varies by voice and language. Fair. But a tutor explaining a phrase, or a character slipping into their native tongue for one sentence, is now a one-line edit instead of a whole new recording.

the hype is real but so is the catch

People on X are calling it "actually insane" and saying "it's so over for standard voiceovers." The Uncle Roger demo did numbers because the model nailed his exasperated sighs.

But here is what the hype posts skip.

The license is not open source. It is the Fish Audio Community License v1.0. Free for research and non-commercial work. Free for commercial use under $500,000 in annual revenue. Go over that, or try to resell it as your own API, and you need to talk to them.

Thing	Reality
API price	$10 per million chars, then $50 after Nov 12
Interactive editing	invite-only, not launched
Local run	~39GB VRAM on dual 3090s

One Reddit user just wrote "Lame license." Another said the same thing with a shrug and admitted they get why a company needs to make money.

There is a quieter complaint buried in that same thread. Someone asked if it does German. Nobody answered. A model claiming 83 languages is not a promise that all 83 land the same way. The benchmark everyone is quoting only tests pronunciation, not whether the crying sounds real. Those are two very different tests.

And on r/TextToSpeech one commenter was flat out done: "its actual shit LOL barely better than breeze with nearly 10x the size." Harsh, maybe wrong, but it is out there.

a quick detour about naming

I keep thinking about why this thing is called Drama 3 when it is really their third generation of a completely different family.

The fish name makes sense, the company is Fish Audio after all. But numbering is where speech model releases get weird. S2, S2.1 Pro, then Drama 3. Somewhere an intern won an argument about branding and now everyone has to remember which model is actually newer.

San Francisco people name everything after a river or a peak. AI labs name things after the model that came before with a bigger number stapled on. Nobody is out here naming a TTS model "Greg." That would at least be memorable.

the honest part

Most people do not need this.

If you make two videos a month and the robot voice is fine, Drama 3 is overkill. The install is rough. Three people in one thread were trying to figure out whether their card can even hold it.

The 39GB number from that dual 3090 setup is not a rounding error. A single 48GB card is the clean path, and most of us do not own one. The GitHub setup log writing custom kernels is a hint that this is early.

There is also the part where the model did not exist a week ago in this form. It was in preview, behind an invite, and then suddenly the weights were on Hugging Face. That speed is great for hype and rough for anyone who needs stable tooling. A funny detail: if you set the model header wrong on an API call, the request does not fail. It silently falls back to the old S2.1 Pro model. You might think you are testing Drama 3 and be listening to last year's model.

And the promoting discount ends November 12. After that the API is five times the price. If your budget assumed ten bucks a million characters forever, it is not.

I could be wrong about how many people this reaches. But my read is that Drama 3 changes things for the people making long audio dramas and games, not for the person who wants a voice for a Wednesday TikTok.

The gap that matters is the license, not the model. If you are a small solo creator, you are fine. If you are a company that wants to sell Drama 3 as a service, the open weights are bait and the real product is a contract.

And if you are the person who just wants a robot to read your blog posts out loud, none of this is for you yet. Come back in a year when someone builds a wrapper with a nice button.

ending thought

I did not expect a comment about custom GPU kernels to be the thing that stuck with me. But that guy ran a 35B speech model on hardware most of us could buy used, and he only did it because he got kicked off the closed one.

That is the actual headline. Not the benchmark. The fact that the door moved.

Somewhere the ElevenLabs folks are having a very normal Tuesday about this. Or not. I have no idea what they think, and honestly I would love to sit in on that meeting.

One by onestack.dev: The React Framework Nobody Asked For

Dishant Sharma — Tue, 13 Oct 2026 12:10:35 +0000

The creator of One almost didn't post it. Nate Wienert, the guy behind Tamagui, opened his own Show HN with this line: "HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things."

He shipped it anyway on October 4, 2024. It hit 506 points and pulled 254 comments. And the weird part is what those comments were about. Barely anyone argued about whether One was good. They argued about being tired.

One is a React framework from onestack.dev. The pitch is that it unifies React web and React Native behind a single Vite plugin, so you stop running two frameworks, two bundlers, and a pile of glue code. The site leads with a benchmark: 3.6 seconds to cold-bundle a production iOS app, against 19.5 seconds for Metro. Same machine.

That number is the whole sales pitch. And I think it's the least interesting thing on the page.

What One actually is

If you build for web and mobile, you already know the setup tax. Next.js for the web. Expo for native. Two routers, two config systems, one long argument about shared components.

One replaces both with a npx one and a single plugin. Routing is typed and file-system based. You get nested layouts, groups, and .platform file forking, so a component can branch per platform without a mess.

The native side is where it gets cocky. One generates SwiftUI and Jetpack Compose bindings straight from the platform SDKs. So instead of hunting wrappers, you write this:

<One.iOS.Button label="Save" onPress={save} />
<One.Android.Switch isOn={on} onIsOnChange={setOn} />
<One.Haptics.impact('medium')>

Haptics, storage, notifications, purchases, over-the-air updates with rollback. All in the box. No Expo required, though it still plays nice with Expo modules if you want them.

And there's zero lock-in, which is the part I did not expect. It builds to a plain dist folder. Your output targets are Vercel, Cloudflare, or a Hono server you run yourself.

The reaction was not about the framework

Here is what surprised me. I went in expecting a fight about Vite versus Metro. What I found was a support group.

The top threads were people telling their own stories. One dev at forty-something: "I'm definitely getting too old... I see this great work called 'one' and I get immediately turned off by so many 'new things.' It's me. Definitely me."

Another was blunter. "My immediate reaction to this wasn't excitement but, 'Oh fucking hell, not another one.'" He went on to call the churn "a waste of the limited time I have left in my life."

Nobody said One was bad. They said it was one more thing.

That's the whole reaction in one sentence. Not a review. A sigh.

And the stack people had retreated to tells you everything. Laravel and Vue3. Django with "larger doses of React where we need interactivity, but absolutely no SPA." PHP, htmx, Postgres, plain HTML. Rust and server-side rendering. One guy reduced his whole stack to C# middleware and full page reloads.

The tool isn't the problem. The workflow is.

That's the real story of the One launch. Not whether One works. Whether anyone has the appetite left to find out.

The honest critique nobody led with

The most useful comment in the whole thread came from a native iOS developer who actually downloaded the TestFlight demo. He didn't argue. He tested.

Here's what he found:

the notifications tab wouldn't scroll at all on his phone
dark mode didn't follow his system setting
tapping a feed item caused a jarring navigation title transition after the screen changed
hitting back from a notification dropped him on the Feed tab, not where he started

He also said the whole thing had "the normal uncanny valley feeling that React Native gives off." React Native trying to look native, but not quite making it.

Nate replied to that one directly, which I respect. He admitted the demo app "just has minimal investment" because a small team had a hundred things to pull off at launch.

A framework that promises to erase a hundred setup decisions is still built by a small team. And the demo shipped with bugs you'd notice in five minutes.

One year later, it actually shipped

Here's the part that changed my mind. One didn't quietly die the way a lot of Show HN darlings do.

On December 28, 2025, they posted v1 Release Candidate 1. "Over 1,800 commits since the announcement of the alpha about a year ago," Nate wrote. They thanked Pokai Chang for leading most of the work to maturity.

The RC added real things. A Metro mode, so you can ease off Vite for native if migration scares you. Middleware. Sitemaps. Parallel builds using worker threads, about 40% faster static generation.

4,544 stars. 129 forks. 32 open issues. Not React numbers, but alive. Shipping counts for more than a launch spike.

And I hadn't known this until I dug in: One started as a fork of Expo Router, which itself sits on React Navigation. So the framework positioned against Expo is partly built from Expo's own work. They say so on the blog. Small detail, but it says something about who actually built the roads.

The local-first claim that wobbled

One launched with a partnership with Zero to do local-first syncing. That claim got taken apart in the thread, and honestly it's a good read.

The objection: if the server disappears, does your app still work? Can you edit offline and merge later? Does it do end-to-end encryption?

The Zero founder, Aaron, showed up and gave one of the most candid vendor answers I've seen. "Zero won't support offline mutation at launch." And later: "we have recently tried to avoid claiming Zero and Replicache as local-first on our own sites to avoid this controversy."

So the marquee feature of the launch was walked back by the people building it, one week in. That's not a scandal. That's just what honesty looks like when the term got stretched past what the code does.

Right, a tangent. When I research frameworks now, I keep a tab open for the creator's personal blog, and it's almost always better than the launch post.

The pitch deck tells you what the tool does. The blog post six months later tells you what broke. You learn more from one honest "here's what we got wrong" than from ten benchmarks.

I don't know why we keep reading the deck first.

So should you use it

No. Most people should not use One.

If you're shipping a standard web app, use Next.js. If you're shipping a standard mobile app, use Expo. Both have thousands of people who've already hit your bug and posted the fix. The ecosystem is the feature.

One is for a narrow person. You're building genuinely cross-platform, you want web and native from one codebase, and you're willing to be early. The mobile share number is what makes it real. If you ship both, the plumbing you're replacing is actual months of work.

That person exists. There just aren't many of them, and the HN thread proved it. The room was full of people who used to be that person.

And One is not Expo's killer. Read the blog. It's a fork of Expo Router. It plays with Expo modules. This is not a war. It's a shinier path through the same forest.

Where this leaves me

I keep going back to that first line Nate wrote before he posted. He knew the room was tired. He posted anyway, and then spent days in the comments answering the fatigue, not just the code.

That's the thing I'll remember. The framework is clever. The benchmark is fine. But the moment that stuck was a tired room and a guy who showed up to it anyway, then actually shipped v1 a year later.

The churn is real. Most of these frameworks don't deserve your Sunday. But every so often, one of them treats you like an adult about it.

I'll still probably use Expo on my next project. But I'm glad One exists.

SubQ Snap: The Hype, the Benchmarks, and the Reactions

Dishant Sharma — Tue, 13 Oct 2026 07:19:37 +0000

Seven points and one comment. That is what the SubQ Snap launch got on Hacker News, hours in. The comment was a question, and it was not friendly:

Doesn't OpenAI's decision API support up to 1M context on Luna?

On LinkedIn, the same launch hit 220 reactions and 39 comments in fourteen hours. "We launched a new model today!" read one company post. "Feels like Jev on steroids," read an early take being passed around on X.

Same product, same day, two crowds reading two different things.

i had to find out which crowd was right. So i read the launch post, the press release, and every third-party breakdown i could find. The short version: both crowds are right, and neither is fully.

SubQ Snap is a decision model from Subquadratic, a research shop that thinks attention is the real bottleneck. No text generation. You send context, a question, and allowed answers; it picks.

The pitch: up to 384K tokens of text and images in one call, a decision in about a second, and five cents per million input tokens. Output tokens are free.

The timing is the wild part. This is the sixth hosted decision model to ship in about three weeks, after Jev, Perplexity's Decider, Cloudflare's Clef, OpenAI's Decisions API, and Microsoft-Decision-1.

Why care? Because this is where the cost of agents gets decided. And the fight is not about the model.

What a decision model actually does

here's a question people always ask: why would you pay for a model that cannot write? A decision model is a narrow cousin of the LLM. Given context, a question, and a set of allowed answers, it returns a probability for each answer.

Nothing open ended.

That restriction is the whole trick. No generation means no token-by-token output to pay for. Scoring fixed answers is fast, and speed is the point, because an agent makes these calls constantly: which file matters, which tool to call next, did the test pass.

Subquadratic names four jobs for Snap:

routing
tool picking
checking
stopping

A clean list. And a list you can currently build with a regular LLM and careful prompts. Which is the part nobody in the press release mentions.

The context wall

what actually happens is the input, not the answer. The right next call might depend on a constraint from forty turns ago.

A function defined deep in a codebase. A clause on page nine of a contract.

Standard transformers pay quadratic attention. Double the context, quadruple the compute. That is why decision models stayed small.

Jev runs 64K per request, 32K of state. Microsoft's model runs 32K. They decide without seeing most of what matters.

Snap's answer is Subquadratic Sparse Attention, SSA. Linear cost instead of quadratic. So the model can read a whole repo or contract in one call.

Subquadratic says 100K tokens comes back in under a second. That number is theirs, unverified, no hardware named. But the architecture is genuine research, not a wrapper around someone else's API.

Benchmarks and their asterisks

most tutorials tell you to look at the chart. The chart is good.

Decision Index 0.2.1: 61.7 to 57.9. The long-document test: 74.0 to 48.0.

Snap leads on 13 of 16 enterprise tasks. Phishing detection jumps from 25.1 to 47.1. Code output prediction from 57.1 to 73.8.

But read the fine print. Every number is Subquadratic's own. No outside lab has run Snap.

The long-context tests are their adaptations of RULER and LCR. And the headline score, 96.3 on Decision RULER, runs at one million tokens. The product caps at 384K.

They published a benchmark the product cannot accept.

Snap also loses three of sixteen. The embarrassing one is When2Call, which tests whether to call a tool, ask, answer, or decline.

That is one of the four jobs Snap is sold for. It lost 67.0 to 74.6. The model that decides whether to act is not the best at that exact call.

The price war

the problem isn't the benchmarks at all. It's what the benchmarks are for. Look at the field:

Model	Price per M input	Context
Perplexity	$0.04	~262K
Microsoft-Decision-1	$0.042	32K
Jev	$0.042	64K
SubQ Snap	$0.05	384K
OpenAI (gpt-6-luna)	$0.10	n/a
Cloudflare Clef	$0.24	64K

Six models in three weeks. Prices sliding toward zero. Free token grants everywhere; Snap gives the first 10,000 users 100M tokens.

"Cents per decision" is the new marketing line.

That should make you suspicious in one specific way. When a market moves this fast, the model is not the moat.

The workflow is. The people who win own the routing logic, not a vendor relationship.

Meanwhile, the kidney cats

here's the thing that made me laugh during research. i searched Reddit for "subq snap" and the model was nowhere. i got forums about subcutaneous fluids for cats with kidney failure.

i got reviews of SNAP-8 peptide serum for wrinkles. i got a thread about a spring-loaded syringe you snap in place.

"subq" is medical shorthand for subcutaneous. The company named a product after a medical abbreviation and a snack brand's word, then launched it into an AI hype storm. For a while, anyone googling the model gets cat fluids and skincare advice.

i kind of love that. It keeps things honest. The hype lives on LinkedIn, with its 220 reactions and its CEO quote about "radically different ways to scale AI."

The messy internet still serves kidney cats and peptide talk. Every AI launch should have to compete with a cat forum for search traffic. It would keep the marketing humble.

The part nobody wants to hear

Most people do not need a decision model. Not yet. If your agent makes a few hundred calls a day, route with a cheap LLM and move on.

The complexity you add to save pennies is complexity you will maintain forever.

Even if you do need one, do not build on a public preview with a waitlist on day one. The model id is literally subq-snap-preview.

That is not a stability promise. That is a warning.

And the benchmarks? Treat them like a resume, not an audit. Everything is self-reported, compared against one rival, on tests the vendor adapted.

The moment an independent leaderboard runs Snap, the numbers will move. i would bet on that.

The one thing that would make me take Snap seriously is a real repo test. An agent that reads its own codebase, picks files, checks results, and hands me the bill. A week of that beats any chart in the launch post.

i'm still going to try it. 100M free tokens is hard to ignore, and that window is genuinely interesting. But i'll treat the ad copy as ad copy until i see it run.

i keep coming back to that Hacker News comment. Seven points, one question, and it cut through the entire launch in a single line. "Doesn't OpenAI's decision API support up to 1M context on Luna?"

That is this market in one sentence. The lead changes so fast that "first" is a memo, not a moat.

Snap is real engineering, SSA is not a wrapper, and 384K in under a second is genuinely interesting. And so was everyone else three weeks ago.

i'll be watching the independent benchmarks when they land. And checking on the kidney cats. One of those two will tell me more about decision models than the press release did.

Muse Wonder, the Frontier Model That Got Lost in a Forest

Dishant Sharma — Tue, 13 Oct 2026 05:15:17 +0000

The most expensive Pokémon run i've ever seen cost $96.06 and never left the first forest.

Somebody ran Muse Wonder, Meta's new frontier model, at Pokémon Red on launch day. It picked its starter by turn 20 and reached Viridian City by turn 59, right on pace with the fastest agents. Then it walked into Viridian Forest on turn 208 and spent the next 792 turns in there.

Six hours of stream. Almost a hundred dollars. It never beat Brock.

Opus 5.5 played the same game at the same token price and won in 271 turns. It cost $8.44.

Here's why that matters. The launch week was all triumph. Meta called the model a major leap toward personal superintelligence, and Wired crowned the company back at the frontier.

Hacker News gave it the highest compliment it knows: i'm sorry zuck, i wasn't familiar with your game.

And right under that headline, the flagship was paying $12 a minute to wander through a forest.

The gap between the poster and the product is the real story.

Why people lost their minds

i used to think Meta would never catch up in AI. The labs with the best models were the ones that bet everything on them, and Meta always felt like it was running a side project with an ad business attached.

Then the numbers came out.

Muse Wonder launched Oct 12, and Wonder Full with it. Wonder runs through the Meta API at $4 per million input tokens and $20 per million output.

Wonder Full, the stronger one, is locked inside Muse Code subscriptions at $50 or $200 a month. Consumers get it through the Muse app at $20 a month, if they feel like paying.

Where	Price	What you get
Muse app	$20/mo	Wonder
Muse Code	$50 or $200/mo	Wonder + Wonder Full
Meta API	$4/$20 per MTok	Wonder

The headline features are Active Memory and Active Focus. Meta says the model remembers what matters to you across conversations and keeps pushing toward a goal instead of stalling. What that means in practice:

try a different approach when one fails
keep working through blockers
check in before doing something important

On MemoryBench it beats Fable, Opus, and Astra. On the Artificial Analysis index, Wonder Full sits second, behind only Opus 5.5.

Is the scoreboard real

here's a question people keep asking me: is the scoreboard real?

There are literal bets on it. People are gambling on Polymarket and Kalshi over how much of Wonder's lead comes from training on the benchmarks themselves. The top comment on the launch thread asked the same thing, straight up: how much benchmaxxing has been done here?

Meta saw this coming. Its own launch post has a section defending against the accusation, and it coins a phrase for the opposite quality: big model smell, the feeling that a model handles stuff it was never trained on way better than the numbers predict.

look, i get why people are excited. But scores are a starting point, not a review. Every frontier lab trains toward the benchmarks it publishes.

That's not fraud, it's how the game is played. And Wonder's real review is happening in the forest right now.

The comeback nobody voted for

what actually happens is a redemption arc nobody voted for.

A year ago this lab was a punchline. Zuckerberg bought Scale AI for billions, put a twenty-something Alexandr Wang in charge of Meta Superintelligence, and pushed out Yann LeCun, a Turing Award winner, over his loud complaints about LLMs.

Insiders laughed. Wall Street hated the capex. The Metaverse had already burned through money like it was nothing.

Then Muse Spark shipped and quietly became a workhorse. People on Hacker News said it moved 90% of their coding work off Codex. And now Wonder Full lands second on the index, one spot under Opus 5.5, and the same people are acting like they always believed.

i'm sorry zuck, i wasn't familiar with your game

I'm not going to pretend I saw it coming. I called Meta's AI push a vanity project last year. I was wrong about the model.

I still think the company has a trust problem, and we'll get to that.

The race gets cheaper

the problem isn't what you think. It's not the benchmark scores.

If Meta can buy and scale its way to second place, then frontier models stop being a moat. One comment on Hacker News put it plainly: give any country with 20 to 40 billion dollars a couple of years and it will have its own champion model. That's what commoditization looks like, and it's already happening.

Meta also has the distribution to make it sting. WhatsApp holds three times the users of ChatGPT's entire app.

If Wonder quietly powers a good enough assistant inside apps people already open, nobody needs to download a thing. That's the part OpenAI can't copy by making a smarter model.

And OpenAI is having a rough week. Its pro subscription value just got halved, and the IPO talk is wobbling.

The story here isn't only about Meta winning. It's about the whole market getting cheaper and faster at once.

Watching the machines play

Separately, i've been watching people turn AI game runs into a spectator sport. PokéBench keeps a leaderboard of agents playing Pokémon Red, with turn logs and cost per run. It's like horse racing, except the horses are language models and the track is a 1996 game.

It takes me back to watching my cousin play on a Game Boy in the back of a car. Same sport, way higher stakes.

He'd get stuck in Viridian Forest too, then hand me the device and tell me to fix it. I never could either. We'd restart the whole save and pretend it didn't happen.

The difference now is that the AI doesn't ask for help when it's stuck. It just keeps buying more tokens and walking deeper into the trees.

That's the most human thing about it, honestly. i've paid for dumber persistence.

Who should skip this

Most people don't need Muse Wonder. That's not a hot take, that's the price tag talking.

The free Muse app already handles the daily stuff: reminders, notes, small tasks. The moment you jump to Wonder you're paying $20 a month for the memory features, and $100 for the heavier tier. The people who'd actually benefit, the ones running long autonomous jobs, are already on Muse Code at $50 or $200.

And let's talk about the privacy stuff, because it's the part everyone is dancing around. Users complained the Muse agent read private messages without permission.

Meta disputed it, and the AI chief said users may have forgotten what they authorized earlier in a conversation. Maybe that's true.

Maybe it's the creepiest sentence of the year.

Both can be true at once. If you don't trust Meta with your inbox, Wonder doesn't fix that. It makes it sharper.

The forest is still there

i keep coming back to that $96 walk. Not because it proves Wonder is bad. It proves what frontier means right now: a model that can do a hundred useful things and still, with total confidence, spend six hours going nowhere.

They'll fix it. The next run will clear the forest and the headline will change.

But i'll remember the first one. The expensive, honest, slightly embarrassing first one. And next time somebody tells me a model is superintelligent, i'm going to ask one question: did it get past the forest yet?

I Asked for a Video. Claude Motion Gave Me an HTML File.

Dishant Sharma — Mon, 12 Oct 2026 22:29:32 +0000

There's a Reddit post where a guy asked ChatGPT and free Claude for the exact same thing: a 30-second motion graphics video about Reddit. ChatGPT handed him an .mp4, music already added.

Claude handed him an .html file. He asked Claude to convert it, and a few minutes later it worked.

That one detail says more about Claude's new motion push than any launch video does. On October 8, Anthropic put Claude Dashboards and Claude Motion into beta. Motion turns a prompt into a short animated explainer, plays it like a video, and exports as MP4.

The same announcement took Docs, Slides, and Design out of beta on every plan, including Free. On paper, the pitch is simple. Ask for your quarterly report as a 30-second explainer, get a short video you can edit and download.

Anthropic frames it as the opposite of a video generator. No generated people, no fake footage, just your numbers and words moving.

But the hype is running ahead of the product. People are posting "Claude Motion" takes that are actually about Claude Design animations. Others are asking why they can't find the feature anywhere.

One of the most upvoted reaction threads to the launch was about a different thing entirely.

The gap between what people think Motion is and what it actually is, that's the story. i spent a full evening chasing it.

what motion actually is

Here's the question people keep asking: is Claude Motion a video generator? No. And that's the most important fact about it.

Claude writes code that animates text, charts, shapes, and images. It plays like a short video. No video generation model inside, no generated footage, no AI people.

That's a deliberate choice.

The animation is an artifact built from a Motion template. Because it's code, you can change one word, one number, one timing, and the rest stays put. Try that with a Sora clip and you reroll the whole thing.

That's genuinely smart. It's also why the results look like animated slides, not movies. They're not trying to be movies.

who can even use it

The first time i tried this, i couldn't. Claude Motion is a Team and Enterprise beta. Admins have to switch it on, and for enterprises it's off by default.

So the internet is mostly reacting to a product it can't open. The people who can use it work on paid team plans. The people hyping it are often on solo plans with zero access.

The confusion gets worse. A top r/ClaudeAI thread, "Just used Claude Motion for the first time and I'm genuinely impressed," ends with the poster correcting themselves: "my bad, it's actually Claude Design, Animation."

The video pulled real stats about New Zealand house prices over 30 years without the user digging them up. That's cool. It's also not the product they claimed to test.

what the professionals saw

Most tutorials tell you the hype version. The r/MotionDesign thread "What kind of Motion survives AI?" is the honest version.

A working motion designer watched Claude's output and called it beginner-level. No keyframes. And keyframes are where the magic happens.

He figured cheap talking-head explainer work is basically cooked.

Keyframes are where the magic happens.

The commenters agreed. The bland corporate default style, the stock vector slop, that's what gets eaten first. One of them said it best:

you'll never convince clients with beer budgets to have wine tastes.

Meanwhile Hacker News barely showed up. The launch story got a handful of points and almost no conversation.

Reddit argued. HN shrugged.

the trade you're actually making

What actually happens is you trade control for speed. Here's the honest comparison:

	Claude Motion	video model (Veo, Sora)
output	code, exported as mp4	pixels
edit one number	the rest survives	reroll everything
people and footage	none, by design	yes, sometimes uncanny
cost	plan usage, longer costs more	per generation

Motion counts against your plan's usage. Longer and more complex animations burn more than a typical message. A "30-second explainer" is not free, and on most plans it's not even reachable.

i like the direction. Code you can edit beats video you can't. But shipping it to two plan tiers while naming it next to a feature that already does animations, that's how you get a launch where nobody's sure what they're reacting to.

the detail almost nobody covered

Here's what surprised me. The standalone Claude Design site shuts down on December 14. Anthropic is folding Design into Claude and closing the old URL.

People have made more than 45 million docs, decks, and designs inside Claude. A lot of the "motion" love online comes from Design, not Motion. People produce polished animated videos in a day with zero motion graphics training, and the exact prompts get passed around like recipes.

So while the new feature with the confusing name waits in beta for team plans, the thing people actually love is quietly moving houses. The shutdown is the bigger story for anyone who makes things.

a word about names

Every name collides these days. Search "Claude Motion" on Reddit and you get the feature, plus a r/GTA post asking about the motion capture actor for Claude from GTA 3, plus a thread called "Claude Motion Sickness" where a team feels physically ill after long coding sessions.

The sickness one is real and it's not about animation at all. Extended sessions, dual screens, that car-sick feeling when the workday finishes. Their environment hasn't changed in six years.

Nobody can explain it.

And the GTA post is my favorite. Claude from GTA 3 makes grunting sounds when he falls. People genuinely want to know who did the grunts.

The internet is a beautiful place.

Every product name is now a three-way collision. The feature, the profession, and some unrelated thing people feel. "Motion" hit all three in one week.

real talk

Most people don't need Claude Motion. If you're on a solo plan, you can't open it. If you need real motion design, it won't give you keyframes.

If you need people or footage, it refuses on purpose.

Here's what it won't do:

no generated footage or people
no keyframes to bend
no audio on export, that's on you

It's for teams that need internal explainers, board decks, onboarding walkthroughs, all-hands videos. That's the whole lane. It's a good lane, and it's narrow.

And the thing people are actually excited about is Claude Design's animation, which is available now and goes by a different name. Anthropic shipped two overlapping things and let the internet sort out which is which. i could be wrong here, but the launch shows it: the most-engaged "Motion" content is about something else.

If you're a motion designer, don't panic yet. The cheap work is at risk. The work with a point of view isn't.

And if you're a team lead who hates making slides, this could genuinely save you. Both things are true.

i keep coming back to the html file. A guy asked for a video and got a file that wouldn't play anywhere. He asked again, it converted, it worked.

That's Claude Motion in one image. Almost a video, one step from where you expect it, fine once you know the trick.

The hype will keep coming. Every week there's a new demo that looks like it ended a profession. But the people who actually move slides and charts and numbers, they're not dead, they're just on a different plan tier.

someday, exporting your first explainer won't make you think about file formats at all. That's the day the name finally makes sense. until then, i'll be here, converting html files.

Everyone's Talking About Claude Next. Nobody Knows If It's Real.

Dishant Sharma — Mon, 12 Oct 2026 04:11:22 +0000

A post appeared on my feed with 2.8K likes. It said a model called Claude Next is being tested inside Claude Code right now. It makes images, video, and music that don't look generated.

Pure JavaScript, the leaker claimed. "It is over for image and video generation."

I checked the account.

No Anthropic confirmation. No release notes. No blog post.

Just one tester on X with a history of spotting unreleased models, plus a video of something animated.

My first thought: here we go again.

Anthropic has not said a single word about Claude Next.

Not confirmed. Not denied. Not even a wink.

The company just shipped Opus 5.5 and Sonnet 5.5, and the internet has already moved on to a model that may not exist.

That's the part that gets me. Not the leak. The speed of the leap.

A rumor becomes a headline becomes a product in people's minds in about eleven hours.

Why should you care? Because this is how the AI news cycle works now.

It doesn't start with a launch. It starts with a screenshot and a confident tweet.

And everyone, including people who should know better, starts planning their lives around it.

I spent the evening reading the thread.

The reactions. The skeptics. The memes.

Here's what i found.

Two models, one name

here's a question people always ask: what even is Claude Next?

Trick question. It's two different things wearing the same name.

Three years ago, Anthropic's IPO deck mentioned a frontier model, tentatively called Claude-Next. Planned to be ten times more capable than the best model of the day. Training cost: around one billion dollars, spread over an 18-month cycle.

That was the old Claude Next. A budget line. A promise.

The new Claude Next is a leak. A tester on X says it shows up inside Claude Code when you're not expecting it. It supposedly burns tens of millions of tokens on a single generation.

It makes Opus 5.5 look primitive, in his words.

Same name. Totally different thing.

One is a plan. The other is a rumor wearing a plan's clothes.

That confusion matters. When people argue about whether Claude Next is real, they're not even arguing about the same thing.

	Old Claude-Next	Leaked Claude Next
What it is	IPO deck plan	X posts from a tester
Capability claim	ten times today's models	makes Opus 5.5 look primitive
Evidence	investor materials	screenshots and a video

The leak treadmill

what actually happens is a pattern i've watched repeat for a year.

A codename shows up in a model selector or a tool like Cursor.
A power user screenshots it.
The AI community goes feral for 48 hours.
The model ships under a boring name, or everyone forgets.

The list from the last year alone:

Honeycomb EAP
Mythos
Fable 5.5
wafer EAP
and now, Claude Next

Some were real. Some were A/B tests. One of them, people joked, was probably just Opus with a new temperature setting.

The best reaction I found to the whole circus was a parody leak. Someone announced Claude opus-Optimus-prime-9000, coming next Friday, with the caveat that Gemini told them. It got upvotes.

That's where we are. The community has leak fatigue, so it started leaking fake leaks to cope.

But here's the thing about Claude Next specifically. The timing is odd.

Video without a video model

i used to think generated video meant a video model. Diffusion, frames, the whole pipeline. Claude Next, per the leak, does something else.

The claim: it generates animations, visual scenes, and physics-based motion purely through code.

JavaScript. Canvas. Web tech.

No native image model. No native video model. The media comes out of the model writing code that renders it.

If that's true, it's a strange and interesting bet. OpenAI and Google both ride dedicated models for images and video. Anthropic's rumored answer is: make the language model so good at writing rendering code that you don't need them.

I cannot verify any of this. Neither can you. Zero official confirmation.

The most honest summary I saw on Reddit was a comment with 18 upvotes:

i don't know what bro was saying in that tweet, but cool.

Still, I get the appeal. Code is compact. Code is inspectable.

A model that renders through code can be fixed and reused in ways a generated mp4 can't.

Claude is building Claude

here's the detail that actually made me stop scrolling. It wasn't the leak.

Anthropic says its own models now lead 26 percent of the company's AI research and development. Over 90 percent of the work involves Claude in some capacity. Claude helps build the next version of itself.

So Claude Next is a leaked name and a description of the workflow at the same time. Whatever it ends up being, a meaningful chunk of it will have been made by the thing it replaces.

Nobody knows what that does to a model's design. Not the public. Not really the company either, i suspect.

Everyone is making this up as they go, including Anthropic.

And that, more than any anime video, is what i find worth watching.

About the codenames

Tangent, but stay with me.

Everyone names AI models like fantasy characters now.

Mythos. Honeycomb.

Fable. Next.

My home directory is a museum of names i gave up on: fix_shit_v2.py, final_final_2.py, script_OLD_DO_NOT_USE.py.

I think about this every time a codename leaks. The people building these models get cool names because the models ship and get famous. The rest of us name our work the way you name a fish you're about to eat.

There's status in it. Leak a model called Mythos and you sound like you're inside the story. Tell me about your script called temp3 and I know exactly what your life is like.

Both are honest. Only one gets the likes.

Anyway. Back to the model that may or may not exist.

Who should ignore this

Let me be blunt. Most people reading this should not care about Claude Next yet.

It is not released. It is not confirmed. No access, no waitlist, no price, no API.

If you're not a power user living inside Claude Code, this leak changes nothing you can do tomorrow.

The biggest misconception is that Claude Next is a thing. It is a codename that has floated around for three years, plus one very good tweet. That's the entire public evidence.

The hype machine runs anyway. People are literally betting on which model ships next. Prediction markets track release dates like they're game scores.

That pressures a company to ship before a model is ready, and we've seen how that ends more than once.

Do not buy a subscription because of a rumor. Do not cancel one either. The announcement is free, and it lands eventually.

i still don't know if Claude Next is real. Maybe it ships next month as Opus 5.6. Maybe the leak was a clever test.

Maybe Anthropic is quietly letting the community do its marketing for free.

If it ships and the code-rendering stuff holds, I'll be genuinely curious. I'll even admit I was one of the people refreshing feeds all evening.

But the most honest sentence I found all day was the top comment on that Reddit thread: i don't know what bro was saying, but it looked cool.

That is the whole AI news cycle in one line.

The OpenAI Decisions API Hype Met a Jar of Marbles

Dishant Sharma — Mon, 12 Oct 2026 03:55:44 +0000

A developer ran a thousand trials against OpenAI's brand new Decisions API. Loaded coin, biased to 70% heads. The API nailed it, sampled heads almost exactly 70% of the time.

Then he tried a jar of marbles. Five red, three blue, two white.

True odds of drawing red, 50%. The API picked red 86% of the time.

He reordered the answer options, moved red from first to last. The number dropped to 73%.

Same question, same jar, same model. Just a different order on the list.

i could not stop thinking about that.

This is the API everyone spent a week losing their minds over. OpenAI announced it at DevDay, powered by a specialized gpt-6-luna, aimed squarely at the fast decision market TypeSafe's Jev had just made famous.

The public beta landed days later. The takes were loud.

Jev killer. The end of a whole startup category.

And buried under all of it was this quiet experiment where a probability moved because someone rearranged a list.

If you're going to hand a model your routing logic, you should know about the marble jar first.

What the Decisions API actually is

The idea is simple and i wish more launches were this honest. Instead of generating text token by token, the model returns one of three typed answers:

predicates: yes or no, with a probability
choices: pick one from a fixed list you define
scores: rate against a rubric

No essays. No filler. Just a judgment, fast.

OpenAI claims up to 10x speedups because there's no long-form generation. In theory that's around 150ms per call instead of 1.6 seconds of text. For high-volume routing, that math is attractive.

The catch is what you give up. The model can't explain itself. It can't show its work.

You get a verdict and a number instead.

The Jev fight

here's a question people always ask about this launch: was it a copy?

TypeSafe's Jev went from viral curiosity to a $7.5B valuation at over $100M ARR in what felt like weeks. It defined the category.

Then OpenAI shipped a direct answer almost immediately. The r/singularity thread summed up the mood: "Takes away a massive chunk of the market TypeSafe was eyeing."

The top Reddit reply was less impressed.

Wait, it's a copy of Jev, and essentially just a super light Luna?

The benchmark numbers landed somewhere in between. LangWatch ran both on LLM-as-a-judge tasks:

	OpenAI Decisions	TypeSafe Jev
Accuracy	75.2%	63.7%
Median latency	243 ms	429 ms
Cost per 1k decisions	$1.09	$0.42

OpenAI faster and more accurate. Jev less than half the price. The stat nerds called it a statistical tie with a price gap.

The slow part nobody tweeted

The interesting complaint came a few days later. A thread on r/LLMDevs titled Jev alternatives called the Decisions API "disappointingly slow." That is not what you expect after a launch built on a 10x speed claim.

Same story as always with speed launches. The benchmark is a toy. Real traffic is not.

People trying to route support tickets found the median latency fine and the tail annoying, enough seconds to feel broken.

i think the deeper issue is what OpenAI measured against. Compared to its own generation endpoints, this is fast. Compared to a small model doing the same classification job, the gap shrinks fast.

One more thing nobody puts in the launch post: both models fall apart when the answer needs actual math.

Adding up invoice line items? Hard fail on both. The model judges, it does not calculate.

Microsoft showed up three days later

And then the weirdest thing happened. Microsoft dropped Microsoft-Decision-1, its own decision-scoring model, three days after OpenAI's beta.

The twist: they built it by post-training Alibaba's open-weight Qwen3.5-9B. Not an OpenAI base. Microsoft, OpenAI's biggest partner, used a Chinese open model for its fast judgment layer.

It's cheaper too. $0.042 per million input tokens, no output charges. Text-only, 32k context.

Microsoft claims it wins a 36-benchmark suite of nearly 150,000 blind questions, running 35x faster than flagship models like GPT-6 Sol. They're already planning to rebase it on their own MAI models.

i read that as a statement. Microsoft doesn't want to depend on OpenAI for the cheap, boring, high-volume judgment layer.

So now three players are fighting over the same job: judge a thing, fast, cheap. The winner becomes the default brain inside every routing system.

A break from the benchmarks

i have a folder on my desktop called "launch week." Every time a company announces the fastest model ever, i screenshot the announcement and drop it in there.

There are forty files now. None of them is the fastest model ever anymore.

it's a weird hobby but it keeps me honest.

gpt-6-luna, Jev, Decision-1, Dots. Every name was the future for exactly one week.

i told a friend about the folder once. She said the real pattern was companies running out of nouns. i think about that every launch.

i remember reading a Jev alternatives thread and watching people argue about whether some open model called Strom "looks OK." Not great. OK.

That's where the category already is. A new thing appears and within a month it's a commodity with a spreadsheet of tradeoffs.

And the naming. That's the part i can't get past.

Your infrastructure now depends on models named like indie bands. Jev sounds like a fantasy novel character. Luna sounds like a perfume.

Decision-1 sounds like a Star Trek android.

The honest part

Most people don't need this. Let's be clear about that.

If you're routing a few thousand decisions a day, a normal model with a JSON schema does the same job. Slower, sure, but free, because you already pay for the model.

This category only matters at volume. Content moderation at millions of items. Ticket routing across an enterprise.

Agent loops that would otherwise burn thousands of tokens deciding between two options.

And if you do use it, don't trust the raw probabilities. The marble experiment is right there.

A model whose confidence shifts 13 points because you reordered a list is giving you a vibe, not a measurement.

Treat the score as a hint, build your own thresholds, and test the order of your answer options before you ship.

One more honest note: the 10x claim only applies when you were generating text you didn't need. If your workflow writes a paragraph, this API is useless. It's a switch, not a writer.

i keep coming back to that marble jar.

The coin was perfect. The jar was a mess.

And that's the whole story of this API in one experiment. Great when the question is clean. Weird when the world shows up with mess and order and bias.

i'll use it for triage. i won't ask it for truth.

maybe the real lesson is simpler. The hype cycle moved faster than the calibration. Everyone wanted to argue about who killed Jev, and almost nobody asked whether the probabilities held up when you shuffled the answers.

that question is worth more than all the launch takes. and i still haven't found a good answer to it.

Omarchy Is Fine. The Hype and Hate Around It Are the Story

Dishant Sharma — Sun, 11 Oct 2026 12:12:52 +0000

there's a reddit thread on r/omarchy titled "why is omarchy good and deserving of all the hype?" and the top answer is basically "it's not that deep man. it's just an operating system. use it or don't."

that's the whole omarchy discourse in one comment. ninety people argued under a post asking why everyone either loves it or hates it, and the most honest take was a shrug.

i think that comment annoyed me more than it should have. because omarchy isn't just an operating system. it's a stress test for how the linux community handles fame, money, and ai agents showing up all at once.

dhh shipped it as an opinionated arch + hyprland setup in august last year. since then it's pulled in millions in sponsorship, a hackerone bug bounty, a security researcher showing any process could escalate to root, and enough youtube hot takes to fill a festival. chris titus asked if it's the "arch savior or overhyped reskin." linux ninja made a video literally called "reacting to the omarchy hype train."

the interesting part isn't the distro. it's watching everyone lose their minds over it.

what it actually is

omarchy is arch linux with dhh's dotfiles, preconfigured hyprland, and a bunch of opinions. that's the whole thing. he says it himself: his "platonic ideal of what a developer environment should look like," packaged so you can run exactly what he runs.

the omakase name is the point. chef's choice. you don't decide, dhh decided for you.

most tutorials tell you linux is about choice, and then hand you a config file with 400 lines of comments. omarchy flips that. the choice was made, the config is done, and you can change everything later if you care enough.

people who like it say it's the first arch setup that feels finished out of the box. people who hate it say it's a bunch of config files, not a real distro. both are right. it's literally a github repo of configuration layered on arch.

the money changed the conversation

here's the thing that makes omarchy different from every other arch rice: the funding.

cloudflare sponsored it. digitalocean put in millions. namespace is paying $100,000 a year. spacexai donated $1.5 million in grok tokens. the omacom foundation became the exclusive sponsor of hyprland's main developer.

that's when the discourse stopped being about window managers.

the tool isn't the problem. the money is.

a distro is usually a fun side project. omarchy became a funding vehicle with opinions, and suddenly every conversation about it is also a conversation about whoever dhh decides to pay. that's uncomfortable for a community that runs on volunteer goodwill.

the security stuff is real

the most important omarchy post of the year wasn't a hype video. it was a security write-up from 0xcc.io titled "omarchy: any user process can escalate to root."

the default user was in the docker group. since the docker daemon runs as root, any process in your session could ask it to mount the host filesystem and read /etc/shadow without a password. the write-up showed it in three commands:

$ id
uid=1000(tester) gid=1000(tester) groups=1000(tester),967(docker),992(input),998(wheel)
$ docker run --rm -v /:/hostroot alpine cat /hostroot/etc/shadow
root:$6$...

the fix shipped fast, and the researcher was fair about that. but the pattern is worrying. another write-up called it "predictable security issues" from development practices. when your os is vibe-coded, the security model is whatever the vibe included.

that's the trade nobody talks about at the hype party. a bad npm script on omarchy wasn't just a bad npm script, it was a root shell.

the "not a distro" fight

i used to think the "omarchy isn't a real distro" argument was pedantic. then someone pointed out it has no kernel team, no package repos, no release engineering. it's arch with a skin.

but so is half of linux, if you're honest. the line between a distro and a config collection is vibes anyway. ubuntu is debian with opinions. garuda is arch with opinions and a dragon. the difference is that omarchy's opinions got famous.

the deeper critique is the one that stings: people say it's "hype around ricing." that the productivity gains are just tiling windows, which you could get from any window manager. and they're not wrong about that. omarchy is a really pretty, well-curated arch setup. it is not a new operating system.

why every thread becomes a culture war

the loudest criticism of omarchy has nothing to do with docker.sock. it's about the founder and the politics of who he funds. there are long essays calling the project a power grab, accusing it of funneling money toward people the author disagrees with.

and there are equally loud defenders saying none of that matters and it's just an os.

i'm not going to litigate the politics here. but i will say this: you can't separate the distro from the drama anymore. the reddit thread "i really like omarchy but i don't understand the hate" has 167 answers and they run the full spectrum. nobody agrees on what this project even is.

that's the honest sign of a hype cycle. the product got drowned out by the conversation about the product.

the tangent: everyone wants a better computer

while researching this i fell into the omarchy widget showcase and the plugins are honestly the best part of the whole thing. there's a 1-bit desktop pet you can feed and scrub clean. there's minesweeper that plays with vim motions. someone wrote an airpods battery widget for the bar.

this is the part of linux i actually love. not the distro wars, the weird little things people build because they can. peppa the pig desktop environments from people who learned config languages in a weekend. pewdiepie running a "russian nuclear core" build.

omarchy didn't invent any of this. hyprland and the ricing community did. omarchy just put a pretty fence around it and made it easy to find. that part is genuinely good.

real talk

most people should not install omarchy.

if you're happy on ubuntu or fedora, stay. if you use your computer for work and don't want to think about your desktop, omarchy is a whole new thing to think about. if you're on a machine with one browser tab and a prayer, the arch base alone might eat your day.

it's for people who want dhh's exact setup, or people who want a polished starting point for ricing. that's a real audience. it is not everyone, and the hype keeps pretending it is.

the security history should also make you think twice before making it your daily driver. the docker group thing was fixed, but "fixed fast" isn't "never happened."

the ending

i keep coming back to that reddit comment. "it's just an operating system. use it or don't."

it's the least useful take and also the most useful one. omarchy generated millions in funding, a root escalation write-up, a hundred hours of youtube discourse, and when you strip it down it's an arch setup with strong opinions. if you want it, try it in a vm. if you don't, nobody's forcing you.

but the hype cycle is worth watching either way. because the next famous person to vibe-code a distro is going to inherit all of this: the money questions, the security questions, the culture war. omarchy is just the first one loud enough to break the internet.

i think i'll keep my fedora. but i finally understand why people are mad about a bunch of dotfiles.

Qwen-Image-2.1-Turbo: The 8-Step Image Model That Runs on Your GPU

Dishant Sharma — Sun, 11 Oct 2026 10:59:09 +0000

The top comment on the Qwen-Image-2.1-Turbo release thread said it better than I could: "I've been so impressed with Qwen Image 2.1 both in its quality and its speed that I wouldn't really have thought there'd be a need for a turbo." That comment showed up the same day the Turbo dropped. And then I ran the Turbo myself and understood why it exists anyway.

Here is the timeline, because the pace is the story. Qwen-Image-2.1 landed on September 20, 2026. Alibaba open-sourced a 7 billion parameter image model that does generation and editing in one place, with native transparency baked in. Nineteen days later, on October 9, they shipped Qwen-Image-2.1-Turbo, an 8-step version of the same model. Pro and Turbo APIs went live the same day. Two releases in three weeks.

I test image models the way everyone does now. I throw weird prompts, face swaps, and transparent logo jobs at them and watch them fail. Most fail in predictable ways. This one kept doing the thing I asked for, which is rarer than it sounds.

Why you should care: the weights are open, it runs on a mid-range GPU, and it does transparent PNGs and character sheets that used to cost you a paid tool and an afternoon.

The interesting part is not the quality. It is what the model does that other open models simply do not.

What it actually is

Here is a question people keep asking: what is Qwen-Image-2.1, exactly? People on r/StableDiffusion had a whole thread titled "Any info on what Qwen Image 2.1 actually is?" because the numbering made no sense to anyone. Qwen-Image-2.0 was never open-sourced, and a 3.0 was already floating around. But here is the honest version.

It is a unified text-to-image and image editing model. The visual generation component is about 7.1B parameters across 32 Single-Stream DiT layers. That is roughly a third the size of the original Qwen-Image, which ran 20B. Someone on Hacker News nailed the reaction: "It's a heck of a lot smaller than Qwen-Image 1."

The smaller size is the point. Alibaba calls it the "most balanced and cost-effective" model in the series, and for once the marketing is accurate. Mixed-granularity attention and prefix KV cache reuse keep the compute low. Output goes up to 2K, around 2752 pixels depending on aspect ratio.

Small model, big output, open weights. That combination is what got everyone excited in the first place.

The transparent PNG that changes everything

The feature nobody predicted was native transparency. Qwen-Image-2.1 generates images with a real alpha channel. No background removal tool, no manual masking, no fighting with rembg.

I asked for a sticker-style character on a fully transparent background. It came out with the alpha channel intact. No green screen, no white box, no cutout artifacts. That has been a genuinely annoying part of the workflow for years, and this model just deletes it.

Use cases stack up fast:

sticker packs with real transparent layers
product shots you can drop onto any background
game assets with proper alpha
extracting subjects straight out of photographs

People on r/StableDiffusion called it "a new standard for open models." That is not hype, it is the one feature where this model is ahead of basically every open competitor.

Editing that finally works

The editing side is where this thing gets stupid good. It accepts up to 10 reference images at once. You can point at local edits with circles, painted annotations, or separate masks. And it keeps identity consistent for people and products.

The r/StableDiffusion crowd found the killer use immediately: "this is the first open-source image editing model capable of creating Character Design Sheets." Character sheets used to mean hours in a drawing tool or a paid service. Here it is a prompt and ten reference images.

One gotcha nearly everyone hits: this model is meant to be sampled without guidance. The CFG knob that makes Stable Diffusion behave actually hurts here. Turn it off and results get more cohesive, more photorealistic, truer to the source. Most tutorials written before this release tell you the wrong thing.

Turbo: eight steps to the same picture

Qwen-Image-2.1-Turbo uses the exact same 7B architecture. The only real change is the sampler: 8 denoising steps instead of the usual ~30ish, and the checkpoint ships its own recommended sampling schedule that Diffusers loads automatically.

On a modern GPU, that means images land in a couple of seconds. Reddit's reaction to the base model's speed was already "I wouldn't have thought there'd be a need for a turbo," and yet the Turbo genuinely feels different in interactive work. You stop waiting between iterations and start treating the model like a brush.

Day-0 support arrived everywhere at once: ComfyUI, Diffusers, vLLM-Omni, SGLang. And the hardware bar is friendlier than it looks. bfloat16 weights want roughly 14-16GB of VRAM, but quantized builds (INT8, FP8, GGUF) run in as little as 4-8GB. The FP8 build is what most people are actually running.

The version numbers are a mess and I love it

Can we talk about the naming for a second? Qwen shipped a 3.0 before this 2.1, the 2.0 was never open, and nobody outside Alibaba can explain the sequence. The HN thread had people openly confused about what they were downloading. It is the most unhinged version numbering in AI right now and I kind of respect it.

And then there is the official example prompt. The README's flagship demo prompt is a roughly 700 word description of a hand-drawn chemistry study poster about iron displacing copper, complete with reactivity series ladders, electron shell diagrams, and a footnote about "Cu²⁺ ions." Subscripts and all. Some engineer at Alibaba wrote that thing by hand and I need to know how long it took them.

That is the version of this release I did not expect: a small fast model with a silly official example and version numbers that make no sense. Genuinely endearing.

The honest part

Here is what nobody in the demo videos tells you. Qwen-Image-2.1 is not Apache 2.0. Alibaba dropped the permissive license for the Qwen Research License, and the open source community noticed immediately. The HN thread hit around 483 points and a solid chunk of the debate was about the license. Reddit put it bluntly: "the license is very restrictive. They said they're working on it."

If you want to ship a commercial product, read the fine print before you build your pipeline on this. That is a real constraint, not a footnote.

The other honest thing: do not run this locally just to feel cool. If you have a GPU with 14GB+ of VRAM, sure, quantize and go. If you do not, use the hosted API and move on. The API is fast, it is cheap, and you will not spend a weekend fighting CUDA versions.

And the turbo is not free. Eight steps means slightly less fine detail than the full sampler. For 90% of prompts you will not be able to tell. For the last 10%, keep the base checkpoint around.

One last thing

I keep coming back to the transparent PNG. Every other feature in this release is an improvement on something that already existed. Text models render text better, editing models edit better, speed models are faster. Alpha channel support is the only one that removes an entire step from a real workflow.

That is the kind of thing that makes a model stick. It is not the biggest release of the year, and it is not the one with the most impressive single image. It is the one that changes how you actually work, on hardware you already own, with weights you can hold in your own hands.

The next Qwen release is probably two weeks away at this pace. I will be there with a weird prompt ready. I hope the version number makes sense that time.

Pi Durable Shipped, Then the Hype Took Over the Timeline

Dishant Sharma — Sat, 10 Oct 2026 13:11:36 +0000

Originally published at dishantsharma.dev.

Within hours of the launch, a Hacker News comment called Pi Durable a Cloudflare acquisition target. That is the kind of sentence that makes a project's week. It also makes the people who built it nervous, because it means the hype has started.

Pi 1.0 shipped on October 1, 2026, from Earendil. Tucked into the same release was Pi Durable, an experimental package for agents that can run for days, crash, and pick up exactly where they stopped.

The internet did what it does. Half the reaction was a love letter to minimalism. The other half was people pointing out that this thing will happily run commands without asking you first.

what pi durable actually is

Here's a question people always ask: what is a harness?

A harness is storage plus the machinery that runs one or more agent conversations in parallel. It holds the transcript, calls the models, runs the tools.

Every coding agent has one. Most of them hide it.

Pi Durable makes the harness the point. It checkpoints the transcript, the tool calls, and the model requests into storage before executing anything. If the process dies, your laptop sleeps, or the container gets redeployed, a new process opens the same storage and keeps going.

The context window is a non-issue, because compaction summarizes older messages before they overflow. Even a conversation with tens of thousands of messages stays bounded.

That is what the word durable means here. Not reliable. Not smart.

Just remembering.

it survived the crash. nobody restarted it. it just kept going.

That is the whole pitch, in one sentence.

I ran the idea past a friend who runs agents in production. His reaction was the honest one. He said a crash-resumable agent sounds great until you remember the agent is the thing that caused the crash.

The Pi team's answer is that the harness only guarantees the state survives. It does not promise the agent behaves. That is a narrower claim than the hype suggests, and it is the more useful one.

the design that makes people argue

What actually happens when a harness is this minimal is that everybody has an opinion.

Pi's core is tiny. A system prompt under 1,000 tokens and four primitive tools: read, write, edit, bash.

No plan mode. No sub-agents. No MCP by default.

If you want a permission manager or undo support or web access, you write a small extension or install one.

That is why the reactions split. One crowd calls it the Neovim of harnesses, minimal and endlessly extensible. The other crowd points out the obvious: out of the box, it executes commands natively, with no confirmation, in your real environment.

Both crowds are right, and the difference is who you trust with a terminal.

The minimalism crowd has a real argument on their side. Bloated system prompts create instruction conflicts, and conflicts create agents that ignore half their rules. A 1,000-token prompt does not have that problem, because there is nothing to conflict with.

the cloudflare moment

The most interesting reaction was the infrastructure one.

Pi Durable ships storage backends for memory, SQLite, and JSONL. The SQLite and JSONL code has no Node APIs, so with a small adapter it runs on Bun or inside a Cloudflare Durable Object.

Cloudflare shipped PiHarness in its Agents SDK the very next day. That was the fastest adoption I have seen a new agent framework get, and it tells you how hungry platforms are for durable state.

The Hacker News take was blunt. Nothing like durable objects with containers really exists elsewhere, so Pi Durable makes Pi a good acquisition target for Cloudflare.

I have seen this pattern before. A minimal tool gets adopted by a platform, and the platform adopts it back.

It is not a bad thing. It is how the tool reaches people who never would have found it on Hacker News, and it is a warning that the roadmap may stop belonging to the community.

	Pi Durable	Monolithic agents
System prompt	Under 1,000 tokens	Heavy, bundled
Token use per turn	About 3x less	High
Persistence	Durable, survives crashes	Tied to one session
Safety defaults	None, asks nothing	Pop-ups and sandboxes
Setup	You assemble it	Download and run

the source that agents can read

The whole source, without tests, is about 15,000 lines. Roughly 150,000 tokens with GPT, 250,000 with Claude. The storage backends alone are 3,000 lines, which an agent can usually skip.

That number matters more than it looks. A harness small enough for a model to understand means a model can debug it, extend it, and reshape it.

That is the malleability the Pi people keep using. The harness is not a fixed product. It is something you assemble, and your agent is part of the assembly line.

The storage interface is small enough to implement on anything, a key-value store or Postgres. One process owns a storage at a time, and other clients attach to that process. That design is why the Cloudflare integration took a day instead of a quarter.

The honest reviews land in the same place. Setup friction is real. The tool loop can spiral when a task is not dead simple.

But the token savings and the crash survival are not hype, and people who run local models love it.

the honest part

Do not run this against your main machine on day one.

Out of the box there is no permission layer. Read, write, edit, bash, all native, no questions. That is a feature if you are building a harness, and a hazard if you are just curious.

Start with the memory or JSONL backend, run it on a throwaway task, and add the permission extension before you let it touch real files. The minimalism is the product. The safety is a component you install.

I did exactly that on a dead side project. It took an evening to get a loop running and another evening to trust it enough to point it at a scratch repo. Worth it, but not a five-minute setup.

And if you need batteries included, Pi is not for you. Claude Code and its peers will keep being heavier and safer and friendlier. That is a real tradeoff, not a marketing gap.

The biggest misconception is that durable means dependable. Pi Durable survives crashes. It does not promise the agent makes good decisions, only that it remembers where it stopped.

what i keep coming back to

The acquisition comment is still stuck in my head. Not because it is true, but because of what it revealed.

A tiny harness with clean storage interfaces is exactly the shape of thing platforms buy. And the Pi team knows it. They built the interfaces small on purpose, then let Cloudflare integrate the next day.

That is the hype working correctly. The tool did the work, the community argued, the platform noticed, and the timeline got a story.

The agents will be long-running either way. It was only ever a question of where they run, and who owns the storage when they wake up.