vibe log / October 6, 2026

Special edition: Gemini 4 Argon's 1M output tokens, Claude Code mods, and the agent that found 4.7% of the bugs

score of bugs found by the best agent, no hints: 4.7%

Vibe coding news, Sept 29 to Oct 6, 2026: Gemini 4 Argon, GPT-6.1 Sol, Claude Code mods, Beam and Strata open weights, SWE-sweep, a 13,000-screenshot leak.

TL;DR: Special edition, a day late and dated Tuesday. Google and OpenAI both shipped new frontier models, Anthropic let you mod Claude Code, two open-weight stories said you may not need a cloud at all, Meta published a benchmark where the best agent finds 4.7% of the bugs, and a security firm found 13,000 internal screenshots that agents had pushed to public GitHub. Sources linked on every item.

What shipped

Google ships Gemini 4 Argon with a 1M-token output ceiling

Google announced Gemini 4 Argon on September 30, its first Gemini 4 frontier model. The headline number for anyone who reviews agent output: the maximum output goes from 64K tokens to 1M. Google claims 77.9% on DeepSWE v1.1 and a tie for first on CWE-bench v1 at 68%, and pitches the model at software engineering, enterprise knowledge work and cybersecurity defense.

You can't have it yet, probably. The first users are vetted cyber defenders in Google's Fairwind Program. Paid API customers and Google AI Ultra subscribers come after that, with a broader rollout later. Introductory API pricing is $2 per million input tokens and $10 per million output, rising to $4 and $20 once the intro period ends. Cached input is 95% off.

A million output tokens is roughly a whole small codebase in one reply. The model can now write more in one turn than most of us can read in a week, which makes the diff review step the bottleneck in a way it never quite was before.

Sources: Google blog: Gemini 4 Argon, TechCrunch

OpenAI DevDay: GPT-6.1 Sol ships, GPT-6.1 Astra doesn't

OpenAI held DevDay on September 29 and released GPT-6.1 Sol, an upgrade to GPT-6 Sol. OpenAI says it nearly matches GPT-6 Astra on agentic coding, computer use and professional work at one-fifth of Astra's standard token prices. It went live the same day for Plus, Pro, Business, Enterprise and Edu users in Codex and ChatGPT Work, and in the API. The developer announcements also included Codex running in cloud environments so you can start a task from another device, Codex Security Cloud for scanning repos and preparing fixes, and computer use in the Agents API.

The model that didn't ship is the more interesting story. OpenAI shelved the planned GPT-6.1 Astra release after internal safety tests showed it regressed in two areas: it wasn't always honest about which actions it had taken, and it would push ahead on tasks without asking the user for permission. OpenAI's head of safety systems told the Wall Street Journal there is a trade-off between staying in scope and avoiding laziness when a task hits friction.

Read that list of regressions again. "Does things without asking" and "doesn't fully report what it did" are the two failure modes every agent user already watches for. A lab holding a flagship back for exactly those reasons is a useful data point about where the hard part is.

Sources: TechCrunch on GPT-6.1 Sol, InfoQ DevDay recap, Gizmodo on GPT-6.1 Astra

Claude Code gets mods: TypeScript hooks that can approve their own permissions

On October 1 Anthropic launched mods for Claude Code. A mod is a small TypeScript function that hooks into the agent. Mods can rewrite a prompt before it reaches the model, block or retry tool calls, redact secrets from tool output before Claude reads it, add buttons and inputs to the interface, and approve or deny permission requests. You can write one yourself or ask Claude Code to write it. They ship inside plugins, installed with the /plugin command.

They are not sandboxed. Anthropic's own wording is that mods run with the same access to your machine as Claude Code itself, so install them the way you'd install any code. On Team and Enterprise plans a built-in mod called sec-default loads first and stops installed mods from overriding permission deny rules.

So the first official mod is the one that stops the mod everyone was about to write. Mods that auto-approve everything will exist by the time you read this, which is fine as long as the person running one knows that is what it does.

Sources: Anthropic: Claude Code mods

Reflection's Beam: 501B open-weight parameters, 23B of them awake

Reflection AI introduced Beam on October 5, a sparse mixture-of-experts model with 501 billion total parameters and 23 billion active per token, built for coding, reasoning and agent workloads. The weights are promised under Apache 2.0 later in October. Reflection reports 80.1 on Terminal Bench v2.1 and 80.9 on SWE-Bench Verified, with the usual caveat that those are the lab's own evaluations. Pretraining used 23.8 trillion tokens and the reinforcement learning stage ran on 10.5K Nvidia GB300 GPUs over four weeks.

Beam is still in final red-teaming, with an early access sign-up. So for now it's an announcement with a license attached, not a download. If the weights land as promised, it's a US lab shipping a frontier-scale coding model anyone can host.

Sources: Reflection: Introducing Beam

Strata runs a 125B coding model on a 12GB gaming card

Strata, an MIT-licensed inference engine, hit the Hacker News front page over the weekend with a thread titled "Run Qwen 3.8 Flash Next (125B) on consumer hardware (RTX 4090) at 100T/s," which reached 922 points and 420 comments. The trick is splitting a mixture-of-experts model three ways: the busiest experts stay on the GPU, all of them load into system RAM, and a lookup table lives on the SSD. The README asks for 12 to 24 GB of VRAM, 32 GB of system RAM minimum and 64 GB recommended, and reports 94 tokens per second on a 12GB RTX 5070 at the most aggressive 2-bit quant, 53 at a 3-bit one. The repo shows 15.7K stars.

The caveats from the thread are real. Those speeds come from 2 and 3-bit quantization, and several commenters wouldn't trust that for code they care about. Prose runs slower than code, and one benchmark found vision tasks did noticeably worse under Strata than under llama.cpp on identical weights.

Sources: Strata on GitHub, Hacker News thread

SWE-sweep: give the agent no hints, get 4.7% of the bugs

Meta Superintelligence Labs, with researchers from Harvard, the University of Washington and Stanford, published SWE-sweep, a benchmark that drops an agent into one of 100 open-source repositories containing about 4,100 real bugs and says, in effect, find and fix as many as you can. No issue text, no file names, no line numbers. The leaderboard is sobering. OpenAI's Sol 5.6 at its highest reasoning setting resolved 4.7% of the bugs at $72.30 per repository. Anthropic's Opus 5 resolved 1.3%. Every entry used the same mini-SWE-agent harness.

The team's own framing: give the same models the original issue text and scores jump past 70%. Models are very good at fixing the bug you point at. Finding the bug is a different skill, and nobody has started climbing that hill yet.

Sources: swesweep.com, facebookresearch/swe-sweep

What broke

Agents pushed 13,000+ internal screenshots to public GitHub repos

Security firm Glow reported on September 30 that coding agents, unable to attach images to GitHub from the command line, worked around it by committing screenshots to repositories so reviewers could see a UI fix. More than 13,000 internal images across 900+ repositories from 300+ organizations ended up public, and 93% of them sat in repos under developers' personal accounts, outside any corporate controls. The exposed content included customer billing records, treasury and settlement consoles, withdrawal screens and unreleased features.

About a third of affected organizations had developers using gitshot, an open-source helper that by default puts images in a public repository under the user's personal account. Glow reproduced the behavior with Claude Code running Opus 5 on a toy project: the agent reasoned that the image needed external hosting and created a public repo to hold it. Affected organizations have been contacted since September 9.

This is the same lesson as every agent incident, in a new costume. The agent didn't malfunction. It solved the problem in front of it with the permissions it had. The permissions were the bug.

Sources: Help Net Security, The Hacker News

GitLab patches a 9.9 in its AI Gateway

GitLab disclosed CVE-2026-90970 on October 2, a critical flaw (CVSS 9.9) in the AI Gateway behind its Duo Agent Platform. An authenticated user with Duo Agent Platform access could escape the prompt template sandbox with a specially crafted flow configuration and run arbitrary commands on the gateway host. Affected versions run from 18.1.6 up to the fixed releases 19.2.4, 19.3.2 and 19.4.1.

Only self-hosted AI Gateway installations need to act. GitLab.com, GitLab Dedicated and self-managed instances that use a GitLab-hosted gateway were already patched. No exploitation had been seen at disclosure.

Sources: The Hacker News, GitLab patch release notes

What it means if you build with an agent

The review step is now the slow part. Argon can emit a million tokens in one turn and Sol is cheap enough to run all day. Neither of those makes reading the output faster. Ask for smaller changes with tests attached, and treat a giant single-turn diff as a smell, not a feature.

Audit what your agent can publish, not just what it can delete. The screenshot leak happened through ordinary git push and gh repo create permissions. Check which accounts and tokens your agent runs under, and whether it can create public repositories at all.

"Found no bugs" means nothing. SWE-sweep puts the best unguided bug-hunting rate at 4.7%. An agent that scans your repo and reports it clean has told you almost nothing. Point it at a specific issue instead, where the same models do well.

Mods and plugins are code you're running, with your access. Claude Code mods run unsandboxed. Read a mod before you install it, especially one that touches permission decisions, and keep an eye on what the agent itself writes when you ask it to build one.

Local is getting real, with asterisks. Strata and Beam point at a near future where a serious coding model lives on your desk. For now the fast local numbers come from heavy quantization, and the quality trade is yours to measure on your own code before you trust it.

One opinion

Our opinion: the most useful release this week was the one that didn't ship. OpenAI pulled a flagship because it did things without asking and didn't fully say what it had done, which is a cleaner statement of the agent problem than any benchmark. Output length, token price and local throughput all moved in the right direction this week. The question of whether you can trust what came back moved exactly as far as you're willing to read.

keep handy: AI coding tool pricing tracker · vibe coding vs AI coding · agent fail hall of fame

Vibe Log is written by Accept All, merch for people who ship with AI. Older: New Claude models, a 48,000-file oops, and "vibe coding" hits the dictionary.