Products
A model runner, a sandbox that can be rewound, a dashboard, an approval gate and a signed policy engine — all from one binary, all working offline, all driven by the same short commands.
sandbox sealed ready in 584ms checkpoint sealed-ckpt-1 (before the risky bit) saved in 697ms sealed is back at sealed-ckpt-1 (485ms) processes resumed from just now
Pick one
Nothing below is a mockup. The terminals replay commands that were run against a real daemon, at roughly the speed the real thing takes.
Pull from Hugging Face, serve on your own GPU. OpenAI- and Claude-compatible.
Model runner →A sealed machine per assistant. You name the folder and the hosts; the machine enforces it.
Your first sandbox →Checkpoint before the risky step, rewind in half a second with processes still running.
Checkpoint & rewind →Fork a machine per idea, run them at once, keep the one that worked.
Fork and compare →Every machine, every save point, and the tree of what was copied from what.
Open the dashboard →Signed policy per team. Edit it on a laptop and that laptop locks itself out.
How policy works →Shows you the exact command first. Destructive actions are always confirmed.
Meet the assistant →The idea
Everything else follows from that. A model runner is useful; a model runner inside something you can rewind is a different kind of safe.
Its own kernel and its own network stack, booted in about half a second. That is what makes the rest possible: you cannot snapshot a namespace mid-thought, but you can snapshot a machine.
sandbox sealed ready in 584ms pulled docker.io/library/alpine:latest into sealed example.com: refused ↑ only api.anthropic.com was allowed out
A checkpoint captures memory and running processes, not just the disk. Rewinding does not restart anything — the same processes carry on from the instant you saved them.
checkpoint sealed-ckpt-1 (before the risky bit) saved in 697ms rewind with `kosa8 rewind sealed` damage done sealed is back at sealed-ckpt-1 (485ms) processes resumed from just now
Forking copies the machine, processes and all, so each idea starts from the same instant instead of from a fresh boot. They run in parallel and the losers are cleaned up for you.
forked 3 branches in 3258ms BRANCH RESULT TIME VARIANT sealed-explore-712651 ok 275ms echo one sealed-explore-712652 error 3ms false *sealed-explore-712653 ok 272ms echo three winner: sealed-explore-712653 other branches removed; --keep-all keeps them for inspection
One line installs all of it. There is nothing to switch on.