Anthropic's sandbox-runtime is a research preview from 2025. The October 20 release notes are a Windows change. An October 24 article is an account of the project, not a launch.
sandbox-runtime's October 20, 2026 release is a Windows change to a preview that already existed. MarkTechPost's October 24 piece introduces the project. It is not a ship date.
The short version
No. The GitHub project dates from 2025, and the npm package is the same preview. The October 20 release, v0.0.81, is a Windows change. MarkTechPost wrote about the project on October 24. This page does not print a profile, a settings file, or a way around the sandbox.
October 24 is the article, not the project
MarkTechPost published an introduction to Anthropic's sandbox-runtime on October 24, 2026. The repository it describes was already public. The release this page will use is v0.0.81, dated October 20, 2026, because that is a dated change rather than a slogan. The npm package name is @anthropic-ai/sandbox-runtime at that same version. GitHub and npm are the project. MarkTechPost is the account that put it on today's wire. A meet-the-project headline can be accurate about the tool and still wrong about the calendar. This page keeps the calendar.Arc's sunset is a different browser decision.
What the October 20 notes actually say
The v0.0.81 notes are about Windows. They describe a write-restricted token, a change in how readable a profile is, and an install path that does not open loopback unless the caller asks. An earlier tag, v0.0.80 on October 16, is a different note, about a callback's truth test and nested user namespaces on Linux. This page names those as release-note subjects. It does not quote a profile, a policy file, or a command. A token that is write-restricted is the project's description of a limit, not a recipe for building one.the advisory is the place a severity belongs.
A preview is not a container product
The repository describes an operating-system sandbox for an agent: the platform's own mechanism on each host, rather than a container runtime the project ships. That sentence is the project's summary of scope. It is not a finding that the sandbox contains every tool call, and it is not a comparison this page measured. Beta and research preview are the project's own labels. MarkTechPost's introduction does not promote those labels into a general-availability date. Asked directly, Is the npm package a second product? No. It is the same preview the repository publishes. Two URLs, one project. MarkTechPost is the outside account.memory safety notes are a different kind of claim.
Two of the three sources are Anthropic
The repository and the npm package are the same publisher. Using both is how a reader checks that 0.0.81 is the version the package index shows, not how this page invents a second lab. MarkTechPost is the independent account, and its job in this brief is the October 24 date. Where the article restates the README, the README wins. Where the article sounds like a launch, the release history wins. Asked directly, What operating systems does the project name? The project describes macOS, Linux, and Windows paths. v0.0.81's notes are the Windows ones. A description of three hosts is not a promise that every path changed on October 20.Node's October patches are a different runtime.
What this page leaves in the repo
Seatbelt profiles, bubblewrap arguments, Windows firewall rules, and any bypass belong to the repository and stay there. A news brief can say the project claims an OS sandbox without a container, name the October 20 version, and say who it is for: people already using this preview. It cannot become a setup guide. The impact of the Windows note is a tighter default on that host, as the notes describe it, not a new product line. The document named in the sources is the record this page will keep.
Who is in scope
The preview is for developers running the tool the package ships. It is not a control plane Anthropic turned on for every API customer on October 24. Nothing in the release note says existing Claude accounts changed. A reader who does not run this package is outside the note. A reader who does is looking at a Windows delta on a preview, with the rest of the project unchanged by that one tag. The document named in the sources is the record this page will keep.
The honest calendar
2025: the repository exists. October 16, 2026: v0.0.80. October 20: v0.0.81, Windows. October 24: MarkTechPost. That order is the whole correction. The wire item is real. The launch it can be mistaken for is not. Asked directly, Is October 24 the sandbox-runtime launch? No. MarkTechPost's date is the article. The project and the October 20 release are older. Asked directly, Does this page explain how to configure the sandbox? No. The project's own description is that it uses the operating system's sandbox rather than a container. The settings stay in the repository.a patch window is a version, not a profile.
What the page will not add
No sample configuration. No statement that the sandbox replaces a container in production. No claim that October 24 shipped a version. The record is the release note plus the article's date. The short answer this page will stand on is this: No. The GitHub project dates from 2025, and the npm package is the same preview. The October 20 release, v0.0.81, is a Windows change. MarkTechPost wrote about the project on October 24. This page does not print a profile, a settings file, or a way around the sandbox.
Why the npm link is here
The package page is the public index of the same version. If the index and the GitHub tag ever disagree, the tag is the release and the index is a mirror that has not caught up. On the read this page is using, they agree on 0.0.81. Asked directly, What did sandbox-runtime v0.0.81 change? The release notes say it is a Windows change: a write-restricted token, a note about profile readability, and loopback installs left off unless asked. This page does not print the flag.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Is October 24 the sandbox-runtime launch?
No. MarkTechPost's date is the article. The project and the October 20 release are older.
What did sandbox-runtime v0.0.81 change?
The release notes say it is a Windows change: a write-restricted token, a note about profile readability, and loopback installs left off unless asked. This page does not print the flag.
Does this page explain how to configure the sandbox?
No. The project's own description is that it uses the operating system's sandbox rather than a container. The settings stay in the repository.
What operating systems does the project name?
The project describes macOS, Linux, and Windows paths. v0.0.81's notes are the Windows ones. A description of three hosts is not a promise that every path changed on October 20.
Is the npm package a second product?
No. It is the same preview the repository publishes. Two URLs, one project. MarkTechPost is the outside account.