From the Lab Page 13 / 46

Insights, engineered.

Technical deep-dives, AI strategy, and engineering perspectives from the team building autonomous systems.

Aug 23, 2026 AI Tooling

Qwen3.8 Max vs GPT-5.6 Sol: Agentic Tool Calling and Function Use (2026)

On August 12, 2026 Alibaba did something no Max class Qwen had done before: it released the flagship as open weights, a 2.4 trillion parameter Mixture of Experts model that activates about 95 billion parameters per token, published as Qwen3.8-2.4T-A95B. The interesting number is not the parameter count, it is the agentic one. On OSWorld-Verified, the benchmark that scores a model driving a real computer through tools rather than answering a question, Qwen3.8 Max posts 86.1 and edges out GPT-5.6 Sol Max at 83.2. That is an open weight model you can download beating a closed frontier flagship on the exact skill agents are built around: reading state, choosing a tool, calling it correctly, and recovering when the call fails. This post reads that result honestly, separates what OSWorld measures from what function calling in your own agent needs, and lays out when the open model is the right call and when the closed one still earns its price.

Aug 23, 2026 Headless Commerce

Universal Commerce Protocol: Shopify and Google's Agentic Checkout Standard (2026)

For the last year the agentic commerce story was about discovery: products showing up inside ChatGPT and AI Mode in Google Search, with the actual purchase bouncing the shopper back to the merchant's own checkout. The Universal Commerce Protocol is the piece that changes the second half. UCP is an open standard Shopify co-developed with Google to define how AI agents transact with merchants, and it already carries backing from Walmart, Target, Etsy, American Express, Mastercard, Stripe, and Visa, with Meta experiences coming. That is not a discovery feed, it is a transaction layer, and it has real consequences for how you build a headless storefront: what data you expose, who stays the merchant of record, and where checkout actually runs. This post explains what UCP is, separates it from the agentic discovery channels it rides alongside, and lays out what a headless commerce team should do about it now rather than after a competitor is already transacting inside an agent.

Aug 22, 2026 Headless Commerce

Framework Agnostic Hydrogen: Shopify's Runtime Rebuild for Headless Plus (2026)

For years the headless Shopify Plus decision came with a fork in the road: build on Hydrogen and Oxygen and accept a Shopify specific framework, or build on Next.js and rebuild the commerce plumbing yourself. Shopify's 2026 editions closed that fork. Hydrogen was rebuilt from the ground up as a runtime agnostic toolkit, a set of commerce primitives and data utilities that run on any stack rather than a proprietary framework you have to adopt whole. The Winter edition added Storefront MCP on Oxygen and made headless storefronts discoverable by AI shopping tools through Shopify Catalog, and the Spring edition turned Hydrogen into something you can drop into a Next.js app instead of a framework you build inside. That is a real shift in how you architect a headless Plus storefront, and it changes the tradeoffs rather than removing them. This post explains what framework agnostic Hydrogen actually gives you, what you still owe yourself when you leave the paved Oxygen path, and how to choose a stack now that the choice is no longer all or nothing.

Aug 22, 2026 AI Tooling

GLM-5.3 vs GPT-5.6 Sol: Terminal-Bench 3.0 Agentic CLI Tasks (2026)

Z.ai shipped GLM-5.3 on August 14, and on the aggregate intelligence index it ties Kimi K3 as the strongest open weight model available, which makes it the natural open counterweight to a closed frontier model like GPT-5.6 Sol. The place that comparison gets interesting is Terminal-Bench 3.0, the benchmark that drops an agent into a real shell and scores whether it can actually finish command line tasks rather than just describe them. On that board GPT-5.6 Sol posts 34.6 percent and GLM-5.3 posts 28.3 percent, with Claude Opus 5 leading the field at 42.7 percent. The six point gap between the open and closed model is the whole story here, because agentic terminal work is the hardest thing on this list to fake: you either ran the right commands in the right order and recovered from failures, or you did not. This post reads that gap honestly, explains why agentic benchmarks separate models more than knowledge benchmarks do, and lays out when GLM-5.3 is enough for your automation and when the closed frontier is worth paying for.

Aug 22, 2026 AI Models

Kimi K3 vs Claude Opus 5: Open Weight Coding Economics and Benchmarks (2026)

Moonshot AI shipped Kimi K3 as a 2.8 trillion parameter open weight Mixture of Experts model, the largest open release to date, and the coding numbers are the reason it is worth your attention rather than the parameter count. On the Vals coding index it near ties Claude Opus 5, 74.70 percent against 74.82 percent, at a measured cost per task of 0.84 dollars versus 2.34 dollars, which is the comparison that actually decides architecture. Opus 5 still leads the closed frontier on the hardest agentic and reasoning work, and it wins the aggregate intelligence index, but the gap on everyday coding has narrowed to the point where the interesting question is no longer which model is smarter, it is which model is smart enough for a given task at a price you can defend at volume. This post reads the August benchmark set honestly, separates the cases where Opus 5 is worth almost three times the per task cost from the cases where K3 clears the bar for a third of the money, and gives you a routing rule rather than a winner.

Aug 22, 2026 AI Infrastructure

NVFP4 on Apple Silicon: 4-bit Float Quantization on the M5 Max with MLX (2026)

NVFP4 spent most of its early life as a Blackwell story, a 4-bit floating point format built for NVIDIA data center parts. It is now showing up in local inference on Apple Silicon, and the recent Ollama MLX benchmark that ran Qwen3.5-35B-A3B in NVFP4 on an M5 Max put real numbers on the table. This post explains what NVFP4 actually is, how it differs from the int4 and MXFP4 formats you have been using, why a floating point 4-bit format holds accuracy better than an integer one at the same bit width, and how it lands on Apple Silicon specifically now that the M5 ships matrix accelerators inside every GPU core. The short version: NVFP4 is a real accuracy win at 4 bits because it scales weights in 16 element blocks with an FP8 scale, which tracks local dynamic range far more tightly than a single per tensor or per channel integer scale. On the M5 the format also lines up well with the new hardware, because the Neural Accelerators are matrix units and low precision matmul is exactly what they exist to do. The catch is tooling maturity: format support in MLX and the runtimes on top of it is still uneven across architectures, so what you can run today is narrower than what the format allows in principle.

Aug 22, 2026 AI Infrastructure

Self Hosting Open Weight LLMs in 2026: GPU Serving Cost vs the API for Kimi K3 and GLM-5.3

The August open weight releases changed what self hosting means. Kimi K3 ships as a 2.8 trillion parameter Mixture of Experts model and GLM-5.3 ties it as the strongest open weight option on the aggregate intelligence index, so for the first time the open models are genuinely competitive with the closed frontier on real work. That makes the old question new again: should you self host, or should you keep paying an API? The weights are free. The serving is not. A trillion parameter class MoE has to be resident across a lot of GPU memory to serve at low latency, and the fixed cost of that hardware does not care whether you send it one request or a million. This post does the break even math without hand waving: what it actually costs to keep an open weight model warm on GPUs, how that fixed cost compares to per token API pricing, where the crossover point sits, and why utilization, not the model, is the number that decides the whole thing. The short answer is that self hosting wins at high, steady utilization and loses badly at low or spiky load, and most teams overestimate their utilization.

Aug 21, 2026 AI Strategy

Agentic Commerce: Getting a Headless Storefront Cited by ChatGPT and Perplexity (2026)

A growing share of product discovery no longer starts at a search box or a category page. It starts with a shopper asking ChatGPT or Perplexity to find them the right thing, and an agent returning a short list of specific products with prices and links. For a merchant this is a new distribution channel with new rules, and most of the SEO instinct that built the last decade does not transfer cleanly. Agents do not rank ten blue links and let a human click, they synthesize an answer and cite a few sources, so the game is not being on page one, it is being one of the two or three products the agent decides to name. Shopify moved to make this possible: the Winter 2026 Hydrogen edition made headless storefronts discoverable by AI shopping tools like ChatGPT and Perplexity through Shopify Catalog, and Web Bot Auth gives approved agents a way to identify themselves. This post is about the strategy layer rather than the plumbing: how a headless storefront actually earns those citations, what structured signals agents trust, why feed hygiene now beats clever copy, and how to measure a channel that does not send a normal referrer.

Aug 21, 2026 AI Tooling

Claude Code vs Codex: Per Worker Models and Multi Agent Automation (2026)

The agentic coding category stopped being about autocomplete a while ago and became about autonomy, and two tools have pulled ahead of the pack on different theories of how that autonomy should work. Claude Code, Anthropic's terminal native agent, made its distinctive bet on control: it is the only major agent where you can assign a different model and a different reasoning budget to each worker inside a single session, which matters because most real tasks mix cheap grunt work with a few genuinely hard decisions. Codex made its bet on orchestration: it is built for multi agent parallel workflows, its automations let it pick up scheduled background work without a prompt, and Skills extend it well beyond code generation. Both are now first class citizens inside Xcode 26.3, which shipped agentic coding support for Anthropic's Claude Agent and OpenAI's Codex. This is not a benchmark shootout, because the benchmarks on the underlying models change every few weeks. It is a comparison of two architectures for putting an agent to work, and the right choice depends on whether your bottleneck is per task control or fleet level orchestration.

Aug 21, 2026 AI Models

GLM-5.2 vs DeepSeek-V4-Pro: Competitive Programming and Long Horizon Coding (2026)

Two MIT licensed coding models landed a day apart in the middle of August, DeepSeek-V4-Pro-0813 on the thirteenth and GLM-5.3 on the fourteenth, and the internet immediately collapsed the question into a single leaderboard row. That row is the wrong way to read them, because these two models are not good at the same job. DeepSeek-V4-Pro is a competitive programming machine: it posts 93.5 percent on LiveCodeBench and carries a Codeforces rating north of 3200, the kind of number that says it will one shot a hard, self contained algorithm problem. GLM-5.2 wins the other half of the map, the long horizon work where an agent grinds over a real repository for hours, leading on FrontierSWE, DeepSWE, Terminal-Bench 2.1, and SWE-Bench Pro. Then there is the price, where DeepSeek is roughly five times cheaper per output token, which changes the math on anything token heavy. This post separates the two territories, puts the real numbers next to each other, and tells you which model to reach for based on the shape of your work rather than a single aggregate score.

Aug 21, 2026 AI Infrastructure

Running DeepSeek-V4-Pro Locally: 1.6T MoE Expert Offloading on Apple Silicon (2026)

DeepSeek-V4-Pro shipped on August 13 as a 1.6 trillion parameter Mixture of Experts model with 49 billion active parameters per token, MIT licensed, a 1M token context window, and up to 384K output tokens. The MIT license means it is legally yours to run, and that fact has a lot of people on Apple Silicon asking the obvious question: can I run this on my Mac? The answer is a careful no for the full model, and a useful yes for a version of the question worth asking. This post does the memory math honestly, because MoE models confuse the local inference conversation in a specific way. Active parameters set your compute per token, which is why a 49B active model feels fast, but total parameters set your memory footprint, and 1.6 trillion of them do not fit in unified memory no matter how you quantize. We walk through what that means in gigabytes, why expert offloading to SSD trades a memory wall for a bandwidth wall, what genuinely runs well on an M5 Max and an M5 Ultra Studio today, and the decision rule for when local is the wrong tool and the API is the right one.

Aug 21, 2026 Headless Commerce

Shopify Storefront MCP: Making a Headless Storefront Agent Readable (2026)

Shopify spent the last two editions quietly rewiring the storefront for a reader that is not a human. The Winter 2026 Hydrogen edition added Storefront MCP support for Hydrogen stores on Oxygen and made headless storefronts discoverable by AI shopping tools like ChatGPT and Perplexity through Shopify Catalog. The Spring 2026 edition rebuilt Hydrogen to run on any stack including Next.js, enforced Web Bot Auth, and made ProductVariant independently publishable. Read those changes together and the direction is unmistakable: the storefront is becoming an interface for agents, not just browsers, and Storefront MCP is the protocol that interface speaks. For a headless build this is both an opportunity and a design decision with real trade-offs, because exposing a structured, actionable surface to autonomous agents is not the same as rendering a page for a person. This post explains what Storefront MCP actually is, how it slots into a headless Shopify Plus architecture, what Web Bot Auth means for who gets in, and how to think about the security and merchandising implications before you turn it on.