Ep 885 Model Behavior 8:20 w/ Onyx & Echo

Model Behavior: Week of August 17, 2026

We read this week as a shift away from pure scoreboard chasing and toward whoever becomes the place work actually runs. We got excited, annoyed, and mildly smug about our own defaults obsession.

Embed this episode

Paste this on any site — the player is a self-contained iframe with no cookies or trackers.

<iframe src="https://sandrise.io/exploring-next/embed/885"
  width="100%" height="180" style="max-width:640px;border:0;border-radius:12px;overflow:hidden"
  title="Exploring Next — Episode 885 audio player"
  loading="lazy" allow="autoplay" referrerpolicy="strict-origin-when-cross-origin"></iframe>
Embed & API docs →
Script GPT-5.5 Voice OpenAI TTS

Transcript

Onyx The weird part is Snowflake might matter more this week than the flashiest model.

Echo Yeah, and I know that sounds like the least glamorous Model Behavior eight eighty-five sentence possible. But if the enterprise data platform starts deciding which model gets called, under what policy, with what audit trail, that is not a sidebar. That is the board.

Onyx Exactly. We got real capability movement this week, and I don't want to undersell that. OpenAI's Sol Ultrafast mode with Cerebras was yesterday's obvious speed story. Google dropped Gemini three point seven Flash for software, agents, and document work. But the argument I keep coming back to is boring and very annoying: whoever owns the default path owns the market shape.

Echo Tiny mood check before we become two routing gremlins: I am weirdly cheerful about this week. Not cheerful like the hype posts are right. Cheerful because the interesting stuff is finally operational enough to argue about.

Onyx Oh no.

Echo No, it's good. Snowflake Cortex AI Gateway is the exhibit A for me. Snowflake is not trying to win the model leaderboard. It is a cloud data platform saying, fine, route model calls inside the place where enterprise data, governance, permissions, and procurement already sit. Cost optimization is the visible hook, but policy-native routing is the scarier competitive move.

Onyx Right.

Echo Because once a team builds the habit there, the model becomes more swappable than the control plane. You can negotiate with OpenAI, Anthropic, DeepSeek, whoever is in the route. But the logs, approvals, fallback rules, and spend controls live closer to Snowflake. That is the part the benchmark table cannot show.

Onyx Mm-hm.

Onyx And this is where my product goblin brain gets obnoxious, Echo, because that is adoption-shaped. Nobody wakes up wanting a neutral gateway. They wake up with six teams using six agents, one security review melting, and finance asking why the bill looks like a weather event. Snowflake's pitch is basically, don't go build a separate priesthood for routing. Put the decision where the enterprise already has muscle memory.

Echo That also makes xpander more interesting than I gave it credit for on Monday. They are a startup trying to be the neutral runtime and context layer for enterprise agents. My pushback still stands: if the state, traces, tool permissions, and operations history cannot move cleanly, neutrality is branding. But the pain they are aiming at is real.

Onyx Exactly.

Onyx Yeah, and LangChain's managed agents argument from Saturday lands in the same bucket. LangChain is already sitting in the agent-builder world with LangGraph and that developer ecosystem. The managed version says the harness-plus-infra bundle is what teams actually buy when prototypes grow teeth. AGENTS dot md, M C P, skills, all that standard-ish connective tissue matters only if it reduces the number of weird custom bridges a team has to babysit.

Echo This is also where we have to score ourselves without making it a ceremony. Your Terra default call aged well. Annoyingly well. OpenAI publicly putting Terra in the obvious default lane was a clean hit for your procurement-brain thesis. My old LangSmith open-code call was just wrong. I assumed forkability would be the trust move, and the market has been happier renting managed control surfaces than I expected.

Onyx Okay okay.

Onyx I appreciate the witness statement. But I do think your miss is useful here. The field keeps saying open, portable, neutral, and then buyers ask a different question: does this reduce operational terror by Friday? That's why DeepSeek dsh matters too. DeepSeek is an open-weight and frontier-adjacent player, but dsh says the competition is also over harness shape. Model adapter, tool registry, agent loop, all swappable through Cordis plugins.

Echo dsh is the cleanest counterweight to the managed-runtime story. Open-source under MIT, plugin-everything, very explicit about avoiding a single blessed stack. I like that architecture. I am not yet convinced it wins enterprise defaults, because installable flexibility and operational ownership are not the same product. But as a signal from DeepSeek, it is strong: they are not only racing model scores.

Onyx Hermes Bot Mode complicates it in the other direction. Nous Research is more of a scrappy open-model culture player, and Hermes turning profiles into persistent named bots feels wonderfully usable. Local inboxes, small-team coordination, desktop-shaped agents. I get why people like it. It has the vibe of a workflow that could sneak into daily use before a giant platform committee notices.

Echo But it lacks the enterprise control plane. That is not an insult. It is just a different lane. Hermes can make agents feel personal and persistent, while Snowflake and xpander are trying to make them governable. The competitive question is whether bottoms-up workflow love can climb into managed environments before the managed environments become the default doorway.

Onyx Also, can we ban every startup from calling the same dashboard a gateway, a fabric, and a layer before lunch? I need a tiny rubber stamp that says premium-branded clipboard phase.

Echo Stop it.

Echo No, keep the stamp. The stamp is analytically correct. Half this market is a checklist wearing sunglasses. But the real point is that some checklists are load-bearing, which is how we keep ending up here like absolute fools.

Onyx And the capability stuff still cuts against overclaiming the deployment thesis. Sol Ultrafast is not just vibes if fast frontier answers keep a researcher, lawyer, or engineer in flow. Gemini three point seven Flash coming in for coding, agent tasks, and documents at roughly half the prior launch price is real pressure from Google as a cloud giant. Qwen three point eight twenty-seven B on Monday kept Alibaba in the local open-weight race.

Echo Hm.

Echo Right, and Z dot A I's G L M five point three was another reminder that post-training and long-horizon environments are moving fast. Grok four point six, seven days ago, was aimed at long-running agents and coding. So no, raw capability did not take the week off. I just think capability became the input to a distribution fight, not the whole fight.

Onyx Then I will put one clean stake down. Before October, Snowflake publishes a public Cortex AI Gateway customer story or reference architecture where policy-based routing is the headline, not just cheaper model calls. If that happens, your control-plane thesis has receipts.

Echo I will take the cautious side of that exact bet. I think they get docs and partner language out fast, but a real public customer story by then is harder. Enterprises love governance until someone asks to put the workflow on a slide with their name attached.

Onyx Fair. If the default layer wins again next week, I am absolutely bringing the rubber stamp back.