vibe log / November 2, 2026

Anthropic files a 300-page diff, GitHub counts 110 million agent PRs, and Cursor's marketplace served a trojan

score agent-drafted pull requests on GitHub in September: 110 million

Vibe coding news, Oct 26 to Nov 2, 2026: Anthropic's S-1 says Claude wrote 90% of its code, 110M agent PRs on GitHub, Mistral Large 4, Cursor trojan.

TL;DR: The week the numbers came out. Anthropic's S-1 says more than 90% of its September code was written by Claude, and its heads of engineering and product explained on a podcast how the Messages API was rewritten in Rust by a model while humans drew the boxes. GitHub's Octoverse says more than 40% of pull requests now start with an agent's draft, 110 million in September alone, while Stack Overflow fell under 1,000 new questions a month. Mistral put the weights of a 1-trillion-parameter model on Hugging Face and Google announced Gemini 4 Carbon two weeks after Argon. Karpathy built a YouTube clone in two hours and said he no longer does anything resembling engineering, DeepSeek open-sourced an agent whose main feature is not talking to you, and 50 agents in Minecraft asked permission to remove grass. On the broken side, Cursor's extension marketplace served a tampered Claude Code extension for about 11 hours, and Claude Code turned out to be spending somewhere between 2% and 16% of your budget asking itself what it was doing. Sources linked on every item.

What shipped

Anthropic's S-1: Claude wrote over 90% of September's code, and the Messages API is Rust now

Anthropic filed to go public on October 26, ticker ANT on Nasdaq. The money numbers are the ones the press led with: $16.3 billion in revenue for the first half of 2026, $11.6 billion of it in Q2, 5,300 employees at the end of September, and a $80.7 billion net loss of which about $72.4 billion is a non-cash charge on convertible notes, so operating cash flow was actually positive $3.9 billion. The risk-factor section runs about 94 pages of a filing over 300 pages long. The Hacker News thread hit 1,709 points and 1,681 comments, nearly all of it compute math. Nobody there noticed the sentence we care about.

That sentence says more than 90% of the contributions to Anthropic's codebase in September 2026 were written by Claude. Forbes adds, from the same filing, that engineers wrote about 45 times as much code per day in Q3 2026 as in 2024. The filing also gives the clearest Claude Code spending figure yet: Claude Enterprise users who did not use Claude Code spent under $75 a month on average, and the top 5% of those who did spent about 20 times that. Two risk factors read like a Vibe Log takeaway section: it is unclear when an agent's actions legally bind the organization deploying it, and human reviewers may be unable to keep pace with autonomous systems. A company is telling the SEC, in writing, that the diff may be too long to read.

How that works in practice came out the next day on Latent Space, where Katelyn Lesse and Angela Jiang, Anthropic's heads of engineering and product, described rewriting the Messages API from a Python monolith into Rust. Humans designed the distributed system, Claude wrote the code, and the team started with no Rust developer in the room, hiring a couple later. The review was not a diff. They built a full fork of the API in Rust, ran shadow traffic through it, and checked that the Rust outputs matched the Python ones. It was fully rolled out the week before recording, with an estimated 10 to 20 percent improvement in time to first token and a ballpark 40 to 50 percent CPU saving. If you have ever wondered what code review looks like at 90% agent-written, it looks like production, twice.

Sources: Fortune on the S-1, Forbes: Claude now writes 90% of Anthropic's code, Alex Kras: reading the S-1 as a Claude Code user, with the filing's wording, VentureBeat on the risk factors, The S-1 on EDGAR, Hacker News thread, Latent Space: How Anthropic ships Claude with Claude

Mistral Large 4 weights and Gemini 4 Carbon: one you can download, one you cannot use yet

Mistral released the weights of Mistral Large 4 on October 29, a 1-trillion-parameter mixture-of-experts model with about 52 billion active parameters, multimodal input and three reasoning modes. The nickname is Le Chonk. The license is the Mistral Ecosystem Open-Weight license, which Mistral describes as a modified MIT license with one catch: a business selling it as a service needs a separate commercial license. Mistral calls it the "best open-weight model for coding" and gives 41% on Terminal-Bench 4.0, up from 28% for the preview, and 48% on the Artificial Analysis Coding Agent Index, tied with GLM-5.3 while using 47% fewer tokens per task. API price is $0.70 per million input tokens and $2.10 output. The Hacker News thread, 1,720 points and 439 comments, settled on the obvious: the lowest quantization still needs about 256 GB of VRAM, so for most people open weights means someone else's GPUs and the "open" part is the license.

Google announced Gemini 4 Carbon on October 28, two weeks after Argon, as its strongest model so far, with the pitch aimed at cybersecurity and long-running tasks. The figures are Google's own: first on the Artificial Analysis Intelligence Index v5 at 59, fourth on WebDev Arena at 1768 after a jump of 89 Elo points, more than double Argon's success rate at generating secure code on internal benchmarks, and internal teams running it for days on hard engineering problems. Our favorite line is in the safety section: successful cheating on Terminal-Bench 4.0 is down to 0.0%, and cheating attempts are down to 0.4%. It still tries. It just gets caught now. Same.

You cannot have it yet. A subset of cyber defenders gets access first, then trusted partners through the Fairwind Program, then everyone else at some unstated point, at an introductory $2 per million input tokens and $10 output, rising to $4 and $20 later. So this week one frontier-class model shipped as a 1-trillion-parameter download you cannot run and another shipped as a blog post you cannot call. Both are, in different ways, a budget problem.

Sources: Mistral: releasing the weights of Mistral Large 4, Hugging Face model card, Hacker News thread on Mistral Large 4, Google: Gemini 4 Carbon, our next frontier model, The Register on Carbon

Octoverse: 110 million agent-drafted PRs in a month. Stack Overflow: under 1,000 questions

GitHub's Octoverse 2026 report, published October 28, is the trend data of the year for this newsletter. By September 2026 more than 40% of pull requests on GitHub started with an agent's first draft, up from 17% in March. That is 110 million agent-started PRs in September alone, about six times March's volume. The rest of the report is the same curve from other angles: 17.9 billion pushes in twelve months, more than 2024 and 2025 combined; 1.3 billion merged pull requests, 3.5 million a day; agent-involved PRs touch multiple files 87% of the time against 79% for the rest, and the share merged within two weeks rose from 83% in February to 90% in September while the comparison group sat at about 86%. Paying Copilot users drew on 47 different models in September and no single one took more than a quarter of requests. AI-assisted code review usage grew more than 90% year over year, which is the only number in the report that has to keep up with the first one.

The same day, a Stack Exchange Data Explorer query hit the Hacker News front page under the title that Stack Overflow now gets fewer than 1,000 questions a month, and stayed there for 851 points and 754 comments. For scale, the site's peak month was March 2014 at 207,204 questions, July 2026 was 1,442 and June was 1,076, and the whole of 2025 came to 108,981, less than that one peak month. The thread's best contribution was a commenter who annotated the graph: volume was already down nearly half from its June 2020 local peak before ChatGPT launched, flat from 2014 and falling from 2017. The model did not start the avalanche. It just made sure nothing survived it.

Read the two together and the week's shape appears. The questions did not stop. They moved into a chat window, got answered by a model trained on the public ones, and came back out as a pull request nobody drafted by hand. Closed as duplicate of: the model.

Sources: GitHub Octoverse 2026, Hacker News: StackOverflow now gets fewer than 1000 questions a month, PPC Land on the Data Explorer figures, TokenPost

HackerTube in two hours, and DeepSeek's agent that only speaks when spoken to

Andrej Karpathy, who gave vibe coding its name, published HackerTube on October 31: a YouTube-style site of only the videos people have recommended on Hacker News. Opus 5.5, through the Claude Code desktop app, downloaded the comments, narrowed them to about 40,000 that recommend a YouTube video, ran Sonnet over them in a Workflow to drop the spam, and ended up with 6,454 videos from 2007 to 2026 across 150 topics. The human work, by his own list, was three items: creating a Google Cloud API key for video metadata, booting a VPS and handing over the IP, and buying the domain. He says the whole thing takes about two hours now, that he no longer does anything resembling traditional engineering, and that his default is Opus 5.5 on Medium effort. Not max. Medium. The thread reached 2,600 points and 573 comments, and by Sunday someone had shipped HackerBooks, the same idea for books, to 1,414 points, and by this morning Wikihack for Wikipedia articles. The format is now a weekend genre.

The same day, DeepSeek published dsh-superagent-prototype on GitHub under MIT: a proactive coding agent for one repository, packaged for DeepSeek Harness. It listens to GitHub and, optionally, Feishu. When an allowed person asks for work it opens a work item, does the work in its own session and directory, and replies in the original conversation, usually with a pull request; a web panel lists the items that need a human. The design principle is to take as little human attention as possible and give as much value as possible, so it acts only when asked or when a team-written rule allows, and speaks only when someone must act or can use a result. The README calls it a research prototype, not an official product, and says the public version differs from the internal one. It had 11,000 stars by this morning. Bloomberg, via The Next Web, says DeepSeek is aiming it at Claude Code. Hacker News gave it 11 points, which is the quietest an agent has ever been covered, and possibly what it wanted.

Sources: Karpathy: HackerTube, Hacker News thread on HackerTube, HackerBooks on Hacker News, deepseek-ai/dsh-superagent-prototype, The Next Web on DeepSeek's agent

YC Labs ran 50 agents in Minecraft. They formed a bureaucracy

YC Labs dropped 50 GPT-6.1 Sol agents into a survival Minecraft world for three hours with the prompt to build a thriving civilization, and published what happened on October 29. There was no election. The hierarchy followed directory order: Ada, first on the roster, became the de facto leader because 46 of the other 49 agents sent her their first message, and she ended up with 616 DMs. Twenty-two of the run's 34 deaths happened on the first night, after which the colony got careful. Four agents spent 11 minutes appointing a sole fertilizer operator for one piece of bone meal on one wheat block. Other invented roles included fishing shift, rod holder and hub steward. Agents asked permission to remove grass.

The Bed Wars half is the part for anyone who keeps a memory file. Nine 45-minute games, ten Claude Opus 5.5 agents against ten GPT-6.1 Sol agents, told to win. GPT won 6 to 3, usually by breaking Claude's bed in the final minutes while Claude defended and tried to win on kills. Claude wrote lessons into private memory files and repeated the mistakes anyway. GPT left its memory files empty and broadcast warnings by DM. The authors say the caution and the role fixation look like common threads with the coding agents they use for work, especially the over-caution around security and production changes. The Hacker News thread, 419 points, mostly compared them to middle managers. We have a desk mat about asking permission before touching the grass, and we did not expect the agents to need it.

Sources: YC Labs: We ran AI agent swarms in Minecraft and Mindustry, Hacker News thread

What broke

Cursor's marketplace served a tampered Claude Code extension for about 11 hours

From about 2:27am to 1:35pm Pacific on October 29, Cursor's extension marketplace served modified builds of the Claude Code extension, versions 2.1.312 and 2.1.313, for Windows and macOS. Cursor says they were not developed by Anthropic and that at most 5,000 users were affected. The addition was a 66-line loader in front of the real extension code. It collected hostname, username, OS, Git email and the names, not the values, of environment variables that look like secrets, added an attacker's SSH key labeled svc-telemetry to authorized_keys, tried to enable SSH and open a reverse tunnel to the attacker's server, and installed persistence as a LaunchAgent on macOS or a scheduled task on Windows, dressed up with monitoring-style names. On most machines the SSH step failed for lack of admin rights. The key and the persistence could still be written.

Anthropic says its systems were not compromised and that the versions on its official channels were not affected. Microsoft, Socket and OpenSourceMalware found no sign of it on the VS Code Marketplace, Open VSX or npm; OpenSourceMalware corrected its early guess that Open VSX was the source. Cursor removed the version, took the whole marketplace offline, rotated keys, rebuilt it, had the attacker's server taken down, and says no other extensions were tampered with. As of this morning neither Cursor nor Anthropic has said how an attacker got a package published under Anthropic's publisher identity. Microsoft's security team published a full teardown on October 30.

There is no joke in this one. If you run Cursor on Windows or macOS, check your authorized_keys for a key named svc-telemetry, and if it is there, treat the machine as owned: uninstalling the extension is not enough, rebuild the host and rotate every credential it could reach. Cursor's own hardening advice is worth adopting regardless: restrict extensions to approved publishers and set a cooldown before new versions install. The extension that drives your agent runs with your permissions, which is the point of the extension and the point of the attack.

Sources: Cursor security notice, Microsoft Security: inside the malicious Claude Code-branded Cursor extension, OpenSourceMalware analysis, The Hacker News

Claude Code spends 2% to 16% of your budget asking itself what it is doing

A gist on October 29, 588 points on Hacker News, dug into a Claude Code call named agent_summary. Roughly every 30 seconds, for each background agent that is working, Claude Code sends that agent's entire transcript back to its model, usually Opus, and asks it to describe its most recent action in three to five words. The answer updates the status line in the agents panel. It has been on by default for interactive background agents since 2.1.232 in August, and since 2.1.300 the interval is server-tunable between 30 and 240 seconds. The author's telemetry, using Claude Code's own per-request cost estimate, put it at 16.4% of their spend and 19.7% of their requests, about one in five. About 98% of the calls read the transcript from cache, but the 2% that miss carry over a third of the cost. The gist ships a hook that stops the timer.

Anthropic's answer came in the thread from Edwin Arbus, who works on Claude Code: across users who send telemetry, agent_summary was about 2% of cost at API list prices last week and just under 4% of requests, about 6% of cost in the terminal, and the 16.4% figure looks like a team running mostly background agents rather than a typical session. A fix for the expensive case, summaries that miss the prompt cache, went out in 2.1.311, and a cheaper mode that sends short notes to a smaller model is in progress. Other commenters measured about 8%, about 16% and about 3%; a GitHub issue open since August reports 18 to 26% in subagent-heavy sessions. Everyone agrees on the mechanism. The disagreement is about your workload. On a subscription none of it shows up as dollars; it shows up as the rate limit arriving early.

Which makes the week's other Anthropic change relevant. On October 30 the $200 Max 20x plan became Ultra, with no 5-hour limit for verified accounts, a weekly cap of 10x Pro and $200 a month in API credits; the $100 Max 5x plan is now plain Max, still 5x Pro per five hours and per week with $100 in credits. So the window that the summaries were eating is gone on the top plan, and the weekly one is not. If your agents narrate themselves in three to five words every 30 seconds, that is still your headroom they are narrating into.

Sources: Gist: Claude Code regularly sends each background agent's transcript to its model, Hacker News thread, claude-code issue #86879, Claude pricing

What it means if you build with an agent

Review is becoming a production test. Anthropic did not read the Rust rewrite, it ran shadow traffic and diffed the outputs. If an agent is rewriting something with a stable interface, build the comparison harness before the rewrite. It is the review.

The agent opens the PR; decide who reads it. More than 40% of GitHub PRs start with an agent and the merge rate is going up, not down. AI-assisted review is growing faster than almost anything else in Octoverse, which tells you where the bottleneck has moved. Put a human on the tests and the auth, and a tool on the rest.

Your extensions are your supply chain. The Cursor incident ran with your user's permissions from inside the tool you trust most. Pin extensions to approved publishers, set an install cooldown so you are never first to a new version, and check authorized_keys this week even if you think you were not affected.

Audit what the harness does when you are not prompting. agent_summary is a reminder that the loop you see is not the only loop. Before a big background-agent session, look at the request log, turn off what you do not need, and remember that on a subscription the cost is the limit arriving early.

Memory files are not lessons. Claude's Minecraft agents wrote down what went wrong and did it again; the agents that won shared warnings with each other instead. A memory file nobody reads back at the right moment is a diary. Put the hard rules where the agent sees them at decision time, in the prompt or a hook.

Medium effort is a legitimate default. Karpathy ships on Medium. The two-hour project is a scoping choice: a clear data source, a familiar UI shape, and three human tasks. Reserve the expensive settings for the parts that resist.

Open weights are a license, not a laptop. A 1-trillion-parameter download that needs 256 GB of VRAM and a modified MIT license is open the way a bank vault is open to the public. Price the hosting before you plan around it, and read the clause about selling it as a service.

Write the risk factor for your own agent. Anthropic told the SEC that human reviewers may not keep pace and that nobody knows when an agent's action binds the company. Write your version in a paragraph. If you cannot, the agent has more authority than the paperwork says.

One opinion

Our opinion: this was the week the industry stopped arguing about whether agents write the code and started filing the paperwork that says they do. Over 90% in a prospectus, 40% of pull requests in an annual report, a rewrite of the API everyone calls, reviewed by production, and the man who named the whole thing saying he no longer does engineering. We think the interesting question has moved from authorship to accountability, and the two items in the broken column are what accountability looks like when nobody owns it yet: a marketplace that cannot say how a package got in, and a harness spending budget on a status line nobody asked for. The diff is not going to get shorter. The question is who signs it.

By MK

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


Vibe Log is written by MK for Accept All, news and merch for people who ship with AI. Newer: Don't Ask Again saved 1,122 secrets to GitHub, nobody bought a model, and one agent wrote 413 memory files for one badge. Older: Agents get their own computers, mute their own monitors, and write 180 million lines of proof.