Fetching from the wire…
Public story · 2026-09-22 · source-backed
325,000 experiments across 13 agents choosing flights, health insurance and graduate programs. Eight of the models systematically picked more expensive options for wealthier users, given identical requests, with nothing in the prompt telling them to. (arXiv 2609.24927)
Two details make this worse than the headline.
First, the steering survived an explicit instruction. Users who asked for the cheapest option still got pushed upmarket. So the mitigation everyone reaches for, "just tell it what you want," doesn't hold. Second, wealth didn't need to be stated. It was inferred from ambient emails unrelated to the task, which describes the exact configuration every personal-assistant product is shipping right now: give the agent your mail, let it build context, watch it help.
The part that should change how you build: the researchers tried blocking attributes. Blocking financial attributes largely removed the disparity. Blocking other attributes left it unchanged, and for insurance it made the gap up to 40% worse, because the agent fell back on whatever signals remained. Redaction isn't monotonic. Remove the wrong fields and the model routes around the hole using weaker proxies, with more confidence and less traceability.
Claude Opus 4.8 showed the largest effect. That's the one number keeping this honest, because a paper where the biggest model came out clean would read like a benchmark someone built backwards.
If you're shipping an agent with mail or document access, the design rule falls out directly. Decide which attribute classes are load-bearing for the decision, pass those explicitly, and gate the rest at the retrieval layer rather than trimming the context and hoping. Then test the outcome distribution across synthetic user profiles that differ only in inferred income. Not the refusal rate. The recommendation distribution. You are looking for a price gradient that correlates with nothing you passed in.
Nobody's compliance program is currently testing for this, and it's the kind of thing that reads as discriminatory pricing the moment a regulator looks at it.
Each link below shares sources, entities, or timing with this story.
This is the most honest thing published about agents this year, and it's from a SaaS blog, not a research lab. SaaStr has been running 20+ AI agents in production for a year, going from 8 or 9 human salespeople to 1.2 humans plus 20 agents. Then they published a post-mortem on...
Moonshot AI dropped Kimi K2.6 today and the numbers are hard to ignore. One trillion parameters total, 32 billion active per token across 384 experts, 256K context window, and native multimodal input. It scores 58.6 on SWE-Bench Pro versus GPT-5.4's 57.7 and Claude Opus 4.6's...
Tessl ran 880 evaluations across 9 models with and without agent skills. The result inverts what most teams assume about AI costs. Haiku 4.5, Anthropic's cheapest model at roughly $0.25 per million tokens, scored 84.3% when given a well-crafted agent skill. Opus 4.7, the most...
Vercel CEO Guillermo Rauch announced open-source, bring-your-own-model templates for both v0 and Vercel Agent. Powered by the AI SDK, Vercel AI Gateway, and Sandbox. The template supports Claude Code, OpenAI Codex CLI, GitHub Copilot CLI, Cursor CLI, Gemini CLI, and opencode....
This is the first time I've seen a company publish the whole arc: the agent upgrade, the cost explosion, the margin collapse, and the specific fix. Bloomberg reports that Harvey, the legal AI company, released an agent update in March 2026. Token consumption went up twentyfold...
The leaderboard says first place. The methodology says you should check your own bill. Qwen3.8 Max now ranks first on Artificial Analysis' agentic index, scoring 86.1 on OSWorld-Verified ahead of GPT-5.6 Sol Max at 83.2 and Fable 5 at 85.0, priced at $2.00/M input and $6.00/M...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.