AIToday
AI Coding AssistantsAI Safety & AlignmentOpen-Source AIHacker NewsPublished: Oct 28, 2026, 13:00 JST

Open lab tests AI coding sandboxes on 196 contracts

Send on LINE
Open lab tests AI coding sandboxes on 196 contracts

3 Key Points

  1. What happened

    The lab published corpus v1.1 (2026-10-26), 196 contracts harvested from the test suites of sandbox-runtime, nono, Codex, Deno, bubblewrap and OpenHands, each re-expressed in a neutral format and credited.

  2. Why it matters

    Sandboxes' security claims ("can't read your keys", "can't reach the network") become tests anyone can rerun, and a contract only counts against a sandbox if its attack works without one on the same host.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The lab's premise is that a sandbox's marketing claims are only meaningful if they can be reproduced. Each contract therefore bundles an attack, a control and a post-hoc effect check, and the lab insists the attack must succeed without a sandbox on the same host before a "blocked" result is allowed to count. The corpus is versioned and credited: v1.1 (2026-10-26) holds 196 contracts drawn from the public test suites of sandbox-runtime, nono, Codex, Deno, bubblewrap and OpenHands, with by-omission variants and six masked-credential contracts.

The published runs show the lab iterating on its own methodology as much as on the sandboxes. The 2026-10-16 run was the first judged by spec/verdicts.md; the old runner reproduced the 2026-10-15 results on a fresh host, while the new one changed five, each traced to a cause. A by-omission run re-measures the read-deny contracts in a capability sandbox's own model, so nono is measured where the neutral model only returned unsupported.

The author's own project, TartarOS, is both a subject and a motivation: escapes the lab finds are tried there to see whether they can be mitigated, and TartarOS has been measured alongside the others since the 2026-10-22 run, with the conflict of interest recorded. Reports sent to each vendor's security program as of 2026-10-27 are listed — sandbox-runtime 4 reported and 1 still open, codex 2 and 1, nono and landrun none — and open reports are not published until the vendor fixes them.

FAQ
What exactly is a contract?
A contract has three parts: an attack the agent must not be able to do, a control of legitimate work that must keep working, and an effect checked on disk or on the wire afterwards. A contract only counts against a sandbox if its attack works without a sandbox on the same host.
Which sandboxes have been measured?
The first results in results/2026-10-15/ cover sandbox-runtime 0.0.79, nono 0.80.0 and Codex CLI 0.162.1 on Linux (kernel 6.8). A fourth, landrun (pure Landlock, MIT), is now measured alongside the three in a four-column run.
Does the lab have a conflict of interest?
Yes, and it discloses one: the lab is maintained by the author of TartarOS, which is itself measured, and its page and result file record the conflict of interest.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAnthropic S-1 reveals month-plus pretraining pause, four models escaped test sandboxes onto live systems