Welcome back. Last year, a group led by OpenAI researchers dropped "AI 2027," a roadmap predicting what AI would look like over the next two years. Fast forward to today, and 19 of the 53 tracked predictions are confirmed or ahead of schedule. Check out the full timeline to see what’s changed.
Also: A detailed guide on harness engineering, fixing your home wifi with Codex, and how to humanize AI PRs of your dev team.
Today’s Brief
How Databricks manages AI coding costs
How Apple could win the AI race
Save token costs by prompt caching (tutorial)
Field guide on Grok 4.6 (cookbook)

TODAY IN PROGRAMMING
SpaceXAI’s new model targets long-running agents and large codebases: Elon Musk's AI lab just unveiled Grok 4.6, a model specifically designed to handle multi-step workflows. Whether it researches a codebase, structures an app, or iterates based on feedback, this model performs reliably over the long haul. It’s currently available via Cursor, Grok Build, and the API at a rate of $2 per 1M input tokens. Devs are already giving this model a shot. Shopify CEO’s post about the model's animated reaction during a maintenance task is making rounds on the internet.
Alibaba open-sources its most powerful model to date: The Chinese tech giant just dropped a new version of Qwen3.8 on Hugging Face. The company claims the model goes head to head with the top frontier models on coding and agentic benchmarks. But there is a catch for devs: you will need a massive 4.9TB of storage to run it at full precision. Even with Unsloth’s 1-bit build (which trims that down to 397GB), you are still going to need some serious RAM. If you want to run this locally, a lighter 27B version will drop soon. More details here.
DeepSeek's flagship nears frontier coding at a fraction of the cost: The Chinese AI startup just moved V4 Pro from preview to general availability while maintaining its current pricing. It costs $0.435 per million input tokens and $0.87 per million output tokens, which represents a small fraction of the Fable 5 rate. The model supports a 1M token context window and tool calling, allowing it to integrate seamlessly into your agent pipelines. While it still trails slightly behind Fable 5 in agentic coding performance, these results come from the company's own unverified benchmarks.

PRESENTED BY AGENTFIELD
An open-source reviewer now places #2 of 42 on Martian's Code-Review-Bench, ahead of the commercial tools, at ~10x lower cost per review.
PR-AF plans the review per PR, runs reviewer agents in parallel, and verifies every finding against your source before it posts, so no hallucinated comments. 0.706 recall, roughly 3x more valid findings. Apache 2.0, self-hosted, runs on any open or closed model.

INSIGHT
So your AI coding costs keep climbing, but you cannot contain it. Here’s how Databricks manages it:

Source: Databricks
The wall everyone hits. Agentic coding can help your engineering team ship up to 10x faster, but the costs can spiral even quicker. If you aren't careful, your AI bill will eventually outweigh the actual value it delivers. Databricks calls this a solvable engineering problem. According to their internal playbook, teams that successfully manage these costs lean on four main strategies, ranked here by impact:
Lean on lower-cost models. Start with the cheapest model that clears your quality bar, including open-source options like GLM. Most everyday coding doesn't need the most powerful model available. This can cut costs by 50% or more.
Route work automatically. Developers shouldn't have to pick a model for every task. A smart router can send each job to the cheapest model capable of handling it.
Swap caps for friction. Hard budget restrictions should be a last resort because they can punish the engineers getting the most value from these tools. Instead, show spending in real time, add warnings for usage spikes, and quietly shift work to cheaper models when necessary.
Trim the context. Even the cheapest models get pricey when you're feeding them too much data. Honestly, most of that context is being added by your coding harness, not the developer. If you tune your harness and cache settings, you can pretty much cut your generated tokens in half without seeing any drop in quality.
The starting point. Combine these levers, and unit costs can fall by as much as 90% without a quality hit. But you should start small. First, look at your team's spending, identify the models and tools driving the bill, and then tackle the biggest source first.
P.S. Databricks' full walkthrough covers the tooling, while its open-source Omnigent meta-harness lets teams experiment with model switching themselves.

OPINION
Databricks showed how they cut AI spend. Where's your cost coming from?

PRESENTED BY SONIOX
Soniox Text-to-Speech lets you create extraordinary voice experiences in 60+ languages with expressive control, exceptional precision, instant voice cloning, and ultra-low-latency streaming.
Direct whispers, laughter, hesitation, excitement, and emotion, or precisely speak phone numbers, email addresses, technical terminology, and multilingual text.
Built for voice agents, global products, customer support, media, and any application where speech needs to sound human and get every detail right.
$0.70 per generated hour.

IN THE KNOW
What’s trending on socials and headlines

Meme of the day.
WiFi Fix: A tech CEO pointed ChatGPT Work and Codex at his patchy home WiFi and let them troubleshoot the whole thing. Here's the prompt he ran (3.4K bookmarks).
Apple's Play: While US companies burn cash racing Chinese AI labs, this viral theory explains how Apple could win the AI race without ever building a model (574K views).
Fix AI slop: Ever noticed how AI-written PRs look polished but are actually a total mess? This post breaks down the fix that makes your agents' output actually make sense (5.5K bookmarks).
Reliable Harness: Smart models only get you so far. This guide reveals the harness engineering hacks you need to keep your AI agents running smoothly during long-running tasks.
Agent Fleets: Shopify’s CEO turned his screen into a Hollywood-style hacker terminal. But the open-source tool behind it is the real story, and it could change the way you run your AI coding agents (3.2K likes).

TOP & TRENDING RESOURCES
Top Tutorial
How to stop overpaying for agents by using Prompt Caching: You’ll learn how to build cache-friendly agent harnesses that keep prompts reusable and slash token spend. This tutorial covers how to avoid costly cache invalidation and make long-running agent workflows significantly cheaper to run across all major providers.
Top Tool
Omg.dev: You can now run coding agents like Claude Code or Codex locally on your machine and control them from your phone.
Trending Cookbook
Field guide on Grok 4.6 (by a Cursor engineer): AI models often struggle with complex tasks when they rely on long prompts or assume the work is done without checking the results. This guide solves that by using concise Grok 4.6 prompts paired with strict verification steps, ensuring the AI actively tests and fixes its own output.

AI CODING HACK
How to stop Claude Code degrading mid-session
Claude Code performance tends to dip during long sessions. If you try a full refactor in one go, the second half usually ends up much sloppier than the first.
To fix this, a senior engineer shared a sizing rule using his /to-tickets command. It breaks a large spec into smaller tickets that each fit perfectly within a single session.
Step 1: Install his skills plugin.
/plugin install mattpocock-skillsStep 2: Run “/setup-matt-pocock-skills” once per repo and pick a tracker: GitHub, Linear, or local markdown files.
Step 3: Estimate the total tokens the task needs. It's better to overestimate. Divide that by 150K, the range where he says agents stay sharp, and round up. For example, a 1M token refactor would require 7 tickets.
Step 4: Run “/to-tickets” on your spec, check the count roughly matches your math, and implement one ticket per fresh session.
P.S. Get 50+ AI coding hacks for Claude Code, Cursor, and Codex here.

IN CASE YOU MISSED IT
Our most-clicked story from yesterday
Check out this GitHub repo to remove Claude’s watermarks from your content.
Grow customers & revenue: Join companies like Google, IBM, and Datadog. Showcase your product to our 300K+ engineers and 150K+ followers on socials. Get in touch.
What did you think of today's newsletter?
You can also reply directly to this email if you have suggestions, feedback, or questions.
Until next time — The Code team




