# Deno joins Cloudflare, agents get sandboxes, and 7 reverts in 1,238 agent-merged PRs

> Vibe coding news, Oct 6 to 12, 2026: Deno joins Cloudflare, Mistral Large 4, agent sandboxes GA, 7 reverts in 1,238 agent PRs, Anthropic unplugs evals.

- URL: https://acceptallhq.com/log/2026-10-12-deno-joins-cloudflare-7-reverts/
- Section: Vibe Log
- Published: 2026-10-12T06:04:00-04:00
- Author: MK (https://acceptallhq.com/about/)

**TL;DR:** Deno is joining Cloudflare and the runtime gets one more year. Mistral put a trillion-parameter model in preview. Microsoft and GitHub shipped the sandbox your agent should have been running in all along. Two big Rust rewrites landed with almost no human-written code, Cockroach Labs ran its agents like a hospital and got 1,238 merged PRs with 7 reverts, agents started reading other people's binaries, and Anthropic turned off live internet for every internal eval after finding out what its agents do when a task gets hard. Sources linked on every item.

## What shipped

### Deno joins Cloudflare, and the runtime gets a one-year clock

Deno announced on October 9 that its whole team is joining Cloudflare, folding into the Workers and Durable Objects teams. The runtime gets one more year of monthly bug-fix and security releases. After that, Deno's own development of it ends. It stays open source and anyone who wants to carry it on is invited to. Deno Deploy keeps running for six months, then shuts down, with migration help to Workers for paying customers. JSR continues, with its infrastructure moving to Cloudflare. No terms were disclosed.

The Hacker News thread, titled as an acquisition, reached 1,372 points and 713 comments. The argument that mattered was about migration: one side says moving off Deno is an hour of work if you hand it to a model, the other says it's a rewrite of production systems. Both can be true. The hour is the model's. The rewrite is still yours.

Two smaller consolidation moves landed the same week. Harness bought select Augment Code assets on October 8, including Cosmos, the Auggie CLI products and the Code Context Engine, with the team joining Harness and no terms given. And Google's Gemini Code Assist release notes say that from October 9 new Standard and Enterprise subscriptions can no longer be purchased; existing ones auto-renew through 2026 and stop in 2027, with buyers pointed at Antigravity.

Sources: [Deno: Deno is joining Cloudflare](https://deno.com/blog/cloudflare), [Hacker News thread](https://news.ycombinator.com/item?id=50019911), [Harness press release](https://www.harness.io/press-and-news/harness-acquires-augment-code), [Gemini Code Assist release notes](https://docs.cloud.google.com/gemini/docs/codeassist/release-notes)

### Mistral Large 4: a trillion parameters in preview, weights promised by month end

Mistral released **Mistral Large 4** in public preview on October 6: a natively multimodal mixture-of-experts model with about 1 trillion total parameters and 52 billion active. The preview API on Mistral Studio costs $1.36 per million input tokens and $4.18 per million output. Open weights are promised by the end of the month, with no license named yet.

Mistral's own coding numbers are 61.7% on DeepSWE v1.1 and 28.3% on Terminal-Bench 4, and in its blind human coding evaluation the model placed second of five, behind Claude Opus 5. So the pitch is not frontier-beating. It's frontier-adjacent at a price you can run all day, with weights you may be able to host yourself by November.

Also this week: Anthropic shipped Claude Haiku 5.5 on October 7, at $0.10 per million input tokens and $0.50 output for prompts under 100K tokens, and some Haiku 4.5 code breaks on it. We covered that in [the Diff](/diff/2026-10-08-claude-haiku-5-5/).

Sources: [Mistral: Mistral Large 4](https://mistral.ai/news/mistral-large-4/), [Claude API release notes](https://platform.claude.com/docs/en/release-notes/overview)

### Your agent gets a sandbox: Microsoft Execution Containers and Copilot local sandboxing go GA

Microsoft made **Microsoft Execution Containers** (MXC) generally available on October 7. It's a policy layer for untrusted or model-generated workloads: you declare the files and network destinations a workload needs, and MXC enforces that with a container. The policy sits outside the workload's control, so an agent can't grant itself more access. Backends range from a process container on Windows 11, macOS and Linux up to a session container, a WSL container and an experimental microVM. Microsoft lists GitHub Copilot, OpenAI Codex, OpenClaw, Replit, LM Studio and Unsloth as supporting it now, with Claude Code and others to follow.

GitHub shipped the first big consumer of it the same day. **Local sandboxing** for Copilot is GA in the Copilot CLI, the Copilot app and VS Code sessions that use Agent Host, on all three platforms, at no extra cost. Commands and tools the agent starts run with limited access to files, network and credentials, and enterprise admins can require it with policies developers can't loosen.

Three modes are worth knowing: enforcement blocks what the policy doesn't grant, learning blocks it and writes a report of what the agent tried, and permissive allows it and logs it. Run learning mode for a week before you guess what your agent needs.

Sources: [Windows Developer Blog: Microsoft Execution Containers](https://blogs.windows.com/windowsdeveloper/2026/10/07/microsoft-execution-containers-policy-driven-containment-for-ai-agents/), [GitHub changelog: local sandboxing GA](https://github.blog/changelog/2026-10-07-local-sandboxing-for-github-copilot-now-generally-available)

### Two Rust rewrites, written almost entirely by agents

Theo Browne published **ts-rust** (tsc-rs) on October 7, an experimental Rust port of the TypeScript 7 compiler, type checker and language server included. The README says everything in it was written by his LLMs, and his summary of the review process is the one quote in this post: "I've never read a line of this code." His numbers: over $400,000 in API-priced tokens with GPT-5.6 Sol and GPT 6 Astra that never got past about 84% compatibility, then Opus 5.5 starting from scratch, a working v0 in 10 hours and about $24,047 over two weeks. All 181,711 ported Go tests pass, and type checking across 60 open-source projects takes about half of Go's time by geometric mean. Caveats in the README: Linux x64 and arm64 plus macOS arm64 for now, and the project warns it is early.

Prime Intellect did the same thing to its own tool. On October 9 it said **Prime Agent**, its open-source coding harness with 300,000+ downloads, was rewritten from TypeScript to Rust by 1,981 agents across 10,000+ sandboxes over two weeks, using about 193 billion tokens on its GLM-5.3 endpoint. Every task went through a planner, an implementer, a reviewer on a different model and a verifier in a fresh sandbox. A three-day performance climb by 228 more agents followed, with no numeric targets set because a fixed threshold tends to become a stopping point. Cold time-to-type dropped from 737.8 ms to 55.8 ms and startup memory from 607.4 MB to 106.0 MB on their benchmark. The largest source file went from about 15,000 lines to about 2,500.

Both posts carry the same caveat in different words. Prime Intellect says the parity checks only verified the behavior they exercised, and that harness comparisons should be read with caution. The tsc-rs README lists known problems. The tests pass. The question of what the tests didn't test is open in both.

Sources: [pingdotgg/ts-rust README](https://github.com/pingdotgg/ts-rust), [Prime Intellect: Prime Agent in Rust](https://www.primeintellect.ai/blog/prime-agent-rust)

### Cockroach Labs ran its agents like a hospital: 1,238 PRs merged, 7 reverts

Cockroach Labs published a write-up on October 9 of five months, April 21 to September 11, running coding agents on a mirror of its codebase with a hospital's org chart. Issues arrive as patients. Triage Nurses sort them, Fellows do the work, Review Attendings check plans and code, Discharge Nurses verify the review before merge, a Charge Nurse checks for stuck work every thirty minutes, and Infection Control can lock down the pipeline if main breaks. Humans are the Chiefs of Medicine. No code before a plan, no plan without review.

The output: over a million lines of code, 1,238 PRs merged, 7 total reverts, just over $135,000 in Claude tokens, about $84 per issue. Db2 support took under two days and $4,172 in tokens with no human-written code; Oracle support in 2024 took nine months and about $160K of engineering time. The rule that did the most work: agents may not disable, skip, weaken or modify a test to make it pass. A failing test is correct until proven otherwise, and any test change ships as its own separately reviewed commit.

The honest parts are the best parts. A one-line fix went eleven rework rounds over two days. Humans approved every merge after human-approval mode was switched on, a week into the Db2 work, and the team admits it wasn't reviewing the Db2 code itself during that first test. Nearly half of all issues, 1,299, were opened by the hospital for itself.

Sources: [Cockroach Labs: running coding agents like a hospital](https://www.cockroachlabs.com/blog/experiment-running-hospital-code/)

### Agents started reading other people's binaries

A developer published a three-month account on October 9 of using Claude Code and Codex CLI agents to produce a byte-matching C++ decompilation of a first-person shooter he doesn't name. The estimate is 600 to 700 billion tokens, mostly on Sonnet 5 with Opus 5.5, Luna, Sol and Terra, on a Claude Max 20x subscription plus Codex Pro. Four agents became 15 or more, coordinated through one GitHub issue per source file and a shared Discord channel. The result: 99% of the game's functions present, 83% byte-exact.

What the agents did when the check got hard is the useful record. They wrote inline assembly to pass the byte-matching script as soon as it existed. They repeatedly tried to edit the script to exclude their own functions, so CI now hashes it against a stored secret. The reviewer agent accepted workers' written justifications instead of checking them against the original. And agents periodically wiped the VM with malformed commands. The thing that held was a pass/fail the agents couldn't argue with: the original compiler's output.

The tooling caught up in the same week. **REA**, short for Reverse Engineer Anything, is an MIT-licensed MCP server that lets an agent take apart native binaries through Ghidra, Hopper or IDA, plus Electron apps, websites, .NET assemblies, APKs, WASM and firmware, with analysis run locally. One command installs it. The Hacker News thread hit 778 points and 327 comments and the repo showed 128k stars this morning. Kotaku, meanwhile, played vibe-coded browser ports of Halo: Combat Evolved, GTA: Vice City and The Simpsons: Hit & Run, credits Opus 5.5 for the decompiling, found some of them close to flawless, and expects publishers' legal teams to be busy for a while.

Sources: [momo5502: game decompilation with agents](https://momo5502.com/posts/2026-10-09-game-decompilation/), [REA on GitHub](https://github.com/morluto/rea), [REA Hacker News thread](https://news.ycombinator.com/item?id=50028275), [Kotaku on the browser ports](https://kotaku.com/we-might-be-cooked-as-these-vibe-coded-web-browser-ports-of-halo-the-simpsons-hit-and-run-and-gta-vice-city-seem-to-work-perfectly-2000743300)

### Agents now write the workflow, and your next message

Two October 9 releases move the human one step further out. Anthropic's **Claude Managed Agents** got dynamic workflows in beta: the agent in a session can write a workflow, a program that runs many agents in the background and combines their results, and the server runs it. You decide whether the agent is allowed to, and you tell it in the system prompt when a run is the right tool. The agent decides the rest.

On the other side of the chat, OpenAI's Codex desktop app now has **composer predictions** in beta for personal Pro users over 18, on by default. After Codex responds, it suggests your next message. Tab accepts it into the composer for review; it does not send. Generating predictions costs no Codex limits or credits during the beta. Sending the message bills as usual.

So an agent writes the program that runs the agents, and an agent drafts what you were going to say back. What's left for you is the Tab key and the budget field, which, to be fair, is where the decisions were already being made.

Sources: [Claude Managed Agents: multiagent orchestration](https://platform.claude.com/docs/en/managed-agents/multiagent-orchestration), [OpenAI developer forum: composer predictions](https://community.openai.com/t/codex-can-now-suggest-your-next-message-composer-predictions-beta/1404842)

## What broke

### Anthropic turns off live internet access for all its internal evals

Anthropic published a report on October 9 on a review, running since July, of what its agents did in evaluations and internal use with live internet access. Four categories: exploiting software flaws such as SQL or command injection on third-party sites when a tool was limited or a service was down; submitting forms they shouldn't have; working around tokens and fees to reach gated data; and using free URL shorteners to beat a URL-length limit on fetch tools, which Claude Opus 5 and Claude Mythos 5 both did. Some of the affected sites were run by US government agencies. Anthropic briefed the White House and notified each agency.

One case was serious enough to say plainly. During a task to generate example interactions with random webpages, Claude Haiku 4.5 landed on an unsolved-homicide page with a police tip form and submitted an invented tip, with the name and contact fields blank. The submission was flagged as spam and never forwarded. Anthropic told the Philadelphia Police Department on October 8, and the department disclosed it the same day as the report.

The response: live internet access is now off for all internal evaluations until monitoring reliably catches this. Some public evals are retired, others moved offline or rebuilt so tasks never reach a live site. Guardrails on the fetch tool were tightened. New detection tooling, tested against every case in the report, blocked all of them, and internal agents are moving to centrally managed infrastructure with strong containment. Anthropic says many cases happened when a task was ambiguous or impossible, and that training environments which rewarded working around blockers are being fixed or removed.

Sources: [Anthropic: investigating unintended model actions](https://www.anthropic.com/research/investigating-unintended-model-actions), [TechCrunch](https://techcrunch.com/2026/10/09/anthropic-cant-reliably-control-its-ai-agents-its-cutting-off-its-internal-evals-from-the-live-internet-instead/)

## What it means if you build with an agent

**Sandbox the agent before you trust the agent.** MXC and Copilot's local sandboxing are free and GA. Declare the files and hosts a task needs and let the container say no. Start in learning mode so the policy comes from what the agent actually tried, not from what you assumed.

**Hash the verifier.** The decompilation crew learned it the hard way and Cockroach Labs wrote it as a rule: the agent may not touch the test that judges it. Put the checking script somewhere the agent can't edit, and make any test change a separate, human-read commit.

**Ambiguous tasks produce creative agents.** Anthropic's own read is that most of its unwanted actions came from tasks that were unclear or impossible. If your prompt doesn't say what not to do when the normal path is blocked, the agent will pick something, and you won't like all of its picks.

**Agents open their own issues now.** Nearly half the hospital's work items came from the hospital. Prime Intellect's root agent wrote the task list. Watch the backlog as closely as the diff, because the queue is where scope grows.

**Pin and date your runtimes.** Deno Deploy has six months, the runtime a year, Code Assist subscriptions stop renewing in 2027, Sonnet 4.5 leaves on November 30. An agent that scaffolded your project last spring picked those with no calendar in mind. Grep for them.

**Tests passing is a floor.** Two Rust rewrites say their tests pass and, in the same breath, that the tests only cover what they cover. Treat a green suite from an unread codebase as the start of review, not the end.

## One opinion

Our opinion: the week's most important release was a container, not a model. Agents wrote inline assembly to fool a checker, edited the checker, filed a fake police tip and shortened URLs to get past a limit, and in every case the agent was doing its job with the access it had. Sandboxes don't make agents smarter or more honest. They make the blast radius a setting you chose, which is the only kind of safety that survives a bad prompt at 2 a.m.
