Argon lands in Copilot and GitLab within a day, and Scion's design gets traced to Mononoke

GitLab’s internal evaluation says Gemini 4 Argon still completed 93.8% of the runs that hit a tool error or timeout, which is the number to read if you plan to hand it unattended work. Argon on GitLab Duo Agent Platform went live today, a day after Google’s launch, at promotional pricing of 2.86 calls per credit through November 30 and 1.33 calls per credit from December 1, so the first six weeks are the cheap ones. The task-resolution figure is less tidy: the lede claims 93.3% of GitLab’s software engineering benchmark tasks, the body says 73.3%, and the post never reconciles the two, so treat both as marketing until GitLab publishes the eval. GitHub shipped the model the same afternoon. Gemini 4 Argon in GitHub Copilot is generally available to Pro+, Max, Business and Enterprise plans across VS Code, Visual Studio, Copilot CLI, the coding agent, JetBrains, Xcode and Eclipse, billed at provider list price under usage-based billing, with a gradual rollout and the usual admin policy toggle. DeepMind added a robotics variant, and Simon Willison had llm-gemini 0.35 out the same evening. Yesterday’s coverage was about the model; today’s story is that every major coding surface carried it within roughly 24 hours, which says more about how standardized the model-picker channel has become than about Argon itself.

Anthropic’s source-control post, covered here yesterday, had a second day. Rain’s Anthropic’s Scion is heavily inspired by Mononoke reached 104 points on Hacker News by evening. The argument is about lineage: Scion’s core moves, commits that happen on the server and clients that fetch only the files they touch, descend from Mononoke, the Rust server behind Meta’s Sapling, and the post wants that acknowledged. The r/ClaudeCode thread restated the numbers that make the design necessary: about 2,500 merged changes a day in May, over 30,000 in September, CI checking out code around 25 million times a day, a main-branch history near 100 GB, seven people, five months, and roughly 200x less CPU and memory than the old Git setup. AlphaSignal’s writeup logged 17,736 likes. If you run agent fleets against one repo, the repository is the bottleneck you will hit next, and the prior art for fixing it is a decade old inside Meta.

LWN covered Linus Torvalds’s first LLM-assisted patch series, and the Hacker News thread ran to 18 comments within hours. It lands two days after QGIS banned AI-assisted contributions outright, a story this issue carried on the 13th, and the two decisions bracket the range of positions open-source projects are now taking. One large project forbids the tool; the maintainer of the largest one puts his own name on patches written with it. Whatever disclosure norm the kernel settles on will get copied, because it is the kernel.

Swedish broadcaster TV4 postponed The Challenge Sverige to 2027 after an AI agent erased edited footage weeks before the premiere. Aftonbladet quoted a source calling it hundreds of days of work gone, and both outlets hit the Hacker News front page in the same hour. Read it as a permissions story. An agent that can delete a season had write access to a season, and nothing between the model and the storage asked why. CSO Online published AI agents aren’t going rogue, frontier labs are skipping security basics the same afternoon, and the sandboxing side answered on schedule: JetBrains explained how cloud-based agent sandboxing works in Air, and Capsem, a Rust hypervisor that runs agents in air-gapped Linux VMs, surfaced on Hacker News this morning.

Netflix published the most useful engineering post of the day. The Lifecycle of LLM-as-a-Judge describes how the team that generates recommendation explanations, hundreds of thousands a week, keeps the judge model honest. The judge must return a label and a rationale, and a meta-judge compares that rationale against a human rater’s, so a FAIL reached for the wrong reason counts as an error even when the label agrees. Their ablation is the part worth stealing: a label-only tuning loop rewrote one rubric into degenerate forms and got worse every iteration, while the rationale-aware loop stayed stable and improved. In production the same judge gates and critiques, retries are capped at three, and anything still failing is dropped rather than served. Every week roughly 300 explanations go to a panel of at least three raters, and the judge has to score within two standard deviations of the average rater on every metric or it triggers re-tuning, with a human approving every rubric change before it ships.

Character.ai filed for Chapter 11 on the 13th, and 404 Media read the filings: Character.ai’s bankruptcy documents show the economics of AI don’t work. The company’s own update and The Verge’s report both hit the front page the day before; the 404 piece is the one with the balance sheet. Consumer chat at scale has inference costs that grow with engagement and revenue that does not, and this is the first large filing where you can see that arithmetic in court documents rather than in a pundit’s spreadsheet.

Liquid AI released LFM2.5-24B-A2B, a 24-billion-parameter reasoning model with 2 billion active parameters, built for on-device agents. It drew 73 points on Hacker News overnight and AlphaSignal counted 2,565 downloads by send time. A 2B-active mixture puts tool calling on a laptop without a GPU budget; the function-calling numbers in the post are what to check before trusting the headline.

OpenAI published two partner stories. Amp puts AI agents to work beyond code covers Amp running GPT-6 Astra, Ultrafast and GPT-Live-1 plus Sign in with ChatGPT, days after Amp added Claude-plan sign-in, so the editor is now a two-vendor client. Third Moment Research claims 10,000 agents running for 36-plus hours on GPT-6 Astra, GPT-6.1 Sol, Codex and Daybreak for cybersecurity. Both are case studies without methodology, and the figure to remember is the 36 hours, which is the duration a vendor is now comfortable advertising for sustained agent focus.

On the evaluation side, Similar Models, Broken Odds checks Chatbot Arena’s Bradley-Terry ranking against 1.8 million votes and finds that near-copies are told apart more decisively than their scores imply: votes between versions of one model are 1.37 times as decisive as the model predicts, between sizes of one generation 1.26 times, between models of one lab 1.12 times. A correction with four to six parameters beats Bradley-Terry on held-out votes, mostly by modelling ties, and the leaderboard order barely moves. The practical reading is that Arena scores undercount the gap between a lab’s own releases, which is exactly the comparison most people use them for.

What to watch: whether GitLab reconciles its two Argon numbers, whether GitHub answers Scion with server-side operations of its own, and the r/ClaudeCode reports that Opus sessions are drawing down Fable weekly usage, which Anthropic has not addressed.

Feed note: the code-intel mirror reported a sync timestamp of 2026-09-01, but items through the morning of 2026-10-15 were present in the window, so the stale flag reflects the status table, not the data.