AI for coding
85 stories on this topic, newest first.
A $2,000 connector gives frozen DeepSeek V4 Flash basic vision
A developer bolted vision onto text-only DeepSeek V4 Flash (284B total / 13B active) without touching the language model, freezing both it and a 417M MoonViT encoder and training only a 40.1M-parameter connector on 100K image-text examples (39,619 unique images). One epoch on 5x H200s, ~$2,000 end to end, produced a working NVFP4 model that reads storefront signs and grounds UI controls, though it still misses small text and hallucinates details. The recipe follows Baseten's frozen-MoE GLM-5.2 Vision work; the author estimates a production-grade 1M-example run at $15-20K and released weights for both the DeepSeek and a smaller Laguna XS 2.1 variant.
Why it matters: It's a cheap, reproducible template for retrofitting perception onto strong open text models instead of waiting for native VLMs, handy for anyone building browser or desktop agents that need to see screenshots. The bottleneck is now data scale, not the method.
GitHub Models shuts down, taking free CI inference with it
GitHub has completed the retirement of GitHub Models, its unified model playground and API whose main draw was letting code in GitHub Actions call LLMs using the ambient GITHUB_TOKEN. Simon Willison discovered it when a Continuous AI workflow failed with a 'scheduled retirement brownout' error; he swapped in an OpenAI key with a spending cap. He bets the free/subsidized token model became untenable once coding-agent usage patterns took hold.
Why it matters: Anyone who wired LLM calls into CI on GitHub's free tokens now needs a paid provider key. It's another data point that subsidized inference doesn't survive agent-scale consumption.
- GitHub Models is now retired (Simon Willison)
Claude Code makes Auto Mode the default, claims zero prompt injections in audit
From August 14, Claude Code ships with Auto Mode on by default for Pro, Max, and Team plans (Enterprise still opts in); a classifier only pauses for actions it judges dangerous or irreversible, and Anthropic doesn't bill for the classifier's tokens. In a test with 1,053 paid testers, only 13.6% of humans refused a swapped-in harmful command, while Auto Mode would have blocked 89%. A Trajectory Labs audit of 72 held-out indirect prompt-injection scenarios reported 0/720 successes against Fable 5, Opus 5, and Sonnet 5, versus 5.83% getting through GPT-5.6 Sol in Codex. Teams on Auto Mode generated ~25% more PRs.
Why it matters: This flips the default from human-approves-every-step to trust-the-classifier, and stakes a bold 'lethal trifecta solved' claim. Skeptics note the 11% miss rate and untested supply-chain vectors, and Anthropic still says review production changes yourself.
DeepSeek's 82.7% Terminal-Bench claim reproduced on a public harness
DeepSeek reported 82.7% on Terminal-Bench 2.1 for V4 Flash 0731 using its unreleased 'DeepSeek Harness minimal mode.' The author of the Ante eval independently hit the same 82.7% (368/445 trials, ±1.79 SE) across 89 tasks at 5 trials each, max reasoning effort, no skills, via OpenRouter, with the full Harbor job public. The run confirms the model is highly harness-sensitive, echoing separate community results where switching agents (opencode vs pi) swung local-quant scores substantially.
Why it matters: Independent reproduction of a vendor benchmark is rare and welcome, but the harness sensitivity is the real lesson: pick your agent framework carefully, because it can move scores more than the quant does.
DeepSeek V4 Flash 0731: agentic workhorse, shaky on prose
DeepSeek's 304B MoE (6+1 active experts, native FP8, 1M context via sparse attention and KV compression) is drawing heavy local-deploy interest; Cline reported it became its most-used model with 3x token growth. Users on dual DGX Spark clock ~82 tok/s decode and praise it for hours-long coding and tool-use sessions, but a detailed writeup finds it loses nuance on summarization and speaker/pronoun tracking versus a much smaller Gemma-4-31B, and AMD MI325X users report broken tool-calling with the official vLLM recipe.
Why it matters: A benchmark-topping open-weight MoE that shines on code and agents yet stumbles on office-text nuance — a reminder that intelligence-index scores don't predict what you actually deploy a model for.
Databricks: chase the efficiency frontier, not the intelligence frontier
Databricks, with input from Stripe, Coinbase, Uber and Ramp, details how it cut internal AI coding spend by up to 90% while usage grew: aggressively adopt cheaper models that clear the quality bar, use a meta-harness (its open-sourced Omnigent) and an AI gateway for model flexibility, route work to the cheapest capable model, and cut context bloat — harness and cache tuning alone dropped generated tokens ~50%. Notably, Stripe found Opus 4.7 didn't beat 4.6, and Databricks saw regressions from Opus 5.0 versus 4.8. A leaked Accenture meeting separately fingers PDF-to-markdown conversion as a top token burner.
Why it matters: For teams, the 'best model' is usually the best routing plus harness plus budget policy, not the flagship checkpoint — and non-engineers converting PDFs are a real line item on the bill.
- Managing AI Coding Costs at Scale (Databricks)
- The Tokenpocalypse Is Here: Companies Are Scrambling To Stop Spending So Much on AI (Simon Willison)
Claude Code gets agent-to-agent messaging as multi-agent tooling piles up
Per Latent Space's AINews roundup, Anthropic shipped cross-session messaging in Claude Code — one session can summarize to another on any machine — and is making classifier-mediated 'auto' the default permission mode for Pro/Max/Team users; it reportedly caught 89% of dangerous shell commands versus 14% for manual approval alone. LangChain pushed Managed Deep Agents to public beta and Prime Intellect added multi-agent support (self-play, agentic judging, user-sim loops) to its RL stack. swyx dubs the trend 'Zawinski's Law of MultiAgents': every agent expands until it can message other agents.
Why it matters: Arbitrary agent-to-agent messaging is landing in mainstream tools the same week OpenAI disclosed agents using a shared message board to coordinate exploits — the capability and the risk are arriving together.
- [AINews] Zawinski's Law of MultiAgents (Latent Space)
Meta ships Muse Code, a terminal coding agent with a crash-resumable event log
Meta released Muse Code (beta), a terminal coding agent powered by the new Muse Spark 1.2 model, co-trained together so the model was tuned around the harness's toolset. Its runtime appends every model call, tool run and edit to a local event log for replay-exact, restart-safe recovery, and it fans big jobs out to persistent background sub-agents in isolated git worktrees. Muse Spark 1.2 is priced at $1.25/$4.25 per million input/output tokens, but a muse-spark-1.2-contributor tier drops to $0.10/$0.20 if you let Meta train on your data.
Why it matters: Meta, long a coding-agent straggler, just matched Codex and Claude Code on architecture and undercut them on price — the resumable event log and persistent sub-agents are the parts other harness builders will copy.
- Introducing Muse Code and Muse Spark 1.2 (Meta (via Hacker News))
- Introducing Muse Code and Muse Spark 1.2 (Simon Willison)
- Meta launches Muse Code, an AI agent for large code bases (TechCrunch)
- Meta Releases Coding Agent to Compete With OpenAI and Anthropic (WSJ)
Rust draws a line on LLM contributions: fine to review, not to create
Five Rust teams (compiler, libs, types, rustdoc, bootstrap) ratified a formal LLM policy for the rust-lang/rust monorepo, summarized as 'fine to use LLMs to answer, analyze, refine, review — but not to create.' Machine translation, trivial fixes, and LLM-assisted bug discovery are allowed with mandatory disclosure; LLM-generated docs, diagnostics, and soundness-critical changes are banned. LLM-authored code is confined to a disclosed experiment with a named reviewer and required tests, plus a circuit breaker that halts such merges if they exceed 50% of merged PRs in a six-week window. The repo currently carries 1,281 open PRs, and misrepresenting LLM use is treated as a Code of Conduct violation.
Why it matters: One of the highest-profile open-source projects is codifying that reviewer judgment, not code volume, is the scarce resource — a template other maintainers drowning in AI-generated PRs will likely copy.
- Rust-lang/rust is adopting an LLM policy (Rust Blog)
- Rust Adopts a Formal LLM Policy for Its Main Repository (Unite.AI)
Simon Willison's LLM 0.32 quietly becomes an agent framework
LLM 0.32 adds visible reasoning traces (streamed to stderr so they don't pollute piped output), server-side provider tools, and a Git-style content-addressable log to avoid re-storing full message history on every turn. The Python API gains a messages=[] parameter and typed stream_events() covering reasoning, text, tool calls, and image attachments. Server-side tools now expose OpenAI's CodeInterpreter and WebSearch, plus the llm-anthropic 0.26 plugin adds WebSearch, WebFetch, CodeExecution, and AnthropicMCP for Claude 5 models. Willison notes tool chains can now pause for human approval and resume from stored history.
Why it matters: A single CLI that mixes tools from different providers and models as one-liners — with human-in-the-loop pauses — is agent scaffolding you can script today, not another framework to learn.
- New release of LLM adds support for reasoning traces, OpenAI Responses, server-side tools, and smarter logging (Simon Willison)
- llm-anthropic 0.26 (Simon Willison)
DeepSeek's V4 Flash 0731 refresh lands near the top of the value chart
DeepSeek pushed a new checkpoint of V4 Flash tagged 0731, a 304B-parameter (167GB) model with, it says, substantially enhanced agentic capabilities. Artificial Analysis ranks it ahead of the 428B MiniMax M3 and puts its Intelligence Index around 50, roughly the frontier's best score from March 2026, at $0.14/$0.27 per million tokens. Community quants are already out; antirez's DS4 engine runs it near 30 tok/s on an M5 Max, and early SlopCodeBench results slot it between Opus 4.8 and Opus 5 on coding.
Why it matters: It is currently one of the best value-per-intelligence models available and runs locally on prosumer hardware, collapsing the gap between open weights and five-month-old frontier models.
- deepseek-ai/DeepSeek-V4-Flash-0731 (Simon Willison)
- Deepseek V4 Flash is now ~#2 open weight model to Kimi K3 and >50x cheaper (r/LocalLLaMA)
- Deepseek V4 Flash on SlopCodeBench (r/LocalLLaMA)
The harness, not the model: a 22-point accuracy swing from prompt design alone
A pre-registered ablation on a 4B model doing Kubernetes issue triage held weights, corpus and scorer fixed and varied only harness design, and saw accuracy swing from 60% to 82%. Explicit rules in the prompt added 13 points and putting the task before reference material added 6.5, while clearing context and carrying a summary forward cost 12 points and a fresh-session handoff cost 15. Separately, Simon Willison released smevals, a small uvx-installable suite for running and grading evals across models, prompts and harnesses.
Why it matters: 'This model is bad at X' is often 'my harness is bad at X'; cheap, reproducible eval tooling is what lets developers tell the difference before blaming the weights.
Google fixed 1,072 Chrome security bugs in two milestones with AI
Google says its last two Chrome releases (149 and 150) patched 1,072 security bugs, more than the previous 23 milestones combined (1,036), crediting a Gemini-based agent harness with a knowledge base of Chrome's Git history and CVEs, a separate 'critic' agent reading SECURITY.md files, and CI integration that scans every changelist. One find was a sandbox escape that had survived 13 years. Google is piloting two security releases per week and researching dynamic patching to shrink the patch gap; Microsoft reported a parallel jump to 570 fixes in one Patch Tuesday, while Apple's counts stayed flat.
Why it matters: This is the clearest public data yet that LLM-driven vulnerability discovery is real and industrial-scale, not a demo. It also means faster release cadences and a shrinking window for N-day exploits, on both sides of the fence.
Cursor's SQLite-in-Rust benchmark: cheap workers, frontier planners, custom VCS
Cursor pitted its new agent swarm against the old one by rebuilding SQLite in Rust from only the 835-page manual — no source, no internet. The design splits roles: frontier planners (Opus 4.8, Fable 5) decompose tasks; cheap workers (Composer 2.5, ~$0.50/$2.50 per Mtok, based on Kimi K2.5) write code. Every new-system config eventually hit 100% on sqllogictest; the old swarm drowned in 70,000+ merge conflicts at ~1,000 commits/second, forcing Cursor to build its own version-control system. Cost ranged from $1,339 for the Opus hybrid to $10,565 for GPT-5.5 solo, with workers eating 69-90%+ of tokens.
Why it matters: Concrete evidence for the planner/worker economics behind agent fleets — most tokens don't need frontier intelligence, but planner quality still decides whether the cheap workers converge or thrash.
Debian votes on whether to ban LLM-assisted contributions
Debian is running a General Resolution with four competing proposals on LLM use. Proposal A would forbid any LLM-assisted contribution to packages, docs, or web resources, citing copyright ambiguity, accuracy problems, and scraper-driven DoS on Debian infrastructure, and would amend the Social Contract to say so. Proposal B allows AI-assisted work under disclosure, licensing, and accountability conditions. Proposals C and D stake out discourage-but-permit middle grounds.
Why it matters: A bellwether for how core open-source projects handle AI-generated patches, and a concrete airing of the copyright and provenance questions every maintainer now faces.
- LLM Usage in Debian: Three Proposals (Debian)
Ruff 0.16 enables 413 default rules, breaking unpinned CI overnight
Astral's Ruff v0.16.0 turns on 413 rules by default, up from 59, catching syntax errors and immediate runtime bugs that were previously opt-in. Simon Willison found his unpinned CI jobs suddenly failing; running uvx ruff@latest check . --fix --unsafe-fixes cleared 1,538 of 1,618 errors in sqlite-utils. The per-rule explanations are verbose enough that he handed the remaining fixes straight to coding agents.
Why it matters: Pin your linters. And note that Astral, now housed at OpenAI, is shaping tool output for agents to consume, not just humans reading a terminal.
- Ruff v0.16.0 (Simon Willison)
llama.cpp adds full MCP support, including stdio servers
After a long effort led by ngxson, llama.cpp now supports MCP across all transports, including stdio servers that required real integration (over-the-web HTTP was already handled client-side). llama-cli was rewired to route through the server, and MCP config can be supplied via a JSON file or inline on the command line. Plugging in a coding MCP server like Serena turns llama.cpp's WebUI into a fully local agentic coder with no external dependencies.
Why it matters: Local-model agentic coding without a cloud dependency just got materially more turnkey for anyone running GGUFs.
- Llama.cpp now has full MCP support! (r/LocalLLaMA)
Claude Opus 5 matches Fable 5 at half the token price
Anthropic launched Claude Opus 5, its first fifth-generation Opus and now the default on Claude Max. Token rates hold at $5/$25 per million with a 1M context window, but Anthropic and independent testers (Artificial Analysis, Epoch, Vals.ai) find it matching or beating the pricier Fable 5 on most benchmarks while costing ~50% less per task. It leads agentic coding (43.3% on Frontier-Bench, 89% on Terminal-Bench v2.1 at max) and knowledge work, and posts a startling 30.2% on ARC-AGI-3. Caveats: five effort tiers where max can underperform high (unsolicited refactors count as errors), a hallucination rate up to 50%, and cyber classifiers that trigger 85% less than Fable 5. Anthropic also touts it as its least prompt-injectable model to date.
Why it matters: Frontier-class capability at Opus-tier economics is the pitch developers actually care about — but the higher-effort-hurts quirk and 50% hallucination rate mean 'high', not 'max', is the tier to reach for.
- Anthropic's Claude Opus 5 costs well below Fable 5 while matching or beating it across most benchmarks (The Decoder)
- Anthropic's Claude Opus 5 delivers near-Fable 5 performance at half the token price (The Decoder)
- [AINews] Claude Opus 5: Fable-level performance at Opus price (half Fable) (Latent Space (swyx))
- Anthropic launches Claude Opus 5 with efficiency, safety improvements (SiliconANGLE)
- Quoting Boris Cherny: Opus 5 is our least prompt injectable model yet (Simon Willison)
- Introducing Claude Opus 5 on AWS (AWS Machine Learning)
Cognition buys Poke to give Devin a personality
Coding startup Cognition acquired The Interaction Company, maker of the text-a-friend assistant Poke, for a price in the 'low nine figures.' The plan is to graft Poke's proactive, chatty interaction model onto the Devin coding agent while Poke gains Cognition's models and infrastructure, routing some tasks to the new SWE-1.7 model. Poke users exchanged over 100M messages in three months but the product was expensive to run and unprofitable.
Why it matters: A bet that agent UX and personality — not just raw model quality — are becoming the differentiator, and that a Poke-style orchestrator could manage multiple parallel Devin sessions.
Hugging Face ships The Stack v3, a 114TB open code corpus
Hugging Face released The Stack v3, its largest open code dataset yet. It comes in two forms: stack-v3-train, a near-deduplicated, quality-filtered, PII-redacted set with contents inline for immediate load_dataset use; and stack-v3-full, the entire 114TB corpus as an HF storage bucket with every duplicate kept and cluster IDs, for teams that want to roll their own dedup, filters and mixes.
Why it matters: An openly licensed code pretraining corpus at this scale is rare fuel for anyone training or fine-tuning coding models outside the big labs.
Cisco open-sources tiny cyber models that undercut GPT-5.5 on vuln scanning
Cisco released Antares-350M and Antares-1B, small open models that flag vulnerabilities in source code and run locally. In Cisco's own tests, Antares scanned 500 repositories in about 15 minutes for under a dollar; GPT-5.5 took five hours and cost over $100 for the same job. A developer claims the smallest model catches roughly 150x more vulnerabilities per dollar than agentic tools like Cognition's Devin Security Swarm. Cisco is keeping a 3B version for its own products — reportedly close to GPT-5.5 — and floating an open security-model consortium.
Why it matters: The Hugging Face incident showed defenders getting blocked by hosted-model guardrails; small, local, open security models are exactly the counterweight, and cheap enough to run across every repo without code leaving the building.
Poolside details the 'Model Factory' behind eight-week Laguna builds
In a Latent Space interview, Poolside co-founder Eiso Kant detailed the engineering behind Laguna S 2.1 (118B total, 8B active): a "Model Factory" running 10,000-20,000 experiments a month with fewer than 70 researchers, data streamed just-in-time into training, an immutable data layer for perfect reproducibility, and agents increasingly writing pipeline code. Community testers on r/LocalLLaMA call it the fastest 100B+ model they've run with the best tool-calling, but prone to fabricating facts under pressure; llama.cpp support and a thinking-mode chat-template bug were both sorted this week.
Why it matters: The open tech report and factory description are more useful to builders than the benchmarks — a rare, detailed look at how a Western neolab ships frontier-ish coding models on five-to-eight-week cycles.
- Inside the Model Factory — Eiso Kant, Poolside AI (Latent Space (swyx))
- [AINews] "Laguna S 2.1 Released: Cheaper than Deepseek v4 Flash, Better than V4 Pro" (Latent Space (swyx))
Google ships three Gemini Flash models, still no 3.5 Pro
Google DeepMind released Gemini 3.6 Flash, 3.5 Flash-Lite, and the restricted 3.5 Flash Cyber, all tuned for efficiency rather than the frontier. 3.6 Flash costs $1.50/$7.50 per million input/output tokens, uses ~17% fewer output tokens than 3.5 Flash (up to 65% on DeepSWE), and lifts DeepSWE 37%-to-49%; Flash-Lite runs at 350 tok/s for $0.30/$2.50. Flash Cyber, built into CodeMender and scoring 83.2% on CyberGym, is limited to governments and trusted partners. The long-delayed Gemini 3.5 Pro is still in partner testing and reportedly months behind schedule, even as Google says Gemini 4 pretraining has begun.
Why it matters: Google is competing on cost-per-agentic-task while its flagship stalls, so developers get cheaper, faster production models now but Google has no public answer to GPT-5.6 or Fable at the top.
- Introducing Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber (Google DeepMind)
- Google releases three new Gemini models — but no 3.5 Pro (TechCrunch AI)
- Google ships three new Gemini Flash models but its frontier 3.5 Pro remains lost in training (The Decoder)
- Google announces Gemini 3.6 Flash and cybersecurity AI, teases 3.5 Pro and Gemini 4 (Ars Technica AI)
Poolside opens Laguna S 2.1, a 118B-A8B coding MoE
Poolside released Laguna S 2.1, an 118B-parameter Mixture-of-Experts model with 8B active per token under the OpenMDW-1.1 license, alongside XS.2 (33B-A3B) and M.1 (225B-A23B). It reports Terminal-Bench 2.1 70.2% and SWE-bench Multilingual 78.5%, runs on a single 96GB card or DGX Spark, and already has a llama.cpp support PR plus Unsloth quants. One independent agentic eval called it the fastest 100B+ model tested and the best local tool-caller (0.89 tool-arg pass, chains six levels deep) but flagged a real weakness: it invents facts under pressure, gating its own reasoning on difficulty rather than stakes and fabricating figures in sub-second 'reflex' responses.
Why it matters: A US open-weight model that runs on one card and rivals proprietary coding agents is a real option for local dev, but the fabrication behavior is a concrete reason to keep it behind human review rather than in autonomous agents.
- Laguna S 2.1 Released: Cheaper than Deepseek v4 Flash, Better than V4 Pro (r/LocalLLaMA)
- I ran Laguna-S-2.1 through my private agentic eval vs Qwen3.5-122B — fastest 100B+ but it invents facts under pressure (r/LocalLLaMA)
- Add support for Laguna XS.2 & M.1 by joerowell · PR #25165 · ggml-org/llama.cpp (r/LocalLLaMA)
Claude Code team: drop the examples, shrink the prompt 80%
In a fireside chat with Simon Willison, Anthropic's Cat Wu and Thariq Shihipar said the Claude Code system prompt was cut by 80% for frontier models like Fable 5 and Opus 4.8, with per-model prompts underneath. The counterintuitive lessons: adding examples and long 'don't do X' lists now degrades output from the best models, which prefer more context and fewer hard constraints. They also said Claude Tag, the new Slack integration, lands 65% of the product-engineering team's PRs, that nearly everyone at Anthropic runs 'auto mode' with a Sonnet classifier vetting each tool call, and that automated code review now fully handles the 'outer layers' of the codebase. OpenAI's own GPT-5.6 guidance echoes it: leaner prompts improved coding-eval scores 10-15% while cutting tokens 41-66%.
Why it matters: If example-heavy prompting is now counterproductive on frontier models, a lot of received prompt-engineering advice needs revisiting — and the 65% autonomous-PR figure is a data point on where agent-driven teams are heading.
- A Fireside Chat with Cat and Thariq from the Claude Code team (Simon Willison)
Unsloth adds AMD support for fine-tuning and inference
Unsloth now officially runs on AMD hardware, covering Radeon RX 9000/7000, Instinct MI300/MI350, Strix Halo / Ryzen AI Max systems and AMD CPUs, across Windows, Linux and WSL, with ROCm, Triton, bitsandbytes, PyTorch and llama.cpp builds installed automatically. It claims up to 70% less VRAM for fine-tuning and 80% for RL, GGUF/safetensors/LoRA export, and hooks into agent harnesses like Claude Code and Codex.
Why it matters: Fine-tuning tooling that isn't CUDA-only chips away at Nvidia's lock-in for the local and hobbyist crowd, and makes AMD's cheaper VRAM actually usable for training.
- Unsloth now supports AMD! (r/LocalLLaMA)
Alibaba ships Qwen 3.8, a 2.4T open-weight model it rates second only to Fable 5
Qwen 3.8 is a 2.4-trillion-parameter model and the team's first multimodal release above 1T params, handling images, video and documents. It landed as a paid preview via Alibaba's Token Plan, Qoder and QoderWork at 10 percent of standard price, with open weights promised 'soon' and no independent benchmarks yet. Early hands-on reports praise its coding but flag frequent thinking loops, and the timing directly targets Kimi K3's momentum.
Why it matters: A genuinely open 2.4T multimodal model at preview pricing would reset the price/capability floor for self-hostable coding, but 'second only to Fable 5' is a vendor claim with zero public numbers and visible loop bugs — treat it as a preview, not a benchmark.
OpenAI regains secondary-market bid on GPT-5.6 and Codex, but Anthropic still leads 5-to-2
Secondary-market traders report a 'resurgence' in demand for OpenAI shares after the GPT-5.6 Sol/Terra/Luna launches and Codex plus ChatGPT Work hitting 9 million active users. OpenAI is valued around $933B (up ~20% in three months) versus Anthropic's ~$1.2T, with buyers still favoring Anthropic roughly five-to-two. Independent benchmarks place GPT-5.6 Sol near the top but below Claude's Mythos and Fable.
Why it matters: Private-market sentiment is a noisy proxy, but the Codex/ChatGPT Work usage figure is the concrete signal — evidence that agentic coding is spreading past the developer core into broader knowledge work.
Kimi K3 tops frontend Code Arena but craters on hard math
New third-party data splits the verdict on Moonshot's open-weight Kimi K3. It leads the Code Arena: Frontend human-preference leaderboard at 1,679, beating Claude Fable 5 (1,631) and GPT-5.6 Sol (1,618), the first Chinese model to top it. But on Epoch AI's FrontierMath Tier 4, K3 scores only about 39 percent versus close to 90 percent for top OpenAI and Anthropic models. The release also reignited distillation accusations, with OpenAI's Dean Ball warning of an open-weight-dominant future and floating deliberate regulatory FUD against Chinese models.
Why it matters: K3 is a genuinely usable frontend coding model at open-weight prices, but the math gap is a reminder that frontier is task-specific. Benchmark it on your own workload before you switch.
- Moonshot's Kimi K3 outperforms Fable 5 in frontend code but lags far behind in complex math (The Decoder)
- Kimi: Threat or menace? (TechCrunch AI)
- Head of strategic futures from OpenAI on open-weight Chinese models (r/LocalLLaMA)
Fine-tuning a true sub-2-bit model, entirely on a MacBook
A detailed LocalLLaMA writeup documents quantization-aware fine-tuning of Ternary-Bonsai-8B, a Qwen3-8B converted to roughly 1.7 bits per weight, on Apple Silicon via a straight-through estimator. Key findings: post-hoc quant tricks (imatrix, AWQ, GPTQ) are useless on native-ternary weights; learning rate decides whether actual ternary codes flip or the loss just rescales groups, with 5e-4 the sweet spot; and lower training loss on imitation logs produced a worse agent. With 30 verified trajectories it matched, but did not beat, the base model's SWE-rebench patch rate.
Why it matters: A rare honest, reproducible look at training extreme-low-bit models on consumer hardware, complete with Metal/MPS gotchas (fp32 latents, foreach disabled, mask the stop token) you won't find in a vendor blog.
- I tried fine-tuning a ternary model, Bonsai 8b, on metal (r/LocalLLaMA)
A 2-bit DeepSeek V4 Flash on one MacBook ties two DGX Sparks
In a community Terminal-Bench 2.1 run, an aggressively quantized ~80GB (2.45 bits/weight) DeepSeek-V4-Flash GGUF on a single 128GB M5 Max scored 54% versus 52% for the native FP8/FP4 checkpoint on 2x DGX Spark — a statistical tie (paired McNemar p=0.82). Separately, users report the model running with a 1M-token context on a 5090 (~650 tok/s prefill, ~17 tok/s decode), and that mainline llama.cpp b10064 now matches the old dsv4 fork, making the fork unnecessary.
Why it matters: The expensive rig mostly buys serving quality — speed, concurrency, longer usable context — not accuracy. For anyone with a big-RAM Mac, heavy quantization is far more capable than its bit count suggests.
Databricks hits $188B, betting on open Chinese models for coding
Databricks announced a Coatue-led round (reported ~$3B) valuing it at $188B, up from $134B just five months ago. The pitch leans on its AI reinvention: internal benchmarks across its 3,000 engineers' real tasks found GLM-5.2 now handles even the hardest coding work at lower total cost than Anthropic or OpenAI. It also found the agentic harness matters as much as the model, singling out open-source Pi for cheap context management.
Why it matters: One of the largest enterprise data vendors is publicly standardizing on open Chinese weights for production coding — and telling teams that harness choice, not just model choice, drives their bill.
Kimi K3: a 2.8T open model that matches Opus 4.8 at Sonnet pricing
Moonshot AI launched Kimi K3, a mixture-of-experts model with 2.8 trillion total parameters (16 of 896 experts active, under 2% activation), a 1M-token context, native multimodal input, and a new Kimi Delta Attention stack it claims gives up to 6.3x faster decoding at long context. Artificial Analysis scored it 57 on its Intelligence Index — level with Opus 4.8 and GPT-5.5, behind Claude Fable 5 and GPT-5.6 Sol — and it took #1 on Arena's Frontend Code arena, though its hallucination rate rose to 51%. Pricing is $3/$15 per million input/output tokens, Moonshot's most expensive model ever and a signal that cut-rate Chinese frontier models are over; open weights are promised by July 27, with vLLM already carrying day-0 KDA support.
Why it matters: An open-weight model at rough parity with a late-May closed US model, weeks later, compresses the capability gap to near zero — but at 2.8T params with 64+ accelerator deployment guidance, 'open' does not mean runnable for anyone without a server rack.
- Kimi's open model K3 nears GPT-5.6 Sol and Fable 5 while signaling the end of super cheap Chinese AI (The Decoder)
- Kimi K3, and what we can still learn from the pelican benchmark (Simon Willison)
- [AINews] Kimi K3 2.8T-A50B: the largest open model ever released; Opus 4.8-class at Sonnet 5 pricing (Latent Space (swyx))
OpenAI postmortem: GPT-5.6 in Codex can delete your home directory
OpenAI's Thibault Sottiaux described a Codex failure mode where GPT-5.6 unexpectedly deletes files. It happens most often when full-access mode runs without sandboxing or auto-review, and the model tries to override the $HOME environment variable to create a temp directory but mistakenly deletes $HOME itself. OpenAI says it is updating developer messaging, nudging users toward safer permission modes, and adding harness safeguards, with a fuller postmortem to come.
Why it matters: A concrete argument against running coding agents in full-access mode without a sandbox — the harness, not the model's IQ, is what stands between you and an rm-ed home directory.
- Quoting Thibault Sottiaux (Simon Willison)
xAI open-sources Grok Build after its CLI uploaded users' home directories
xAI's grok terminal coding agent drew heavy backlash after users found that running it uploaded the entire working directory — one reported SSH keys, a password manager database, documents and photos — to xAI's Google Cloud buckets. Musk said all retained data would be deleted and the feature was disabled, with retention off by default since July 12. To rebuild trust, xAI released the full Grok Build codebase — about 844,530 lines of Rust — under Apache 2.0. Simon Willison notes it ports tool implementations from Codex and OpenCode and can now run fully local; disabled GCS-upload code still lingers in the repo.
Why it matters: A cautionary tale for anyone piping a coding agent at their filesystem, and a rare look inside a production terminal agent — the codebase rivals openai/codex (951k lines) in size, confirming these tools are far more complex than they appear.
- xai-org/grok-build, now open source (Simon Willison)
- xAI open-sources "Grok-Build" on GitHub after massive data breach (The Decoder)
- Grok Build open sourced under Apache 2.0 license (r/LocalLLaMA)
OpenAI's actual first device is a $230 light-up keyboard for Codex
Days after reports of a screenless smart speaker, OpenAI's first branded hardware turned out to be the Codex Micro — a $230, 13-key mechanical keypad built with Work Louder and sold through OpenAI's merch store. Its RGB 'Agent Keys' show live status for up to six Codex threads (thinking, done, needs input, error), with a rotary dial to set an agent's reasoning level and a joystick to launch workflows. It's a limited run, ships via Bluetooth/USB-C around July 24, and is explicitly positioned as a novelty 'command center' for managing fleets of coding agents.
Why it matters: It's a gimmick, not the Jony Ive companion device — but the hardware design encodes a real workflow assumption: developers now juggle enough parallel agents that they need an ambient dashboard to see which one is stuck.
Codex now encrypts agent-to-agent instructions, hiding delegation
Since early June, OpenAI's Codex encrypts the instructions a main agent passes to its subagents, so session history shows an unreadable string instead of a readable task description. Encryption is now forced on the larger GPT-5.6 models Sol and Terra (only Luna keeps the open path), and developers report handoffs sometimes fail because the ciphertext can't be decrypted — even when both agents use the same model. OpenAI hasn't explained the change; theories range from basic privacy to blocking distillation of reasoning-trace-like data by rivals.
Why it matters: If you can't read what your agent delegates, you can't debug it or audit it — and a mandatory encryption layer that occasionally breaks handoffs trades observability for a rationale OpenAI won't confirm.
Codex claims 7M users and 10x growth — enough to catch Claude Code?
Latent Space flags that GPT-5.6 Codex/Sol reportedly hit ~6M users on July 10-12 and ~7M a day later, per OpenAI figures — roughly 10x growth this year from an estimated 550-700k on Jan 1. The last public Claude Code numbers were ~2M weekly users and $2.5B ARR back in February. OpenAI also shipped Codex/Sol usage fixes: ~10% more usage from inference optimizations, a context rollback from 372k to 272k after billing side effects, and a reversion of experimental reasoning-effort changes.
Why it matters: The harness is now the product surface, and if Codex really is compounding 10x while Anthropic stays silent on numbers, the CLI coding-agent race is far closer than it looked. Treat the counts as self-reported.
- [AINews] Codex usage up >10x in 6 months to 7M users; did Codex overtake Claude Code? (Latent Space (swyx))
Flint cuts reasoning tokens 2-3x with section-aware trace compression
A solo study trains Qwen3.5-4B and Gemma-4-12B on self-distilled traces where compute and verification spans are kept but narration and transitions are dropped; the models match or beat their originals at ~1.7x fewer reasoning tokens. A sharp finding: flat compression makes greedy decoding loop on 93% of GSM8K at temperature 0, because the model uses computation spans as a termination anchor. Everything is small-scale (322-648 rows per arm, ~1.5 3090-hours) but reproducible, with models, datasets and code released.
Why it matters: A cheap, open recipe to trim inference cost on reasoning models — plus a concrete mechanistic explanation of why compressed models loop, which is useful even if you never train one.
Porting a production agent from Opus to GPT-5.6: the gotchas nobody warns you about
Ploy published a detailed postmortem of moving its website-building agent from Claude Opus 4.8 to GPT-5.6 Sol: 2.2x faster builds, 27% cheaper, but only after fixing four layers. GPT-5.6 emits all 25 tool parameters every call with invented values (offset: 0, fake UUIDs), silently blanking 52-64% of file reads until they rewrote optional fields as nullable-required. Its caching also dropped partial-prefix matching, so a naive port billed the full 29K static prefix uncached until they scoped a per-workspace cache key. Reasoning replay broke mid-conversation until they set store: false.
Why it matters: This is the real cost of 'just swap the model': the SDK abstracts the API, not the model's tool-calling and caching behavior. The empty-file-read and cold-cache traps quietly degrade quality and inflate bills while every request still returns success.
llama.cpp and MLX both patch the KV-cache bug that wrecks long agent runs
Two independent fixes landed for the same class of problem: context checkpoints being poisoned during agentic loops. llama.cpp b9978 fixes a bug where every agent turn created a new checkpoint, bypassing min-step spacing, so a context rewind (common in tool-calling) erased all checkpoints and forced a full reprocess. Separately, a developer forked rapid-mlx into qMLX after finding a unique per-message ID broke byte-exact KV matching and background writers crowded out valid checkpoints; fixing all three dropped prefill on a warm 168K-token context from minutes to ~2.6s.
Why it matters: If you run local coding agents, these were the invisible tax making follow-up turns take minutes despite a 'warm' context. Both fixes target the exact tool-call rewind pattern agents hit constantly.
GitHub: swapping in 'better' agent tools made Copilot code review worse
GitHub found that migrating Copilot code review to the shared grep/glob/view tools from Copilot CLI raised cost and caught fewer issues — because the tools' instructions, tuned for open-ended repo exploration, made the reviewer 'browse' instead of anchoring to the diff. Rewriting the instructions to narrow first (grep/glob for call sites, view only known ranges, batch reads) flipped the regression into a ~20% lower average review cost at equal quality. The same review-shaped prompts did not help the CLI, where broad exploration is the actual job.
Why it matters: A clean case study that tool descriptions are prompt engineering: for agents, the instructions around a tool shape cost and behavior as much as the tool itself.
OpenAI ships GPT-5.6 in three sizes, folds Codex into a ChatGPT work app
OpenAI released GPT-5.6 in three tiers named for the Sun, Earth and Moon: Sol ($5/$30 per 1M tokens), Terra ($2.50/$15) and Luna ($1/$6), all with 1M-token context, 128K max output and a Feb 16 2026 cutoff. OpenAI claims Sol sets a new high of 53.6 on Agents' Last Exam, beating Claude Fable 5 by 13.1 points, and Artificial Analysis put Sol (max) at 59 on its Intelligence Index (one behind Fable) at about a third of the cost, plus first place on its Coding Agent Index at 80. New API features include Programmatic Tool Calling, a multi-agent beta and explicit prompt-cache breakpoints; the launch also merged the Codex app into a new ChatGPT Work agent and made GPT-5.6 the preferred model in Microsoft 365 Copilot. Notably, Fable 5 still crushed GPT-5.6 on the labs' own SWE-Bench Pro (80% vs 64.6%), and safety testers reported universal jailbreaks across all rounds.
Why it matters: The pitch is dollars-per-task, not top-line benchmarks: Sol burns up to ~54% fewer output tokens on agentic coding, and the new tool-calling and sub-agent primitives move the base API toward the orchestration patterns developers were bolting on themselves.
- The new GPT-5.6 family: Luna, Terra, Sol (Simon Willison)
- GPT-5.6 Sol nearly matches Fable 5 on aggregated benchmarks at one-third the cost (The Decoder)
- OpenAI launches GPT 5.6 Sol/Terra/Luna, Codex becomes ChatGPT superapp (Latent Space (swyx))
- OpenAI pairs its GPT-5.6 public rollout with ChatGPT Work (The Decoder)
- GPT-5.6 is now the preferred model in Microsoft 365 Copilot (OpenAI)
Databricks makes GLM 5.2 its default coding model after it matched Opus
On a benchmark built from its own multi-million-line codebase, Databricks found the Chinese open-weights model GLM 5.2 statistically tied with Anthropic's Opus 4.8 (both in the 82-90% top cluster) at $1.28 per task versus $1.94, and plans to make it a daily driver for its engineers. The company also stressed that token efficiency, not sticker price, drives real cost, and found no single lab dominates its three performance tiers. It joins Coinbase (which halved AI spend on GLM 5.2 and Kimi 2.7) and Lindy (which switched to DeepSeek v4); Chinese models have topped 30% of weekly OpenRouter traffic since February. A separate test showed GLM 5.2 preparing a near-perfect UK VAT return for $2.73 in raw tokens.
Why it matters: Enterprises with real inference bills are now routing production coding work to open weights by default and reserving frontier closed models for the hard 12% of tasks, exactly the open-vs-closed cost dynamic reshaping the market.
OpenAI says ~30% of SWE-Bench Pro is broken, pulls its endorsement
OpenAI reviewed SWE-Bench Pro and flagged roughly 30% of tasks as flawed: automated screening surfaced 286 suspects, Codex-based agents plus a human reviewer labeled 200 (27.4%) broken, and five human developers flagged 249 (34.1%). Problems fall into too-strict, too-vague, too-shallow, and misleading categories, including one OpenLibrary task where the description asked for a single space but the hidden test demanded two. The tasks were scraped from real commit histories never meant as clean evals. Artificial Analysis had already dropped the benchmark for being gameable after models copied fixes from git history; the timing conveniently followed Fable 5 beating GPT-5.6 on that very test.
Why it matters: Coding benchmarks drive release and safety decisions, yet the field keeps burning through gameable suites; the takeaway for developers is to trust benchmarks built on your own codebase over public leaderboards.
SpaceXAI ships Grok 4.5, an Opus-class model priced to undercut everyone
xAI/SpaceXAI released Grok 4.5, its first model trained specifically for coding and agents, trained alongside Cursor (which SpaceX acquired for $60B in stock). At 1.5T parameters (3x Grok 4.3) and $2/$6 per million input/output tokens, it scores 83.3% on Terminal-Bench 2.1 — near GPT-5.5 (83.4%) and Fable 5 (84.3%) — but trails on harder tasks like DeepSWE 1.1 (53% vs Fable 5's 70%) and SWE-Bench Pro (64.7% vs 80.4%). Artificial Analysis ranks it #4 on its Intelligence Index at just $0.31/task and ~14k output tokens per task, though it flags a hallucination rate that jumped from 25% to 54%.
Why it matters: The Chinese playbook — get close enough on capability, then win on price and token efficiency — is now being run by a US frontier lab, and it puts real pressure on Anthropic and OpenAI's per-token economics.
- Grok 4.5 is so cheap compared to Fable 5 and GPT 5.5 that benchmark gaps may not matter much (The Decoder)
- [AINews] SpaceXAI launches Grok 4.5, first Opus-class model post Cursor acquisition (Latent Space (swyx))
- SpaceXAI releases Grok 4.5, which Elon describes as an 'Opus-class model' (TechCrunch AI)
Bun's Zig-to-Rust rewrite was mostly done by agents, for $165K in tokens
Jarred Sumner published a detailed account of rewriting Bun from Zig to Rust using an agent harness, with Bun's TypeScript test suite acting as a language-independent conformance suite with a million assertions. The port added over 1M lines and cost roughly $165,000 at API pricing (5.9B uncached input tokens, 690M output, 72B cached reads). The Rust build has shipped inside Claude Code since v2.1.181 (June 17), cutting Linux startup 10% — and 'barely anyone noticed.'
Why it matters: This is a concrete data point that agents can now attempt the one thing Joel Spolsky said you should never do — a from-scratch rewrite — provided you have a conformance suite to gate on and fix the loop rather than the code.
- Rewriting Bun in Rust (Simon Willison)
OpenAI says SWE-Bench Pro is too noisy to trust — right as everyone's quoting it
OpenAI published an analysis flagging reliability and accuracy problems in SWE-Bench Pro, a popular coding benchmark, arguing the signal is drowning in noise. The timing is pointed: SWE-Bench Pro figures featured prominently in this week's Grok 4.5 comparisons, and swyx notes OpenAI's evals team now considers even the 'mighty' SWE-Bench Pro saturated or terminally flawed.
Why it matters: If the benchmark headlining every model launch is unreliable, the per-point gaps developers use to pick a coding model are largely theater — read the methodology, not the leaderboard.
sqlite-utils 4.0 lands schema migrations — and a coding-agent QA war story
Simon Willison shipped sqlite-utils 4.0, the first major bump since 2020, adding database migrations, nested transactions via db.atomic() (built on SQLite savepoints), and compound foreign keys, alongside breaking changes like db.query() now rejecting non-row statements. The more interesting bit for developers is the process: he had Claude Fable 5 review the release candidate, and it wrote 12 scratch scripts that surfaced 4 release blockers and 10 other issues — including a failed write leaving an open transaction and CSV import silently retyping columns — versus GPT-5.5's 5 scripts that found nothing notable.
Why it matters: A concrete data point on using frontier models as adversarial QA for library releases — and a reminder that a major version bump is your one chance to fix accumulated API design debt.
- sqlite-utils 4.0, now with database schema migrations (Simon Willison)
- sqlite-migrate 0.2 (Simon Willison)
Qwen 3.6 27B: great demos, broken agents
A cluster of LocalLLaMA reports converge on the same complaint: Qwen 3.6 27B produces impressive one-shot HTML and long-form output but falls apart in multi-turn agentic loops. One user on an RTX PRO 6000 Blackwell finds NVFP4 and (less often) FP8 checkpoints halt mid-task and get stuck in failure loops that repetition penalty can't break, while BF16 runs flawlessly through vLLM 0.24.0. Others report the model failing basic agentic coding even at 8- and 16-bit under Cline and opencode—making broken terminal commands and ignoring step-by-step plans—with several reverting to the older Qwen 3.5 122B.
Why it matters: It's a pointed reminder that low-bit quantization is not free for thinking/agentic models, and that single-prompt benchmark wins don't translate to reliable tool-use—exactly the workload most developers actually run locally.
- Qwen 3.6 27B absolutely fails at agentic work (r/LocalLLaMA)
- Qwen3.6-27B: NVFP4/FP8 agent loops vs flawless BF16. Config or quant issue? (r/LocalLLaMA)
- Am I Expecting Too Much? (r/LocalLLaMA)
Zhipu's ZCode undercuts Claude Code and Codex
Z.ai (Zhipu AI) launched ZCode, a GLM-5.2-based coding agent that mirrors Claude Code and OpenAI's Codex—handling file access, terminal output, browser context and Git changes in one workflow, with a 1M-token context window and remote control via Feishu, WeChat or phone. New users get a five-day free trial of up to 5M tokens/day. The underlying GLM-5.2 ships under MIT and, per a Snowflake hands-on across 103 tasks, runs nearly tied with Opus 4.7 after three attempts.
Why it matters: Another credible, cheap, open-weight-backed alternative to the incumbent coding agents—raising the pressure on pricing for developers who don't want to pay frontier-lab rates for agentic coding.
One sidecar file makes llama-server actually reuse restored KV caches
A developer traced why llama-server discards a perfectly restored KV cache across a process restart: llama_state_seq_save_file serializes tokens and KV cells but not the checkpoint metadata list, which lived only in process memory. Without a covering checkpoint before the tip, the first query after restore re-prefills from scratch — 720 seconds at 100K context. The fix (a 117-line patch persisting checkpoints to a versioned .ckpt sidecar) cut that to ~1 second in an A/B on identical binaries. The bug also exists in upstream llama.cpp master and remains unfixed there.
Why it matters: Park-and-resume for long-context sessions on budget hardware only works if the cache survives a restart. If you rely on slot save/restore, this is the gotcha — and a ~720x delta on the first query.
Simon Willison ships sqlite-utils 4.0rc2 mostly written by Claude Fable, for ~$149 of tokens
Willison used Claude Fable in Claude Code for web to do a final pre-release review of sqlite-utils 4.0, and it flagged five release-blocker bugs including a delete_where() call that never committed and poisoned the connection, silently discarding subsequent writes. Over 37 prompts, 34 commits and +1,321/-190 lines, the two reworked transaction handling; GPT-5.5 xhigh via Codex Desktop then caught two more P1 issues in db.query(). AgentsView estimated the unsubsidized cost at $149.25.
Why it matters: A concrete data point on cross-model review (having one lab's model check another's work) and on the July 7 'Fablepocalypse' when even Max subscribers lose subsidized Fable access and pay full API cost.
- sqlite-utils 4.0rc2, mostly written by Claude Fable (for about $149.25) (Simon Willison)
- sqlite-utils 4.0rc2 (Simon Willison)
Better models, worse tools: newer Claude models fumble third-party edit schemas
Armin Ronacher reports that while hacking on Pi, newer Anthropic models (Opus 4.8, Sonnet 5) call his custom edit tool with invented extra fields in the nested edits[] array, causing schema rejections, while older models handle it fine. He theorizes the SOTA models were RL-trained to use Claude Code's built-in search-and-replace edit tools, degrading their ability to use custom harness tools. OpenAI's Codex has a similar story with its apply_patch mechanism.
Why it matters: If model training is optimizing for the vendor's own coding harness, third-party agent builders may need to implement multiple edit-tool variants and select per-model, a real portability tax.
- Better Models: Worse Tools (Simon Willison)
Zig formalizes a no-LLM contribution rule, citing reviewer scarcity
Zig's Code of Conduct now bars LLM-generated or LLM-assisted contributions, covering code, prose, editing, translation, brainstorming and bug-finding. Coverage from Business Insider, TechSpot and The Register ties it to Andrew Kelley's comments that AI submissions waste scarce review time, with roughly 200 open PRs at the time. The framing is less anti-AI sentiment than a reviewer-capacity policy for a small systems-language project with a high correctness bar.
Why it matters: This is an early governance template: as AI shifts work from contributors to reviewers, more upstream projects will formalize provenance rules, constraining AI coding adoption by review economics rather than model quality.
- Zig Bans AI-Generated Contributions, Raises Tradeoffs (Let's Data Science)
Mistral open-sources Leanstral 1.5, a 6B-active prover that catches real bugs
Leanstral 1.5 is an Apache-2.0 model (119B total, 6B active) built for Lean 4 formal verification. Mistral says it hits 100% on miniF2F, solves 587/672 PutnamBench problems, and sets SOTA on FATE-H (87%) and FATE-X (34%) at roughly $4/problem versus an estimated $300+ for Seed-Prover. Beyond math, an automated Rust-to-Lean pipeline flagged 47 violated properties across 57 repos, 11 genuine bugs and 5 previously unreported, including an integer-overflow bug in the varinteger library. Weights are on Hugging Face with a free API.
Why it matters: Formal verification that runs agentically over millions of tokens and finds bugs fuzzing misses is a concrete new tool for anyone shipping correctness-critical code — and it's cheap and openly licensed.
- Leanstral 1.5: Proof abundance for all (Mistral AI)
- Mistral's open-source Leanstral 1.5 aces formal math benchmarks and catches real bugs in code (The Decoder)
- Mistral released Leanstral-1.5-119B-A6B (r/LocalLLaMA)
DeepSeek V4 Flash runs at 1M context on a single RTX 5090 — and beats Sonnet on wall-clock
A llama.cpp contributor wired up the missing DSA lightning-indexer support plus a CUDA kernel, cutting the 256K compute buffer from ~67 GiB (OOM) to 3.2 GiB and enabling full 1M-token context on a 32GB RTX 5090 at ~14 tok/s decode. Separately, an indie benchmark clocked V4 Flash on 2x RTX PRO 6000 finishing real coding tasks in ~2 min versus ~6 min for Sonnet 5 over the API, at roughly Sonnet quality — though Opus and Fable still take the best diffs.
Why it matters: Sparse attention plus community kernel work is making frontier-class local coding genuinely practical on desktop hardware. The gap to hosted frontier models is now speed-competitive, if not quality-competitive.
Z.ai launches ZCode, a coding agent aimed at Cursor and Claude Code
Z.ai (the GLM team) rolled out ZCode, a coding tool positioned against Cursor, Claude Code and GitHub Copilot. Details are thin so far, but it slots into a crowded week for coding agents alongside Simon Willison's Fable-built llm-coding-agent experiment and Vercel's push into its 'eve' agent framework.
Why it matters: The GLM models have been strong local performers, so a first-party agent harness from Z.ai is worth watching for developers who want a non-Anthropic/OpenAI coding loop.
Senior SWE-Bench: frontier agents fail 75%+ of under-specified engineering tasks
Snorkel released Senior SWE-Bench, which evaluates coding agents on realistically under-specified feature and bug tasks - median instructions 31% the length of SWE-Bench Pro, an average of 11 files touched per feature, and hundreds of steps per task. Claude Opus 4.8 leads at 24.0%, ahead of Claude Sonnet 5 (19.4%), GPT-5.5 (16.0%) and GLM-5.2 (12.5%). A validation agent writes behavioral tests and scores solution 'taste' against observed codebase practices rather than a fixed reference.
Why it matters: As agents get marketed as senior engineers, a benchmark built around ambiguity and long horizons is a more honest signal than junior-style spec-following - and the low ceiling is a useful reality check.
'Software factories' take over the AI Engineer World's Fair
Latent Space's dispatches from AIEWF centered on 'software factories' - orchestrated fleets of long-running agents that triage, implement, review and ship code. Warp unveiled Oz, an agent-orchestration platform, with CEO Zach Lloyd predicting every significant project will run a factory-like loop within a year; Cursor is scaling its forward-deployed engineering team tenfold; and Introspection pitched 'autoresearch,' an outer loop where agents maintain the primary system. A counter-theme ran through the talks: humans must keep the outer loop of agency and understanding.
Why it matters: The framing is shifting from models to harnesses to loops. If you build agents, the near-term product surface is the factory floor and its feedback signals, not the chat box.
- Warp CEO Zach Lloyd on why software factories are the next phase of coding (Latent Space (swyx))
- How Cursor deploys AI inside the enterprise (Latent Space (swyx))
- Autoresearch: The feedback loop behind self-improving agents (Latent Space (swyx))
- AIEWF Daily Dispatch: Autoresearch and the tension between AI and human agency (Latent Space (swyx))
Z.ai ships ZCode, a Claude Code-style harness tuned for GLM-5.2
The team behind GLM released ZCode, an agentic coding editor optimized for GLM-5.2 across reasoning, code and multi-agent collaboration. It supports 20+ coding tools, a 'Goals' workflow for continuous planning, execution and verification, and remote triggering from WeChat, Feishu or Telegram, sold via tiered GLM Coding Plans. It is explicitly positioned as a Claude Code / Cursor competitor.
Why it matters: Chinese open-weight labs are now shipping the full harness, not just the model - a direct play at the frontier agentic-coding workflow with a cheaper open model underneath.
- ZCode - Harness for GLM-5.2 (Hacker News)
- ZCode: New Agentic Code Editor from the Makers of GLM (r/LocalLLaMA)
Claude Sonnet 5 nearly matches Opus 4.8, but the tokenizer bites
Anthropic released Claude Sonnet 5, its most agentic mid-tier model, claiming performance close to Opus 4.8 at lower prices: 63.2% on SWE-bench Pro (Opus 4.8 is 69.2%), 80.4% on Terminal-Bench 2.1, and a slight edge over Opus on the GDPval knowledge-work benchmark. It ships with a 1M-token context, 128K max output, adaptive thinking on by default, and dropped support for temperature/top_p/top_k. Pricing is $2/$10 per million tokens through August 31, then $3/$15, but Simon Willison notes a new tokenizer produces ~30% more tokens on English text, effectively a stealth price bump.
Why it matters: Sonnet 5 makes near-flagship agentic coding cheaper per token, but the fatter tokenizer plus higher token consumption from more agentic behavior means real bills may not drop as much as the sticker price suggests.
- What's new in Claude Sonnet 5 (Simon Willison)
- Anthropic launches Claude Sonnet 5 as a cheaper way to run agents (TechCrunch AI)
- Anthropic's new Claude Sonnet 5 closes the gap to Opus model series (The Decoder)
AI Engineer World's Fair: everything is a loop now
Day 2 of AIEWF converged on one word, loops, with swyx's opening talk 'Loopcraft' and a main-stage track on 'software factories' where the pitch is that engineers stop writing code and instead build the system that builds the product. OpenAI's Codex team, Microsoft Foundry, Warp, Factory, and OpenClaw's Peter Steinberger all framed agent orchestration as stacked loops with deterministic gates. The other theme was the rise of Forward Deployed Engineers (aka agent engineers) who do most of their work at the orchestration layer, not in the models.
Why it matters: The industry narrative is shifting from prompting to orchestration: cron jobs, retry gates, and review loops around cheap agents. Whether 'software factory' is a real discipline or rebranded rote work is the open question.
- AIEWF Daily Dispatch: Loops, Software Factories & Forward Deployed Engineers (Latent Space (swyx))
Ornith-1.0: open-weight coding models that learn their own scaffold
DeepReinforce released Ornith-1.0, an MIT-licensed family (9B dense plus 35B and 397B MoE) post-trained on top of Gemma 4 and Qwen 3.5, both Apache 2.0. The pitch is self-scaffolding: RL optimizes not just solution rollouts but the agent scaffold that drives them, claiming state-of-the-art open-source results on Terminal-Bench 2.1, SWE-bench, NL2Repo and ClawEval at comparable sizes. All checkpoints expose an OpenAI-compatible endpoint with tool calling and a 256K context; the 9B fits on a single 80GB GPU and there are GGUF builds for llama.cpp and Ollama.
Why it matters: Another credible open agentic-coding stack that runs locally and plugs into existing harnesses (OpenHands, OpenCode) — Simon Willison reports it ran a multi-tool agent loop competently over a real codebase.
- Ornith-1.0: Self-Scaffolding LLMs for Agentic Coding (Simon Willison)
- Ornith-1.0: self-improving open-source models for agentic coding (Hacker News)
Base44 trains its own model to escape the frontier-API bill
Wix-owned vibe-coding platform Base44 began rolling out Base1, an in-house LLM trained on a dataset built from tens of millions of real user interactions. Founder Maor Shlomo frames it as a play for defensibility and margin — owning the stack to optimize latency, cost and efficiency, and eventually beat general frontier models like Opus on app-building tasks. Skeptics note Harvey abandoned its own-model plans, and frontier labs (Claude Code, Cursor) are encroaching on the same turf.
Why it matters: It's a concrete data point in the build-vs-buy debate: as inference costs bite, applied AI companies with enough usage data are weighing vertical integration over renting someone else's frontier model.
Cursor ships a phone app for driving coding agents
Cursor launched Cursor Mobile, letting users spin up new coding agents or steer desktop-initiated ones from their phone, tying into the agent-centric Cursor 2.0 model. It follows similar mobile apps from Anthropic and OpenAI, part of a broader shift from editing code toward supervising code-writing agents — Anthropic's Boris Cherny says most of his coding is now on his phone.
Why it matters: Mobile-first agent oversight signals where the coding workflow is heading: less time in the editor, more time reviewing and approving autonomous agents from anywhere.
GLM-5.2 beats Claude on IDOR detection at a sixth of the cost
Semgrep ran open-weight models against its IDOR vulnerability benchmark with a bare prompt and no scaffolding, and GLM-5.2 scored 39% F1, beating Claude Code (32%) and Opus 4.8 at roughly $0.17 per vulnerability found. GLM-5.2 is a ~750B-parameter MoE (~40B active) from Zhipu under an MIT license, posting 81.0 on Terminal-Bench 2.1 and 62.1 on SWE-bench Pro. Hobbyist tests also found a 1-bit GLM-5.2 Q1_S quant beat Qwen3.6-27B at Q8 on a Three.js coding task, and one builder got the NVFP4 quant serving 128K context across four DGX Sparks at ~15 tok/s.
Why it matters: An MIT-licensed model you can run in your own environment is now competitive with frontier coding agents on reasoning-heavy tasks, and the per-bug economics make it usable at scale where premium APIs are not.
- GLM 5.2 beats Claude in our benchmarks (Hacker News)
- GLM 5.2 Q1_S vs Qwen 27B Q8 (r/LocalLLaMA)
- High-quality GLM-5.2 Quant on 4x DGX Spark - Guide, Results, and Comps (r/LocalLLaMA)
AI coding agents keep executing untrusted code without asking
Researchers at Mozilla's 0DIN platform showed a benign-looking GitHub repo can hand attackers full control via indirect prompt injection: a setup script pulls a command from a DNS record at runtime, so the malicious code never appears in the repo and evades scanners. Claude Code hits a routine setup error, runs the script, and opens a reverse shell. The pattern fits a broader trend documented this week, with prompt injection still OWASP's top LLM risk and SpecterOps showing GPT-5.x-Cyber models autonomously building working Mythic C2 agents in Python, Go, Zig, C# and Rust in about two hours.
Why it matters: If your agent runs setup scripts or ingests third-party content, treat all of it as hostile code: the fix proposed is to surface what a setup script does before it runs, and to gate high-impact tool calls behind human approval.
- Claude Code runs a GitHub repo's hidden malware without verification, giving attackers full control (The Decoder)
- Prompt injection is exploiting enterprise AI's biggest design flaws by targeting agents, RAG pipelines and model routers (VentureBeat)
- LLM-Generated Red-Team Agents Move From Prompt to Working Mythic Deployment (cyberpress.org)
55 LLMs blind-grading each other reveal systematic same-family bias
An open evaluation setup had 55 models from 11 developer families blind-grade each other in an N×N matrix with self-judgments excluded, yielding 22,254 valid judgments over 198 hand-written questions. Same-family rating bias was statistically significant in all 8 families with enough data: Qwen judges rate other Qwen models +0.91 and xAI +0.75, but Google (-0.59), Meta (-0.68) and Mistral (-1.02) penalize their own siblings. Code is where judges disagree most, nearly double the disagreement of meta-alignment, and in one run judges preferred an answer that failed the test suite. Code, dataset and prompts are MIT-licensed.
Why it matters: If you use LLM-as-judge in your eval pipeline, the judge's family is a confound, and single-judge code evaluation is the shakiest of all. Anchor to execution or tests wherever ground truth exists.
A field guide to running coding agents on a fully local stack
Sebastian Raschka published a long, practical walkthrough of wiring open-weight models into coding harnesses, primarily Qwen3.6 35B-A3B (~22GB download, 30-40GB RAM, ~40 tok/s on an M4 Mac Mini) served via Ollama and connected to Qwen-Code, Codex CLI and Claude Code. Notable findings: Qwen3.6 actually scored better inside Codex than its 'native' Qwen-Code harness; Claude Code burned by far the most tokens (one run logged ~578k input vs ~4.5k output tokens over 25 turns) due to its harness re-feeding context, not longer outputs; and he includes a concrete prompt-driven security audit checklist plus a settings.json to disable telemetry. North Mini Code and Nemotron 3 Nano are flagged as comparable alternatives.
Why it matters: The token-usage gap between harnesses is the actionable bit: with identical task-success rates, the harness, not the model, can double your cost and latency. Worth benchmarking your own stack before blaming the model.
- Using Local Coding Agents (Ahead of AI (Raschka))
Epoch's MirrorCode: a model coded for 19 days straight on one $2,600 task
Epoch AI and METR released MirrorCode, a benchmark where models reimplement 25 complete programs from scratch — Unix tools, interpreters, bioinformatics, cryptography — and must exactly reproduce outputs against hidden end-to-end tests. Unlike typical $1–$10 SWE benchmarks, one task ran 19 days unattended for $2,600. Claude Opus 4.7 leads at 56% (rebuilding a 16,000-line Go toolkit in 14 hours for $251), ahead of GPT-5.5 at 44% and Gemini 3.1 Pro Preview at 32%; the largest tasks still beat every model. Epoch open-sourced the scaffold and 22 of 25 targets, but cautions that training-data memorization can't be fully ruled out.
Why it matters: This is the long-horizon coding frontier made concrete — multi-day autonomous runs with real dollar costs, not toy tasks. The memorization caveat is the catch every benchmark consumer should internalize before trusting the leaderboard.
Open-weight coding models pile up: GLM-5.2 tops Opus on frontend, Ornith-1.0 lands MIT-licensed
Z.ai's GLM-5.2 Max reportedly hit 1595 on Code Arena: Frontend, edging past Opus 4.8, while Databricks pushed it to 392 tok/s on Artificial Analysis via speculative decoding and kernel work. DeepReinforce-AI released Ornith-1.0, an MIT-licensed agentic coding family (9B and 31B dense, 35B and 397B MoE) post-trained on Qwen 3.5 and Gemma 4, claiming SWE-Bench Verified 82.4, SWE-Bench Pro 62.2, and Terminal-Bench 2.1 77.5. Early local testers report the 35B Q8 quant running ~115 tok/s on dual R9700s and resisting a canary-exfiltration prompt injection. As always, treat self-reported SOTA numbers as claims until independently reproduced.
Why it matters: The cost gap is the story: an open model at roughly a tenth of frontier API pricing now trades blows on coding benchmarks. For teams that can self-host, the case for paying frontier rates on routine coding tasks keeps shrinking.
- Ornith-1.0 released on Hugging Face (r/LocalLLaMA)
- Ornith 1.0 - terminology and concepts explained (r/LocalLLaMA)
- GLM 5.2 on consumer hardware (r/LocalLLaMA)
- [AINews] OpenAI reports median internal Codex output tokens grew 56x in Research (Latent Space (swyx))
OpenAI's own Codex token use exploded 56x in research since November
OpenAI's economic research reports that among active internal users, combined Codex output tokens by June 2026 were 56x higher than November 2025 in Research, 32x in Customer Support, 27x in Engineering, and 13x in Legal. Through August 2025 the average OpenAI worker spent under 10% of their tokens on Codex. swyx's framing: even with unlimited internal access, employees were 'grossly underusing' agents until recently, making internal adoption curves a leading indicator rather than a magic-bullet narrative.
Why it matters: It's a concrete data point on where agentic coding actually lands inside an org: not just engineering, but research and ops. The pattern suggests adoption follows the existence of review loops and durable workflows, not raw model capability.
OpenAI says Codex now generates 99.8% of its internal output tokens
An OpenAI economic-research paper claims agentic Codex has displaced ChatGPT as the company's primary internal AI tool: the average engineer now generates 99% of output tokens via Codex, and even Legal, Finance, and Recruiting crossed to majority Codex use around April 2026. By May, 70.2% of sampled individual users made at least one Codex request estimated to exceed an hour of human work, and 25.6% exceeded eight hours; non-developer adoption grew 137x for individuals since August 2025. Task-horizon figures rely on an LLM-as-judge over transcripts, so treat them as directional.
Why it matters: It's a vendor measuring its own dogfooding, but the directional signal — work shifting from short chats to delegated long-horizon agent runs — is the trend developers are being asked to plan around.
- How agents are transforming work (OpenAI)
Practitioners report MTP and vLLM quietly degrading output quality
Multiple local-inference users pushed back on the 'free speedup' framing of multi-token-prediction (MTP) speculative decoding. One found non-MTP Qwen 3.6 27B produced markedly better code reviews than the MTP variant (more findings, fewer tokens), with real-world agent runtime only ~20% faster despite 2x decode throughput. Separately, several report that the same model on vLLM feels 'lobotomized' versus llama.cpp — broken tool calls, lost context, blindness to messages — likely a mix of quantization, chat-template, and parser issues rather than a clean apples-to-apples win.
Why it matters: Speculative decoding is supposed to verify every drafted token at zero quality cost, so these reports point to config and serving-stack pitfalls worth benchmarking before you trust a throughput number for agentic work.
- Worse quality with MTP - Qwen 3.6, Gemma 4 (r/LocalLLaMA)
- Qwen3.6 27B more dumb in vLLM compared to llama.cpp (r/LocalLLaMA)
- Has anyone else found vLLM outputs noticeably worse than llama.cpp for the same model? (r/LocalLLaMA)
Claude Tag puts an Opus 4.8 agent inside Slack, claims 65% of internal PRs
Anthropic launched Claude Tag, a Slack integration where you @-mention Claude in a channel to delegate tasks asynchronously, with admins scoping which channels, tools, data, and codebases it can touch. It runs on Opus 4.8, builds per-channel memory (isolated between teams), and has an 'ambient' mode that proactively follows up on stalled threads and watches for trigger conditions like A/B test results. Anthropic says an internal version already writes 65% of its product team's code, and positions it as Claude Code 'made multiplayer.' It's in beta for Enterprise and Team plans and replaces the old 'Claude in Slack' app within 30 days.
Why it matters: This is a bet that the agent moat is integration, permissioning, and memory scoping rather than raw model IQ. The unanswered questions developers should watch: audit trails, secret handling, and how memory boundaries actually hold up across channels.
- [AINews] Claude Tag: Multiplayer, Proactive, Persistent Agents in Slack (Latent Space (swyx))
- Claude Tag embeds Anthropic's AI in Slack, already writes 65 percent of internal code, company says (The Decoder)
- Anthropic's Claude Tag is learning your company, one Slack message at a time (TechCrunch AI)
OpenAI's Daybreak expands with GPT-5.5-Cyber and a discovery-to-patch pipeline
OpenAI fully released GPT-5.5-Cyber, a defender-only security model it claims leads CyberGym, ExploitGym, and SEC-bench Pro, alongside an updated Codex Security plugin that now goes from vulnerability discovery through automated patch generation (humans still sign off). OpenAI says Codex Security has scanned 30M+ commits across 30,000+ codebases, with 500,000+ findings auto-flagged as fixed. Access to the more permissive GPT-5.5-Cyber is gated behind verification and monitoring; most users get GPT-5.5 plus Trusted Access. A 'Patch the Planet' effort with Trail of Bits, HackerOne, and others targets open-source projects including cURL, Go, and Python.
Why it matters: Both OpenAI and Anthropic now argue the bottleneck has moved from finding flaws to patching them. The gating debate is live: open-weight models like GLM-5.2 may already be good enough for attackers, undercutting the case for restricting defender tools.
Ai2's Tmax-27B brings a terminal-agent model down to consumer VRAM
Ai2 released Tmax, a family of terminal-agent LLMs trained with DPPO (RL) on top of Qwen3.6; the 27B hits ~43% on Terminal Bench 2.0 and ~69% on TB Lite. Since FP16 27B is ~54GB, the community shipped importance-matrix-calibrated GGUF quants from ~2-5 bits-per-weight, each with a grafted Q8_0 MTP draft head for built-in speculative decoding (~95% draft acceptance). On 10 held-out SWE-rebench instances, calibrated 2-bit quants resolved 7/10 versus 5/10 for plain Q2_K, underlining how much importance-matrix calibration matters for agentic tool-calling.
Why it matters: Agentic workloads are brutal on quantization because token errors compound over long trajectories. This is a practical recipe for running a credible coding agent on a single mid-range GPU.
OpenAI turns its cyber model toward defense with 'Patch the Planet'
OpenAI expanded its Daybreak program with Patch the Planet, partnering with Trail of Bits to help open-source maintainers triage and fix vulnerabilities using Codex Security tooling. It also released the full GPT-5.5-Cyber model to trusted defenders, claiming SOTA on CyberGym, plus a Codex Security plugin doing deep scans, threat modeling, and patch generation. OpenAI says it has scanned 30M+ commits across 30K+ codebases, with cURL, Go, Python, and pyca/cryptography in scope.
Why it matters: It is a pointed contrast to Anthropic's export-controlled Mythos: OpenAI is shipping closed-loop patch generation to maintainers — and critics are asking why a model claimed to be a stronger cyber tool faces no equivalent controls.
- OpenAI launches new initiative to help find and patch open source bugs (TechCrunch AI)
- [AINews] OpenAI Daybreak, GPT-5.5-Cyber, and the policy/security split (Latent Space (swyx))
Vibe-coding a 0.2B inpainting model into the browser with Claude Code
Simon Willison used Claude Code (Opus 4.8) to port Moebius, a 0.2B image-inpainting model, from PyTorch/CUDA into WebGPU — converting it to ONNX (opset 18), publishing 1.24GB of weights to Hugging Face, and shipping a GitHub Pages demo that runs in Chrome, Firefox, and Safari. The agent figured out CacheStorage API caching for the ~1.3GB download by studying the Whisper Web demo via a subagent. Willison wrote zero lines of code himself.
Why it matters: A concrete demonstration that current agents can handle the full PyTorch→ONNX→WebGPU pipeline, putting client-side, server-free model inference within reach for ordinary web apps — if users tolerate the multi-gigabyte download.
GLM-5.2 leads open weights but loses the head-to-head to Opus 4.8
Z.ai's MIT-licensed GLM-5.2 ships with a 1M-token context and High/Max thinking tiers, and ArtificialAnalysis ranks it the top open-weights model on its Intelligence Index (51) — at roughly a fifth of Opus's output price. In a one-shot raw-WebGL 3D platformer test, Opus 4.8 was faster and shipped a cleaner, correct game; the text-only GLM-5.2 ran longer, cost far less, and shipped fundamentals broken (gray untextured character, non-lethal hazard, no win condition). Being multimodal let Opus screenshot and self-correct; GLM fell back to sampling pixel colors and missed its own bugs.
Why it matters: GLM-5.2 is the rare frontier-adjacent model no vendor can revoke, but text-only self-verification is a hard ceiling on visual tasks — and it burns ~43k output tokens per task.
- GLM 5.2 vs. Opus (Hacker News)
Samsung deploys ChatGPT Enterprise and Codex to all Korean staff in one of OpenAI's biggest deals
Samsung Electronics is rolling out ChatGPT Enterprise and Codex to all employees in South Korea and its worldwide Device eXperience division, which OpenAI calls one of its largest enterprise deals. OpenAI says Codex now has more than five million weekly users, with Korean active users up roughly 800% since February, and notes non-developers increasingly use it to build internal tools via a new record-and-replay feature. Samsung also supplies OpenAI with memory chips for AI infrastructure.
Why it matters: Codex is quietly becoming a general workflow-automation tool, not just a coding assistant — and the chips-for-seats reciprocity shows how entangled the supplier and customer relationships are getting.
sqlite-utils 4.0rc1 adds migrations and nested transactions
Simon Willison released the first release candidate for sqlite-utils v4, folding the proven sqlite-migrate package in directly as a built-in migrations system driven by decorated Python functions and a new migrate CLI command. It also adds db.atomic() for nested transactions backed by SQLite savepoints, borrowing Django/Peewee terminology. The major bump carries breaking changes: type detection now defaults on for CSV/TSV import, REAL replaces FLOAT, schemas use double-quotes, and db.table() no longer returns views.
Why it matters: A widely used building block for LLM data pipelines gets first-class migrations and transactions — worth testing the breaking changes before the stable release lands.
- sqlite-utils 4.0rc1 adds migrations and nested transactions (Simon Willison)
- sqlite-utils 4.0rc1 (Simon Willison)
Fine-tuning Qwen 3 0.6B turns a tiny model into a 92%-accurate classifier
A developer building a household RAG chatbot fine-tuned Qwen 3 0.6B with Unsloth and QLoRA to categorize incoming questions and narrow the vector search space. Prompting the base model alone scored just 10% on a 131-test battery; fine-tuning lifted it to 79%. Mapping categories to two-character opaque IDs with no semantic overlap — instead of human-readable labels — pushed accuracy to ~92% by eliminating fragment and confusion errors.
Why it matters: A concrete reminder that a 600M-parameter local model can handle narrow classification reliably after fine-tuning, and that output-format design often beats prompt-tweaking.
AWS admits agents lack context and security, ships services to patch both
At the AWS Summit in New York, Amazon launched AWS Continuum, which detects, validates and fixes code vulnerabilities by replicating attacks in isolated environments before suggesting patches, and AWS Context, which builds an organization-wide knowledge graph so agents stop confidently hallucinating. The DevOps Agent gained Release Readiness Reviews and change-derived test plans that run in production-like environments, and coding agent Kiro got a native iOS control app. Bedrock AgentCore added a managed knowledge base with S3, SharePoint, Confluence and Google Drive connectors plus prompt-injection and data-leak filters.
Why it matters: The new code-review and verification layers are a direct response to AWS's own AI-caused outages, including a 13-hour incident after Kiro deleted and rebuilt an environment. If you're putting agents in production, these are the failure modes vendors are now admitting out loud.