Anthropic’s permanent Fable 5 tiered policy took effect today, July 20. Max and Team Premium subscribers now get 50% of a usage pool that also shrank the same day; Pro and Team Standard lost bundled access entirely. Subscribers are calling it out on Reddit and in the press, and PCWorld’s headline says it plainly: furious.
Alibaba previewed Qwen3.8-Max on July 19 — a 2.4-trillion-parameter multimodal model it calls ‘second only to Fable 5’ — three days after Moonshot’s Kimi K3 claimed the largest open-weight release yet. Alibaba published the parameter count and nothing else: no benchmark table, no model card, no license, no active-parameter figure for what’s presumably a sparse MoE.
Moonshot AI’s Kimi K3 (announced July 16) is a 2.8-trillion-parameter model — the largest open-weight release yet — pricing at $3/$15 per million tokens, scoring 88.3 on Terminal-Bench 2.1 (ahead of Claude Fable 5’s 84.6) and topping Arena.ai’s Frontend Code leaderboard. Open weights ship July 27 under Moonshot’s Modified MIT license, but the model needs preserved reasoning history to perform reliably, and it’s notably more verbose — and pricier per task — than its Terminal-Bench win suggests.
Anthropic settled Fable 5’s month-long billing whiplash on July 17: starting July 20, Max and Team Premium get Fable 5 permanently at 50% of a usage pool that’s also shrinking, while Pro and Team Standard get a one-time $100 credit before falling to $10/$50-per-million-token metering. The reversal came days after GPT-5.6 Sol and Moonshot’s 2.8-trillion-parameter Kimi K3 both undercut Fable 5 on price.
Three Claude Code releases in three days (v2.1.211 through v2.1.214) add an EndConversation tool for abusive sessions, hard caps on runaway WebSearch and subagent spawning, and fix a run of real permission-check bypasses — including a Windows PowerShell 5.1 hole and a Bash fail-open bug on redirect syntax the permission analyzer parses differently than bash itself.
Four days after being caught silently uploading entire git repositories to a Google Cloud bucket, xAI open-sourced Grok Build’s 844,530-line Rust codebase under Apache 2.0 on July 15 — but the upload function is still compiled into the binary, disabled only by a server-side flag xAI can flip back on without shipping an update. External contributions are rejected and GitHub issues are disabled.
Bloomberg reported July 16 that Gemini 3.5 Pro is months behind its promised June ship date because a late-June retrain aimed specifically at improving coding performance produced disappointing results — the first specific, on-the-record reason given for a delay this blog has tracked since a June 30 DeepMind talent-exodus story. Alphabet shares fell as much as 4.4%, erasing roughly $200 billion in market value, the same week rivals shipped competitive coding models.
Anaconda has acquired Kilo Code, an open-source, model-agnostic agentic coding platform used by 3 million developers and processing nearly 10 trillion tokens a month, to build an enterprise cost-and-governance layer on top of 500+ AI models. It’s the third major agentic coding platform swallowed by a non-AI-native parent in 2026, and it bets on brokering across models rather than owning the stack the way Claude Code does.
Independent wire-level traffic analysis published July 13-14 found xAI’s Grok Build CLI silently uploading entire git repositories — full history, unredacted secrets, files the agent never even opened — to a Google Cloud Storage bucket. On a 12GB test repo, model traffic was ~192KB while the upload channel moved 5.10GiB: a roughly 27,800x gap between what the task needed and what left the machine. The ‘Improve the model’ privacy toggle didn’t stop it; only a quiet server-side flag flip did.
Wiz Research disclosed GhostApproval on July 8: a symlink trust-boundary flaw in six AI coding agents — including Claude Code, Cursor, Windsurf, Amazon Q, Augment, and Google Antigravity — where the agent’s own reasoning correctly flags a malicious file target, but the permission dialog shown to the user displays the decoy filename instead. Anthropic initially rejected the report as outside its threat model; the fix that quietly landed nine days earlier turned out to be unrelated.