
What happened
Chock launched a sandbox-first AI coding harness that runs agents inside the OS's own sandbox on a throwaway copy, under an uneditable chock.zon policy, with every turn and tool call in an append-only, hash-chained session log.
Why it matters
Security and platform teams get attribution — which commits came from an agent — plus a log an auditor can verify without trusting the agent, and a sandbox that cannot be switched off.
What to watch
Attribution covers only sessions run under Chock, so its worth depends on rollout coverage; sealing is only as good as key custody. Chock is pre-alpha.
WHO IT HITSSecurity and platform teams at organizations where developers already run coding agents next to production credentials get a sandbox, policy, and audit trail they can hand to auditors. The log helps establish which commits came from an agent, with the rest human by elimination.
Summaries like this, every morning.
Chock enters a landscape where coding agents already run commands, write files, and reach the network, often next to production credentials on developer machines. The harness's pitch is that most other harnesses ask the agent to be careful, while Chock puts what an agent may do outside the agent's control. Its policy file, chock.zon, sits in the project and can be read but not edited by the agent; if an action needs approval and nobody answers, it is refused.
The comparison table is based on reading source code, not documentation. It says ten harnesses were read, and the three that sandbox at all mount the whole filesystem into the sandbox, and none keeps a tamper-evident log. Chock's answer is an append-only, hash-chained log where each event carries the hash of the one before it, plus an organisation policy that projects can narrow but not widen.
The limits are explicit. Attribution is worth what rollout coverage is, sealing depends on key custody, and there is no remote attestation or hardware root of trust. Whether this changes how security teams admit agent sessions likely hinges on whether the remaining roadmap links — a signature on the commit and a forge attesting the push — ship, and on whether the log's tamper evidence holds up in an audit.
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 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.
Levent Alpöge published a 4-page remark.pdf saying he believes he found a Riemann Hypothesis proof with Claude…

On 2026年11月1日, EveryInfra tested Claude Opus 5.5, Sonnet 5.5, and Fable 5.1 and found forced tool calls return…

MetAI published the five-block structure of its AI育成プログラム for companies, schools and local governments, coveri…

AWS added a distributed KV caching skill to its Agent Toolkit for AWS, letting coding agents like Kiro and Cla…

The Elders published a "Humanity Threshold" declaration dated 16 July 2026 calling for a treaty that would bar…

A practitioner whose offline scores stopped matching click-through rates abandoned scattered blog posts and wo…
