Hive Hold Seal · preview
Your sandboxes disappear. The record of what ran in them, and when they disappeared, does not.
Agent sandboxes are built to vanish the moment they stop. That is the right default until someone anticipates litigation. Courts already treat agent prompts, outputs and logs as ordinary electronically stored information, and the duty to preserve applies to them the same way it applies to email. Hive Hold Seal keeps the sandbox ephemeral and keeps the record outside it: each session committed to an outside witness before the agent starts, each deletion witnessed and timestamped, and counsel's hold signed in so any covered sandbox deleted without a preservation export leaves a gap anyone can see. It works with any agent and any sandbox, because it sits where sandboxes are created and deleted.
Why now
Agent records are already evidence. Sandboxes were never built to keep them.
Litigators at Spencer Fane write that courts are treating prompts, outputs and AI logs like any other electronically stored information, subject to the same discovery and preservation duties as email and chat. Spencer Fane, Prompts and production
Kilpatrick's July 2026 alert reads Rule 37(e) as applying to generative AI prompts and outputs with no special standard: if a party anticipates litigation, these records belong in the hold like everything else, and losing them is judged under the same rule. Kilpatrick, Discoverability of generative AI prompts and outputs
Federal guidance on agentic AI lists sandbox and network logs among the evidence to keep, and asks for tamper-resistant logs with reliable timestamps. ComplexDiscovery's reading is that those logs belong in storage the agent cannot reach. ComplexDiscovery, on federal agentic AI guidance
When did it vanish?
The line that matters is the moment the duty attached. The deletion record has to say which side it fell on.
Deleting a sandbox before a duty to preserve attaches is ordinary operations. After it attaches, deletion of covered material is the problem. In every dispute about which side of that line a deletion fell on, the deletion record belongs to the party whose conduct is in question. Hive witnesses the deletion itself and anchors its time with a public timestamp service no party controls.
How it works
A commitment before the agent starts, a receipt when the sandbox goes, and the hold signed in.
Session commitment
Before the agent starts, whatever creates the sandbox signs a session record with fingerprints of the sandbox, its image, its labels and its repos, and the witness signs it with its own time. The agent inside never sees the key that signed it, and the record holds no content.
Release receipt
When the sandbox is deleted, the deleter signs a release naming the session, the reason, every hold in force and any preservation export, and the witness signs it and has it timestamped. The delete goes ahead either way; if the witness can't be reached, a signed witness.missing takes its place.
Hold Seal
Counsel signs a hold with a key the customer keeps, naming its scope by labels or repos, and the witness signs and timestamps it. From then on, every release that scope covers must name the hold, and a covered release with no preservation export shows as a gap.
Action-level detail optional
Any recorder that links in, such as Hive Recorder 1.3, keeps its own signed line for every tool call and a sandbox.release line naming the same release hash. The checker ties the two together, so the action record and the deletion record prove each other.
Any agent, any sandbox
The seal sits at create and delete. The agent inside never changes.
Hold Seal never runs inside the sandbox. It sits on the two calls every sandbox platform already has, create and delete, so the agent, its image and its tools stay exactly as they were. There are four ways in: the witness API for any language, TypeScript and Python SDKs, a two-line wrapper around an existing create and delete pair, and a cluster controller that seals pods by label with no change to the agent image. In the sessions below, one agent had a recorder linked in and the other had no Hive code at all.
Four real sessions
Two agents, two kinds of sandbox, one hold. Each checked in your browser.
Loading the run...
Break it yourself
12 ways to change the story afterwards. Each one is caught.
Each case is a changed copy of one of the sessions above. Most are re-signed with the deleter's or the hold's own keys, which is exactly what someone with those keys could do afterwards. The witness's signed memory and the public timestamp catch every one. The expected result is shown next to each case before you run it.
It never blocks
No Hive component can hold a call or a deletion.
Every wait is capped: 250 ms for the witness, then the call or the delete goes ahead and a signed witness.missing records the gap; 120 seconds for a preservation export, then the delete goes ahead and the release says the export failed. Session D proves it: the witness was cut off at the network for 90 seconds in the middle of the session, the agent kept working, every call ran, and the record shows each unwitnessed call as a gap instead of a stall.
What this does not show
What the record proves, and what it leaves to people.
- It does not decide what a hold should cover. Counsel writes the scope; Hold Seal applies it the same way every time.
- It does not judge relevance. A covered session is covered because its labels or repos match, nothing more.
- It does not state any legal conclusion about any record.
- It covers sandboxes whose create and delete calls pass through a Hive surface. A sandbox created or deleted around it is visible only as a missing release.
- Hive runs the default witness and is a second party, not an independent auditor. The checker accepts customer- or auditor-run witnesses.
In your browser, this page checks every signature, the witness's signed memory, and that each independent timestamp names the right hash and its time. The command-line checker also verifies the timestamp authority's own signature on each token with openssl.
Install
Two lines around the create and delete you already have.
The wrapper, in TypeScript. Python is the same shape.
In a cluster, the controller seals pods labelled hive.dev/seal=true. The keys stay in the controller's Secret and are never mounted into agent pods.
Download the four sessions and twelve cases
If your agents run in sandboxes that delete themselves and you want this on your own sessions, write to [email protected].
Founder, Hive